How to Collect Oracle Sessions (Processes) Information when Cannot Collect System State Dump or Hanganalyze Output
(Doc ID 2371213.1)
Last updated on NOVEMBER 22, 2022
Applies to:
Oracle Database Exadata Express Cloud Service - Version N/A and laterOracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Information in this document applies to any platform.
Purpose
Collecting oracle sessions (processes) information if you missed to take system state dump (SSD) or hanganalyze output (HA).
> How to Collect Diagnostics for Database Hanging Issues (Doc ID 452358.1)
This information does NOT replace SSD or HA, but it could be supplementary information to help locking and hanging issues.
There are two sources to get oracle session information:
1. (g)v$active_session_history
This is in ASH memory area which is part of shared pool and have every 1 second sample.
2. DBA_HIST_ACTIVE_SESS_HISTORY
This is backed from Ash area to SYSAUX tablespace and have every 10 seconds sample.
If hanging or locking issues happens and instance is not bounced, then hurry to get data from (g)v$active_session_history before it is purged.
Troubleshooting Steps
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
| Purpose |
| Troubleshooting Steps |
| References |