Querying "Server Tasks" Buscomp results in error - "SBL-CSO-01013: Internal: the SCC context has not been initialized"
(Doc ID 539589.1)
Last updated on FEBRUARY 03, 2019
Applies to:Siebel Tools - Version 22.214.171.124 SIA  and later
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 126.96.36.199  Cons Goods
Database: Oracle 188.8.131.52
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server
This document was previously published as Siebel SR 38-2450594777.
Checked for Relevance on 09-Sep-2010
Checked for Relevance on 28-AUG-2013
While the query on the virtual Business Component "Server Task" was successful in the first Workflow Process execution, it failed in all subsequently executed Workflow processes with the following error:
(srsctx.cpp (366) err=4601013 sys=0)
SBL-CSO-01013: Internal: the SCC context has not been initialized
In an attempt to periodically release Assignment Manager cache, a small script invoking the "Release" method on the related AM buscomp is used. This works successfully. This script is run by means of a Repeating Comp Request scheduled WFP.
Because releasing assignment manager cache when any Assignment Manager task is running (either Batch or Dynamic) is not a good practice. Another piece of script was implemented Querying the "Server Tasks" buscomp within the "Server Admin" busobject. According to Bug 10451636 this is supported.
See sample script below:
var oBc1 = oBo.GetBusComp("Enterprise Server");
var oBc2 = oBo.GetBusComp("Server Task");
oBc1.ExecuteQuery(); // there's only one Enterprise server
oBc2.SetSearchSpec("Service Component", "AsgnMgr");
// don't release rules now!!
// release rules now...
This script works fine the first time it's run (as Bus Serv within WFP through Workflow Process Manager comp). Any subsequent executions will fail. Only when the Workflow Process Manager component is bounced, the script will work again, for one time.
running 184.108.40.206 ...
Running through the Bus Serv Sim does work correctly.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|