oracle06004,RMAN-06004处理过程

中午,NETBACKUP的工程师说备份有错误,叫帮忙解决

Full backup requested

Recovery Manager: Release 10.2.0.2.0 - Production on Thu Apr 19 18:47:02 2007[@more@]

Copyright (c) 1982, 2005, Oracle. All rights reserved.

connected to target database: BDB (DBID=1955257682)

connected to recovery catalog database

RMAN>

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of resync command at 04/19/2007 18:47:05

RMAN-06004: ORACLE error from recovery catalog database: RMAN-20011: target database incarnation is not current in recovery catalog

以上是错误的LOG信息,初步断定是恢复目录没有同步,先采取以下措施

$ sqlplus

SQL*Plus: Release 10.2.0.2.0 - Production on Fri Apr 20 14:53:08 2007

Copyright (c) 1982, 2005, Oracle. All Rights Reserved.

Connected to:

Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production

With the Partitioning, OLAP and Data Mining options

SQL> select DBID,NAME,DBINC_KEY, RESETLOGS_CHANGE#, RESETLOGS_TIME

2 from rc_database_incarnation;

DBID NAME DBINC_KEY RESETLOGS_CHANGE# RESETLOGS_TI

---------- -------- ---------- ----------------- ------------

2766741381 GZDB 2 1 28-SEP-06

2766741381 GZDB 15689 42207957 03-NOV-06

3567755650 REPORT 673 1 26-SEP-06

2770581111 GZDB 25839 1 11-NOV-06

3605337364 SZDB 67091 1 07-DEC-06

746243157 CDR 131873 1 26-SEP-06

3599018465 SZDB 236568 1 27-SEP-06

1955257682 BDB 720127 1 15-DEC-06

1955257682 BDB 769883 7.9103E+12 21-MAR-07

3971394927 TESTPMY 749867 1 12-APR-07

3971394927 TESTPMY 784993 7.9107E+12 19-APR-07

DBID NAME DBINC_KEY RESETLOGS_CHANGE# RESETLOGS_TI

---------- -------- ---------- ----------------- ------------

3971394927 TESTPMY 788809 7.9107E+12 20-APR-07

12 rows selected.

SQL> select DBID,NAME,DBINC_KEY, RESETLOGS_CHANGE#, RESETLOGS_TIME

2 from rc_database_incarnation where dbid=1955257682;

DBID NAME DBINC_KEY RESETLOGS_CHANGE# RESETLOGS_TI

---------- -------- ---------- ----------------- ------------

1955257682 BDB 720127 1 15-DEC-06

1955257682 BDB 769883 7.9103E+12 21-MAR-07

SQL> exit

Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production

With the Partitioning, OLAP and Data Mining options

$ rman catalog target

Recovery Manager: Release 10.2.0.2.0 - Production on Fri Apr 20 14:55:15 2007

Copyright (c) 1982, 2005, Oracle. All rights reserved.

connected to target database: BDB (DBID=1955257682)

connected to recovery catalog database

RMAN> reset database to incarnation 769883;

database reset to incarnation 769883

target database incarnation not found in control file

RMAN> resync catalog;

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of resync command at 04/20/2007 14:56:25

RMAN-06004: ORACLE error from recovery catalog database: RMAN-20011: target database incarnation is not current in recovery catalog

RMAN> list incarnation;

RMAN> exit

Recovery Manager complete.

虽然是RESET了,但是incarnation依然没有一致,也就是说问题还没有解决.继续......

$ rman target catalog

Recovery Manager: Release 10.2.0.2.0 - Production on Fri Apr 20 14:57:45 2007

Copyright (c) 1982, 2005, Oracle. All rights reserved.

connected to target database: BDB (DBID=1955257682)

connected to recovery catalog database

RMAN> list incarnation;

RMAN> Register database;

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03009: failure of register command on default channel at 04/20/2007 14:58:23

RMAN-20002: target database already registered in recovery catalog

RMAN> exit

Recovery Manager complete.

$ rman target catalog

Recovery Manager: Release 10.2.0.2.0 - Production on Fri Apr 20 15:00:38 2007

Copyright (c) 1982, 2005, Oracle. All rights reserved.

connected to target database: BDB (DBID=1955257682)

connected to recovery catalog database

RMAN> list backup;

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of list command at 04/20/2007 15:00:43

RMAN-06004: ORACLE error from recovery catalog database: RMAN-20011: target database incarnation is not current in recovery catalog

RMAN> exit

Recovery Manager complete.

$ rman catalog

Recovery Manager: Release 10.2.0.2.0 - Production on Fri Apr 20 15:05:06 2007

Copyright (c) 1982, 2005, Oracle. All rights reserved.

connected to recovery catalog database

RMAN> list incarnation;

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of list command at 04/20/2007 15:05:13

RMAN-06171: not connected to target database

RMAN> exit

Recovery Manager complete.

还是不行,只好重新注册了.

$ rman catalog target

Recovery Manager: Release 10.2.0.2.0 - Production on Fri Apr 20 15:20:31 2007

Copyright (c) 1982, 2005, Oracle. All rights reserved.

connected to target database: BDB (DBID=1955257682)

connected to recovery catalog database

RMAN> UNREGISTER DATABASE NOPROMPT;

database name is "BDB" and DBID is 1955257682

database unregistered from the recovery catalog

RMAN> Register database;

database registered in recovery catalog

starting full resync of recovery catalog

full resync complete

RMAN> exit

Recovery Manager complete.

叫NETBACKUP工程师尝试备份,OK了.那边一直问我是什么原因造成的,

1. The database has been duplicated from outside RMAN and the DBID had not been modified,

consequently the DBID is the same for the cloned and the production database...

2. The cloned database has been registered in the RMAN catalog.

但是我也纳闷,因为只需要reset就可以,但是事实看来不行,我怀疑是有修改了恢复目录.