Hmmm...don't see any mention of a request for a PORAdata tape here, but
that's where you are trying to send your data. Does this client have its own
tape drive or does it send data across the network to a central server to a
tape drive used by many backups? Also do your other Oracle backups go to the
same pool?
Have you tried backing up a single, small tablespace without the control
file or archive logs?
Cheers
Mark
In daemon log of server, there are only this messages ... Starting of error
was 15/12/2004... Filesystem backups have no problem... Rman scripts including
archivelog backups also have this error...
****************************************************************************
Before failing ,there are these messages...
12/24/04 03:09:19 nsrd: Jukebox 'L700e' failed: All of the devices are in use
by nsrmmd
12/24/04 03:09:25 nsrd: express:index:atlas done saving to pool
'PBootstrapIndex' (BOOTSTRAP.002) 991 MB
12/24/04 03:09:30 nsrd: express:index:express saving to pool 'PBootstrapIndex'
(BOOTSTRAP.002)
12/24/04 03:09:53 nsrd: media notice: 9840b tape CBSLIVE_ARCHIVELOG_A.004 on
rd=bergama:/dev/rmt/5cbn is full
12/24/04 03:09:53 nsrd: media notice: 9840b tape CBSLIVE_ARCHIVELOG_A.004 used
46 GB of 20 GB capacity
12/24/04 03:09:58 nsrd: Jukebox 'L700e' failed: All of the devices are in use
by nsrmmd
12/24/04 03:10:07 nsrd: express:index:express done saving to pool
'PBootstrapIndex' (BOOTSTRAP.002) 202 MB
12/24/04 03:10:07 nsrd: express:bootstrap saving to pool 'PBootstrapIndex'
(BOOTSTRAP.002)
12/24/04 03:10:07 nsrd: media critical event: Waiting for 1 writable volumes
to backup pool 'KBTESTYTL' tape(s)
on express
12/24/04 03:10:15 nsrd: media info: verification of volume
"CBSLIVE_ARCHIVELOG_A.004", volid 231274920 succeede
d.
12/24/04 03:10:18 nsrd: write completion notice: Writing to volume
CBSLIVE_ARCHIVELOG_A.004 complete
12/24/04 03:10:19 nsrd: media info: suggest mounting CBSLIVE_ARCHIVELOG_A.006
(708655) on bergama for writing
to pool 'PKOCBANKARCHIVELOG'
12/24/04 03:10:19 nsrd: media waiting event: Waiting for 1 writable volumes to
backup pool 'PKOCBANKARCHIVELOG'
tape(s) on bergama
12/24/04 03:10:27 nsrd: media notice: setting (9840) block size to (256 KB)
12/24/04 03:10:27 nsrd: media notice: setting (LTO Ultrium-2) block size to
(256 KB)
12/24/04 03:10:33 nsrmmdbd: media db is saving its data. This may take a
while.
12/24/04 03:11:09 nsrmmdbd: media db is open for business.
12/24/04 03:11:09 nsrd: media info: suggest relabeling SUNsys.120 (707003) on
express for writing to pool 'PSU
Nsys'
12/24/04 03:11:12 nsrd: express:bootstrap done saving to pool
'PBootstrapIndex' (BOOTSTRAP.002) 21 MB
12/24/04 03:11:12 nsrd: rd=bergama:/dev/rmt/5cbn 7:Eject operation in progress
12/24/04 03:11:20 nsrd: nsrjb notice: nsrjb -j L700e -O8394 -l -R -M -J
express SUNsys.120
12/24/04 03:11:21 nsrd: media info: Suggest manually labeling a new writable
volume for pool 'PORAarch'
12/24/04 03:11:22 nsrd: media info: suggest mounting SUNsys.194 (708886) on
express for writing to pool 'PSUNs
ys'
12/24/04 03:11:26 nsrd: Jukebox 'L700e' failed: All of the devices are in use
by nsrmmd
12/24/04 03:11:27 nsrd: Jukebox 'L700e' failed: All of the devices are in use
by nsrmmd
12/24/04 03:11:27 nsrd: Jukebox 'L700e' failed: All of the devices are in use
by nsrmmd
12/24/04 03:11:30 nsrd: deactivating mmd #1705
12/24/04 03:11:30 nsrd: Calling mm_deactivate for mmd 1705 thats using device
/dev/rmt/4cbn with volume BOOTSTR
AP.002 on host null
12/24/04 03:11:30 nsrd: write completion notice: Writing to volume
BOOTSTRAP.002 complete
/RAPOR/files/file.vega: No such file or directory
/RAPOR/files/file.diners: No such file or directory
12/24/04 03:11:49 nsrd: savegroup alert: LIVEORA.T2.full completed, total 10
client(s), 0 Hostname(s) Unresolve
d, 1 Failed, 9 Succeeded. (efes Failed)
****************************************************************************
Daemon log of client; (At error time, there is no log...)
11/03/04 14:33:25 nsrexecd: Recvd signal to kill process group - pid=-18075,
sig=2
11/03/04 14:33:25 nsrexecd: Recvd signal to kill process group - pid=-27731,
sig=2
11/23/04 09:12:44 nsrexecd: Recvd signal to kill process group - pid=-9278,
sig=2
11/23/04 09:12:44 nsrexecd: Recvd signal to kill process group - pid=-22991,
sig=2
11/24/04 17:59:41 nsrexecd: Recvd signal to kill process group - pid=-14441,
sig=2
11/24/04 17:59:41 nsrexecd: Recvd signal to kill process group - pid=-14387,
sig=2
12/08/04 13:43:23 nsrexecd: Recvd signal to kill process group - pid=-25038,
sig=2
12/08/04 13:43:23 nsrexecd: Recvd signal to kill process group - pid=-9480,
sig=2
12/12/04 17:58:22 nsrexecd: Recvd signal to kill process group - pid=-11901,
sig=2
12/12/04 17:58:22 nsrexecd: Recvd signal to kill process group - pid=-11899,
sig=2
12/15/04 20:49:31 nsrexecd: Recvd signal to kill process group - pid=-11596,
sig=2
-----Original Message-----
From: Mark Bradshaw (BTOpenWorld) [mailto:notthehoople < at > btopenworld.com]
Sent: Friday, December 24, 2004 10:39 AM
To: Barıs¸ Yeter; NetWorker List
Subject: Re: [Networker] Strange legato - rman error
Hi,
What does the daemon.log on your NetWorker server say about this backup?
Does it see it at all? What about filesystem backups for this client - do
they work or do they fail as well. Finally is there anything in the
daemon.log on your failing client?
Cheers
Mark
At first, we thinked media error...
I labeled new 9840 media ... Only for this client, I took this error every
day for 10 days... But after new media, the same problem appeared... Also,
other clients have no problem which uses the same media & drive...
Drive:9840B
Library : L700e
Sbtio.log
***************
SBT-5604 12/24/04 01:47:46 nwora_asdf_save: asdf_ouput_section() failed
xdr=0x10343da00: bp=0x1047a9b28: send_len=262144: type=12800:
fhand=0x103439748: wrapper=0x0: directp=0x1034c4600
SBT-5604 12/24/04 01:47:46 nwora_asdf_save: asdf_ouput_section() failed
xdr=0x10343da00: bp=0x1047a9b28: send_len=262144: type=12800:
fhand=0x103439748: wrapper=0x0: directp=0x103504800
SBT-5604 12/24/04 01:47:46 nwora_asdf_save: asdf_ouput_section() failed
xdr=0x10343da00: bp=0x1047a9b28: send_len=262144: type=12800:
fhand=0x103439748: wrapper=0x0: directp=0x103544a00
SBT-5604 12/24/04 01:47:46 nwora_asdf_save: asdf_ouput_section() failed
xdr=0x10343da00: bp=0x1047a9b28: send_len=262144: type=12800:
fhand=0x103439748: wrapper=0x0: directp=0x103584e00
SBT-5604 12/24/04 01:47:46 nwora_session_close: savefile finish error
SBT-5604 12/24/04 01:49:51 nwora_remove: The saveset '566972758' was aborted.
SBT-5604 12/24/04 01:50:00 nwora_remove: The saveset '566972758' was aborted.
-----Original Message-----
From: Anuj Mediratta [mailto:anuj < at > ace-data.com]
Sent: Friday, December 24, 2004 9:29 AM
To: 'Legato NetWorker discussion'; Baržs¸ Yeter
Subject: RE: [Networker] Strange legato - rman error
Hi,
RMAN gives this error when Legato marks a media suspect or is unable to
write due to media or drive related issues - mostly dust etc.
You need to clean the drive and relabel the media, a better idea would be to
discard this media and use a fresh media.
Regards,
Anuj Mediratta
Phone: 9312634262
To know more about our services, do log on to
www.ace-data.com
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU] On
Behalf Of Baris Yeter
Sent: Friday, December 24, 2004 12:43 PM
To: NETWORKER < at > LISTMAIL.TEMPLE.EDU
Subject: [Networker] Strange legato - rman error
Hi,
I got an RMAN error... I opened TAR to oracle ...But, Oracle said that this
is Legato Error...Dou you have an idea?
Only one client has this error for 10 days... Other oracle clients(same
configuration) have no errors...
Best regards...
Legato client version: 7.1 64 bit
Oracle NMO : 4.1 64 bit
Oracle 9.2.0.5 64bit
****************************************************************************
****************************************************************************
3> run {
4> set command id to "wf1";
5> allocate channel t1 type 'SBT_TAPE'
6> parms 'ENV=(NSR_SERVER=express,NSR_DATA_VOLUME_POOL=PORAdata)';
7> backup incremental level 0
8> filesperset 8
9> (database format 'WFTSTYTL_0_%s_%p');
10> sql "alter system archive log current";
11> sql "alter system switch logfile";
12> backup
13> (archivelog all
14> format 'WFTSTYTLal_set0_%s_%p_%u');
15> backup
16> (current controlfile
17> format 'WFTSTYTLctl_%s_%p');
18> }
19>
RMAN-06005: connected to target database: WFTSTYTL (DBID=2023722850)
RMAN-06008: connected to recovery catalog database
RMAN-03022: compiling command: set
RMAN-03023: executing command: set command id
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: t1
RMAN-08500: channel t1: sid=11 devtype=SBT_TAPE
RMAN-08526: channel t1: NMO v4.1.0.0
RMAN-06421: sent command to channel: t1
RMAN-03022: compiling command: backup
RMAN-03023: executing command: backup
RMAN-08008: channel t1: starting incremental level 0 datafile backupset
RMAN-08502: set_count=340 set_stamp=545706656 creation_time=24-DEC-04
RMAN-08010: channel t1: specifying datafile(s) in backupset
RMAN-08522: input datafile fno=00009
name=/export/home05/oradata/WFTSTYTL/fax_data01.dbf
RMAN-08522: input datafile fno=00003
name=/export/home05/oradata/WFTSTYTL/rbs01.dbf
RMAN-08522: input datafile fno=00005
name=/export/home05/oradata/WFTSTYTL/TIM01.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
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
"WFTSTYTL_0_340_1", blockno 3442177 (blocks
ize=512)
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: nwora_asdf_save: asdf_ouput_section() failed
xdr=0x18e57c0: bp=0x18d3d90: send_len=65536: type=12800: fhand=0x18d14f0:
wrapp
er=0x0: directp=0x8d462000
RMAN-10031: ORA-19624 occurred during call to
DBMS_BACKUP_RESTORE.BACKUPPIECECREATE
Recovery Manager complete.
<snip>
Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
