Workflow Process Manager Component Crashing - Error SBL-OSD-02006 After Changes to Permissions on Siebel Filesystem
(Doc ID 2859901.1)
Last updated on SEPTEMBER 05, 2023
Applies to:
Siebel CRM - Version 16.19 [IP2016] and laterInformation in this document applies to any platform.
Symptoms
Workflow Process Manager Component is crashing with the following error message found in the Siebel Enterprise log file:
The same component crash behavior can be observed in multiple application servers.
CALLSTACK
Called from:
/opt/apps/siebel/siebsrvr/lib/libsslcosd.so(+0x7195)[0xf748f195]
/opt/apps/siebel/siebsrvr/lib/libsslcosd.so(+0x798e)[0xf748f98e]
[0xf77c8410]
/opt/apps/siebel/siebsrvr/lib/libsslcshar.so(CCFMap<CCFElemStr, CCFElemPtr >::Lookup(char16_t const*, void*&) const+0x59)[0xf75819a9]
/opt/apps/siebel/siebsrvr/lib/libsscfcmn.so(CSSMapStringToOb::Lookup(char16_t const*, CObject*&) const+0x2e)[0xf73c47ee]
/opt/apps/siebel/siebsrvr/lib/libsscfdm.so(CSSSqlObj::ActivateField(CSSSqlField*, int, int, int)+0x7cf)[0xf1be092f]
/opt/apps/siebel/siebsrvr/lib/libsscfdm.so(CSSSqlObj::DeactivateFields(int)+0x3ae)[0xf1be251e]
/opt/apps/siebel/siebsrvr/lib/libsscfdm.so(CSSSqlObj::Reset()+0x26e)[0xf1be328e]
/opt/apps/siebel/siebsrvr/lib/libsscfdm.so(CSSContextManager::GetSqlObj(char16_t const*, CSSSqlObj*&, CSSModelPhysDef*)+0x295)[0xf1a280f5]
/opt/apps/siebel/siebsrvr/lib/libsscfdm.so(CSSSqlBCDef::CreateSqlObj(CSSModelPhysDef*, CSSSqlObj*&)+0x131)[0xf1b6d6a1]
/opt/apps/siebel/siebsrvr/lib/libsscfdm.so(CSSSqlObj::GetMvgSqlObj(char16_t const*, CSSSqlObj*&, int)+0x2ae)[0xf1c10c1e]
/opt/apps/siebel/siebsrvr/lib/libsscfdm.so(CSSSqlObj::FieldValue(CSSRecord*, SSstring const&, SSstring&, int*, bool)+0xbae)[0xf1c0ed7e]
/opt/apps/siebel/siebsrvr/lib/libsscfdm.so(CSSProfileAttrMgr::UpdateRecord(char16_t const*, int, int, int)+0x98b)[0xf1b2c92b]
/opt/apps/siebel/siebsrvr/lib/libsscfdm.so(CSSProfileAttrMgr::TriggerLoad(char16_t const*, int, int)+0x210)[0xf1b2d0e0]
/opt/apps/siebel/siebsrvr/lib/libsscfdm.so(CSSProfileAttrMgr::Get(char16_t const*, CSSProfileAttr*&)+0x95)[0xf1b2dcd5]
/opt/apps/siebel/siebsrvr/lib/libsscfdm.so(CSSProfileAttrMgr::Get(char16_t const*, SSstring&)+0x3a)[0xf1b2de4a]
/opt/apps/siebel/siebsrvr/lib/libsscfdm.so(CSSModelPhysDef::GetProfileAttr(char16_t const*, SSstring&)+0x30)[0xf1af0b00]
/opt/apps/siebel/siebsrvr/lib/libsscfom.so(CSSModel::Login(SSstring const&, SSstring const&)+0x389)[0xf1ead2c9]
/opt/apps/siebel/siebsrvr/lib/libsscfom.so(CSSModel::Login(int (*)(SSstring&, SSstring&, int, char16_t const*, char16_t const*, int&, SSstring&), void (*)(char16_t const*), int (*)(char16_t const*, char16_t const*, SSstring&))+0x290)[0xf1eadab0]
/opt/apps/siebel/siebsrvr/lib/libssscscom.so(ccfOMSess::Login(char16_t const*, char16_t const*, int)+0x83b)[0xf3ee374b]|
/opt/apps/siebel/siebsrvr/lib/libsssabsvm.so(+0x5709)[0xf3eec709]
/opt/apps/siebel/siebsrvr/lib/libsssabsvm.so(bsvmMTServer::BatchMain(void*, SrmRequest*)+0xf2)[0xf3eed1b2]
siebmtshmw(smiMainThread::CompBatchMain(void*, SrmRequest*)+0x2a)[0x805d5ba]
siebmtshmw(SmiRequest::CallBatchEntryPts(scrRecovInfo*)+0xdf)[0x8084eaf]
siebmtshmw(SmiRequest::CallBatchEntryPts()+0x71)[0x8085111]
siebmtshmw(SmiRequest::ProcessRequest(long, SrmSisConnHndl*, CSSSISRequestMsg*, unsigned long, unsigned char*, unsigned int)+0xa6b)[0x80867bb]
siebmtshmw[0x80883c5]
siebmtshmw(_smiBatchQ::ProcessRequest(void*, void*, void*&)+0x3b)[0x808850b]
siebmtshmw(_smiWorkQueue::ProcessWorkItem(void*, void*, void*&)+0xc8)[0x807cf08]
siebmtshmw(_smiWorkQueue::WorkerTask(void*)+0x311)[0x8081851]
siebmtshmw(SmiThrdEntryFunc(void*)+0x729)[0x806f819]
/opt/apps/siebel/siebsrvr/lib/libsslcosd.so(+0x13fa1)[0xf749bfa1]
/opt/apps/siebel/siebsrvr/lib/libsslcwsl.so(+0x225f)[0xf77c425f]
/opt/apps/siebel/siebsrvr/mw/lib/libmfc400su.so(_AfxThreadEntry(void*)+0xaf)[0xf705cb2f]
/opt/apps/siebel/siebsrvr/mw/lib/libkernel32.so(MwThread(void*)+0x136)[0xf624fe16]
/usr/lib/libpthread.so.0(+0x6bbc)[0xf606bbbc]
/usr/lib/libc.so.6(clone+0x5e)[0xf5e5c27e]
The issue can be reproduced at will on customer environment with the following steps:
1. Bring the Siebel Server up
2. As part of the Siebel Server startup Workflow Process Manager is started
3. Workflow Process Manager component crashes after a while
Changes
The crashes started to happen after an issue with the NFS mounted Siebel Filesystem that had to have the permissions reset.
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |