Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> RMAN error after changing UNDO tablespace
Hi there!
After changing the UNDO tablespace of my Oracle 9i database
from undotbs1 (with datafile undotbs01.dbf), because it has grown
too big, to a newly created tablespace undotbs2 (with datafile
undotbs2_1.dbf), the recovery manager RMAN fails backing
up the whole database with the following error messages:
RMAN> backup database;
Starting backup at 24-JUN-04
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00002 name=/OracleDB/testbas2/undotbs01.dbf input datafile fno=00001 name=/OracleDB/testbas2/system01.dbf input datafile fno=00012 name=/OracleDB/testbas2/AMSDB.dbf input datafile fno=00005 name=/OracleDB/testbas2/example01.dbf input datafile fno=00010 name=/OracleDB/testbas2/xdb01.dbf input datafile fno=00006 name=/OracleDB/testbas2/indx01.dbf input datafile fno=00009 name=/OracleDB/testbas2/users01.dbf input datafile fno=00011 name=/OracleDB/testbas2/NEGOISST1.dbf input datafile fno=00003 name=/OracleDB/testbas2/cwmlite01.dbf input datafile fno=00004 name=/OracleDB/testbas2/drsys01.dbf input datafile fno=00007 name=/OracleDB/testbas2/odm01.dbf input datafile fno=00013 name=/OracleDB/testbas2/UNDOTBS2_1.dbf input datafile fno=00008 name=/OracleDB/testbas2/tools01.dbfchannel ORA_DISK_1: starting piece 1 at 24-JUN-04
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: ===========================================================RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/24/2004 20:32:26
I looked up the error messages:
ORA-19502 write error on file "string", blockno string
(blocksize=string)
Cause: Write error on output file. Action: Check the file. ORA-27072 skgfdisp: I/O error Cause: READ/WRITE/READV/WRITEV system call returned error, additional information indicates starting block number of I/O. Action: Check errno.
The mount point where the backup is written to resides on another
host, but seems to work because a second instance running on
the database server can be backed up without any problems.
Does somebody has an idea what could be going wrong here?
Thanx in advance,
-Andreas.
Received on Thu Jun 24 2004 - 15:26:47 CDT
![]() |
![]() |