IT44632: IBM STORAGE PROTECT BUILT-IN SERVERMON CREATED HUGE SIZE OF SERVERMON.LOG THEN FILLS UP INSTANCE DIRECTORY CAUSED SERVER CRASHED

8.1.25.000-IBM-SPSRV-WindowsX64-340
8.1.25.000-IBM-SPSRV-Linuxx86_64-340
8.1.25.000-IBM-SPSRV-Linuxs390x-340
8.1.25.000-IBM-SPSRV-Linuxppc64le-340
8.1.25.000-IBM-SPSRV-AIX-340

APAR status

• Closed as program error.

Error description

• The IBM Storage Protect Server built-in servermon created the
  servermon.log in the srvmon directory,
  
  which can befound in the instance home directory of the server.
  
  
  From servermon.log, the symptom of the following sequence of
  messages can occur many times
  
  within one second if servermon is unable to connect to db2:
  
  Establishing DB2 connection
  Db2 Database Object is valid - ping to confirm and obtain
  connection
  Ping to DB failed &{
  {sqlconnect; DATABASE=TSMDB1; AUTOCOMMIT=1; 0x8c9e00}
  
  0 {0 0} [] map[] 0 0 0xc420234180 0xc4a8fe8d80 false map[]
  map[] 0 0 0 <nil> 0x4cc170} database/sql/driver:
  [IBM][CLI Driver] SQL1032N  No start database manager command
  was issued.  SQLSTATE=57019
  Setting Schema failed=database/sql/driver: [IBM][CLI Driver]
  SQL1032N  No start database manager command was issued.
  SQLSTATE=57019 result=<nil>
  Retry connect failed database/sql/driver: [IBM][CLI Driver]
  SQL1032N  No start database manager command was issued.
  SQLSTATE=57019
  Unable to connect to server database sleeping.
  
  The result is that it can quickly fill up the instance home
  directory of the server.
  

Local fix

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.25. Note that this is     *
  * subject to change at the discretion of IBM.                  *
  ****************************************************************
  

Problem conclusion

• This problem was fixed.
  Affected platforms:  AIX, Linux, and Windows.
  Platforms fixed: AIX, Linux, and 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