Link to home
Start Free TrialLog in
Avatar of mlin125
mlin125

asked on

RMAN-03007 ORA-19502

The rman & veritas has been working until July 5 and stoped running.  I tried to schedule and run the backup.sh from Veritas scheduler and got the following error in my log file.


RMAN-06005: connected to target database: ATI (DBID=3600115557)

RMAN-06008: connected to recovery catalog database

RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: t1
RMAN-08500: channel t1: sid=63 devtype=SBT_TAPE
RMAN-08526: channel t1: VERITAS NetBackup for Oracle8 - Release 3.2GA

RMAN-03022: compiling command: backup
RMAN-03025: performing implicit partial resync of recovery catalog
RMAN-03023: executing command: partial resync
RMAN-08003: starting partial resync of recovery catalog
RMAN-08005: partial resync complete
RMAN-03023: executing command: backup
RMAN-08008: channel t1: starting incremental level 0 datafile backupset
RMAN-08502: set_count=7308 set_stamp=595555763 creation_time=12-JUL-06
RMAN-08010: channel t1: specifying datafile(s) in backupset
RMAN-08522: input datafile fno=00006 name=/u04/oradata/ATI/indx01.dbf
RMAN-08522: input datafile fno=00005 name=/u02/oradata/ATI/data01.dbf
RMAN-08522: input datafile fno=00002 name=/u02/oradata/ATI/tools01.dbf
RMAN-08522: input datafile fno=00008 name=/u03/oradata/ATI/data02.dbf
RMAN-08522: input datafile fno=00003 name=/u03/oradata/ATI/rbs01.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 t1
RMAN-10035: exception raised in RPC: ORA-19502: write error on file "bk_7308_1_595555763",
 blockno 21186433 (blocksize=512)
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: sbtwrite2: sbtwrite2() failed.
RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECREATE

Recovery Manager complete.

Wed Jul 12 01:12:18 PDT 2006 ----------------End of Script------------------



================================================================================


Some said because the archive log should backup first before db backup and that was why it fails.  But when we try to run archive backup from rman and got the error as the following.

RMAN-08504: input archivelog thread=1 sequence=35182 recid=70138 stamp=595396307
RMAN-08504: input archivelog thread=1 sequence=35183 recid=70140 stamp=595399747
RMAN-08504: input archivelog thread=1 sequence=35184 recid=70142 stamp=595402574
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 t1
RMAN-10035: exception raised in RPC: ORA-19502: write error on file "al_7313_1_595597857", blockno 580481 (blocksize=512)
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: sbtwrite2: sbtwrite2() failed.
RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECREATE

Recovery Manager complete.

Wed Jul 12 11:58:13 PDT 2006 ----------------End of Script------------------


===========================================================

Any help appreciate~


Avatar of MikeOM_DBA
MikeOM_DBA
Flag of United States of America image



RMAN will compute the space needed for a COPY backup regardless of the backup type and if there is no space on disk it will exit with the above error.



Ooops, that is when writing to DISK and there is no space.

When writong to tape, this error is returned from the media management software which is linked with Oracle and usually requires contacting the media management vendor.


Avatar of mlin125
mlin125

ASKER

archive backup from rman works now but still getting the error for db backup~~ dont think its the tape space issue~~ because archive logs were backup to the same tape.

Any suggections ~ ?
ASKER CERTIFIED SOLUTION
Avatar of MikeOM_DBA
MikeOM_DBA
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of mlin125

ASKER

Thank you~ We got it resoved already~ but thanks for your reply!