Links
• Home
• Oracle DBA Forum
Frequent Oracle Errors
•TNS:could not resolve the connect identifier specified
•Backtrace message unwound by exceptions
•invalid identifier
•PL/SQL compilation error
•internal error
•missing expression
•table or view does not exist
•end-of-file on communication channel
•TNS:listener unknown in connect descriptor
•insufficient privileges
•PL/SQL: numeric or value error string
•TNS:protocol adapter error
•ORACLE not available
•target host or object does not exist
•invalid number
•unable to allocate string bytes of shared memory
•resource busy and acquire with NOWAIT specified
•error occurred at recursive SQL level string
•ORACLE initialization or shutdown in progress
•archiver error. Connect internal only, until freed
•snapshot too old
•unable to extend temp segment by string in tablespace
•Credential retrieval failed
•missing or invalid option
•invalid username/password; logon denied
•unable to create INITIAL extent for segment
•out of process memory when trying to allocate string bytes
•shared memory realm does not exist
•cannot insert NULL
•TNS:unable to connect to destination
•remote database not found'>ora-02019
•exception encountered: core dump
•inconsistent datatypes
•no data found
•TNS:operation timed out
•PL/SQL: could not find program
•existing state of packages has been discarded
•maximum number of processes exceeded
•error signaled in parallel query server
•ORACLE instance terminated. Disconnection forced
•TNS:packet writer failure
•see ORA-12699
•missing right parenthesis
•name is already used by an existing object
•cannot identify/lock data file
•invalid file operation
•quoted string not properly terminated
RMAN error

RMAN error

2004-11-19       - By Black, Alain

Reply:     1     2     3     4     5  

Are you using a logical name for the server or the physical name?

Doc ID 99610.1 from metalink.oracle.com
Excerpt from the note:
Solution Description
-- ---- ---- ---- --
You need to change the Backup/Recovery configuration to use the physical
node name instead of the logical node name.

Explanation
-- ---- ---
In a Unix cluster environment there are two distinct entities that
identify  the individual servers, one being a logical host name and the
other being  the actual physical name of the node. When you change the
Backup/Recovery  configuration to use the physical node name the backup
will perform  successfully directly to tape.

That or it's a vendor specific error and we'd need to know what 3rd
party software you're using for the Media Management.

-Alain.

-- --Original Message-- --
From: Andrej Vavro [mailto:andrej.vavro@(protected)]
Sent: Friday, November 19, 2004 12:24 AM
To: DELE UDUMA
Cc: suse-oracle@(protected)
Subject: RE: [suse-oracle] rman error

Hi,

I have the same issue with DP5.0 W2000 cell manager and 8.1.7 on SLES. I
am
interested in it. Have you solved it already?

Andrej

-- --Original Message-- --
From: DELE UDUMA [mailto:DUDUMA@(protected)]
Sent: Thursday, November 11, 2004 5:57 PM
To: suse-oracle@(protected)
Subject: [suse-oracle] rman error


I am trying to use rman to backup to tape, I have this error.
Can somebody help?

RMAN> run
2> {
3> allocate channel c1 type 'SBT_TAPE'
PARMS='ENV=(NSR_SERVER=tape_srv,NSR_GROUP
=oracle_tapes)';
4> backup
5> (database filesperset=4);}

RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: c1
RMAN-08500: channel c1: sid devtype=SBT_TAPE
RMAN-08526: channel c1: Data Protector A.05.10/209

RMAN-03022: compiling command: backup
RMAN-03023: executing command: backup
RMAN-08008: channel c1: starting full datafile backupset
RMAN-08502: set_count set_stampT1933714 creation_time-NOV-04
RMAN-08010: channel c1: specifying datafile(s) in backupset
RMAN-08522: input datafile fno013
name=/oradata2/mbcuat2/datambcuat2_bmrs02.d
bf
RMAN-08522: input datafile fno001
name=/oradata/mbcuat2/mbcuat2_syst01.dbf
RMAN-08011: including current controlfile in backupset
RMAN-08522: input datafile fno005
name=/oradata/mbcuat2/mbcuat2_usr01.dbf
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 c1
RMAN-10035: exception raised in RPC: ORA-19506 (See ORA-19506.ora-code.com): failed to create
sequential
file
, name="0ag4qg4i_1_1", parms=""
ORA-27028 (See ORA-27028.ora-code.com): skgfqcre: sbtbackup returned error
ORA-19511 (See ORA-19511.ora-code.com): Vendor specific error: OB2_StartObjectBackup() failed ERR(-2)
RMAN-10031: ORA-19624 (See ORA-19624.ora-code.com) occurred during call to
DBMS_BACKUP_RESTORE.BACKUPPIECECRE
ATE

RMAN>



--
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting


--
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting