ALTER DATABASE ENABLE BLOCK CHANGE TRACKING USING FILE Fails With ORA-4031"Scntab_krcpx" And ORA-19760
(Doc ID 738410.1)
Last updated on FEBRUARY 20, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.3 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database 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.
Enabling Block Change Tracking via the following SQL command:
systematically raises the following errors:
ORA-04031: unable to allocate ....bytes of shared memory ("shared pool","...","....","scntab_krcpx")
ORA-19760 signalled during: ALTER DATABASE ENABLE BLOCK CHANGE TRACKING USING FILE '<full path>'...
Enabling Block Change Tracking in order to use RMAN incremental backups.
It is a must to use such change-tracking file to track the physical location of all database changes and benefit of fast RMAN incremental backups.
RMAN uses this file to quickly identify the blocks which have been modified, avoiding the time-consuming task of reading the entire datafile to determine which blocks have changed.
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