Datasource Is Suspended Due To MySQL Database Failover And Failed To Recover After The Database Was Recovered
(Doc ID 2342870.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Communications Services Gatekeeper - Version 6.0.0 and later
Information in this document applies to any platform.
There was a hard disk failure (IO spike) in the virtual store which triggered the database to return errors for a couple of seconds. After the database recovered, OCSG failed to recover, there were lots of errors '"Pool wlng.localTX.datasource is Suspended, cannot allocate resources to applications" in the log. All NT hosts show 'Warning' health state in WebLogic Console, reporting stuck threads, until OCSG was manually restarted about 1 hour later.
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