SEO

#1 (**permalink**) 02-24-2008, 01:08 PM

Hi,

We are implementing RMAN. I've run into a few test cases where I
received the following error:

RMAN-06089: archived log
/u01/app/oracle/admin/mpcpilot/arch/arch_1_145202.arc not found or out
of sync with catalog

I am not sure how this happened. I got around it by running this small
script:

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

Here is my question: Whould it be feasible to run a crosscheck command
before each RMAN backup and check the log file for any errors before
the actual backup begins?

Thanks,

Arthur

#2 (**permalink**) 02-24-2008, 01:08 PM

amerar@iwc.net wrote:
> Hi,
>
> We are implementing RMAN. I've run into a few test cases where I
> received the following error:
>
> RMAN-06089: archived log
> /u01/app/oracle/admin/mpcpilot/arch/arch_1_145202.arc not found or out
> of sync with catalog
>
> I am not sure how this happened. I got around it by running this small
> script:
>
> run {
> allocate channel for maintenance type disk;
> change archivelog all crosscheck;
> release channel;}
>
> Here is my question: Whould it be feasible to run a crosscheck command
> before each RMAN backup and check the log file for any errors before
> the actual backup begins?
>
> Thanks,
>
> Arthur
>

WHAT test cases?
Did you get the RMAN-06089 when backing up, after manual deletion
of archived redo logs? Don't - let RMAN back them up, and remove them.

And yes - you can do a crosscheck - before or after.
--
Regards,
Frank van Bortel

#3 (**permalink**) 02-24-2008, 01:09 PM

Note to OP: It is important for these types of questions to state the
version and whether you are using some sort of high availability
software. See note: 1035665.6 on metalink, too. For example, if you
are moving arcs around and change some ownership/protection, you can
run into this.

I do crosschecks before the backup, since I'm removing things from disk
at various times and nocatalog, and I want to start the rman at a known
state. I purposefully leave several days of arcs on disk, since it is
possible for rman to miss things and one never knows when you might
need something older or newer in a restore.

Here is an example of a missing thing:

The "backup archivelog all" at the end of an rman run command
apparently generated sequences 2835 and 2836 at 20:33, Oracle decided
to spit out 2837 at 20:35, and rman said it was done at 20:37. When I
did the (standby database) restore, RMAN-06025: no backup of log thread
1 seq 2837 scn 23012872 found to restore.

I had expected any arcs generated before rman said it was done would be
included.

jg
--
@home.com is bogus.
http://www.cio.com/archive/050105/comair.html

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

RMAN Question