Siebel Remote: Transaction Processor (TxnProc) run state reported as 'Partially Offline'
Last updated on JULY 11, 2017
Applies to:Siebel Financial Services CRM - Version 18.104.22.168  and later
Information in this document applies to any platform.
Siebel Remote - on version 22.214.171.124 :
On a Production environment, Transaction Processor's run state shows as 'Partially Offline' where as all other components (including Transaction Router, Transaction Merger, etc) have run state as 'Online' or 'Running'.
Checking from time to time the txns backlog - MIN(TXN_ID), MAX(TXN_ID), COUNT(*) from S_DOCK_TXN_LOG table, that count seems to be not increasing steadily, but also decreasing at times.
As the count value is reducing, that suggests that some txns processing is taking place on that Remote server.
Recently there were applied the 2 new QFs for 126.96.36.199 (QF0101006 and QF0001086) but could not relate this to the component state; only that now was checked if all components are up and running and that is why this issue was noticed. Disk space is also fine on the box.
When trying to start the TxnProc component via srvrmgr command, the below message is returned:
SBL-ADM-60070: Error reported on server 'sblapp8' follows:
SBL-SVR-01042: Internal: Communication protocol error while instantiating new task SBL-SVR-09127: Internal: Fail to initialize the shared memory resource f
SBL-SVR-09124: Internal: Cannot allocate shared memory resource for the current process. Most likely we have reached the maximum number of processes.
SBL-SVR-09127: Internal: Fail to initialize the shared memory resource for the process.
SBL-SCL-00131: Either the RC2 or the AES cryptography engine is not initialized.
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