-
Good morning all. I have yet another RMAN 'opportunity'.
We currently do a full database backup each night. At the end of our script we backup our archive logs. We do not use a recovery catalog. Oracle 8.0.6 & AIX 4.3.2
run {
allocate channel d1 type disk;
backup
format "/oraback/db_back%s_$DATE"
(database);
sql 'alter system archive log current';
backup
filesperset 1
format "/oraback/arch_back%s_$DATE"
(archivelog all delete input);
We ran into some problems last week where we did some database maintenance and did not turn the archive logs off. The archive log directory filled up and we inadvertantly deleted 56 archive logs. Now, my RMAN will not archive the new logs out of the directory. We get these errors:
RMAN-00569: ================error message stack follows================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: backup
RMAN-06089: archived log /oracle/archdest/arch.log1_710.dbf not found or out of
sync with catalog
How can I get RMAN past this?
Thanks in advance for your help.
DJ
-
Have you tried doing a resync of the Recovery Catalog?
-
We don't use a recovery catalog. We use the nocatalog option. (I will be changing this in the future - I'm just not there yet.) What can I do in the meantime?
-
Try to run the script, and remove the part that backs up the Archive Logs. That will give you a working backup.
-
If I remove the part that backups the logs, will I put it back in tomorrow? Will it still delete them out of my archive directory? Will it remove the references to the deleted ones? Or will it ask for them again after I put the backup line back in?
My archive log filesystem is on schedule to fill up tomorrow. (We keep getting more archive logs, none of them are being deleted.) I have searched and searched for a solution. I have found a couple of references to run this command from inside RMAN:
change archivelog all validate;
Will that fix it or make it worse? Thanks for your help, I'm getting a bit nervous.
Debi
-
I don't know the answer to your question.
I would recommend that you do an operating system backup so that you have something in case of db failure. You need a good backup.
Good luck.
-
From Metalink..
.
.
.
.
The common mistake is migrating or removing archived redo log files without
using RMAN which rises error RMAN-6089 during the backup or restore
operation. It may be not feasible to make archived redo logs unavailable with
above approach after massive file deletion. To notify the recovery catalog about
missing archived redo logs, a change archivelog all validate command will be
more suitable.
RMAN> change archivelog all validate;
It should fix your problem.
