I concur that the problem is often on the client.

Unfortunately, a status 6 message can mean nearly anything.  If the script
that calls the RMAN commands exits non-zero you get a 6, if the media
manager has an error then you get a 6, sunspots making static on your
favorite radio station then you get a 6.

Make sure you create the additional logging directories on the client that
are mentioned in the Oracle Agent guide.  I find the best diagnosis is
between the output of the rman script (don't send in-script errors to
/dev/null) and the logfiles in ../netbackup/logs/user_ops/dbext/logs (job
info), ../netbackup/logs/dbclient (Sched, status, params) &
../netbackup/logs/bphdb (STDOUT & STDERR).

-M

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Wayne T
Smith
Sent: Friday, November 18, 2005 9:01 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] **** Status 6 in NB for RMAN policies *****


Ray.Hill AT ny.frb DOT org wrote, in part,  on 11/18/2005 9:55 AM:
> I've been getting status 6 every time the Rman backups run. Does any 
> one have any ideas on this. The scripts are all on point so its not 
> that easy.

In my limited experience, the problem is back on the client.  A quick 
look at the logging your RMAN script produces should point you in the 
right direction.  My typical status code 6's are from inactive DBs or a 
full file system.  In any event, you can't (or I don't know how to) see 
the problem by just looking at your backup server.

cheers, wayne
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu