ADSM-L

Re: Volume has still SEGMENT references

2001-02-07 09:47:56
Subject: Re: Volume has still SEGMENT references
From: "Malbrough, Demetrius" <d_malbrough AT TI DOT COM>
Date: Wed, 7 Feb 2001 08:46:50 -0600
These are two APARs that I found which reference your problem:

APAR= PQ45067  SER=                            IN INCORROUT
UNABLE TO DELETE OFFSITE VOLUME WITH DISCARDDATA=YES OR UPDATE
OFFSITE VOLUMES TO READWRITE, READONLY, OR DESTROYED.

Status: CLOSED                              Closed: 01/12/01

Error Description:
Offsite volumes needing to be returned to scratch status fail
during delete volume discarddata=yes or update volume to
readwrite, readonly, or destroyed. The Move Data command

SCRATCH - it still has SEGMENT references.
ANR9999D asvol.c(1641): Unknown result code (267)  while
deleting a volume.
ANR2032E UPDATE VOLUME: Command failed - internal server error
detected.
ANR1423W Scratch volume xxxx is empty but will not be deleted -
volume access mode is "offsite".
ANR2017I Administrator xxxx issued command: MOVE DATA xxxx
ANR2209W Volume xxxx contains no data.
Unable to audit the volume while in access mode offsite.

Local Fix:
Run:
DSMSERV AUDITDB ARCHSTORAGE FIX=YES
This unfortunately requires halting the server and, depending
on the size of the database, could take quite a long time to
complete.


Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
All TSM Server platforms v3.7 and later.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When changing the status of an empty volume from 'OFFSITE',
the update can fail with an internal server error detected.
Two 9999D diagnostic messages are issued as well.  The
first states the volume cannot be deleted to SCRATCH as it

still has SEGMENT references.  The second diagnostic indicates
an unknown result code while deleting the volume.

****************************************************************
* RECOMMENDATION:                                              *
Apply fix when available.
****************************************************************
When changing the status of an empty volume from 'OFFSITE',
the update can fail with an internal server error detected.
Two 9999D diagnostic messages are issued as well.  The
first states the volume cannot be deleted to SCRATCH as it
still has SEGMENT references.  The second diagnostic indicates
an unknown result code while deleting the volume.
  The first diagnostic message from asvol() indicates orphan
entries in the server db for tracking volume information.  The
fix removes the orphan entries after verifying the rest of the
db is not linked to those entries.


Temporary Fix:


Comments:
MODULES/MACROS:   NONE

Problem Conclusion:
The root cause of this problem is orphan entries within a sub-

section of the server DB.  To correct, these entries are
verified as orphans and then removed.  The second diagnostic
message was corrected by coding for the return code.

APAR= PQ45067  SER=                            IN INCORROUT
UNABLE TO DELETE OFFSITE VOLUME WITH DISCARDDATA=YES OR UPDATE
OFFSITE VOLUMES TO READWRITE, READONLY, OR DESTROYED.

Status: CLOSED                              Closed: 01/12/01

Error Description:
Offsite volumes needing to be returned to scratch status fail
during delete volume discarddata=yes or update volume to
readwrite, readonly, or destroyed. The Move Data command

SCRATCH - it still has SEGMENT references.
ANR9999D asvol.c(1641): Unknown result code (267)  while
deleting a volume.
ANR2032E UPDATE VOLUME: Command failed - internal server error
detected.
ANR1423W Scratch volume xxxx is empty but will not be deleted -
volume access mode is "offsite".
ANR2017I Administrator xxxx issued command: MOVE DATA xxxx
ANR2209W Volume xxxx contains no data.
Unable to audit the volume while in access mode offsite.

Local Fix:
Run:
DSMSERV AUDITDB ARCHSTORAGE FIX=YES
This unfortunately requires halting the server and, depending
on the size of the database, could take quite a long time to
complete.


Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
All TSM Server platforms v3.7 and later.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When changing the status of an empty volume from 'OFFSITE',
the update can fail with an internal server error detected.
Two 9999D diagnostic messages are issued as well.  The
first states the volume cannot be deleted to SCRATCH as it

still has SEGMENT references.  The second diagnostic indicates
an unknown result code while deleting the volume.

****************************************************************
* RECOMMENDATION:                                              *
Apply fix when available.
****************************************************************
When changing the status of an empty volume from 'OFFSITE',
the update can fail with an internal server error detected.
Two 9999D diagnostic messages are issued as well.  The
first states the volume cannot be deleted to SCRATCH as it
still has SEGMENT references.  The second diagnostic indicates
an unknown result code while deleting the volume.
  The first diagnostic message from asvol() indicates orphan
entries in the server db for tracking volume information.  The
fix removes the orphan entries after verifying the rest of the
db is not linked to those entries.


Temporary Fix:


Comments:
MODULES/MACROS:   NONE

Problem Conclusion:
The root cause of this problem is orphan entries within a sub-

section of the server DB.  To correct, these entries are
verified as orphans and then removed.  The second diagnostic
message was corrected by coding for the return code.
<Prev in Thread] Current Thread [Next in Thread>