Siebel Campaigns Are Failing with "Unable to find job with Id" error
(Doc ID 2333784.1)
Last updated on AUGUST 18, 2020
Applies to:Siebel Marketing - Version 188.8.131.52.18 [IP2014] and later
Information in this document applies to any platform.
When attempting to Load a Campaign with a Segment in an OBIEE Clustered Environment, the following error occurs.
Operation 'getJobInfo' of Web Service 'com.siebel.analytics.web/soap/v1.JobManagementService' at port 'JobManagementServiceSoap' failed with the following explanation: "Unable to find job with Id "1021". Too much time may have expired since you generated or accessed this job.".(SBL-EAI-04308)
The issue can be reproduced at will with the following steps:
1. Have OBIEE installed and configured as a Cluster with 2 Servers.
2. Setup a Campaign with a Segment
3. Load it
4. Either during PrepareCache or WriteListFiles, the error above will occur
If you take a look in the related log, you will see that the EAI request took (0.034 seconds) less than the default timeout setting of 120 secs:
It means that the Job is not timing out, but for some reason it is not being found.
- OBIEE has 2 Servers Clustered
- Catalog is in a NFS shared mount point
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document