Home » RDBMS Server » Backup & Recovery » ORA-19511: Error received from media manager layer, error text:
ORA-19511: Error received from media manager layer, error text: [message #238537] Fri, 18 May 2007 08:24 Go to next message
msethi
Messages: 1
Registered: May 2007
Junior Member
Hi I am getting this error message during RMAN backup and the database does not come up after this, it has to brought up manually.

Any help would be appreciated.

Thank you
Malini

This is the errors that were found in the backup:

Script /export/home/oracle/dba/backup/scripts/tsie_rman_cold_backup.sh
==== started on Fri May 18 02:00:06 EDT 2007 ====


RMAN: /devdata2/oradata/app/oracle/product/920/bin/rman
ORACLE_SID: tsie
ORACLE_USER: oracle
ORACLE_HOME: /devdata2/oradata/app/oracle/product/920

NB_ORA_FULL:
NB_ORA_INCR:
NB_ORA_CINC:
NB_ORA_SERV:
NB_ORA_POLICY:

Default - Full backup requested

Recovery Manager: Release 9.2.0.6.0 - 64bit Production

Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.

connected to target database: TSIE (DBID=467939031)

RMAN> RMAN>
connected to recovery catalog database

RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27> RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27>
starting full resync of recovery catalog
full resync complete
Oracle instance shut down

connected to target database (not started)
Oracle instance started
database mounted
database opened

Total System Global Area 2149028960 bytes

Fixed Size 734304 bytes
Variable Size 805306368 bytes
Database Buffers 1342177280 bytes
Redo Buffers 811008 bytes

database closed
database dismounted
Oracle instance shut down

connected to target database (not started)
Oracle instance started
database mounted

Total System Global Area 2149028960 bytes

Fixed Size 734304 bytes
Variable Size 805306368 bytes
Database Buffers 1342177280 bytes
Redo Buffers 811008 bytes

allocated channel: ch01
channel ch01: sid=12 devtype=SBT_TAPE
channel ch01: VERITAS NetBackup for Oracle - Release 6.0 (2006031019)

allocated channel: ch02
channel ch02: sid=13 devtype=SBT_TAPE
channel ch02: VERITAS NetBackup for Oracle - Release 6.0 (2006031019)

allocated channel: ch03
channel ch03: sid=14 devtype=SBT_TAPE
channel ch03: VERITAS NetBackup for Oracle - Release 6.0 (2006031019)

allocated channel: ch04
channel ch04: sid=15 devtype=SBT_TAPE
channel ch04: VERITAS NetBackup for Oracle - Release 6.0 (2006031019)

allocated channel: ch05
channel ch05: sid=16 devtype=SBT_TAPE
channel ch05: VERITAS NetBackup for Oracle - Release 6.0 (2006031019)

sent command to channel: ch01
sent command to channel: ch02
sent command to channel: ch03
sent command to channel: ch04
sent command to channel: ch05

Starting backup at 18-MAY-07
channel ch01: starting incremental level 0 datafile backupset
channel ch01: specifying datafile(s) in backupset
input datafile fno=00012 name=/devdata1/oradata/oradata/tsie/stagerdb_01.dbf
input datafile fno=00004 name=/devdata1/oradata/tsie/dbf/npdrs_index01.dbf
input datafile fno=00018 name=/devdata1/oradata/tsie/dbf/tool01.dbf
input datafile fno=00025 name=/devdata1/oradata/tsie/dbf/METRICS_INDEX.dbf
input datafile fno=00031 name=/devdata1/oradata/tsie/admin/streams_tbs.dbf
input datafile fno=00032 name=/devdata1/oradata/tsie/admin/logmnrts.dbf
input datafile fno=00024 name=/devdata1/oradata/tsie/dbf/METRICS_DATA.dbf
input datafile fno=00014 name=/devdata2/oradata/oradata/tsie/stagerdb_03.dbf
channel ch01: starting piece 1 at 18-MAY-07
channel ch02: starting incremental level 0 datafile backupset
channel ch02: specifying datafile(s) in backupset
input datafile fno=00016 name=/devdata1/oradata/oradata/tsie/stagerdb_05.dbf
input datafile fno=00015 name=/devdata2/oradata/oradata/tsie/stagerdb_04.dbf
input datafile fno=00029 name=/devdata2/oradata/tsie/dbf/HTMLDB1.dbf
input datafile fno=00007 name=/devdata2/oradata/oradata/tsie/siebeldb2_01.dbf
input datafile fno=00030 name=/devdata2/oradata/tsie/dbf/FLOW_1.dbf
input datafile fno=00028 name=/devdata2/oradata/oradata/tsie/odm01.dbf
input datafile fno=00026 name=/export/home/oracle/dba/bi/data/cs_olap_01.dbf
input datafile fno=00023 name=/devdata1/oradata/oradata/tsie/stagerdb_06.dbf
channel ch02: starting piece 1 at 18-MAY-07
channel ch03: starting incremental level 0 datafile backupset
channel ch03: specifying datafile(s) in backupset
input datafile fno=00034 name=/devdata1/oradata/oradata/tsie/stagerdb_07.dbf
input datafile fno=00003 name=/devdata1/oradata/tsie/dbf/npdrs_data01.dbf
input datafile fno=00009 name=/devdata2/oradata/oradata/tsie/siebeldbx_02.dbf
input datafile fno=00021 name=/devdata2/oradata/oradata/tsie/siebeldbx_04.dbf
channel ch03: starting piece 1 at 18-MAY-07
channel ch04: starting incremental level 0 datafile backupset
channel ch04: specifying datafile(s) in backupset
channel ch05: starting incremental level 0 datafile backupset
channel ch05: specifying datafile(s) in backupset
input datafile fno=00035 name=/devdata1/oradata/oradata/tsie/stagerdb_08.dbf
input datafile fno=00005 name=/devdata1/oradata/tsie/dbf/siebeldb01.dbf
input datafile fno=00022 name=/devdata2/oradata/tsie/dbf/undotbs02.dbf
input datafile fno=00033 name=/devdata2/oradata/oradata/tsie/XDB1.dbf
input datafile fno=00027 name=/devdata2/oradata/oradata/tsie/example01.dbf
input datafile fno=00002 name=/devdata1/oradata/tsie/dbf/undotbs01.dbf
input datafile fno=00008 name=/devdata1/oradata/oradata/tsie/siebeldbx_01.dbf
input datafile fno=00010 name=/devdata1/oradata/oradata/tsie/siebeldbx_03.dbf
channel ch05: starting piece 1 at 18-MAY-07
including current SPFILE in backupset
including current controlfile in backupset
input datafile fno=00013 name=/devdata1/oradata/oradata/tsie/stagerdb_02.dbf
input datafile fno=00001 name=/devdata1/oradata/tsie/dbf/system01.dbf
input datafile fno=00019 name=/devdata2/oradata/tsie/dbf/user01.dbf
input datafile fno=00006 name=/devdata2/oradata/tsie/dbf/siebeldb02.dbf
input datafile fno=00020 name=/devdata2/oradata/tsie/dbf/webapp01.dbf
input datafile fno=00011 name=/devdata2/oradata/oradata/tsie/siebeldbx2_01.dbf
channel ch04: starting piece 1 at 18-MAY-07
channel ch03: finished piece 1 at 18-MAY-07
piece handle=bk_7007_1_622864852 comment=API Version 2.0,MMS Version 5.0.0.0
channel ch03: backup set complete, elapsed time: 00:40:35
channel ch03: starting incremental level 0 datafile backupset
channel ch03: specifying datafile(s) in backupset
input datafile fno=00017 name=/devdata1/oradata/oradata/tsie/stagerdbx_01.dbf
channel ch03: starting piece 1 at 18-MAY-07
released channel: ch01
released channel: ch02
released channel: ch03
released channel: ch04
released channel: ch05
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ch05 channel at 05/18/2007 02:41:28
ORA-19502: write error on file "bk_7009_1_622864852", blockno 11493889 (blocksize=512)
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: Error received from media manager layer, error text:
VxBSASendData: Failed with error:
Server Status: Communication with the server has not been iniatated or the server status has not been retrieved from the server.

RMAN> RMAN>

Recovery Manager complete.

Script /export/home/oracle/dba/backup/scripts/tsie_rman_cold_backup.sh
==== ended in error on Fri May 18 02:42:11 EDT 2007 ====

[Updated on: Fri, 18 May 2007 08:24]

Report message to a moderator

Re: ORA-19511: Error received from media manager layer, error text: [message #239121 is a reply to message #238537] Mon, 21 May 2007 09:16 Go to previous message
Frank Naude
Messages: 4581
Registered: April 1998
Senior Member
From http://mailman.eng.auburn.edu/pipermail/veritas-bu/2005-March/027371.html -
  • Check to ensure your Oracle machine is registered as a server within NetBackup.
  • Check if a normal (automatic) schedule exists within your Oracle policy in addition to the application backup schedule.
Previous Topic: Loss of Controlfile
Next Topic: Plese suggest the solution for following test cases of recovery
Goto Forum:
  


Current Time: Tue Nov 26 21:44:39 CST 2024