ADSM-L

Re: TAPES not becoming scratch after upgrading to 3.1.2.2

1999-04-26 09:48:21
Subject: Re: TAPES not becoming scratch after upgrading to 3.1.2.2
From: Clint Placette <Clint.Placette AT FDC-INVEST DOT COM>
Date: Mon, 26 Apr 1999 09:48:21 -0400
Here is a suggestion.  Try taking a couple of tapes that your having the
problem
out of the library manually.  Check them back in to the library.  It may
not be
pretty but it may be a solution.

______________________________ Reply Separator
_________________________________
Subject: Re: TAPES not becoming scratch after upgrading to 3.1.2.20
Author:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> (Kenneth Sparks
<ken_x_sparks AT AMOCO DOT COM>) at INET
Date:    4/21/99 2:17 PM






               Have you checked them in and what is your reuse delay?


       ______________________________ Reply Separator
       _________________________________
       Subject: Re: TAPES not becoming scratch after upgrading to 3.1.2.20
       Author:  lhumar (lhumar AT VIC.BIGPOND.NET DOT AU) at unix,mime
       Date:    4/20/99 7:26 PM


       G'day Peter,

       The tapes will return to scratch once you've mounted them.

       Leo Humar
       LCS Pty Ltd
       lhumar AT vic.bigpond.net DOT au

       -----Original Message-----
       From: Peter Gill <Peter_Gill AT RACV.COM DOT AU>
       To: ADSM-L AT VM.MARIST DOT EDU <ADSM-L AT VM.MARIST DOT EDU>
       Date: Wednesday, April 21, 1999 10:18 AM
       Subject: TAPES not becoming scratch after upgrading to 3.1.2.20


       >I have recently upgraded from ADSM server from 3.1.1.6 to 3.1.2.20
       >(Clients upgraded appropriately).   Since then, I have accumulated
       about
       >50 tapes with a status of EMPTY.  When I change the access from
       OFFSITE
       >to READWRITE, the tape should become scratch (These are copypool
       >tapes).   I keep getting a server error.    I have logged this with
       IBM
       >and have done a database audit.  The database audie had
       inconsistencies
       >with 3 tapes. I   fixed these and now get a clean database audit
       >result.   About 20 tapes have returned to scratch status but the
       rest
       >have not.  I have tried updating the acess to every valid value and
       get
       >the same error (Example below).
       >
       >Has anyone experienced this problem before?
       >Has anyone got any ideas?
       >
       >+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
       +++
       +++++
       >
       >04/21/99 09:49:02     ANR2017I Administrator PJG01 issued command:
       >UPDATE VOLUME
       >                       SAP002 ACCESS=READWRITE
       >WHERESTGPOOL=SAP_TAPE_COPYPOOL
       >                       WHEREDEVCLASS=3590DEV1
       >04/21/99 09:49:02     ANR1425W Scratch volume SAP002 is empty but
       will
       >not be
       >                       deleted - volume state is
       "mountablenotinlib".
       >04/21/99 09:49:02     ANR9999D asvol.c(1626): Unknown result code
       (166)
       >while
       >                       deleting a volume.
       >04/21/99 09:49:02     ANR2032E UPDATE VOLUME: Command failed -
       internal
       >server
       >                       error detected.
       >
       >+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
       +++
       +++++
       >
       >
       >
       >Regards, Peter Gill
       >
       >_______________________________________________________
       >Peter Gill
       >UNIX Systems Administrator
       >RACV Information Systems
       >Level 6, 550 Princes Highway, Noble Park,  VIC  3174
       >AUSTRALIA
       >
       >(P) +61 3 9703 6018  (F)  +61 3 9790 2559  (M)  0419 484 675
       >mailto:Peter_Gill AT racv.com DOT au
       >_______________________________________________________
<Prev in Thread] Current Thread [Next in Thread>
  • Re: TAPES not becoming scratch after upgrading to 3.1.2.2, Clint Placette <=