Troubleshooting the Siebel CRM Integration with Oracle Unity

The following table provides troubleshooting information for various error conditions you might encounter in your Siebel CRM integration with Oracle Unity:

Error	Symptom	Explanation	Solution
Incremental CSV file is not generated when data is updated.	The end user creates a new record or modifies an existing record. However, the incremental CSV file is not generated.	For incremental loading to work, the Transaction Processor (TxnProc) component is required, and also a recurring Search Incremental Indexer job.	Try the following: Make sure that the TxnProc component is running. Make sure that the Search Incremental Indexer job is created and in Active status. Make sure an Export Engine is configured and its status is Active. The category for this business component that is associated to the Export Engine must have the status Completed.
Insufficient inputs to perform this operation (SBL-SRH-60007).	When trying to Export or Export All from the Export Engine Settings view, the administrator gets this error.	One or more driver parameters are configured incorrectly.	Try the following: Refer to the log file of the Application Object Manager. The log file shows the parameter that is configured incorrectly. Provide the correct value for this parameter and proceed with Export or Export All.
GC overhead limit exceeded in the OOS File Upload Service JBS log.	The CSV file is created in the local File System and is not uploaded to Oracle Object Storage.	When the JVM runs out of memory, this error is encountered.	Try the following: Verify the RAM size in the system where the OOS File Upload JBS is running. Verify the max JVM size specified on the Tomcat where the OOS File Upload JBS is deployed. If your max JVM size is less, you can increase it, based on the available RAM size. Restart the Tomcat where the OOS File Upload JBS is deployed.
Unable to upload the CSV file to Object Storage.	Certificate error is seen while uploading the CSV file to Object Storage.	The Tomcat that runs the OOS File Upload Service does not have the Root Certificate of the OCI cloud where you are trying to upload.	Try the following: Download the Root Certificate of the OCI cloud where you are uploading the file. Import the certificate into the trust store of the Tomcat where the OOS File Upload Service JBS is running. Restart the Tomcat.
Unable to open or find the private key file.	Private key not found error is seen while uploading the CSV file to Object Storage.	The Tomcat is not able to find the private key file that is specified in the driver parameter key_file.	Try the following: Make sure that the private key file is present in the path specified in the driver parameter key_file. Make sure that the private key file is accessible to the Tomcat where the OOS File Upload Service JBS is running.