Last updated on MAY 17, 2015
Applies to:Siebel System Software - Version 7.5.3  and later
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Professional)
Version: 7.8.2 
This document was previously published as Siebel SR 38-3148536821.
***Checked for relevance on 18-May-2015***
We have begun to see an increasing amount of inactive SADMIN connections which are causing us to hit our peak connections.
We do not want to increase this value on the database any more because of CPU usage and disk I/O on the database server.
Our DBA consistently notices SEVERAL inactive SADMIN connections on the database.
I have been inclined to looking at the Synchronization Manager and modifying the MaxCtxCache parameter with the following command:
Then shutting down and restarting the component.
I have also looked at modifying the ConnIdleTime parameter for the SynchMgr and ObjMgr components.
It still seems as though we are getting a tremendous amount of INACTIVE connections which eventually causes us to max out our connections again.
Is there anything else we need to be taking into consideration?
How can we limit the number of inactive DB connections without impacting the system?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms