MANUAL segment management on tablespace for AUD$ and FGA_LOG$ could lead to database hanging with gc current request waits
(Doc ID 1434614.1)
Last updated on OCTOBER 12, 2023
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
- A general hang on the database is described by users
- No new sessions are coming into the database. Only users with sys or sysdba role can connect
- Wait events for most of chains include gc buffer busy acquire, gc current request. The same block is referenced on the wait event
- If a hanganalyze is generated, the current session involved in the wait is an insert into aud$
Example of the chain generated by hanganalyze command level 3. Note that 11.2, dia0* process will be generated if a hang is detected. It will include also dump of hanganalyze:
The syntax is for RAC environment, as gc buffer busy acquire wait is RAC specific wait.
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