Chatta subito con l'assistenza
Chat con il supporto

NetVault Plug-in for Oracle 11.3 - User Guide

Introducing Quest® NetVault® Backup Plug-in  for Oracle Defining a backup strategy Installing and removing the plug-in Configuring the plug-in Backing up data Using the Oracle® Flashback Database Restoring data
Restoring and recovering data: an overview Performing User Managed restores Using advanced User Managed restore procedures Performing RMAN restores Using RMAN types of recovery in a non-RAC environment Using advanced procedures with RMAN restores
Maintaining the Recovery Catalog Using the RMAN CLI Using the Plug-in with Oracle® RAC Using the Plug-in in a failover cluster environment Using the plug-in with Oracle® Data Guard Troubleshooting

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 Backup 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
1
Cancel the hung backup job.
2
Remove the lock on the Control File.
a
Start SQL*Plus, and connect with administrator privileges to the local instance.
SQLPLUS SYS AS SYSDBA
b
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>
c
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
-------- -------------------
130 12118
132 5643
133 3184
134 3100
135 12116
d
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 =>
3
Ensure that the NetVault Backup Server and Do Restore from NetVault Backup 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 Backup Server and Do Restore from NetVault Backup Server settings are defined as detailed in Configuring default settings.

•
RMAN-03002: failure of Duplicate Db command at <date_hour>
•
RMAN-03015: error occurred in stored script Memory Script
•
RMAN-06054: media recovery requesting unknown log: thread <number> scn <number>

On Oracle® 9i, the plug-in’s Clone Database operation might complete with errors due to RMAN attempting to apply a log beyond the available logs in the backup stream.

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.

Oracle RMAN output not displayed correctly in binary logs

Problem

When running RMAN based jobs, the Plug-in for Oracle redirects the output from Oracle RMAN to the NetVault Backup binary logs. In this manner, the output from Oracle RMAN can be viewed in the NetVault Backup binary logs. However, the output for Oracle RMAN is incorrectly displayed or not displayed in the NetVault Backup binary logs.

Possible causes

Depending on the NLS_LANG setting, such output might not be displayed correctly, or not displayed in the NetVault Backup binary logs. The reason is because the encoding of the output generated by Oracle RMAN cannot be displayed by the NetVault Backup binary logs.

Resolution

To resolve this issue, change the NLS_LANG setting to an UTF-8 character set.

For example, if you have set NLS_LANG to JAPANESE_JAPAN.JA16SJISTILDE, and the NetVault Backup binary logs fail to correctly display the output generated by Oracle RMAN, then the NLS_LANG can be changed to JAPANESE_JAPAN.UTF-8 for the messages to be displayed correctly in the NetVault Backup binary logs. For more information, see NLS_LANG option in Adding a database.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione