Status 6 means, don't call the backup guy, call the Oracle DBA... LOL

The Netbackup job calls an oracle script, which (should) contain information about where oracle logs the output of the job. That log file will have the reason for the error.

Tip - on new policies, 90% is typo in oracle scripts - client, policy name mistyped, etc.

Are you saying you're backing up an Oracle d/b & it's failing with Status Code 6?
If so, can you provide the full error details? NetBackup version, O/S on master/client etc?

If it helps, looking at this T/N for Status 6 - there are a lot of Oracle related errors, each with an ORA error as well as the NetBackup error code:

This Technote contains a table for NetBackup's Status Codes, with links to potential resolutions for each.

It may be worth looking in the Oracle Admin Guide for NetBackup in the troubleshooting section?
Veritas NetBackup (tm) 6.5 for Oracle Administrator's Guide for UNIX and Linux
Veritas NetBackup (tm) 6.5 for Oracle Administrator's Guide for Windows

I'll try to find some logs...

I don't know beans about oracle.

I 'm moving the archivelogs to another partition ... while I cant help.

what shoul I ask to de DBA?

that depends on what's in the logs! ;)

***Edit***
Can't harm to post them (or excerpts from them) here too. :)

Andy,

netbackup 6.5.4

orecle is running over Solaris 10 Container,

it was running and somehow it stops running.

Then I think the DBA has a larger issue than backups on his/her hands :)

One thing to ask, and this could be a quick learning experience for future backup failures, is where they keep the rman logs.  If you find their location, and if you have permission to read them, tail -50 the rman log, and it will tell you why Oracle thinks the backup failed.  This can usually be a good place to start when tracking down the issue.  This way, you can quickly point out to the DBA what you think might be wrong.

When you tail the file, you will see a pretty obvious error stack if something went wrong.  If Oracle simply does not know what to do with the rman script that NBU is provided, it will simply say that the database was not backed up.

***EDIT***

The rman logs are kept on the client, not the master/media server, so you would have to have access to the client in order to read them. 

Where should I find the rman log?

is there any patern?

find / -name <something> -print

they have always been the script_name_,<date>.out

So if your script is called "hot_database_backup.sh" then your logfile would be "hot_database_backup.sh_102109.out"

I'm not sure if this is something that can be modified for different environments.

which contents should be known by your DBA 
log files are usually .out files under /opt/oracle or something like that

 released channel: ch00
INF - RMAN-00571: ===========================================================
INF - RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
INF - RMAN-00571: ===========================================================
INF - RMAN-03002: failure of backup command at 10/22/2009 11:42:19
INF - RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
INF - ORA-19625: error identifying file /usr2/archivelogs/DBFAT/1_33103_684406673.log
INF - ORA-27037: unable to obtain file status
INF - SVR4 Error: 2: No such file or directory
INF - Additional information: 3
INF - Recovery Manager complete.
INF - End of Recovery Manager output.
INF - End Oracle Recovery Manager.

I agree with rjrumfelt - start with the rman log. You need to find rman error message.
The most common reason for failure of Archive log backups is that there are either no logs to be backed up or expected logs no longer there due to manual intervention (move/delete).
Whenever you start using rman, rman manages archive logs.

as I had to move files to another partition, is that the cause of the problem????

the problem is, if it was working i didn't  had to move..

by tha way thaks a lot folks

Wow Marinanne too..

what a great help team.

I sent the error to the DBA lady,

I think that RMAN is not updating the log.. or something...

is there something that I could do in paralell??

whille the DBA don't answer?

Who will have the solution vote??