Symptom or Error Message
The Transaction Router Siebel Remote server task may fail under certain conditions which will cause a backlog in the transactions to be routed to Siebel Remote mobile users and regional nodes. Symptoms of a Transaction Router failure are usually an error on the Status field on the Server task applet, and the Task State field would report that the task has exited with an error:
Task State: Exited with error
Status: ERROR: 1 client(s) failed with errors, 0 client(s) successful
To generate more detailed trace information:
• In Siebel 7, follow the instructions detailed in FAQ 1944, regarding component tracing and log files, and FAQ 1894, regarding SQL-based event logging.
• In Siebel applications versions 5.x and 6.x, run the Transaction Router task with the following parameters set:
Sql flag = 3
Trace flag = 7
Error flag set = 7
There are three main causes for Transaction Router failures:
1. Connectivity and RDBMS behaviors
2. Errors when reading from and writing to .dx files
3. Errors when accessing cache files and docking directories
The first step in diagnosing a Transaction Router failure issue is to try to determine whether the failure was a one-time occurrence or a persistent failure. This is easy to achieve by simply trying to restart the Transaction Router. If the Transaction Router starts and continues processing without further error then it is likely that the cause may be poor network connectivity, database connectivity, or another intermittent system issue at the time of failure. You can then inspect the log file to see why the Transaction Router failed. If the Transaction Router fails again after restarting then it is likely that you have a persistent failure which will require some action to be taken before it can restart and continue without failing. Typically the first step is to increase the tracing as detailed above, then restart the Transaction Router and review the more detailed log for the commonly seen issues as detailed below.
1. Connectivity and RDBMS Behaviors
Review the Transaction Router log file for RDBMS and network related errors. The errors below are examples of RDBMS errors that have been seen in Transaction Router log files:
ORA-01000: maximum open cursors exceeded
ORA-04031: unable to allocate 4096 bytes of shared memory
ORA-03113: end-of-file on communication channel
ORA-03114: not connected to ORACLE
[IBM][CLI Driver][DB2/SUN] SQL0437W Performance of this complex query may be sub-optimal. Reason code: “6”. SQLSTATE=01602
[IBM][CLI Driver][DB2/6000] SQL0911N The current transaction has been rolled back because of a deadlock or timeout. Reason code “68”. SQLSTATE=40001
[IBM][CLI Driver][DB2/6000] SQL0973N Not enough storage is available in the “APP_CTL_HEAP” heap to process the statement. SQLSTATE=57011
MS SQL Server
[MERANT][ODBC Siebel Database driver][SQL Server]ct_results(): network packet layer: internal net library error: Net-Library operation terminated due to disconnect
[MERANT][ODBC Siebel Database driver][SQL Server]ct_cmd_alloc(): user api layer: external error: The connection has been marked dead.
[Microsoft][ODBC SQL Server Driver][SQL Server]SHUTDOWN is in progress. Log off
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionRead (recv()).
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite (send())
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error
[Microsoft][ODBC SQL Server Driver]Communication link failure
2. Errors When Reading from and Writing to .dx Files
Review the Transaction Router log file for Siebel errors. The errors below are examples of Siebel application errors that have been seen in Transaction Router log files:
SBL-DCK-00142: Error opening transaction file C:\SIEBEL\docking\TXNPROC0005115.dx for read
Unable to read an item from the User Txn Log file.
SBL-TXR-00026: Error in the main function
NOTE: In Siebel applications prior to version 7.5.3, the error numbers are the same without the SBL prefix, namely DCK-00142 and TXR-00026.
3. Errors When Accessing Cache Files and Docking Directories
Review the Transaction Router log file for Siebel errors. The errors below are examples of Siebel errors that have been seen in Transaction Router log files:
SBL-CSC-00119: Block number xxx exceeds file size (yyy blocks)
SBL-CSC-00213: Invalid visibility database. Shutdown and restart *all* routers to rebuild
SBL-DCK-00123: Error opening file C:\SIEBEL\docking\J_LIBAIRE0000091.log for read
SBL-DCK-00250: A newer version of the dobjinst.dbf must be rebuilt by starting transaction processor with parameter “TSDbRecreate” set to “TRUE”
SBL-CSC-00128: Cannot get exclusive access to Tall/Skinny database for node %NODE%
SBL-CSC-00103: Error reading 204 bytes from dbfile at 0 (0 bytes read)
SBL-CSC-00202: An attempt was made to seek past the end of a data block
SBL-CSC-00301: Invalid value 0 for argument pVisDataInfo->createLatch
SBL-CSC-00120: Not enough space in buffer cache
NOTE: In Siebel applications prior to version 7.5.3, the error numbers are the same without the SBL prefix, namely CSC-00119, CSC-00213, DCK-00123, DCK-00250, CSC-00128, CSC-00103, CSC-00202, CSC-00301, and CSC-00120.
1. Connectivity and RDBMS Behaviors
RDBMS errors are not generated by the Siebel application, but they are reported in the log files to aid with troubleshooting. The examples given above have all been caused by underlying network issues, incorrect database configuration, or incorrect tuning. It is recommended to involve your DBA, because many RDBMS errors can be resolved by database tuning alone. Database tuning should be done in conjunction with the recommendations made in Siebel Bookshelf.