cancel
Showing results for 
Search instead for 
Did you mean: 

Backup Failed with Status 6

tonzy5171
Level 1

Below is the error output from the backup logfile.

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ch03 channel at 09/14/2016 09:44:34
ORA-19506: failed to create sequential file, name="arch_20160914_PERP-30689_1_922527873",
parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
VxBSACreateObject: Failed with error:
Server Status: Communication with the server has not been initiated or the server status has not been retrieved from the serve

3 REPLIES 3

Michael_G_Ander
Level 6
Certified

https://vox.veritas.com/t5/NetBackup/General-database-backup-error-troubleshooting/m-p/675381 gives some hints to troubleshooting database backups

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

Marianne
Level 6
Partner    VIP    Accredited Certified

Difficult to even try and assist with NO background information whatsoever.

This error looks like comms issues between Oracle client and the master: 

Server Status: Communication with the server has not been initiated or the server status has not been retrieved from the server

But this looks like archive log backup: name="arch_....  which MAY indicate that database backup was successful and MAYBE only this particular job is failing?

Please try to give as much info as possible and ensure all log folders are in place on Master, Media server and Oracle client as per Troubleshooting section in NetBackup for Oracle Administrator's Guide  .

Please also check and confirm Client Connect timeout settings on master and media server.

 

tonzy517
Level 1

Thank You for the Respond.

Veritas support that I engage, after troubleshooting found out the file permision of the backup script need to change to 777.