ORACLE 9i RMAN ERROR RMAN-00571 RMAN-00569 RMAN-03002 RMAN-03014 RMAN-03009 RMAN-20032
RMAN>
Starting backup at 11-JAN-16
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 01/11/2016 19:15:19
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of full resync command on default channel at 01/11/2016 19:15:19
RMAN-20032: checkpoint change# too low
We face generally face issue, when restore a database a database using OS copy instead of RMAN , however RMAN is configured for the database.
In this case . you can open the database using restored file(OS copy) but in RMAN will not run as checkpoint in RMAN catalog and control file are different.
Sol:-
1. Login with Catalog database
Connect Cataloguser/password@rmancatalogdb
2. Find out the db_key,dbid of database in which you are facing issue.
SQL> SELECT db_key, dbid, name FROM rc_database WHERE name = 'ORCL';
DB_KEY DBID NAME
---------- ---------- --------
23085 1312293510 ORCL
3. Unregistered database from catalog.
SQL> EXECUTE dbms_rcvcat.unregisterdatabase(23085 , 1312293510);
PL/SQL procedure successfully completed.
SQL>
4. Login with database for which you are running RMAN command.
$. oraenv
$orcl
$RMAN
$connect target /
$connect catalog Cataloguser/password@rmancatalogdb
$Register database.
Now you can run any command.
RMAN>
Starting backup at 11-JAN-16
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 01/11/2016 19:15:19
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of full resync command on default channel at 01/11/2016 19:15:19
RMAN-20032: checkpoint change# too low
We face generally face issue, when restore a database a database using OS copy instead of RMAN , however RMAN is configured for the database.
In this case . you can open the database using restored file(OS copy) but in RMAN will not run as checkpoint in RMAN catalog and control file are different.
Sol:-
1. Login with Catalog database
Connect Cataloguser/password@rmancatalogdb
2. Find out the db_key,dbid of database in which you are facing issue.
SQL> SELECT db_key, dbid, name FROM rc_database WHERE name = 'ORCL';
DB_KEY DBID NAME
---------- ---------- --------
23085 1312293510 ORCL
3. Unregistered database from catalog.
SQL> EXECUTE dbms_rcvcat.unregisterdatabase(23085 , 1312293510);
PL/SQL procedure successfully completed.
SQL>
4. Login with database for which you are running RMAN command.
$. oraenv
$orcl
$RMAN
$connect target /
$connect catalog Cataloguser/password@rmancatalogdb
$Register database.
Now you can run any command.
No comments:
Post a Comment