-- RMAN is hung or it is very slow
-- Clearing RMAN repository
-- Troubleshoot the issue
-- Troubleshoot RMAN-06214 error
RMAN>DELETE FORCE NOPROMPT OBSOLETE DEVICE TYPE DISK;
If RMAN-06214 still occurs, then try
RMAN>CROSSCHECK COPY OF CONTROLFILE;
allocate channel for maintenance type sbt; -- as per your configuration set.
or
allocate channel for maintenance type disk;
rman> DELETE FORCE NOPROMPT OBSOLETE DEVICE TYPE SBT;
or
DELETE FORCE NOPROMPT OBSOLETE DEVICE TYPE DISK;
if not,
1) Cancel any Delete obsolete command sessions
2) RMAN>CROSSCHECK COPY OF CONTROLFILE;
3) Start the delete obsolete command with debug enabled to check whether RMAN is hung or it is very slow :
rman target / debug trace=debug1.trc log=rman1.log
RMAN> { your commands }
Upload to oracle, the debug1.trc and rman1.log for review.
Also upload the output of the below command :
RMAN> show all;
Note: Analyze the trace file or upload to Oracle support as a proactive measure.
Sample investigation :
~~~~~~~~~~~~~~~~~~~
--- When issue faced
--- As per my configuration setting
$export NLS_DATE_FORMAT="DD-MON-RRRR HH24:MI:SS"
$rman target / debug all trace=debug.trc log=debug.log
RMAN>set echo on;
RMAN>show all;
RMAN>CONFIGURE CHANNEL DEVICE TYPE DISK clear;
RMAN>CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' clear;
RMAN>allocate channel for maintenance device type sbt parms 'SBT_LIBRARY=oracle.disksbt, ENV=(BACKUP_DIR=/tmp)';
RMAN>crosscheck backup completed before 'sysdate -2' device type 'SBT_TAPE';
RMAN>delete force noprompt expired backup;
RMAN>list backup;
Caution : To configure / de-configure in RMAN in production database is to be verified first. To change/ run any command in production database is with your risk.
-- Clearing RMAN repository
-- Troubleshoot the issue
-- Troubleshoot RMAN-06214 error
RMAN>DELETE FORCE NOPROMPT OBSOLETE DEVICE TYPE DISK;
If RMAN-06214 still occurs, then try
RMAN>CROSSCHECK COPY OF CONTROLFILE;
allocate channel for maintenance type sbt; -- as per your configuration set.
or
allocate channel for maintenance type disk;
rman> DELETE FORCE NOPROMPT OBSOLETE DEVICE TYPE SBT;
or
DELETE FORCE NOPROMPT OBSOLETE DEVICE TYPE DISK;
if not,
1) Cancel any Delete obsolete command sessions
2) RMAN>CROSSCHECK COPY OF CONTROLFILE;
3) Start the delete obsolete command with debug enabled to check whether RMAN is hung or it is very slow :
rman target / debug trace=debug1.trc log=rman1.log
RMAN> { your commands }
Upload to oracle, the debug1.trc and rman1.log for review.
Also upload the output of the below command :
RMAN> show all;
Note: Analyze the trace file or upload to Oracle support as a proactive measure.
Sample investigation :
~~~~~~~~~~~~~~~~~~~
--- When issue faced
--- As per my configuration setting
$export NLS_DATE_FORMAT="DD-MON-RRRR HH24:MI:SS"
$rman target / debug all trace=debug.trc log=debug.log
RMAN>set echo on;
RMAN>show all;
RMAN>CONFIGURE CHANNEL DEVICE TYPE DISK clear;
RMAN>CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' clear;
RMAN>allocate channel for maintenance device type sbt parms 'SBT_LIBRARY=oracle.disksbt, ENV=(BACKUP_DIR=/tmp)';
RMAN>crosscheck backup completed before 'sysdate -2' device type 'SBT_TAPE';
RMAN>delete force noprompt expired backup;
RMAN>list backup;
Caution : To configure / de-configure in RMAN in production database is to be verified first. To change/ run any command in production database is with your risk.
No comments:
Post a Comment