Networker

Re: [Networker] Strange legato - rman error

2004-12-25 02:49:49
Subject: Re: [Networker] Strange legato - rman error
From: Barış Yeter <barye AT KOCBANK.COM DOT TR>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Fri, 24 Dec 2004 14:03:58 +0200
Ok... But, I got this error while library was not busy...

input datafile fno=00039 name=/global/khome01/oradata/KBLIVE/event_data02.dbf
channel t2: starting piece 1 at 22-DEC-04
released channel: t1
released channel: t2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on t1 channel at 12/22/2004 01:00:59
ORA-19502: write error on file "KBTESTFULL_9872_1", blockno 14303233 
(blocksize=512)
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: Error received from media manager layer, error text:
   nwora_asdf_save: asdf_ouput_section() failed
xdr=0x1034bdd50: bp=0x103479788: send_len=262144: type=12800: fhand=0x1033f44e8
: wrapper=0x0: directp=0x3c7fbc000

-----Original Message-----
From: Mark Bradshaw (BTOpenWorld) [mailto:notthehoople AT btopenworld DOT com] 
Sent: Friday, December 24, 2004 1:05 PM
To: Barış Yeter; NetWorker List
Subject: Re: [Networker] Strange legato - rman error

Ok, if you can backup successfully during the day but not during the night
it sounds as though you don't have the resources needed to carry out the
backup anymore. Can you change the time of this backup til earlier? You
might find that the backup failure changes to a different client if your
system is overloaded.

You have lots of messages in the server daemon.log saying that NetWorker
cannot get a tape drive as they are all in use. Perhaps if you can change
the time of this RMAN backup to run at a time when other RMAN backups are
running and thus are successfully grabbing a tape drive you may mind your
backups now work.

> 
> This client (has gigabit interface) backups its data via LAN...
> Other oracle backups go to the same pool...
> After this error, I tried backup again... And there is no problem...
> But I have this problem every day repeatedly since 15/12/2004...
> 
> 
> 
> -----Original Message-----
> From: Mark Bradshaw (BTOpenWorld) [mailto:notthehoople AT btopenworld DOT com]
> Sent: Friday, December 24, 2004 11:03 AM
> To: Baržs¸ Yeter; NetWorker List
> Subject: Re: [Networker] Strange legato - rman error
> 
> 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 DOT 
>> 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
>> 
<snip>

<Prev in Thread] Current Thread [Next in Thread>