Oracle 8, RMAN and good Hot Backup Procedure

[SBA_1]

We have recently moved into the big bad world of HOT Oracle backups, from our previous cold backup strategy. Initial testing proved ok, and paved the way to enable our production backup to utilise hot backups. However, since running hot backups on our production database, I have encountered a problem where archive logs are not(do not appear to be) being backed up. The attached barlist has been used in 2 of our TEST instances, and successfully recorded archive log files, and backed them up to tape. The error I am receiving from Omniback is:
RMAN-03022: compiling command: sql
RMAN-06162: sql statement: alter system archive log current
RMAN-03023: executing command: sql

RMAN-03022: compiling command: backup
RMAN-03026: error recovery releasing channel resources
RMAN-08031: released channel: dev_1
RMAN-08031: released channel: dev_2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: backup
RMAN-06089: archived log /u04/archives/PRD/arch76689.arc not found or out of sync with catalog

I have looked, and cannot find this archive log file in our archive log directory.

Also wondering whether any improvements could be made to the script (eg include current control file, etc)

Any help greatly appreciated. From what I have seen in here already, points should be easy to come by!

[harry d brown jr]

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x541136e69499d611abdb0090277a778c,00.html

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xdb1072106351d5118fef0090279cd0f9,00.html

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xd65268c57f64d4118fee0090279cd0f9,00.html

search on

rman AND oracle AND omniback AND log AND hot AND backup

Don't forget to click on boolean


live free or die
harry

[Printaporn_1]

Hi,

Connect rman to target database

do

allocate channel for maintenance type disk;
change archivelog all crosscheck;
release channel;


exit from rman.

this would help solve your problem.

[Brian Crabtree · Accepted solution]

You should check to see if you have a process deleting log files outside of rman. As long as you are backing up the archivelogs using the "delete input" option, you should not get this failure.

To bypass this error, you will want to issue "change archivelog all validate;" after connecting to the database and catalog if you are using one.

Brian

[Joaquin Gil de Vergara]

first of all be sure thsat you have enterprise edition... if not you can??t use more than 1 channell

The second question: you must resync the catalog.... in the RMAN prompt type
resync catalog;

and then

sql 'alter system switch logfile';
change archivelog all validate;

[SBA_1]

Thanks for all of these replies.
It looks like there is more than one way to skin a cat!
change archivelog all validate;
was the command I needed to issue to correct this issue.

I probably should have mentioned that we are NOT using a recovery catalog, and using the control files. This being the case, should I modify the script to include current control file?
Also, we have a nightly purge job that deletes all archive logs older than 4 days. My question is: Can I add

change archivelog all validate;

into the backup script to ensure that the catalog is in sync prior to backing up the archive logs?

I have added the delete input statement to address the issue of deleting archive logs as we back them up.

Further assistance here is greatly appreciated.

[Joaquin Gil de Vergara]

if you use the delete input RMAN statement you don`t need to delete the archives with external procedures... RMAN deletes it when are copied and always be in sync!

I think that you must configure an instance as recovery catalog... is not very dificcult