RMAN Error - restore database validate

Question

Hi all
I am trying to validate a full database backup taken on tape using 'restore database validate' command but for some reason this command spits out multi-page long PL/SQL code (below truncated output). I have searched all over for a solution but can't seem to figure out the problem.
Any assistance will be appreciated.
RMAN> allocate channel for maintenance type SBT_TAPE parms 'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
2> crosscheck backup;
3> restore database validate;
4> release channel;
5> exit;
allocated channel: ORA_MAINT_SBT_TAPE_1
channel ORA_MAINT_SBT_TAPE_1: SID=82 device type=SBT_TAPE
channel ORA_MAINT_SBT_TAPE_1: Data Protection for Oracle: version 5.4.1.0
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=c-822607628-20101006-02 RECID=66 STAMP=731711718
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=DB_20101007_77_2dlpsj84_1_1.dbf RECID=67 STAMP=731794692
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=CF_20101008_116_3klpt5iv_1_1.ctl RECID=106 STAMP=731813472
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=c-822607628-20101008-01 RECID=107 STAMP=731813518
Crosschecked 42 objects
Starting restore at 08-OCT-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=110 device type=DISK
DBGANY: CMD type=IRESTORE cmdid=1 status=NOT STARTED
DBGANY: 1 STEPstepid=1 cmdid=1 status=NOT STARTED devtype=SBT_TAPE bs.stamp=731812991 step_size=0 Bytes
DBGANY: 1 TEXTNOD = -- rsdf_start
DBGANY: 2 TEXTNOD = declare
DBGANY: 3 TEXTNOD = /* restoreStatus */
DBGANY: 4 TEXTNOD = state binary_integer;
DBGANY: 5 TEXTNOD = pieces_done binary_integer;
DBGANY: 6 TEXTNOD = files binary_integer;
DBGANY: 7 TEXTNOD = datafiles boolean;
DBGANY: 8 TEXTNOD = incremental boolean;
DBGANY: 9 TEXTNOD = device boolean;
DBGANY: 10 TEXTNOD = /* restorebackuppiece */
DBGANY: 11 TEXTNOD = done boolean;
DBGANY: 12 TEXTNOD = currcf boolean;
DBGANY: 266 TEXTNOD = sys.dbms_backup_restore.restoreCancel(FALSE);
DBGANY: 267 TEXTNOD = exception
DBGANY: 268 TEXTNOD = when others then
DBGANY: 269 TEXTNOD = krmicd.writeMsg(1005,
DBGANY: 270 TEXTNOD = 'c. dbms_backup_restore.restoreCancel() failed');
DBGANY: 271 TEXTNOD = end;
DBGANY: 272 TEXTNOD = sys.dbms_backup_restore.setRmanStatusRowId(rsid=>0, rsts=>0);
DBGANY: 273 TEXTNOD = end;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-00600: internal error, arguments [6000] [] [] [] []

Answer 1

Hi Sybrand
So here's the deal:
1) 'backup validate database;' is run before RMAN backup to check for any logical or physical corruption in datafiles or archivelogs.
If the backup validation discovers corrupt blocks, then RMAN updates the V$DATABASE_BLOCK_CORRUPTION view with rows describing the corruptions.
2)
a- 'restore database validate;' is run after RMAN backup to check for any logical or physical corruption in backupsets.
b- 'validate backupset <n>;' is also run after RMAN backup to check for any logical or physical corruption in backupsets. The difference being you have to run it for each individual backupset as opposed to the previous option (2a), which loops through all existing backupsets.
I believe for now only option 2b is available for use in my case.
Cheers.