-
Hello All,
I have an 816 database on unix and on the same box I have an rman 816 instance. The problem started when 1 of my junior dba delete bunch of an archive logs from the arch mountpoint. As you know that once you have created rman and created the catalog then registered the db...it (rman instance) reseyncs itself with the prod database..so when you kick off rman backups the hot back should not only do a hotbackup but also archive all arch logs with rman..
The issue is my database is out of sync with rman and i have tried resynching it as well...i believe the only solution i have left is reset logs delete all archive logs and resync the database.... what do you guys think? dont we reset logs when we recover db? alter database open reset logs? when i type that in..i get messages...used for recover only..am i doing something wrong/? pls advise....
-
Here are some ideas.
First, the RMAN database should not be on the same server as the database it will potentially restore.
Second, you can unregister the database following these steps and then reregister the database:
SQL> select db_key, db_id from db;
SQL>execute dbms_rcvcat.unregisterdatabase(db_key, db_id);
SQL> select db_key, db_id from db;
to determine that the db is no longer registered.
Then you will need to register the database again.
Good luck.
-
hi dknight...what about the archive logs which are out of sync?
You are just giving me a solution to register/unregister the database..but i will have to eventually fix the out of synch error....
-
After you re-register the database, take another backup with RMAN.
Then, the archive log files that were deleted should be obsolete.
Maybe I am missing your point?
-
Dave...how will the archive logs be deleted?
I ran backup using omniback connected to rman...
-
