SBL-DAT-00353: Business component '%1' is already in cached update mode.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.6 [16186] FIN
Database: Oracle 9i
Application Server OS: IBM AIX 5L 5.1
Database Server OS: IBM AIX 5L 5.1

This document was previously published as Siebel SR 38-1518006091.

Symptoms

SBL-DAT-00353, SBL-OMS-00203, SBL-OMS-00107

Hi,

We clicked on the Contact Tab and subsequently, the child tab (Close Accounts) and upon applet load we hit the error below.

[0] Business component '<?>' is already in cached update mode.(SBL-DAT-00353) (0x6c21)

We have found the following SR 38-1117423721. We increased the table space and truncated the S_DOCK_TXN_LOG table but it does not solve the error.

I am attaching the "WfProcMgr" log for your reference.

Thanks.

Solution

Message 1

For the benefit of other readers:

Description

When we click on the Contact Screen Tab and subsequently, the child view tab "Close Accounts" we receive the following error:

"[0] Business component '<?>' is already in cached update mode.(SBL-DAT-00353) (0x6c21)"

We have found the following Service Request #38-1117423721.   We increased the table space and truncated the S_DOCK_TXN_LOG table but it does not solve the error.

I am attaching the "WfProcMgr" log for your reference.

On further investigation, the error only happens on workflows that the persistent frequency and persistent level set to "highest". If those fields were not set, the error does not occur.

Resolution

Since this was in a test environment, logging was increased to see if additional information was given in the log files, following the instructions in Bookshelf > Siebel Server Administration Guide > Using the Siebel Server Manager Command-Line Interface to sign into srvrmgr and running the following command (substituting the component alias for CompName):

change evtloglvl %=5 for comp CompName

After the behavior was reproduced, three log files were provided:

1) WfProcMgr_5142.log_startup.txt (log file obtained directly after restarting the Application server)

2) WfProcMgr_5225.log_no_error.txt (log file of workflow fired successfully)

3) WfProcMgr_5232.log_with_error.txt (log file of workflow with error)

(continued...)

Message 2

(continued...)

The following two errors were found in the "WfProcMgr_5232.log_with_error.txt" file (but not found in the other files):

StpExec    End    4    2004-07-25 15:22:57    Stopping step instance of 'Start' with a 'Completed' status.
ObjMgrLog    Error    4    2004-07-25 15:22:57    (SBL-DAT-00353) Business component 'Workflow Process Property Instance' is already in cached update mode.
ObjMgrLog    Error    4    2004-07-25 15:22:57    (SBL-DAT-00353) Business component '<?>' is already in cached update mode.
PrcExec    End    4    2004-07-25 15:22:57    Stopping process instance of 'UOB EAI VBC Sync' with an 'Error' status.

and:

ObjMgrLog    Error    4    2004-07-25 15:22:56    (SBL-DBC-00111) An error has occurred writing to a record.

Please continue or ask your systems administrator to check your application configuration if the problem persists.
SQLParseAndExecute    Execute    5    2004-07-25 15:22:56    ORA-01654: unable to extend index SIEBEL.S_WF_PROP_VAL_U1 by 27309 in tablespace SIEBEL_INDEXES
ORA-06512: at line 37

The error regarding the "unable to extend index" implies that the Oracle database is running out of tablespace for the SEARCH_INDEXES tablespace. It was recommended to work with the DBA to address that error.

The error was resolved by extending the table Index space.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3 [16157] Com/Med
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: Sun Solaris 2.8

This document was previously published as Siebel SR 38-1117423721.

Symptoms

SBL-DAT-00353

Hi !!

Since today morning, we are seeing weird error message whenever any operation in performed in our application. The error message is attached with this SR. The error text says "Business component <?> is already in cached update mode." A search on supportweb for this message returned nothing. We checked the WF logs, everything was fine till yesterday evening. The only activity that was done today morning was reconfiguring the URL on the webserver. We also tried bouncing the app server, web server and gateway but that did not correct the issue. To experiment, we imported a couple of WF proceeses from other environment and activated and reconfigured the server. But we are still getting the error message. We also tried clearing the cache on the server, and also bounced object manager a couple of times. This did not help either. Pls help.

Pls. cc Samir.S.Purohit@xo.com while reply to this email.

Thanx.
Samir.

Solution

Message 1

For the benefit of others:

The following error message was displayed whenever any operation was performed in the application.

"Business component <?> is already in cached update mode.(SBL-DAT-00353)"

The behavior was due to tablespace having been used up in the database. The tables for S_DOCK_TXN_LOG and WF Log were full. After cleaning up the space, the problem disapeared.