Re: rman problem

"Bud Socks" <bud_socks_at_gmx.de> wrote in
news:bbn44i$b9hjs$1_at_ID-2182.news.dfncis.de:

> hi there,
>
> we are about to use rman with a 3rd party backup solution on a
> w2k/ora817 system.
>
>
>
> To check the functionality of rman i have tried to backup a datafile -
> unfortunatelly
> rman terminates with errors :
>
>
>
>
> Recovery Manager: Release 8.1.7.4.1 - Production
>
> RMAN>
> RMAN-06005: connected to target database: tst (DBID=120816315)
> RMAN-06009: using target database controlfile instead of recovery
> catalog
>
> RMAN> 2> 3>
> RMAN-03022: compiling command: allocate
> RMAN-03023: executing command: allocate
> RMAN-08030: allocated channel: sbt
> RMAN-08500: channel sbt: sid=14 devtype=SBT_TAPE
> RMAN-08526: channel sbt: MMS Version 0.0.0.32
>
> RMAN-03022: compiling command: backup
> RMAN-03023: executing command: backup
> RMAN-08008: channel sbt: starting full datafile backupset
> RMAN-08502: set_count=174 set_stamp=495891991 creation_time=05-JUN-03
> RMAN-08010: channel sbt: specifying datafile(s) in backupset
> RMAN-08522: input datafile fno=00001
> name=H:\ORACLE\tst\SAPDATA1\SYSTEM_1\SYSTEM.DATA1
> RMAN-08011: including current controlfile in backupset
> RMAN-00571:
> ===========================================================
> RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
> =============== RMAN-00571:
> ===========================================================
> RMAN-03007: retryable error occurred during execution of command:
> backup RMAN-07004: unhandled exception during command execution on
> channel sbt RMAN-10035: exception raised in RPC: ORA-19506: failed to
> create sequential file, name="abcdefgh.1", parms=""
> ORA-27007: failed to open file
> ORA-19511: SBT error = 7009, errno = 0, sbtopen: can't connect with
> media manager
> RMAN-10031: ORA-19624 occurred during call to
> DBMS_BACKUP_RESTORE.BACKUPPIECECREATE
>
> RMAN>
> RMAN-08031: released channel: sbt
>
> Recovery Manager complete.
>
>
> what did i do wrong ?
>
>
> thanx
>
> Bud
>
>

Which media manager. Let me guess.... Backup Express (we see these errors frequently with that product even though everything is properly configured). If it were up to thet DBAs we would have sacked B/EX long ago and found something more reliable. Received on Thu Jun 05 2003 - 12:46:08 CDT