RMAN-00600 Error

From: Pete's <empete2000_at_yahoo.com>
Date: 16 Feb 2004 06:14:49 -0800
Message-ID: <6724a51f.0402160614.c3342cd@posting.google.com>

Backup Server:
Sun 280 Solaris 2.9
901 RMAN Catalog running on an 8.1.7 EE database Veritas Netbackup DataCenter 4.5 MP 3

Production Server:
  P660-6H1 AIX 4.3.3 ML09
  Primary Site for an HACMP Cluster and DataGuard   9.0.1.3 EE Database, 24x7.
  Veritas NB Oracle DB Extension

This system has been working flawlessly for the last 1.5 yrs, but, a couple weeks ago I received the following intermittent RMAN-00600 error backing up the primary site for Dataguard and HA: RMAN-00600: internal error, arguments [13014] [26] [] [] []

A trace file would get created but with virtually no text in it and would be a couple minutes after the failure. I opened a TAR w/ Oracle, gave them the trace, and they could not find anything in their docs regarding this error and said I was the only one encountering it. Before they soft closed it, it happened again with the same symptoms. It happened once again late last week, so, I my RMAN script, I turned debug on and turned tracing on in the tape channel. After turning it, two traces were produced. I sent those off to Oracle as well as the RMAN output. I'll post an example shortly. I re-opened the TAR, but so far support has no additional information to give me.

RMAN> connect target sys/XXXXXXX_at_PROD1

2> connect catalog rman901/XXXXXXX_at_PRODCAT1
3>   sql 'alter system archive log current';
4> debug on ;
5> run {
6> # Hot database level 1 cumulative incremental backup
7> allocate channel t1 type 'SBT_TAPE' trace=1
8>   parms="ENV=(NB_ORA_CLASS=emsdb1_PROD1,

NB_ORA_SCHED=dailyincremental)";
9> allocate channel t2 type 'SBT_TAPE' trace=1 10> parms="ENV=(NB_ORA_CLASS=emsdb1_PROD1, NB_ORA_SCHED=dailyincremental)";

11> backup current controlfile for standby;
12> backup
13>   incremental level 1
14>   cumulative
15>   skip offline
16>   skip readonly
17>   skip inaccessible
18>   tag hot_PROD1_bk_level1_cm
19>   filesperset 20
20>   format 'bk_PROD1_hot_cm_lv1_%U_%t_%s'
21>   (database);
22> }
23> debug off ;
24> resync catalog;
25>

I checked Veritas' logs and it looks as though the control file gets backed up, then goes on to start the db backup and then fails.

Does anyone know of any other tracing I could do? Would sql 'alter session set events '10046.......'' trace help determine this problem?

TIA,
Pete's Received on Mon Feb 16 2004 - 08:14:49 CST