RMAN Failure to Network Drive

From: Matt <mccmx_at_hotmail.com>
Date: 30 Jun 2004 04:08:50 -0700
Message-ID: <cfee5bcf.0406300308.3727bf0@posting.google.com>

Intermittently our RMAN full backup fails to a remote network share.

Oracle 8.1.7.4.1 Target DB, 8.1.7.4.1 Catalog (and 8.1.7.4.1 RMAN executable) - all on MS Windows.

The following is the error in the RMAN log:

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS

---

RMAN-00571: ===========================================================

RMAN-03007: retryable error occurred during execution of command: backup
RMAN-07004: unhandled exception during command execution on channel d1 RMAN-10035: exception raised in RPC: ORA-19504: failed to create file "r:\HR83PRD\HR83PRD_DB_l4fpk3cv_1_1.bak"

ORA-27044: unable to write the header block of file
OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 64) The specified network name is no longer available.

RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECREATE Recovery Manager complete.

Metalink has very few hits on this message, probably because it is actaully an OS error rather than an RMAN error.

However I did see one recommendation that setting DISABLE_OOB to ON in the client side sqlnet.ora can help in this scenario.

This would mean changing this parameter on the PROD DB server...

Anyone know of any issues with disabling out of band breaks (either performance or Dead Connection Detection related).

Metalink was also pretty vague on this parameter as was the Net 8 Admin Guide.

Thanks in advance.

Matt Received on Wed Jun 30 2004 - 06:08:50 CDT