Shulou(Shulou.com)06/01 Report--

Oracle Study-- RMAN enabled block change tracking error

System environment:

Operating system: RedHat EL6

Oracle: Oracle 11g R2

Target DB: prod

Catalog DB: orcl

An ORA-600 error occurred when starting "block change tracking" after using rman backup for incremental backup!

Case study:

1. Enable block change tracking

11:23:43 SYS@ prod > alter database enable block change tracking using file'/ home/oracle/blk.trc' reuse

Database altered.

Alarm log:

Alter database enable block change tracking using file'/ home/oracle/blk.trc'

Block change tracking file is current.

Starting background process CTWR

Tue Apr 07 11:36:55 2015

CTWR started with pid=33, OS id=5576

Block change tracking service is active.

2. Create a backup script through rman

[oracle@rh7 dbs] $rman target / catalog rman/rman@orcl

Recovery Manager: Release 11.2.0.1.0-Production on Tue Apr 7 11:29:41 2015

Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.

Connected to target database: PROD (DBID=239333010)

Connected to recovery catalog database

RMAN > create global script global_del_obso comment'A script for obsolete backup and delete it'

{

2 > 3 > crosscheck archivelog all

4 > delete noprompt expired archivelog all

5 > allocate channel ch2 device type disk

6 > delete noprompt obsolete recovery window of 15 days

7 > release channel ch2

8 >}

RMAN-00571: =

RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =

RMAN-00571: =

RMAN-03002: failure of create script command at 04/07/2015 11:29:58

RMAN-06004: ORACLE error from recovery catalog database: ORA-03114: not connected to ORACLE

Alarm log:

[oracle@rh7] $tail-f / u01/app/oracle/diag/rdbms/prod/prod/trace/alert_prod.log

Tue Apr 07 11:27:16 2015

Errors in file / u01/app/oracle/diag/rdbms/prod/prod/trace/prod_ctwr_4912.trc (incident=39841):

ORA-00600: internal error code, arguments: [krccacp_badfile], [1513065], [0], [624054], [0], []

Incident details in: / u01/app/oracle/diag/rdbms/prod/prod/incident/incdir_39841/prod_ctwr_4912_i39841.trc

Errors in file / u01/app/oracle/diag/rdbms/prod/prod/trace/prod_ctwr_4912.trc:

ORA-00600: internal error code, arguments: [krccacp_badfile], [1513065], [0], [624054], [0], []

CTWR (ospid: 4912): terminating the instance due to error

Tue Apr 07 11:27:19 2015

ORA-1092: opitsk aborting process

Instance terminated by CTWR, pid = 4912

You can see from the log that the CTRW process turned off Instance!

3. Stop using block change tracking

11:31:33 SYS@ prod > alter database disable block change tracking

Database altered.

Elapsed: 00:00:01.13

Alarm log:

Alter database disable block change tracking

Tue Apr 07 11:31:50 2015

Block change tracking service stopping.

Stopping background process CTWR

Deleted file / home/oracle/blk.trc

Completed: alter database disable block change tracking

Tue Apr 07 11:34:36 2015

Then create a backup script through rman:

[oracle@rh7 dbs] $rman target / catalog rman/rman@orcl

Recovery Manager: Release 11.2.0.1.0-Production on Tue Apr 7 11:29:41 2015

Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.

Connected to target database: PROD (DBID=239333010)

Connected to recovery catalog database

RMAN > create global script global_del_obso comment'A script for obsolete backup and delete it'

{

2 > 3 > crosscheck archivelog all

4 > delete noprompt expired archivelog all

5 > allocate channel ch2 device type disk

6 > delete noprompt obsolete recovery window of 15 days

7 > release channel ch2

8 >}

This is a successful backup script!

Note:

The same error occurred later. After deleting the trace file "blk.trc" under the operating system, it returned to normal. It is not clear what the specific cause of this problem is.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.