Disabling BCT (BLOCK CHANGE TRACKING) Generates ORA-01265 & ORA-15028
(Doc ID 1611159.1)
Last updated on MARCH 07, 2025
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.5 to 12.1.0.1 [Release 10.2 to 12.1]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 Cloud Exadata Service - Version N/A and later
Generic (Platform Independent)
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 +<DGNAME>/<DB_NAME>/changetracking/ctf.256.835288493
Fri Dec 27 16:43:36 GMT 2013
Errors in file /<PATH>/admin/<DB_NAME>/udump/<DB_NAME>_ora_29035.trc:
ORA-01265: Unable to delete CHANGE TRACKING +<DGNAME>/<DB_NAME>/changetracking/ctf.256.835288493
ORA-15028: ASM file '+<DGNAME>/<DB_NAME>/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.
Changes
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 |