Examples and notes on rman
Section 3: RMAN errors and troubleshooting:
Err 1: Missing archived redolog:
================================
Problem: If an archived redo is missing, you might get a message similar like this:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 03/05/2008 07:44:35
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /dbms/tdbaeduc/educroca/recovery/archive/arch_1_817_617116679.arch ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Solution:
If archived redo logs are (wrongly) deleted/moved/compressed from disk without being backed up, the rman catalog will not know this has happened, and will keep attempting to backup the missing archived redo logs. That will cause rman archived redo log backups to fail altogether with an error like:
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
If you can, you should bring back the missing archved redo logs to their original location and name, and let rman back them up.
But if that is impossible, the workaround is to “crosscheck archivelog all”, like:
rman <<e1
connect target /
connect catalog username/password@catalog run {
allocate channel c1 type disk ; crosscheck archivelog all ; release channel c1 ;
} e1
Or just go into rman and run the command:
RMAN> crosscheck archivelog all;
You‟ll get output like this:
validation succeeded for archived log archive log filename=D:REDOARCHARCH_1038.DBF recid=1017 stamp=611103638 for every archived log as they are all checked on disk.
That should be the catalog fixed, run an archivelog backup to make sure.
Err 2: online redo logs listed as archives:
===========================================
Testcase: a 10g 10.2.0.3 shows after recovery with resetlogs the following in v$archived_log. It looks as if it will stay there forever:
SEQ# FIRST NEXT NAME DIFF STATUS 814 1.7E+07 1.7E+07 12 D 815 1.7E+07 1.7E+07 42877 D 816 1.7E+07 1.7E+07 12 D 817 1.7E+07 1.7E+07 47857 D
2 1.7E+07 ####### redo01.log2.8147E+14 A 0 0 0 redo02.log#######
We dont know what is going on here.
Err 3: Highlevel overview RMAN Error Codes
==========================================
RMAN error codes are summarized in the table below.
0550-0999 Command-line interpreter 1000-1999 Keyword analyzer
2000-2999 Syntax analyzer 3000-3999 Main layer 4000-4999 Services layer
5000-5499 Compilation of RESTORE or RECOVER command 5500-5999 Compilation of DUPLICATE command
6000-6999 General compilation 7000-7999 General execution 8000-8999 PL/SQL programs
9000-9999 Low-level keyword analyzer 10000-10999 Server-side execution
11000-11999 Interphase errors between PL/SQL and RMAN 12000-12999 Recovery catalog packages
20000-20999 Miscellaneous RMAN error messages
Err 4: RMAN-03009 accompinied with ORA- error:
==============================================
Q:
Here is my problem; When trying to delete obsolete RMAN backupsets, I get an error:
RMAN> change backupset 698, 702, 704, 708 delete;
List of Backup Pieces Do you really want to delete the above objects (enter YES or NO)? YES RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of delete command on ORA_MAINT_SBT_TAPE_1 channel at
#######
ORA-27191: sbtinfo2 returned error Additional information: 2
What in the world does "Additional information: 2" mean? I can't find any more useful detail than this.
A:
Oracle Error :: ORA-27191 sbtinfo2 returned error Cause
sbtinfo2 returned an error. This happens while retrieving backup file information from the media manager"s catalog.
Action
This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
A:
---> ORA-27191 John Clarke:
My guess is that "2" is an O/S return code, and in
/usr/sys/include/errno.h, you'll see that error# 2 is "no such file or directory. Accompanied with ORA-27191, I'd guess that your problem is that your tape library doesn't currently have the tape(s) loaded and/or can't find them.
Mladen Gogala:
Additional information 2 means that OS returned status 2. That is a file not found error. In plain Spanglish, you cannot
delete files from tape, only from the disk drives.
Niall Litchfield:
The source error is the ora-27191 error
(http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10744/e24280.htm#ORA-27191) which suggests a tape library issue to me. You can search for RMAN
errors using the error search page as well
http://otn.oracle.com/pls/db10g/db10g.error_search?search=rman-03009, for example A:
---> RMAN-03009
RMAN-03009: failure of delete command on ORA_MAINT_SBT_TAPE_1 channel at date/time RMAN-03009: failure of allocate command on t1 channel at date/time
RMAN-03009: failure of backup command on t1 channel at date/time etc..
-> Means most of the time that you have Media Management Library problems
-> Can also mean that there is a problem with backup destination (disk not found, no space, tape not loaded etc..)
ERR 5: Test your Media Management API:
======================================
Testing the Media Management API
On specified platforms, Oracle provides a diagnostic tool called "sbttest". This utility performs a simple test of the tape library by acting as the Oracle database server and attempting to communicate with the media manager.
Obtaining the Utility
On UNIX, the sbttest utility is located in $ORACLE_HOME/bin.
Obtaining Online Documentation
For online documentation of sbttest, issue the following on the command line:
% sbttest
The program displays the list of possible arguments for the program:
Error: backup file name must be specified
Usage: sbttest backup_file_name # this is the only required parameter <-dbname database_name>
The display also indicates the meaning of each argument. For example, following is the description for two optional parameters:
Optional parameters:
-dbname specifies the database name which will be used by SBT to identify the backup file. The default is "sbtdb"
-trace specifies the name of a file where the Media Management software will write diagnostic messages.
Using the Utility
Use sbttest to perform a quick test of the media manager. The following table explains how to interpret the output:
If sbttest returns... Then...
0
The program ran without error. In other words, the media manager is installed and can accept a data stream and return the same data when requested.
non-0
The program encountered an error. Either the media manager is not installed or it is not configured correctly.
To use sbttest:
Make sure the program is installed, included in your system path, and linked with Oracle by typing sbttest at the command line:
% sbttest
If the program is operational, you should see a display of the online documentation.
Execute the program, specifying any of the arguments described in the online documentation. For example, enter the following to create test file some_file.f and write the output to sbtio.log:
% sbttest some_file.f -trace sbtio.log
You can also test a backup of an existing datafile. For example, this command tests datafile tbs_33.f of database PROD:
% sbttest tbs_33.f -dbname prod
Examine the output. If the program encounters an error, it provides messages describing the failure.
For example, if Oracle cannot find the library, you see:
libobk.so could not be loaded. Check that it is installed properly, and that LD_
LIBRARY_PATH environment variable (or its equivalent on your platform) includes the directory where this file can be found. Here is some additional information on the cause of this error:
ld.so.1: sbttest: fatal: libobk.so: open failed: No such file or directory
ERR 6: RMAN-12004
=================
Hi,
I m facing this problem any pointers will of great help....
1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00579: the following error occurred at 12/16/2003 02:46:31 RMAN-10035: exception raised in RPC:
RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECREATE
RMAN-03015: error occurred in stored script backup_db_full RMAN-03015: error occurred in stored script backup_del_all_al
RMAN-03007: retryable error occurred during execution of command: backup RMAN-12004: unhandled exception during command execution on channel t1 RMAN-10035: exception raised in RPC: ORA-19506: failed to create sequential file, name="l0f93ro5_1_1", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
sbtbackup: Failed to process backup file.
RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECREATE
OR another errorstack
RMAN-12004: unhandled exception during command execution on channel disk13
RMAN-10035: exception raised in RPC: ORA-19502: write error on file "/db200_backup/archive_log03/EDPP_ARCH0_21329_1_492222998",
blockno 612353 (blocksize=1024) ORA-27072: skgfdisp: I/O error
HP-UX Error: 2: No such file or directory Additional information: 612353
RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECREATE OR another errorstack
RMAN-12004: unhandled exception during command execution on channel ch00
RMAN-10035: exception raised in RPC: ORA-19599: block number 691 is corrupt in controlfile C:\ORACLE\ORA90\DATABASE\SNCFSUMMITDB.ORA RMAN-10031: ORA-19583 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECREATE
OR another errorstack
Have managed to create a job to backup my db, but I can't restore. I get the following:
RMAN-03002: failure during compilation of command RMAN-03013: command type: restore
RMAN-03006: non-retryable error occurred during execution of command: IRESTORE RMAN-07004: unhandled exception during command execution on channel BackupTest
RMAN-10035: exception raised in RPC: ORA-19573: cannot obtain exclusive enqueue for datafile 1 RMAN-10031: ORA-19583 occurred during call to DBMS_BACKUP_RESTORE.RESTOREBACKUPPIECE
Seems to relate to corrupt or missing Oracle files.
Note 1:
Subject: OERR: RMAN-12004 unhandled exception during command execution on channel %s Doc ID: Note:291388.1 Type: REFERENCE
Last Revision Date: 22-NOV-2004 Status: PUBLISHED
{ This note contains error information about an "RMAN"
error number. It may contain additional support notes as described in Note 22080.1 }
Error: RMAN-12004 (RMAN-12004)
Text: unhandled exception during command execution on channel %s ---Cause:
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
So, RMAN-12004 always means that you should investigate on the accompanying error messages.
Note 2:
Subject: RMAN-12004, RMAN-10035, ORA-27072 Errors With Incremental RMAN Backup Doc ID: Note:437444.1 Type: PROBLEM
Last Revision Date: 24-JUL-2007 Status: MODERATED In this Document
Symptoms Cause Solution
---This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.
Applies to:
Oracle Server - Enterprise Edition - Version: 10.1.0.5.0 This problem can occur on any platform.
Symptoms
Getting this error during the incremental backups with rman:
RMAN-00579: the following error occurred at 06/20/2007 04:12:30 RMAN-03015: error occurred in stored script inc_wed
RMAN-03007: retryable error occurred during execution of command: backup RMAN-12004: unhandled exception during command execution on channel ORA_DISK_1 RMAN-10035: exception raised in RPC: ORA-19502: write error on file
jsikni42_1_1, blockno 6924289 (blocksize=512) ORA-27072: skgfdisp: I/O error
Linux Error: 2: No such file or directory Additional information: 6924289
RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.
BACKUPPIECECREATE Cause
The filesystem involved was out of space.
Solution
Add space to the filesystem involved in your backup.
---ERR 7: ORA-27211
================
Q:
Continue to get ORA-27211 Failed to load media management library A:
had a remarkably similar experience a few months ago with Legato NetWorker and performed all of the steps
you listed with the same results. The problem turned out to be very simple. The SA installed the 64-bit version
of the Legato Networker client because it is a 64-bit server. However, we were running a 32-bit version of Oracle on it.
Installing the 32-bit client solved the problem.
A:
Cause: User-supplied SBT_LIBRARY or libobk.so could not be loaded. Call to dlopen for media library returned error.
See Additional information for error code.
Action: Retry the command with proper media library. Or re-install Media management module for Oracle.
A:
Exact Error Message
ORA-27211: Failed to load Media Management Library on HP-UX system Details:
Overview:
The Oracle return code ORA-27211 implies a failure to load a shared object library into process space.
Oracle Recovery Manager (RMAN) backups will fail with a message "ORA-27211: Failed to load Media Management Library"
if the SBT_LIBRARY keyword is defined and points to an incorrect library name. The SBT_LIBRARY keyword must be set
in the PARMS clause of the ALLOCATE CHANNEL statement in the RMAN script. This keyword is not valid with the SEND command
and is new to Oracle 9i. If this value is set, it overrides the default search path for the libobk library.
By default, SBT_LIBRARY is not set.
Possible quick solution:
Check permissions on libraries like listed in the PARMS of the allocate channel statement.
Other Troubleshooting:
If an ORA-27211 error is seen for an Oracle RMAN backup, it is necessary to review the Oracle RMAN script and verify if SBT_LIBRARY is either not set or is set correctly. If set, the filename should be libobk.sl for HP-UX 10, 11.00 and 11.11,
but libobk.so for HP-UX 11.23 (ia64) clients.
Example of an invalid entry for HP-UX 11.23 (ia64) clients:
PARMS='SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.sl' Example of a correct entry for HP-UX 11.23 (ia64) clients:
PARMS='SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so' Master Server Log Files: n/a
Media Server Log Files: n/a Client Log Files:
The RMAN log file on the client will show the following error message:
RMAN-00571: ===========================================
RMAN-00569: ======= ERROR MESSAGE STACK FOLLOWS =======
RMAN-00571: ===========================================
RMAN-03009: failure of allocate command on ch00 channel at 05/21/2005 16:39:17 ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library Additional information: 25
Resolution:
The Oracle return code ORA-27211 implies a failure to load a shared object library into process space.
Oracle RMAN backups will fail with a message "ORA-27211: Failed to load Media Management Library"
if the SBT_LIBRARY keyword
is defined and points to an incorrect library name.
To manually set the SBT_LIBRARY path, follow the steps described below:
1. Modify the RMAN ALLOCATE CHANNEL statement in the backup script to reference the HP-UX 11.23 library file directly:
PARMS='SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so'
Note: This setting would be added to each ALLOCATE CHANNEL statement. A restart of the Oracle instance is not needed for this change to take affect.
2. Run a test backup or wait for the next scheduled backup of the Oracle database
ERR8: More on DBMS_BACKUP_RESTORE:
==================================
Note 1:
The dbms_backup_restore package is used as a PL/SQL command-line interface for replacing native RMAN commands, and it has very little documentation.
The Oracle docs note how to install and configure the dbms_backup_restore package:
“The DBMS_BACKUP_RESTORE package is an internal package created by the dbmsbkrs.sql and prvtbkrs.plb scripts.
This package, along with the target database version of DBMS_RCVMAN, is automatically installed in every Oracle database when the catproc.sql script is run. This package interfaces with the Oracle database server and the operating system to provide the I/O services for backup and restore operations as directed by RMAN.”
The docs also note that “The DBMS_BACKUP_RESTORE package has a PL/SQL procedure to normalize filenames on Windows NT platforms.”
Oracle DBA John Parker gives this example of dbms_backup_restore to recover a controlfile:
declare
Here are some other examples of using dbms_backup_restore:
DECLARE
devtype varchar2(256);
done boolean;
BEGIN
devtype := dbms_backup_restore.DeviceAllocate (type => '',ident => 'FUN');
dbms_backup_restore.RestoreSetDatafile;
dbms_backup_restore.RestoreDatafileTo(dfnumber => 1,toname => 'D:\ORACLE_BASE\datafiles\SYSTEM01.DBF');
dbms_backup_restore.RestoreDatafileTo(dfnumber => 2,toname => 'D:\ORACLE_BASE\datafiles\UNDOTBS.DBF');
--dbms_backup_restore.RestoreDatafileTo(dfnumber => 3,toname => 'D:\ORACLE_BASE\datafiles\MYSPACE.DBF');
dbms_backup_restore.RestoreBackupPiece(done => done,handle => 'D:\ORACLE_BASE\RMAN_BACKUP\MYDB_DF_BCK05H2LLQP_1_1', params => null);
dbms_backup_restore.DeviceDeallocate;
devtype := dbms_backup_restore.DeviceAllocate (type => '',ident => 'FUN');
dbms_backup_restore.RestoreSetArchivedLog(destination=>'D:\ORACLE_BASE\achive\');
dbms_backup_restore.RestoreArchivedLog(thread=>1,sequence=>1);
dbms_backup_restore.RestoreArchivedLog(thread=>1,sequence=>2);
dbms_backup_restore.RestoreArchivedLog(thread=>1,sequence=>3);
dbms_backup_restore.RestoreBackupPiece(done => done,handle => 'D:\ORACLE_BASE\RMAN_BACKUP\MYDB_LOG_BCK0DH1JGND_1_1', params => null);
dbms_backup_restore.DeviceDeallocate;
devtype varchar2(256);
done boolean;
BEGIN
devtype := dbms_backup_restore.DeviceAllocate(type => '',ident => 'FUN');
dbms_backup_restore.RestoresetdataFile;
devtype := dbms_backup_restore.DeviceAllocate (type => '',ident => 'FUN');
dbms_backup_restore.RestoreSetDatafile;
dbms_backup_restore.RestoreDatafileTo(dfnumber => 1,toname => 'D:\ORACLE_BASE\datafiles\SYSTEM01.DBF');
dbms_backup_restore.RestoreDatafileTo(dfnumber => 2,toname => 'D:\ORACLE_BASE\datafiles\UNDOTBS.DBF');
--dbms_backup_restore.RestoreDatafileTo(dfnumber => 3,toname => 'D:\ORACLE_BASE\datafiles\MYSPACE.DBF');
dbms_backup_restore.RestoreBackupPiece(done => done,handle => 'D:\ORACLE_BASE\RMAN_BACKUP\MYDB_DF_BCK05H2LLQP_1_1', params => null);
dbms_backup_restore.DeviceDeallocate;
devtype := dbms_backup_restore.DeviceAllocate (type => '',ident => 'FUN');
dbms_backup_restore.RestoreSetArchivedLog(destination=>'D:\ORACLE_BASE\achive\');
dbms_backup_restore.RestoreArchivedLog(thread=>1,sequence=>1);
dbms_backup_restore.RestoreArchivedLog(thread=>1,sequence=>2);
dbms_backup_restore.RestoreArchivedLog(thread=>1,sequence=>3);
dbms_backup_restore.RestoreBackupPiece(done => done,handle => 'D:\ORACLE_BASE\RMAN_BACKUP\MYDB_LOG_BCK0DH1JGND_1_1', params => null);
dbms_backup_restore.DeviceDeallocate;
END;
/
ERR 9: RMAN-00554 initialization of internal recovery manager package failed:
=============================================================================
connected to target database: PLAYROCA (DBID=575215626)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04004: error from recovery catalog database: ORA-03135: connection lost contact keys:
RMAN-00554
RMAN-04004 ORA-03135 ORA-3136
>>>> In alertlog of the rman, we can find:
WARNING: inbound connection timed out (ORA-3136) Thu Mar 13 23:09:54 2008
>>>> In Net logs sqlnet.log we can find:
Warning: Errors detected in file /dbms/tdbaplay/ora10g/home/network/log/sqlnet.log > ***********************************************************************
> Fatal NI connect error 12170.
>
> VERSION INFORMATION:
> TNS for IBM/AIX RISC System/6000: Version 10.2.0.3.0 - Production
> TCP/IP NT Protocol Adapter for IBM/AIX RISC System/6000: Version 10.2.0.3.0 - Production
> Oracle Bequeath NT Protocol Adapter for IBM/AIX RISC System/6000: Version 10.2.0.3.0 - Production > Time: 18-MAR-2008 23:01:43
> Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=57.232.4.123)(PORT=35844))
Note 1:
RMAN-00554: initialization of internal recovery manager package failed
Is a general error code. You must turn your attention the the codes underneath this one.
For example:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed RMAN-06003: ORACLE error from target database:
ORA-00210: cannot open the specified control file
ORA-00202: control file: '/devel/dev02/dev10g/standbyctl.ctl'
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed RMAN-04005: error from target database: ORA-01017: invalid
username/password;
ERR: RMAN-20242: specification does not match any archive log in the recovery catalog
===================================================================================
Starting backup at 17-MAY-08 released channel: t1 released channel: t2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 05/17/2008 23:30:13 RMAN-06004: ORACLE error from recovery catalog database:
RMAN-20242: specification does not match any archive log in the recovery catalog
Note 1:
Oracle Error :: RMAN-20242
specification does not match any archivelog in the recovery catalog Cause
No archive logs in the specified archive log range could be found.
Action
Check the archive log specifier.
Note 2:
Some of the common RMAN errors are:
RMAN-20242: Specification does not match any archivelog in the recovery catalog.
Add to RMAN script: sql 'alter system archive log current';
Note 3:
Q:
RMAN-20242: specification does not match any archive log in the recovery ca Posted: Feb 12, 2008 7:52 AM Reply
A couple of archive log files were deleted from the OS. They still show up in the list of archive logs in Enterprise Manager.
I want to fix this because now whenever I try to run a crosscheck command, I get the message:
RMAN-20242: specification does not match any archive log in the recovery catalog I also tried to uncatalog those files, but got the same message.
Any suggestions on what to do?
Thanks!
A:
hi,
from rman run the command list expired archivelog;
if ther archives are in this list they will show, then i think you should do a crosscheck archivelog all;
then you should be able to delete them.
regards
Note 4:
The RMAN error number would be helpful, but this is a common problem - RMAN-20242 - and is addressed in detail in MetaLink notes.
Either the name specification (the one you entered) is wrong, or you could be using mismatched versions between RMAN and the database (don't know since you didn't provide any version details).
Note 5:
Q:
Hi there!
We are having problems with an Oracle backup. The compiling of the backup command fails with the error message: RMAN-20242: specification does not match any archivelog in the recovery catalog
But RMAN is only supposed to backup any archived logs that are there and then insert them in the catalog...
Did anybody experience anything similar?
This is 8.1.7 on HP-UX with Legato Networker
This is 8.1.7 on HP-UX with Legato Networker