Re: RMAN-00600 Error

"Ron" <support_at_dbainfopower.com> wrote in message news:<ctydndXf0eTb7q_dRVn-vg_at_comcast.com>...
> Hello Pete,
>
> Any recent changes on system (upgrades, etc)?
>
> Can you check with SA is any system errors are showing up?
>
> Another thing: If possible, can you run dbv to verify that database
> datafiles are okay?

Responding to Daniel Morgan's:

The information you posted about string literals is more than support has told me, which has been not much of anything. Yesterday, I found in veritas logs that it was complaining of string literals when it errored. After finding that in the logs, I cut the lengths down all string literals so they were less than 10 characters. Still received the same errors writing to disk and tape.

Responding to Ron:

No changes have been made to this system for over 2 to 3 months, OS or DB software wise.

BTW, this is fixed. The solution? I didn't think of it right away, but, I manually ran a resync on the catalog and reran a backup and it worked. It looks like the recovery catalog got mucked up somehow, don't know what but I'd sure like to know. Reason I didn't think of resync'ing the catalog before is after running any rman script, i.e. backup script, I write the scripts so that they perform a resync of the catalog(I would have thought this would have caught it). I guess I've learned an important step in troubleshooting RMAN, no matter what the error, always run a resync even if you think it's not going to help.

Thanks for your suggestions gentlemen.

Hope this helps someone else.
Pete's Received on Wed Feb 18 2004 - 10:35:24 CST