GenNewDb job remains in "QUEUED" status.
Last updated on FEBRUARY 24, 2017
Applies to:Siebel CRM - Version 126.96.36.199  and later
Information in this document applies to any platform.
GenNewDb job remains in Queued status.
However, there are some jobs executed in success (ex; WfProcMgr, XMLPReportServer).
For this issue, we can refer the following document.
"WHY DO COMPONENT JOBS STAY IN QUEUED STATUS? (Doc ID 1075006.1)"
But the causes written in it were not applied.
The situation that became clear by an additional investigation is as follows,
- Due to SRProc log, GenNewDb job was once changed into STATUS="ACTIVE" as a target task for execution.
The job was returned to "QUEUED" afterwards.
- Due to SRBroker log, following error was output,
GenericLog GenericError 1 0000031d53581760:0 2014-04-24 17:34:08 (srbthrd.cpp (314) err=1311771 sys=0) SBL-SVR-01051: SISNAPI connection is refused by the Siebel server: (null)
GenericLog GenericError 1 0000031d53581760:0 2014-04-24 17:34:08 (srbroute.cpp (2094) err=3735579 sys=0) SBL-SRB-00027: Invalid routing information.
GenericLog GenericError 1 0000031d53581760:0 2014-04-24 17:34:08 (smimtsh.cpp (305) err=1311771 sys=0) SBL-SVR-01051: SBL-SVR-01051: SISNAPI connection is refused by the Siebel server: (null)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms