Server User Not Able to Login, getting Serve Busy Or Incorrect Credentials Although Credentials Are Correct When Using DB Connection Pooling
(Doc ID 501356.1)
Last updated on NOVEMBER 22, 2019
Applies to:Siebel System Software - Version 126.96.36.199  and later
Siebel CRM - Version 17.0 [IP2017] and later
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 188.8.131.52 
Database: Oracle 184.108.40.206
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: Sun Solaris 2.7
Siebel users are getting lot of server busy errors when they trying to login or Get the login page back with "The user ID or password that you entered is incorrect. Please check the spelling and try again." error message though they enter correct information. These errors are intermittent but the frequency increase over the time, at some point the frequency is to high that a restart of the Siebel Server is required to get it back to normal.
The Object Manager is using DB connection pooling for the Object Manager and if a SQL statement runs for more than 5 mins a rule in the Database level kills the connection to avoid performance issues. Customer would like to known the impact of this DB rule, that is what happens if a connection gets killed at the database level? Will Siebel know that and not use that connection again? Or Siebel uses the connection for the first time and if that fails will it discard that connection and create a new connection? Or just that connection is still available to Siebel and tries to reuse it and error out multiple times?
Here is a sample error message in the Siebel Web Server Extension (SWSE) log file:
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