ORA-00064 After 12.2 Upgrade When SHARED_POOL_RESERVED_SIZE Is Set
(Doc ID 2430555.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database Exadata Express Cloud Service - Version N/A and laterOracle Database - Enterprise Edition - Version 12.2.0.1 to 18.5.0.0.0 [Release 12.2 to 18]
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Information in this document applies to any platform.
Symptoms
After the database upgrade to 12.2, the following error might be seen during startup:
PRCR-1013 : Failed to start resource ora.improve_dg.db
PRCR-1064 : Failed to start resource ora.improve_dg.db on node node1
CRS-5017: The resource action "ora.improve_dg.db start" encountered the following error:
ORA-00064: object is too large to allocate on this O/S (1,<some value>,gc name table).
PRCR-1064 : Failed to start resource ora.improve_dg.db on node node1
CRS-5017: The resource action "ora.improve_dg.db start" encountered the following error:
ORA-00064: object is too large to allocate on this O/S (1,<some value>,gc name table).
Changes
Upgrade from 11.2 to 12.2 using DBUA.
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 |