High DB Memory Caused by Application Requests - DB2 ZOS Connection Cause Large Number Of Unique Names
(Doc ID 2746855.1)
Last updated on JANUARY 26, 2021
Applies to:Siebel CRM - Version 19.7 and later
Information in this document applies to any platform.
Siebel application is not accessible and none of the batch jobs are successful. Even after restarting Siebel enterprise, issue still existing.
It was found that Database level memory is too high which is causing database unstable.
Siebel Component logs like SRBroker*.log, Wokrflow*.log reported with below error:
GenericLog GenericError 1 000000025f93018a:0 2020-10-24 00:36:56 Objectmanagerfout: ( De DB2-database kan niet worden geopend. Misschien is de server uitgeschakeld of bevat de database voor de server fouten. Neem contact op met de systeembeheerder.(SBL-DBC-00103) (0x760067))
GenericLog GenericError 1 000000025f93018a:0 2020-10-24 00:36:56 Objectmanagerfout: ( [IBM][CLI Driver][DB2] SQL30108N A connection failed in an automatic client reroute environment. The transaction was rolled back.
DB vendor team concluded that they are receiving a large number unique connection names(also called as transaction names) from Siebel. There is only 2GB of memory allocated to hold these unique application names. After 3-4 days this memory gets filled up and then the database instance doesn¿t work any more. The only way to recover is to restart the Db2 instances.
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