In Siebel Environment, while start the application, all jobs goes into Queued state. New Jobs stuck in Queued Status. SBL-SMI-00033

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Problem:    

In Siebel Environment, while start the application, all jobs goes into Queued state. New Jobs stuck in Queued Status. SBL-SMI-00033

Solution:

One of the SRProc tasks is exiting with the error, SBL-SMI-00033. Please see here the task, from the 'list tasks for comp SRProc' output:

SRProc 5242887 15260 Exited with error Interactive 2010-01-26 10:42:31 2010-01-26 10:43:31 SBL-SMI-00033: The client exited without closing the SISNAPI co SystemAux 3 Normal


This is a known defect in Siebel version 8.0.0.x on the HP-UX platform. This My Oracle Support posting describes this:

Service Request Processor is exiting with SBL-SMI-00033 error (Doc ID 780307.1)


As a workaround, you will need to restart the SRProc component.

To fix this defect, please apply the latest Fix Pack, which is 8.0.0.8 [20430] released on October 30th last year.

Work around:

1. Unassigned the component SRProc, Synchronized and restarted the Environment.
2. Assigned the component SRProc, Synchronized and restarted the Environment.
3. Changed the password for Comp SRProc from SRVRMGR and restarted the Environment.
4. Changed the Max MTS = 2 and Min MTS = 2 for the SRProc component, Synchronized and restart the environment.

Get Oracle Certifications for all Exams
Free Online Exams.com