Disabling BCT (BLOCK CHANGE TRACKING) Generates ORA-01265 & ORA-15028

(Doc ID 1611159.1)

Last updated on OCTOBER 31, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.5 to 12.1.0.1 [Release 10.2 to 12.1]
Information in this document applies to any platform.

Symptoms

When disabling BLOCK CHANGE TRACKING (BCT file is on ASM), you get ORA-01265 & ORA-15028 on the db alert log:

ALTER DATABASE DISABLE BLOCK CHANGE TRACKING;

Fri Dec 27 16:43:35 GMT 2013
ALTER DATABASE DISABLE BLOCK CHANGE TRACKING
Fri Dec 27 16:43:35 GMT 2013
Block change tracking service stopping.
Fri Dec 27 16:43:35 GMT 2013
Stopping background process CTWR
WARNING: Cannot delete Oracle managed file +DEV_BCTDG01/jldbxd01/changetracking/ctf.256.835288493
Fri Dec 27 16:43:36 GMT 2013
Errors in file /u01/app/oracle/admin/JLDBXD01/udump/jldbxd01_ora_29035.trc:
ORA-01265: Unable to delete CHANGE TRACKING +DEV_BCTDG01/jldbxd01/changetracking/ctf.256.835288493
ORA-15028: ASM file '+DEV_BCTDG01/jldbxd01/changetracking/ctf.256.835288493' not dropped; currently being accessed
Completed: ALTER DATABASE DISABLE BLOCK CHANGE TRACKING
Fri Dec 27 16:44:51 GMT 2013

 

When placing BCT file is on normal filesystem ,you will not hit this issue.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms