Applies to:
Siebel CRM - Version: 8.1.1 SIA [21111] - Release: V8Information in this document applies to any platform.
Symptoms
The Gateway daemon for Siebel Industry Applications version 8.1.1 running on IBM AIX 5.3 against Oracle 11g shows high CPU. This can be observed after starting a Siebel server, which has a duration of 2-3 minutes. After the Siebel server has started the CPU of the Gateway daemon reduces and stabilizes, however the Siebel Workflow components fail after startup. If these failed components are restarted manually via Siebel Server Manager then the CPU increases on the Gateway as before.ERROR MESSAGES
- SBL-DAT-00173: An invalid key was entered.
- SBL-NET-01218: The connection was refused by server %1. No component is listening on port %2.
- SBL-SRB-00040: Cannot open asynchronous SISNAPI connection.
- SBL-GEN-05009: Unable to connect to the gateway server.
- SBL-SVR-00052: Internal: Invalid proc handle
Cause
Issue caused by extremely large SIEBNS.DAT which can be seen by the high CPU in the gateway process originating from the reads performed by the NSClient.Change Request 12-1VM5KED has been logged to address a Product Enhancement Request so that the size of the SIEBNS.DAT does not grow excessively and if it does then to provide means to reduce the size - in particular removing event log level entries.
The large amounts of reads being performed by the NSClient are directly related to the high CPU observed on the gateway
Solution
To reduce the size of the SIEBNS.DAT, the following can be employed,1. Restore backup of SIEBNS.DAT after changing event log levels for large amount of server components
2. Remove unnessary component definitions
References
BUG:12-1VM5KED - PROVIDE RESTRICTIONS ON THE SIZE OF SIEBNS.DAT
Related
Products
- Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel CRM
| HIGH CPU USAGE |
| SBL-SVR-00052; SBL-GEN-05009; SBL-DAT-00173; SBL-SRB-00040; SBL-NET-01218 |
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment