Re: RMAN problem

Are they all running from the same Oracle binaries, have some been patched and noth the failing one . I have seen exactly this message on 8.0.5 on solaris, basically when the serial# increases beyond a particular value rman stops working. To see if this is the case bounce your database and perform a backup immediatly.

Dave Leather
<u554107666_at_spawnkill.ip-mobilphone.net> wrote in message news:l.985777848.1849060058@[193.132.196.9]...
> Hi all,
>
> I am sending this note on behalf of our DBAs who are struggling to fix a
 recurring problem with RMAN. Set up is
>
> AIX 4.3.3
> Oracle 8.1.6
> TSM client 3.7.2
>
> There are 4 oracle Databases running on the system and
> all of them backup using RMAN. 3 of the four backup o.k
> everynight. All four database backups are started in the
> same way and use the same scripts.
>
> The error is as below
>
> Recovery Manager: Release 8.0.5.0.0 - Production
>
> RMAN-06005: connected to target database: IRBL
> RMAN-06008: connected to recovery catalog database
> RMAN-00569: ================error message stack follows==========
> RMAN-00554: initialization of internal recovery manager package failed
> RMAN-07001: could not open channel default
> 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
>
> I cannot see any errors in the TSM log related to the reoccuring failure.
>
> Thats about all the info I can give at the moment. If I've missed some
 vital info I should be able to get it from the DBAs
>
> ANy ideas or suggestions much appreciated
>
> Chris
>
>
>
>
> --
> Sent by rees_chris from my-deja piece of com
> This is a spam protected message. Please answer with reference header.
> Posted via http://www.usenet-replayer.com/cgi/content/new
Received on Thu Mar 29 2001 - 02:14:15 CST