Troubleshooting
Problem
During an attempted upgrade or re-install of the Tivoli Storage Manager server, the installation process fails to successfully install DB2
Cause
The attempted server upgrade failed because one or more DB2 processes were still running when the install was attempted. As a result, there were several DB2 libraries in use that could not be replaced by the upgrade operation, thus, the operation failed.
Diagnosing The Problem
Review the contents of the DB2.log file to determine the reason for the installation failure. An error similar to the following may be seen:
ACUOSI0050E External command action failed with return code 67.
Invocation string: [tsm_install/6.2.1.1/COI/PackageSteps/DB2/FILES/ese/db2setup, -r, /opt/tivoli/tsm/_uninst/plan/tmp/Prefix_ResponseFile.txt, -l, /opt/tivoli/tsm/_uninst/plan/tmp/db2setup.log]
Review the db2setup.log file specified in the previous error for additional information as to the reason for the failure. The db2setup.log file may contain the following error indicating a problem with the db2chgpath program:
-----------------------------------------------------------
ERROR: There were errors during the run of the db2chgpath program to change the embedded runtime path of the related DB2 library and executable files from
/opt/IBM/db2/V9.7/
to
/opt/tivoli/tsm/db2/
You may need to manually rerun db2chgpath.
Check the log file /tmp/db2chgpath.log.229726 for details.
If the rerun is successful, please follow the DB2 quick beginning books to configure DB2 instance(s) and/or DAS as needed.
If the problem persists, please contact IBM DB2 Support.
ERROR: An error occurred while setting DB2 runtime path. Contact a technical service representative.
Setting DB2 library path :.......Failure
ERROR: A major error occurred while installing "DB2 Enterprise Server Edition" on this computer. The installation cannot continue. If the problem persists contact your technical service representative.
-----------------------------------------------------------
The db2chgpath.log file will contain errors similar to the following:
db2chglibpath: Unable to open file for write: '/opt/tivoli/tsm/db2/lib64/libdb2genreg.a': error: 26(Text file busy)
db2chglibpath: Unable to open file for write: '/opt/tivoli/tsm/db2/lib64/libdb2install.a': error: 26(Text file busy)
db2chglibpath: Unable to open file for write: '/opt/tivoli/tsm/db2/lib64/libdb2osse.a': error: 26(Text file busy)
db2chglibpath: Unable to open file for write: '/opt/tivoli/tsm/db2/lib64/libgcf.a': error: 26(Text file busy)
------------------------------------------------------------------
The embedded library path of the following files could not be updated with the current installation path /opt/tivoli/tsm/db2/ due to some unexpected error. Please rerun db2chgpath. If the problem can not be resolved, please contact IBM DB2 Support.
------------------------------------------------------------------
FAIL (unexpected error): /opt/tivoli/tsm/db2/lib64/libdb2genreg.a
FAIL (unexpected error): /opt/tivoli/tsm/db2/lib64/libdb2install.a
FAIL (unexpected error): /opt/tivoli/tsm/db2/lib64/libdb2osse.a
FAIL (unexpected error): /opt/tivoli/tsm/db2/lib64/libgcf.a
------------------------------------------------------------------
These errors indicate that the referenced libraries could not be updated because they were in use at the time of the installation.
Resolving The Problem
This problem can be avoided by ensuring that all DB2 processes are stopped prior to attempting the installation. Halting the Tivoli Storage Manager server, as required, prior to performing the installation will typically result in all DB2 processes being terminated, however, it's possible that one or more processes remain active. Perform the following actions to ensure that all DB2 processes and/or system resources are released prior to attempting another upgrade:
- a. issue the 'ps -ef |grep db2' command to ensure that there are no active DB2 processes; any matching processes should be stopped/killed
NOTE: on AIX the DB2 fault monitor process (db2fmcd) is configured to respawn automatically from /etc/inittab and it is this process that is most commonly responsible for this type of installation failure. To temporarily disable this process from respawning, remove the entry for the db2fmcd process from the /etc/inittab file and issue the 'telinit Q' command from the AIX prompt to re-examine the contents of the inittab file. This should result in the termination of the db2fmcd process. After confirming that the db2fmcd process is no longer active, proceed to the next step.
b. issue the 'ps -ef |grep <DB2 instance>' command to ensure that there are no active processes running under the DB2 instance id; any matching processes should be stopped/killed
c. as the DB2 instance owner, issue the 'ipclean' command to clean up any outstanding IPC resources associated with this instance:
$ /opt/tivoli/tsm/db2/bin/ipclean
$ cd /opt/tivoli/tsm/_uninst
$ ./Uninstall_Tivoli_Storage_Manager -i console
$ rm -R /opt/tivoli/tsm
Once complete, you can then perform a clean install of the Tivoli Storage Manager server code. As the existing 6.3 license package was removed when the Tivoli Storage Manager server was uninstalled, it will be necessary to re-install the 6.3 licenses from an installation package obtained from Passport Advantage website.
[{"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Server","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"6.3","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Product Synonym
TSM Spectrum Protect
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21989898