NetVault Plug-in for Oracle 13.0

Table 5. Troubleshooting backup failures
Error	Explanation
ORA-00245: control file backup operation failed	For RAC environments that use Oracle 11g Release 2 or later, ensure that the snapshot Control File is shared by all nodes in the RAC database. Check the CONFIGURE SNAPSHOT CONTROLFILE NAME TO parameter to determine the current setting. For more information, see Installation prerequisites.
ORA-01031: insufficient privileges on Oracle Backup error	User name specified in the Oracle SYSDBA User Name field of the Add, or Edit, Oracle Database dialog box must have SYSDBA privileges, be included in the Oracle Password File, or be a member of the ORA_DBA OS group. Additionally, if the SYSDBA user is specified in the Oracle Password File, the Use Oracle Password File Authentication option should be selected in the plug-in’s Configure dialog box.
Failed to Connect to Database or ORA-01034: Oracle is not available	Oracle Instance specified in the Oracle SID field of the Add, or Edit, Oracle Database dialog box must be in an OPEN state. The instance must be in an OPEN state to perform backup.
ORA-01123: Cannot start online backup; media recovery not enabled	Oracle Instance is not running in ARCHIVELOG mode as specified in Prerequisites.
RMAN-06062: cannot backup SPFILE because the instance was not started with SPFILE	If either Control File Autobackup Enabled or Use RMAN Commands to backup SPFILE are selected on the Add, or Edit, Oracle Database dialog box, the database must be started with an SPFILE. Create an SPFILE and restart the instance using the SPFILE or use the Edit Oracle Database option to clear these two options and insert the path for the PFILE in the Parameter File(s) Path field.
RMAN-06180: incremental backups require Enterprise Edition	For editions other than Oracle Enterprise Edition, Incremental Cumulative and Incremental Differential backups are not supported. Select either Full or Incremental Level 0 for the Backup Type.
RMAN-06181: multiple channels require Enterprise Edition	Ensure that Number of Channels is set to 1.
Failed to back up all data	If the SYSDBA password has been changed on the Oracle Server, it must be updated in the plug-in’s Database Configuration. For more information, see Removing a saved password.
Flash Recovery Area Backup Fails with 'specification does not match any datafile copy in the repository' or 'specification does not match any backup set in the repository' errors.	A Flash Recovery Area backup was performed; however, the FRA does not contain any recovery files for previous backups that were performed with a Backup Destination of Disk or Both NetVault Media Manager and Disk. You must use the FRA as a Backup Destination before you can perform a backup of the FRA with the Flash Recovery Area backup type.
Backup fails when using DR Series system or QoreStor as the storage device for Oracle Database 12.x or later on Linux or UNIX	If you are running Oracle Database 12.x or later on Linux or UNIX, backups might fail if the device you select for Target Storage is a DR Series system or QoreStor storage device. For more information on avoiding this issue, see Using DR Series or QoreStor as the storage device for Oracle Database 12.x or later on Linux or UNIX.

Backup job hangs

Problem

There is a lock on the Control File and a backup job hangs at log output: “Log Message: Starting Control File and SPFILE Autobackup at <date>.” Or this job is canceled and a subsequent backup job completes with an error message in the log of the job: “ORA-00230: operation disallowed: snapshot control file enqueue unavailable.”

Possible causes

•

Plug‑in for Oracle has not been properly configured; that is, the NetVault Server field has not been set on the Configure dialog box.

•

Control File Autobackup has been enabled without proper configuration of the plug-in.

Resolution

Cancel the hung backup job.

Remove the lock on the Control File.

Start SQL*Plus, and connect with administrator privileges to the local instance.

SQLPLUS SYS AS SYSDBA

Verify that there is a lock on the Control File, and obtain the offending SID with the following query:

SELECT s.SID, USERNAME AS "User"

FROM V$SESSION s,V$ENQUEUE_LOCK l WHERE l.SID = s.SID

AND l.TYPE = 'CF' AND l.ID1 = 0 AND l.ID2 = 2;

In the following example, the offending SID is 133.

SQL> SELECT s.SID, USERNAME AS "User" FROM V$SESSION s,

V$ENQUEUE_LOCK l WHERE l.SID = s.SID AND l.TYPE =

'CF' AND L.ID1 = 0 AND l.ID2 = 2;

SID User

-------- -------------------

133 SYS

SQL>

Obtain the Process ID (SPID) that matches the SID with the following query:

SELECT s.sid,p.spid

FROM v$process p, v$session s

WHERE p.addr = s.paddr order by s.sid;

In the following example, the offending SPID is 3184.

SQL> SELECT s.sid,p.spid FROM v$process p, v$session s

WHERE p.addr = s.paddr order by s.sid;

SID SPID

-------- -------------------

Exit SQL*Plus, and stop the Process in the OS shell:

Kill -9 <spid>

Example:

SQL> exit

Disconnected from Oracle Database 10g Enterprise Edition

10.2.0.1.0 - 64 bit Production

With the Partitioning, Real Application Clusters, OLAP and

Data Mining options

izmir:/export/home/o10g => kill -9 3184

izmir:/export/home/o10g =>

Ensure that the NetVault Server and Do Restore from NetVault Server fields are defined in the default attributes as detailed in Configuring default settings.

Restore fails

Table 6. Troubleshooting restore failures

Error

Explanation

•

ORA-19511: Error received from media manager, error text: SBT error=7011, errno=1, sbtopen: system error

•

ORA-19511: Error received from media manager layer, error text: SBT error= 7063, errno = 0, sbtread: i/o error

•

ORA-27007: failed to open file

•

ORA-27012: Read from file failed

Ensure that NetVault Server and Do Restore from NetVault Server settings are defined as detailed in Configuring default settings.

RMAN-06054: media recovery requesting unknown log: thread <n> seq 40 scn <n>

This error might occur while performing a Clone Database operation. This error results because the old Control File has no record of the new archive log. Running the RMAN command ALTER DATABASE OPEN RESETLOGS brings the database online.

Warning (.. ..) Data Plug-in (… …) Failed with exit code 5

This warning appears if Block Media Recovery is selected with Oracle 11g databases. In spite of the “failed” message, the recovery completes with success and full access to the Oracle recovered data is granted.

The code 5 is a warning issued by Oracle 11g to let you know that recovery is necessary. Because the plug-in already includes the RMAN recovery command while performing Block Media Recovery, this message can be ignored.