Oracle Integration errors
Common Oracle Integration errors, grouped by component. Open one for the exact error text, its likely causes, the fix and the official documentation.
- Errors
- 36
- Components
- 24
- Verified
- 36
36 errors in 24 groups
Adapter connections1
Agent groups1
Attachments1
Certificates1
Connectivity agent6
- Agent Installation Failed: Incorrect OIC Username / Password providedThis connectivity agent error means the agent could not obtain its status from the Oracle Integration server during startup or installation. Allowlist your identity domain, design-time IP address and runtime IP address.
- Agent Startup Failed - Unable to get agent statusThis connectivity agent error means the agent cannot query its status from the Oracle Integration server. Allowlist your identity domain, design-time IP address and runtime IP address.
- Circular loading of installed providers detectedThis Oracle Integration activation error appears when the connectivity agent was running with a JDK whose location was later removed or changed. Restart the agent using the newer JDK version and its location.
- Connectivity agent: java.net.SocketException: Connection resetThis connectivity agent error is caused by a Maximum Transmission Unit (MTU) mismatch. Run ifconfig -a as root and note the network interface.
- Connectivity agent: Message1_1Impl cannot be cast to oracle.j2ee.ws.saaj.soap.MessageImplThis connectivity agent error is a class loading conflict caused by a JDK that is shared with another product. Run the connectivity agent with a JDK installation that has not been modified for use with other products.
- Connectivity agent: Terminate flag activatedThis connectivity agent log line means the agent stopped processing after receiving HTTP 404 or 401 errors continuously for 24 hours, or after the instance was decommissioned. Resolve the conditions causing the error.
Connectivity agent installation1
Connectivity agent installation on Linux1
Connectivity agent JVM1
Instance storage1
Integration activation3
- Activation failure: code too largeA "code too large" activation failure in Oracle Integration means the integration contains too many actions, for example 25 or more stage write actions. Optimize the integration, for example by splitting it into multiple integrations.
- Activation failure: ORA-01654 unable to extend indexORA-01654 during an Oracle Integration activation means the database has reached its size limit. Check that the database is running and has enough space.
- Activation failure: ORA-12516 could not create pool connectionORA-12516 during an Oracle Integration activation means the activation hit database connection pool issues. Check that the database is running and has enough space.
Invoking Oracle Integration services1
JavaScript action1
JSON to XML translation1
Notification action1
REST Adapter4
- OCI Object Storage Search API returns 401 NotAuthenticatedThis 401 from the OCI Object Storage Search API through the Oracle Integration REST Adapter usually points to invalid credentials or an unsupported wildcard search. Make sure the file name being searched does not contain the character.
- SSL: CertificateExpiredExceptionThis Oracle Integration SSL error means the validity window of the server certificate does not include the current time. Renew or redeploy the server certificate.
- SSL: host name does not match the certificateThis Oracle Integration SSL error means the server certificate was not issued for the host name or IP address used. Use the host name present in the certificate SAN, or have the endpoint owner reissue the certificate with the correct DNS or IP SAN.
- SSL: PKIX path building failedThis Oracle Integration SSL error means the server certificate chain is not trusted by the Oracle Integration trust store. Download the server trust chain.
REST Adapter (Authorization Code grant)1
REST Adapter (OCI Signature Version 1)1
REST Adapter (RPST security policy)2
- RPST and OCI Service Invocation: BucketAlreadyExistsA BucketAlreadyExists error through the Oracle Integration REST Adapter can mean the policy only lets the dynamic group read buckets, so creating a bucket fails. Create a policy that allows writing to the bucket.
- RPST and OCI Service Invocation: NamespaceNotFoundA 404 NamespaceNotFound through the Oracle Integration REST Adapter with the RPST and OCI Service Invocation policy means the policy or dynamic group is not set correctly. Set the policy to perform the required operations.
REST Adapter connection1
REST Adapter endpoint wizard1
REST Adapter invoke2
- APIInvocationErrorAPIInvocationError in Oracle Integration is the fault the REST Adapter raises for any HTTP error response or processing error on an outbound invoke. Handle the APIInvocationError with a fault handler in the integration. The errorDetails section contains the actual cause.
- Can not deserialize instance of java.util.ArrayList out of START_OBJECT tokenThis Oracle Integration REST Adapter error means the sample JSON has only one array element, and the adapter needs at least two to generate a valid XML schema. Add a second element to the array in the sample JSON, for example "formInputs": [ "input1", "input2" ].
REST Adapter trigger1
REST-based adapters1
Synchronous integrations1
More for Oracle Integration work:Open Oracle Integration jobsOracle Integration rates and salaries
The iPaaS Brief
Subscribe to The iPaaS Brief.
The iPaaS newsletter for the people who run integrations. From iPaaS Group.
Free. You finish on theipaasbrief.com and confirm by email.