My Oracle Support Banner

OPEN RESETLOGS FAILS ORA-19751, ORA-15046, ASM AND BLOCK CHANGE TRACKING FILE (Doc ID 832496.1)

Last updated on JUNE 11, 2023

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.3 [Release 10.2 to 11.2]
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 Backup Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

10.2.0.2 Database using a 'block change tracking' file stored in ASM. Controlfile and Database is restored and recovered successfully but the open resetlogs fails with:

RMAN-571: ===========================================================
RMAN-569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-571: ===========================================================
RMAN-3002: failure of alter db command at 06/27/2006 12:04:59
ORA-19751: could not create the change tracking file
ORA-19750: change tracking file:
'+<DGNAME>/<DBNAME>/changetracking/ctf.267.594215785'
ORA-17502: ksfdcre:4 Failed to create file
+<DGNAME>/<DBNAME>/changetracking/ctf.267.594215785
ORA-15046: ASM file name
'+<DGNAME>/<DBNAME>/changetracking/ctf.267.594215785'
is not in single-file creation form

Changes

db was restored and recovered using rman and attempted to open with resetlogs.

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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.