Introduction
Oracle Integration Cloud Logs play a critical role in monitoring, debugging, and maintaining integrations built on Oracle Integration Cloud (OIC Gen 3). In real-world projects, logs are not just a troubleshooting tool—they are your primary source of truth when integrations fail, behave unexpectedly, or need performance tuning.
As an Oracle consultant, you will spend a significant amount of time analyzing logs to identify issues such as failed API calls, transformation errors, connectivity problems, and data mismatches. Without a clear understanding of OIC logging, diagnosing issues in production environments becomes extremely difficult.
This blog provides a deep, practical understanding of Oracle Integration Cloud logs, including how to access them, interpret them, and use them effectively in real-time project scenarios.
What is Oracle Integration Cloud Logs?
Oracle Integration Cloud logs are system-generated records that capture execution details of integrations, including:
- Request and response payloads
- Execution status (success, faulted, aborted)
- Error messages and stack traces
- Tracking and diagnostic information
In OIC Gen 3, logging is tightly integrated with the Observability and Monitoring framework, giving better visibility compared to earlier versions.
Logs are primarily accessed through:
- Integration Tracking
- Activity Stream
- Diagnostic Logs (OCI Logging Integration)
Key Features of OIC Logs
1. End-to-End Tracking
You can trace an integration from trigger to final response, including all intermediate steps.
2. Payload Visibility
Logs allow viewing of request/response payloads (based on logging level).
3. Error Diagnostics
Detailed fault messages help identify exact failure points.
4. Instance-Level Monitoring
Each integration execution creates an instance that can be analyzed independently.
5. Integration with OCI Logging
OIC Gen 3 integrates with OCI Logging for centralized log management.
Real-World Integration Use Cases
Use Case 1 – HCM to Payroll Integration Failure
A company integrates Oracle Fusion HCM with a third-party payroll system.
Issue: Employee records are not being processed.
Log Insight:
- Error in payload mapping
- Missing mandatory field (Employee Number)
Resolution: Update mapper logic and reprocess failed instances.
Use Case 2 – ERP Invoice Interface Error
An ERP integration loads invoices via REST API.
Issue: API returns HTTP 400.
Log Insight:
- Invalid date format in payload
Resolution: Correct date format in transformation.
Use Case 3 – OIC Scheduled Integration Not Running
Issue: Scheduled integration is not triggering.
Log Insight:
- No instances created
- Scheduler misconfiguration
Resolution: Fix schedule settings and verify timezone.
Architecture / Technical Flow of OIC Logs
Understanding how logs are generated helps in debugging faster.
Flow:
- Integration Trigger Initiated
- OIC creates an Instance ID
- Each action (invoke, assign, switch) is logged
- Payload snapshots captured (based on log level)
- Logs stored in:
- OIC Tracking Database
- OCI Logging Service
Types of Logs
| Log Type | Description |
|---|---|
| Activity Stream | High-level execution status |
| Integration Tracking | Detailed instance-level logs |
| Diagnostic Logs | Low-level system logs |
| Audit Logs | User and configuration changes |
Prerequisites
Before working with logs, ensure:
- Integration is activated
- Tracking is enabled
- Required roles assigned:
- Service Developer
- Service Monitor
- Access to OCI Console (for advanced logging)
Step-by-Step: Accessing Logs in OIC Gen 3
Step 1 – Navigate to Integration Tracking
Navigation:
Navigator → Integrations → Tracking
Step 2 – Search for Integration Instance
- Enter:
- Integration Name
- Status (Failed / Completed)
- Time Range
Click Search
Step 3 – Open Instance Details
Click on the Instance ID.
You will see:
- Flow diagram
- Execution path
- Status of each step
Step 4 – View Payload
Click on specific actions (Trigger/Invoke)
- Request Payload
- Response Payload
Step 5 – Check Errors
Navigate to Errors section
- Error Code
- Error Message
- Fault Details
Step 6 – Download Logs (Optional)
You can export logs for offline analysis.
Advanced Logging Using OCI Logging
OIC Gen 3 supports integration with OCI Logging.
Steps:
- Go to OCI Console
- Navigate to Logging → Log Groups
- Select OIC log group
- View logs using filters
Benefits:
- Centralized monitoring
- Log retention policies
- Integration with OCI Monitoring & Alerts
Testing the Logging Setup
Example Scenario
Integration: REST → ERP API
Test Steps:
- Send test payload via Postman
- Trigger integration
- Navigate to Tracking
- Verify instance creation
Expected Results:
- Status: Completed or Faulted
- Payload visible
- No missing steps
Validation Checks:
- Check transformation output
- Verify API response
- Confirm no errors in logs
Common Errors and Troubleshooting
1. No Instances Found
Cause:
- Integration not triggered
Fix:
- Check endpoint URL or schedule
2. Payload Not Visible
Cause:
- Logging level set to minimal
Fix:
- Enable payload tracking
3. Generic Error Messages
Cause:
- Exception not handled
Fix:
- Add fault handlers in integration
4. Timeout Errors
Cause:
- External system delay
Fix:
- Increase timeout or optimize API
5. Large Payload Issues
Cause:
- Payload exceeds size limits
Fix:
- Use staged file approach
Best Practices for OIC Logging
1. Enable Business Identifiers
Always configure tracking fields like:
- Employee ID
- Invoice Number
This helps quickly identify transactions.
2. Use Fault Handlers
Capture meaningful error messages instead of generic failures.
3. Avoid Over-Logging in Production
- Use minimal logging in PROD
- Enable detailed logs only during debugging
4. Standardize Error Messages
Use consistent error formats for easier troubleshooting.
5. Use OCI Alerts
Set alerts for:
- Failed integrations
- High error rates
6. Maintain Log Retention Policy
Avoid unnecessary storage consumption.
Summary
Oracle Integration Cloud Logs are one of the most critical components for managing integrations effectively. In real-time projects, logs help you:
- Identify failures quickly
- Debug payload issues
- Monitor integration performance
- Ensure smooth business operations
Mastering OIC logging is not optional—it is a must-have skill for any Oracle Integration consultant.
For deeper reference, always check official Oracle documentation:
https://docs.oracle.com/en/cloud/saas/index.html
FAQs
1. How do I enable payload tracking in OIC?
You can enable tracking while designing the integration by selecting tracking fields and enabling payload logging in settings.
2. Can I access OIC logs from OCI Console?
Yes, in OIC Gen 3, logs are integrated with OCI Logging and can be accessed through Log Groups.
3. What is the difference between Tracking and Activity Stream?
- Tracking → Detailed instance-level logs
- Activity Stream → High-level execution summary