IC92175: ANR1330E/ANR1331E PAIRS WHEN USING MIXED CASING OF THE SAME NAME VOLUMES IN A FILE DEVICE CLASS.

IBM Tivoli Storage Manager V6.3 Fix Pack 5 (6.3.5.000) Server Downloads
IBM Tivoli Storage Manager (TSM) server V6.1.5.x interim fix downloads

APAR status

• Closed as program error.

Error description

• If you use mixed cases of same name volumes in a file device
  class, the possibility exists that one of those volumes will be
  overwritten.
  
  The symptom is caused by the Tivoli Storage Manager server
  always using a fully lower/upper case volume to do writes or
  reads.
  Under the APAR condition, if you have a lower/upper case volume
  and a mixed case volume with the same name, the mixed case
  volume will not be written to on the disk, but rather the
  lower/upper case volume container will be.
  In order for this problem to be encountered, both volumes must
  be defined prior to any one of those volumes being written to.
  The symptom for the APAR include ANR1330E/ANR1331E pairs with
  matching magic numbers:
  
  <date> <time>     ANR1330E The server has detected possible
  corruption in an object that is being restored or moved. The
  actual
  values for the incorrect frame are: magic 53454652 hdr version
  0002 hdr
  length  0032 sequence number 00000148 data length 0003FFB0
  server ID
  00000000 segment ID 0000001541207095 crc 00000000. (SESSION:
  29522,
  PROCESS: 69)
  <date> <time>     ANR1331E Invalid frame detected.  Expected
  magic 53454652 sequence number 00000001 server id 00000000
  segment id
  0000001498527050. (SESSION: 29522, PROCESS: 69)
  and also the potential for the following message:
  ANR9999D_4186073719 FileReadNC(pvrfil64.c:2096) Thread<92>:
  Invalid block
  header: expected magic (5a4d4e50), actual magic (0).
  As an example, if you define the following two volumes in a
  storage pool you would be exposed to the APAR:
  /mountpoint01/storagepool01/adp_p_dedup_001
  /mountpoint01/storagepool01/ADP_P_DEDUP_001
  (Any uppercase/lowercase variation of the same name exposes you
  to the APAR)
    Tivoli Storage Manager Versions Affected: all
    Customer/L2 Diagnostics (If Applicable)
     You can use the following select to verify if you are exposed
  to the APAR:
     "select volume_name from volumes where upper(volume_name) in
  (select upper(volume_name) from volumes group by
  upper(volume_name) having count(*)>1) order by
  upper(volume_name)"
     If the result set is empty you are not exposed to the APAR.
    Alternatively you can collect SHOW BFO command output against
  the bitfile ids (segment ids) from a pair of ANR1330E/ANR1331E
  messages. If you face the APAR, this will show that the objects
  are on two different volumes of the same name with case
  insensitivity (i.e. /filepool/aaa_0A and /filepool/AAA_0A)
    Initial Impact: Medium
    Additional Keywords: TSM volumename lowercase uppercase
  mixture case sensitive
  

Local fix

• 1. Update all case duplicate volumes to read only
  2. Decide which ones should be removed and
     a. Run a move data against them to get all the data possible
        off of them.
     b. If data remains audit them with fix=yes
     c. Delete the volume
  3. For the remaining volumes that were the case dups of those
     now deleted:
     a. Run a move data against them to get all the data possible
        off of them.
     b. If data remains audit them with fix=yes
     c. Update them back to read/write
  4. Delete any files still on the OS representing the deleted
     volumes
  5. Reallocate/define new volumes with non duplicate names equal
     to the number of volumes deleted
  6. Rerun select/query to validate no case duplicated volumes
     exist.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager server users.     *
  ****************************************************************
  * PROBLEM DESCRIPTION: See error description.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in levels 5.5.7.100, 6.1.5.300, 6.2.6,       *
  *                 6.3.4.100 and 6.3.5.                         *
  *                 Note that this is subject to change at the   *
  *                 discretion of IBM.                           *
  ****************************************************************
  *
  

Problem conclusion

• This problem was fixed.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TSM SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels

• R55A PSY

     UP

• R55H PSY

     UP

• R55L PSY

     UP

• R55S PSY

     UP

• R55W PSY

     UP

• R61A PSY

     UP

• R61H PSY

     UP

• R61L PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R62A PSY

     UP

• R62H PSY

     UP

• R62L PSY

     UP

• R62S PSY

     UP

• R62W PSY

     UP

• R63A PSY

     UP

• R63H PSY

     UP

• R63L PSY

     UP

• R63S PSY

     UP

• R63W PSY

     UP