Error 6 is a generic DB backup error which cause the DB jobs to fail. To further troubleshoot this we have to first look in to the RMAN log and see what its saying , I mean find out the error. If your RMAN log showing the same as below and your Oracle version is V10203. Then follow the troubleshooting steps below to fix this.
RMAN Log:-
Script
/opt/rman_script/DBold_oracle_full.sh
==== started on Tue May 28
14:59:30 SGT 2013 ====
RMAN: /OraBase/V10203/bin/rman
ORACLE_SID: DBold
ORACLE_USER: oracle
ORACLE_HOME: /OraBase/V10203
NB_ORA_FULL: 1
NB_ORA_INCR: 0
NB_ORA_CINC: 0
NB_ORA_SERV: DBMSTR
NB_ORA_POLICY: DBold_oracle_daily
Full backup requested
Sun Microsystems Inc.
SunOS 5.10
Generic
January 2005
You have new mail.
RMAN> 2> 3> 4> 5>
6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17>
18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28>
29> 30> 31> 32> 33> RMAN> ed.
connected to target database: DBold (DBID=990954548)
connected to recovery catalog
database
RMAN> 2> 3> 4> 5>
6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17>
18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28>
29> 30> 31> 32> 33>
allocated channel: ch00
channel ch00: sid=136
devtype=SBT_TAPE
channel ch00: VERITAS NetBackup
for Oracle - Release 6.0 (2007070504)
sent command to channel: ch00
Starting backup at 28-MAY-13
released channel: ch00
RMAN-00571:
===========================================================
RMAN-00569: =============== ERROR
MESSAGE STACK FOLLOWS ===============
RMAN-00571:
===========================================================
RMAN-03002: failure of backup
command at 05/28/2013 14:59:36
RMAN-03014: implicit resync of
recovery catalog failed
RMAN-06004: ORACLE error from
recovery catalog database: RMAN-20035: invalid high recid
RMAN>
Recovery Manager complete.
Script
/opt/rman_script/DBold_oracle_full.sh
==== ended in error on Tue May 28
14:59:36 SGT 2013 ====
Steps to Troubleshoot:-
1. Backup the existing user using Oracle exp.
exp userid=Dbusr/Dbusr file=DBOld_catalog.dmp
2. Backup the dump file using NetBackup, set to permanent retention.
3. Disable login for the original user.
sqlplus ‘/ as sysdba’
alter user DBusr account disable;
4. Create a new user on the database, eg rmanuser
To create a New User :-
1. Set up an Oracle database (with the user datafiles and listener).
2. Create a tablespace for the RMAN catalog (modify the path and instance name of the
RMAN catalog database where required):
SQL> create tablespace RMAN_TAB datafile
'D:\Oracle\Oradata\RCATP\TAB01\RMAN_TAB01.dbf' size 300m;
Tablespace created.
SQL>
3. Create the RMAN user as a schema owner for the RMAN tablespace.
SQL> create user rmanuser identified by rmanuser default
tablespace RMAN_TAB temporary tablespace TEMP;
User created.
SQL>
4. Grant unlimited quota to the RMAN user on the RMAN tablespace.
SQL> alter user rmanuser quota unlimited on RMAN_TAB;
User altered.
SQL>
5. Grant the recovery_catalog_owner permission.
SQL> grant recovery_catalog_owner to rmanuser;
Grant succeeded.
SQL>
6. Create the RMAN objects and schema.
D:\Oracle\Product\11.2.0\BIN>rman catalog rmanuser/rmanuser@rcatp
Recovery Manager: Release 11.2.0.1.0 - Production on Thu Jan 27
17:05:14 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All
rights reserved.
connected to recovery catalog database
RMAN> create catalog;
recovery catalog created
RMAN>
5. Register the target database to the catalog.
On DBOld database server:
su - oracle
DBOld
rman target / catalog DBNWusr/DBNWusr@(rman catalog instance)
register database;
To register a database
Connect into RMAN.
D:\Oracle\Product\11.2.0\BIN>rman target / catalog
rmanuser/rmanuser@rcatp
Recovery Manager: Release 11.2.0.1.0 - Production on Thu Jan 27
17:10:17 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All
rights reserved.
connected to target database: ORADB1P (DBID=2937678513)
connected to recovery catalog database
RMAN>
2. Register the target database with the catalog.
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
full resync complete
RMAN>
3. You can also list out the RMAN parameters.
.
RMAN> show all;
RMAN configuration parameters for database with db_unique_name
ORADB1P are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO
'%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO
BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; #
default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; #
default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT'
OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO
D:\ORACLE\PRODUCT\11.2.0\DATABASE\SNCFORADB1P.ORA'; # default
RMAN>
6. Update all RMAN backup scripts to use the new username and password.
7. Retry backup in NetBackup.
No comments:
Post a Comment