Last updated on MARCH 02, 2017
Applies to:Siebel Assignment Manager - Version 126.96.36.199  and later
Siebel CRM - Version 188.8.131.52  and later
Information in this document applies to any platform.
We need help in finding out the root cause of the production incident that happened last week. We seen many issues with of Batch Assignment repeating job over 48 to 72 hours period. There were couple of variations
- Repeating batch assignment instances were in Active status for many hours doing nothing.
- Repeating batch assignment instances failed with error “SBL-SVR-09124: Internal: Cannot allocate shared memory resource for the current process”. We verified we were not reaching to max memory usage on siebel server which have 64 GB of physical memory. Also were well below the max # task for the batch Assignment (205 used out of 500 max tasks)
Restarting siebel services did not help so we finally restarted the Siebel Server HOST and then started siebel services. After this the environment is stable and we not seeing any hung batch assignment repeating instances. Please let me know what logs you need on this. We wanted to avoid this issues in future as it has major impact on the business.
Also can you please confirm if each repeating instance of batch assignment created new DB session or it try to reuse the existing DB session?
Not 100% sure but due to same start time these batch assignment issues seems to be having some co-relation with the Siebel DB incident that happened 6/11 and lasted for about 2 hours. During this Siebel DB incident one of the Siebel DB listener stopped responding and DBA had to kill and restart the listener.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms