No Data in V$ACTIVE_SESSION_HISTORY When Size is _ASH_SIZE=1G
(Doc ID 2268127.1)
Last updated on NOVEMBER 07, 2023
Applies to:
Oracle Database Exadata Express Cloud Service - Version N/A and laterGen 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 Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
- When _ash_size is set to a large size such as 1 gig no samples are collected
- No messages will be recorded in the alert log. A trace file will be produced which contains following message:
*** MODULE NAME:(sqlplus@xxxxxx (TNS V1-V3)) 2017-01-30 11:13:38.222
*** ACTION NAME:() 2017-01-30 11:13:38.222kewa_alloc_chunks: Out of chunk slots (127)
- Before 12.1.0.1 the max setting for "_ash_size" is 254Mb, i.e. 127 chunks of 2 Mb chunksize. Starting in 12c _ash_size can be set to a value greater than 254Mb
Changes
Upgrade to 12c
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |