APAR status
Closed as program error.
Error description
This problem happens when upgrading a Tivoli Storage Manager server from V6 to V7 installed on AIX PowerHA configured with shared instance directory. Following the documented upgrade procedure, the installation fails when upgrading the code on the secondary cluster node with error : " ERROR: Error during "install" phase: Details: ANRI1057E: The installation was not successful. To review errors and correct any issues, review the log file /var/ibm/InstallationManager/logs/native/tsm_logs/db2_uninstall. log and the log files in /var/ibm/InstallationManager/logs/native." Tivoli Storage Manager Versions Affected: AIX PowerHA cluster upgrade from V6.2 or V6.3 to V7.1 Customer/L2 Diagnostics : The db2_uninstall.log file shows: ERROR: The deinstallation process cannot continue while there are DB2 instances related to the current DB2 copy. If you need to move up or down a level from this DB2 level, use the installFixPack command from the DB2 image for the level you desire to move to, which will update this copy. If you are only trying to uninstall this DB2 copy, you must either drop the related instances first, or you can update the instances to another DB2 copy which is at the same version as this DB2 copy, then restart the db2_deinstall command. The install log file "xxx.xml" shows that a previous db2idrop operation failed : message>INFO: com.tivoli.dsm.server.install.utils.CmdUtils.issueCommandExt(700 ) : Command: /opt/tivoli/tsm/db2/instance/db2idrop tsminst1</message> </entry> <entry num='952' time='1421759652724' elapsed='23:54.58' level='ERROR' thread='Thread-45'> <logger>DB2Info</logger> <class>com.ibm.cic.agent.internal.core.IMLoggerImpl</class> <method>error</method> <message>ERROR: com.tivoli.dsm.server.db2.DB2Info.dropInstance(1450) : Failed to drop instance</message> Initial Impact: Medium Additional Keywords: TSM POWERHA SQLLIB HACMP ANRI1057E
Local fix
1. Move all shared resources to the primary node 2. Upgrade the primary node 3. Do not move any resources back over to the secondary 4. From root user, run: db2iset -d <instance> for each configured instance This will remove the db2 instance(s) profile from the DB2 global registry 5. Perform the upgrade on the secondary node 6. Run the following to add the instances(s) again: db2iset -a <instance>
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 level 7.1.3. Note that this is * * subject to change at the discretion of IBM. * ****************************************************************
Problem conclusion
This problem was fixed. Affected platforms: AIX.
Temporary fix
Comments
APAR Information
APAR number
IT06910
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
71A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-02-03
Closed date
2015-05-19
Last modified date
2015-05-19
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
R71A PSY
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.3","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
19 May 2015