Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: RMAN configure channel with multiple parameters
Dear Stephan,
sorry for the long post.
comments embedded
<snip>
> link is needed for the database you backup via RMAN (target)
> Link should be setup as Oracle Owner. Something like :
> lrwxrwxrwx 1 oracle dba 20 Jan 1 2004 libobk.so -> /usr/lib/libnwora.so
removed the old false link and set a new: lrwxrwxrwx 1 oracle oinstall 25 2004-09-07 09:39 libobk.so -> /tina/Lib/libtina_rman.so
again, did reconfigure:
RMAN> run {
CONFIGURE CHANNEL DEVICE TYPE 'sbt_tape'
parms="ENV=(TINA_HOME=/tina,
TINA_SERVICE_NAME=tina, TINA_RMAN_CATALOG=catalog, TINA_RMAN_FOLDER=backupfolder,
<snip of output>
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN> run {
2> allocate channel c1 type 'sbt_tape'; 3> release channel c1; 4> } RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: ===========================================================RMAN-03009: failure of allocate command on c1 channel at 09/07/2004 11:29:18 ORA-19554: error allocating device, device type: SBT_TAPE, device name: ORA-00447: fatal error in background process
in alert log I notice the same error message as seen yesterday: ORA-07445: exception encountered: core dump [strncpy()+33] [SIGSEGV] [Address not mapped to object] [0x0] [] []
I performed another test, allocated a channel manually without
SBT_LIBRARY and backuped 1 datafile:
RMAN> run {
allocate channel c1 type 'sbt_tape'
parms="ENV=(TINA_HOME=/tina,
TINA_SERVICE_NAME=tina, TINA_RMAN_CATALOG=catalog, TINA_RMAN_FOLDER=backupfolder,
allocated channel: c1
channel c1: sid=18 devtype=SBT_TAPE
channel c1: Time Navigator Media Management
Starting backup at 07-SEP-04
channel c1: starting full datafile backupset
channel c1: specifying datafile(s) in backupset
input datafile fno=00028 name=/u02/oracle/oradata/DBNAME/drsys01.dbf
channel c1: starting piece 1 at 07-SEP-04
channel c1: finished piece 1 at 07-SEP-04
piece handle=NULL comment=NONE
channel c1: backup set complete, elapsed time: 00:06:25
Finished backup at 07-SEP-04
Starting Control File and SPFILE Autobackup at 07-SEP-04 released channel: c1
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: ===========================================================RMAN-03002: failure of Control File and SPFILE Autobackup command at 09/07/2004 13:34:53
On the target DB there is a trace file:
<snip>
krbbcb: starting conversation, stamp=536246907, count=22
krbbcb: type=1, incremental=0, level=0, nochecksum=0
Got krbibdf()
krbbsbz: backup set logical blocksize = 8192
krbbbdf: added real file #28, name=/u02/oracle/oradata/DBNAME/drsys01.dbf
Got krbibsta()
Got krbisl()
set limit for device type: "SBT_TAPE", name: ""
device limit "duplex count for piece" set to 1
Got krbibpc()
krbbpc: thread_count = 2 : input_count2 = 1 krbbpc: thread 0xae6d574: bufsize = 1048576, bufcnt = 16, blks/buf = 128 krbbpc: 09/07/2004 13:28:27: backup piece 1 started, outfname=0mfvcujr_1_1krbcsi=0, krbcss=0, krbpfn=0, krbtra=0x1, krbpfl=0x10 krbdsd=0x0xae56268, krbbxp=0x0xae61a9c, krbrxp=0x(nil), krbnas=0 krbbsbct=0
krbb1de: Placing file 28 in directory, flags= 0
Directory block 1, count=1, size=76, offset=28
*** 2004-09-07 13:33:50.963
krbbtgb: end of file /u02/oracle/oradata/DBNAME/drsys01.dbf
*** 2004-09-07 13:34:46.051
krbbpc: 09/07/2004 13:34:46: backup piece 1 finished, handle=
elapsed time: 6:19
krbbpc: backup piece 1: logical blocks=159, header blocks=2 krbbpc: done with file: /u02/oracle/oradata/GUIDES/drsys01.dbf krbbcc: cleaning up conversation, context: 0xae61a9c<snip>
The mentioned file: outfname=0mfvcujr_1_1 exists on tape. The recovery catalog is not in sync. Do you think it is safe to issue a resync catalog?
Thanks in advance and have a nice day
Manuela Mueller
Received on Tue Sep 07 2004 - 09:31:11 CDT
![]() |
![]() |