Batch Component Jobs Go Into Queued Status After New Database Instance Creation From Cloned Database
(Doc ID 2854092.1)
Last updated on MARCH 07, 2022
Applies to:Siebel CRM - Version 19.7 and later
Information in this document applies to any platform.
An existing Siebel QA environment has new database instance created using a clone from Production database, the Gateway Security Profile was redefined as per the instructions on the document below:
SMC Login Failure After the Backend Database Host or Instance is Changed (Doc ID 2371577.1)
Besides the Gateway Security Profile redefinition the Sadmin password was changed on the Siebel configuration, and new ODBC DSN was created on each Siebel Server with the Server parameter set with the new TNS_Alias respective to the database instance in question.
Spite of these changes all batch component jobs are not getting processed and stay in Queued status.
The issue can be reproduced at will with the following steps:
1. Login to the Siebel Application
2. Go to Administrator - Server > Management
3. Submit a new batch job, such as Generate Triggers
4. The job stays in Queued status
New database instance created using a clone from Production database
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