rman bug?

From: lshang <lshang_at_nospam.interaccess.com>
Date: Wed, 10 Nov 1999 17:55:34 -0600
Message-ID: <s2k190trhsq46@corp.supernews.com>

Hello,

I created a recovery catalog on an oracle 8.0.5.1 database and used it to backup a oracle 8.0.5.0 database successfully. But I failed to backup another 8.0.5.0 database. Oracle support said there is a bug. I must upgrade to 8.0.5.1. My question is why it was ok for the first database and not good for the second one.

The error message is following:

RMAN> run {
set command id to "DBid";
allocate channel t1 type 'SBT_TAPE'
parms
'ENV=(NSR_SERVER=ditto.interaccess.com,NSR_DEBUG_FILE=/tmp/nsr_debug.log,N
SR_DATA_VOLUME_POOL=DB Prod)';
allocate channel t2 type 'SBT_TAPE'
parms
'ENV=(NSR_SERVER=ditto.interaccess.com,NSR_DEBUG_FILE=/tmp/nsr_debug2.log,
NSR_DATA_VOLUME_POOL=DB Prod)';
backup filesperset 2
(tablespace service format '%d.%s');
}
RMAN-03022: compiling command: set
RMAN-03023: executing command: set command id

RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-00569: ================error message stack follows================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-07001: could not open channel t1
RMAN-10008: could not create channel context
RMAN-10024: error setting up for rpc polling
RMAN-10006: error running sql statement: select distinct my.sid, sex.serial

from v$mystat my, x$ksusex sex where sex.sid = my.sid RMAN-10002: ORACLE error: ORA-01455: converting column overflows integer datatype

Thanks for any response. Received on Wed Nov 10 1999 - 17:55:34 CST