IC93262: RESTORE DB FAILURE WITH ANR2971E SQL2068N ON LIBRARY CLIENT

IBM Tivoli Storage Manager V6.3 Fix Pack 5 (6.3.5.000) Server Downloads

APAR status

• Closed as program error.

Error description

• "RESTORE DB" on Library Client server may fail with ANR2971E
  SQL2068N because the Library Manager cannot mount a tape volume
  to a specific drive for the library client.  The reason is that
  the library client does not release this specific tape driver
  after pervious operations.  This problem occurs while the device
  serial number mismatch issue is occurring to this specific tape
  drive on the library client for Windows platforms.  When this
  problem occurs, the following messages are logged to the library
  client log file showed below
  >>>
  C:\TSM\Server1>dsmserv RESTORE DB
  ...
  ANR8974I Found new path for LC_name and target name DRV1 old
  path Tape0 new path Tape1. Path information will be updated
  remotely.
  ...
  ANR8337I LTO volume volume_name mounted in drive DRV1 (Tape1).
  ANR0510I Session 1 opened input volume volume_name.
  ANR1363I Input volume volume_name opened (sequence number 1).
  ANR1364I Input volume volume_name closed.
  ANR0514I Session 1 closed volume volume_name.
  ...
  ANR4897I Database restore of operation 0 will use device class
  devc_name and attempt to use 1 streams.
  ANR0406I Session 8 started for node $$_TSMDBMGR_$$ (DB2/NT64)
  (Tcp/Ip node_name(port_numer)).
  ANR0408I Session 6 started for server LM_name (Linux/x86_64)
  (Tcp/Ip) for LIBRARY SHARING.
  ANR8468I LTO volume volume_name dismounted from drive DRV1
  (Tape1) in library library_name.
  ANR0409I Session 6 ended for server LM_name (Linux/x86_64).
  ....
  ANR2971E Database backup/restore/rollforward terminated - DB2
  sqlcode -2068 error.
  ANR2032E RESTORE DB: Command failed - internal server error
  detected.
  ANR9999D Thread<0> issued message 2032 from:
  ANR9999D Thread<0>  000007FEED16E3AE outMsgf()+3e output.c:1182
  ANR9999D Thread<0>  000007FEECA07355 AdmRestoreDb()+12f5
  admdbbk.c:2334
  ANR9999D Thread<0>  000007FEEC99C857 admRestoreDatabase()+187
  admstart.c:3753
  ANR9999D Thread<0>  000007FEEC981322 RestoreDb()+f2
  adsmmain.c:1862
  ANR9999D Thread<0>  000007FEEC9834E1 adsmMain()+ef1
  adsmmain.c:1647
  ANR9999D Thread<0>  000000013F15111B main()+9b dsmserv.c:241
  ANR9999D Thread<0>  000000013F1528DA __tmainCRTStartup()+11a
  crtexe.c:555
  ANR9999D Thread<0>  000000007791F56D BaseThreadInitThunk()+d
  ANR9999D Thread<0>  0000000077A53281 RtlUserThreadStart()+21
  <<<
  
  The library manger will have follow messages in its log file.
  >>>
  ANR0408I Session 37 started for server LC_name (Windows)
  (Tcp/Ip) for library sharing.  (SESSION: **)
  ...
  ANR8337I LTO volume volume_name mounted in drive DRV0
  (/dev/IBMtape0). (SESSION: **)
  ...
  ANR8468I LTO volume volume_name dismounted from drive DRV0
  (/dev/IBMtape0) in library LT250. (SESSION: **)
  ...
  ANR8779E Unable to open drive /dev/IBMtape2, error number= 5.
  (SESSION: **)
  ANR8779E Unable to open drive /dev/IBMtape2, error number= 16.
  (SESSION: **)
  ANR8942E Could not move volume volume_name from slot-element 503
  to slot-element 1015. (SESSION: **)
  ANR8381E LTO volume volume_name could not be mounted in drive
  DRV1 (/dev/IBMtape2). (SESSION: **)
  ANR9790W Request to mount volume volume_name for library client
  LC_name failed. (SESSION: **)
  <<<
  
  The problem may happen when the library client opens the tape
  device that supports the persistent reservation using IBM tape
  device driver or TSM tape device driver on Windows platform.
  
  Tivoli Storage Manager Versions affected:
  Tivoli Storage Manager Server 6.3.0.0 or later versions for all
  supported Windows platform
  
  Additional Keywords:
  
  
  Additional L2 info:
  The problem is caused by the library client does not release the
  persistent reservation before closing the tape drive when it
  detected that the serial number of the drive was mismatch.
  
  Initial Impact:
  Medium
  

Local fix

• Persistent binding may prevent the serial number of the tape
  device being mismatch after rebooting Windows.  Refer to
  http://www-01.ibm.com/support/docview.wss?uid=swg21571889,
  "Resolving the problem" - "Solutions:" - "Option 1".
  ---
  Use persistent binding within the SAN environment. This allows
  Windows to see and connect to the devices in the same consistent
  fashion each time Windows is rebooted. Setting persistent
  binding is done at a SAN level (usually through tools provided
  with the SAN host bus adapter (HBA). Refer to the documentation
  and support pages of the vendor to determine if the HBA supports
  persistent binding.
  ---
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager server users in   *
  *                 a shared library environment.                *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in levels 6.3.4.200, and 6.3.5.              *
  *                 Note that this is subject to change at the   *
  *                 discretion of IBM.                           *
  ****************************************************************
  *
  

Problem conclusion

• This problem was fixed.
  
  Affected platforms: Windows.
  

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

• R63W PSY

     UP