FranklinFaces.com - Oracle & SQL Server Database Forums for all IT Professionals / Oracle Forum / RMAN - Error Codes / RMAN-06000-06999 / RMAN-06059: expected archived log not found. / Latest Posts

RE: RMAN-06059: expected archived log not found.

Admin — Thu, 10 Jun 2010 12:56:55 GMT

RMAN-06059: expected archived log not found

RMAN attempted to backup an archive log file, but couldn't find it.

This can happen for a variety of reasons; the file has been manually moved or deleted, the archive log destination has recently been changed, the file has been compressed, etc.

Your options are either to restore the missing file(s), or to perform a crosscheck. To perform a crosscheck, run the following command from within RMAN:

change archivelog all crosscheck;

It is advisable to perform a full backup of the database at this point.

When an archive log crosscheck is performed, RMAN checks each archive log in turn to make sure that it exists on disk (or tape). Those that are missing are marked as unavailable. If you have got missing logs, this won't bring them back. It will allow you to get past this error and back-up the database though.

RE: RMAN-06059: expected archived log not found.

Admin — Sat, 17 Jan 2009 12:14:11 GMT

Thanks Stacy for the post. Here are some additional information regarding RMAN Crosscheck command.

This is a link to details about RMAN CROSSCHECK command. Hope it helps .

Regards,
Admin

RMAN-06059: expected archived log not found.

stacyliang83 — Thu, 15 Jan 2009 21:38:30 GMT

I got this error code for RMAN and I couldn't figure it out for a long time. Then, I finally did after some research so I'm putting my findings here.

RMAN-06059: expected archived log not found, lost of archived log compromises recoverability.

If archived redo logs are deleted/moved/compressed by accident or if you have some scripts that clear your flash recovery area or what ever you was done to remove from disk without being backed up, the rman catalog will not know this has happened, and will keep attempting to backup the missing archived redo logs. That will cause rman archived redo log backups to fail altogether with an error like the one mentioned above.

If you can, you should bring back the missing archived redo logs to their original location and name, and let rman back them up. But if that is impossible, the workaround is to “crosscheck archivelog all”. Here is sample:

rman <connect target /
connect catalog username/password@catalog
run {
allocate channel c1 type disk ;
crosscheck archivelog all ;
release channel c1 ;
}
EOF

You’ll get output like this:

[i]validation succeeded for archived log
archive log filename=/u05/oradata/archive/redoarch_1038.arc recid=1017 stamp=611103638[/i]

for every archived log as they are all checked on disk. That should be the catalog fixed, run an archivelog backup to make sure.

Hope this helps.

Thanks,
Stacy