IT44751: ANR9999D_3303258819 EXITING ON INITFAILURE FOR SS DURING STARTUP

8.1.22.000-IBM-SPSRV-WindowsX64
8.1.22.000-IBM-SPSRV-Linuxx86_64
8.1.22.000-IBM-SPSRV-Linuxs390x
8.1.22.000-IBM-SPSRV-Linuxppc64le
8.1.22.000-IBM-SPSRV-AIX

APAR status

• Closed as program error.

Error description

• If the master encryption key files are not available or damaged
  (dsmkeydb.kdb and dsmkeydb.sth) during restart of the SP server,
  then the following messages may be reported and fail the server
  startup.   This has been seen with defined Cloud pools.
  
  ANR2284S The server master encryption key has changed. Passwords
  protected with the previous master encryption key are not
  available.
  ANR1636W The server machine GUID changed: 
  ANR2100I Activity log process has started.
  ANR2102I Activity log pruning started: removing entries prior to
  xxx
  ANR4726I The NAS-NDMP support module has been loaded.
  ANR1794W IBM Spectrum Protect SAN discovery is disabled by
  options.
  ANR9999D_3303258819 StartServer(admstart.c:7171) Thread<1>:
  Exiting on initFailure for ss.
  ANR9999D Thread<1> issued message 9999 from:
  ANR9999D Thread<1> 0x142a4c0
  /opt/tivoli/tsm/server/bin/dsmserv(OutDiagToCons+0xb0)
  ANR9999D Thread<1> 0x14329e0
  /opt/tivoli/tsm/server/bin/dsmserv(outDiagfExt+0x1f0)
  ANR9999D Thread<1> 0x505f03
  /opt/tivoli/tsm/server/bin/dsmserv(StartServer+0x3c03)
  ANR9999D Thread<1> 0x50bb3c
  /opt/tivoli/tsm/server/bin/dsmserv(admStartServer+0xec)
  ANR9999D Thread<1> 0x4f0bdc
  /opt/tivoli/tsm/server/bin/dsmserv(main+0x1eac)
  ANR9999D Thread<1> 0x7fa53efd424d
  /lib64/libc.so.6(__libc_start_main+0xef)
  ANR9999D Thread<1> 0x4f0d99
  /opt/tivoli/tsm/server/bin/dsmserv(_start+0x29)
  ANR1912I Stopping the activity log because of a server shutdown.
  
  ANR0369I Stopping the database manager because of a server
  shutdown.
  
  IBM Storage Protect Versions Affected:
  
    IBM Storage Protect Server 8.1.12 and above on all supported
  platforms
  
  Additional Keywords: TS014188571 Cloud Pool DRM
  

Local fix

• If the master key files are damaged or missing:
  If you have made copies of these files, then copy the original
  saved dsmkeydb.kdb and dsmkeydb.sth files back to its instance
  directory.  Then restart the SP server.
  
  Or
  Restore DB with restore keys.
  
  Or
  For restore DB and you didnt do SET DBRECOVERY and set a
  password, or you skipped the restore of these keys, then the
  keys need to have been protected some other way and copied back
  to the original instance user directory.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All IBM Storage Protect server users.                        *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See error description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in level 8.1.22. Note that this is     *
  * subject to change at the discretion of IBM.                  *
  ****************************************************************
  

Problem conclusion

• This problem was fixed.
  Affected platforms:  AIX, Linux, and Windows.
  
  The server will issue a new message, ANR4198E, when it
  encounters this problem, and will continue to start:
  
  ANR4198E Unable to get connection details for connection
  <cloud_connection_name>.
  
  Explanation:
  The server cannot get details about the specified cloud
  connection, possibly because the server master encryption key
  cannot be read. Server initialization will continue but the
  cloud object store associated with the connection will not be
  accessible until the problem is corrected.
  
  System Action:
  Server operation continues.
  
  User Response:
  Review the activity log and dsmffdc.log for errors that might
  have led to this problem. Correct the errors and restart the
  server.
  

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