Question & Answer
Question
How to install the TSAMP bundled with Db2 using db2installSAM from the Db2 installation media.
Cause
Sometime during Db2 installation the TSAMP upgrade was skipped due to the domain being left online when the Db2 installation media was installed on the node/server. Whenever you install a new version/release of Db2 you should always ensure that the domain/cluster is offline prior to installing the media, its during this installation that TSAMP and RSCT are also upgraded. Since TSAMP and RSCT have to always be installed to the same exact location they must be made offline so that the new TSAMP/RSCT version can be installed when installing the Db2 installation media.
Answer
TSAMP is included with the DB2 installation media package, once you install the Db2 installation media, the Db2 installer automatically upgrade your TSAMP/RSCT level to pick up critical TSAMP/RSCT fixes.
1. Here is IBM note that you can refer to upgrading your Db2 servers in an automated HADR environment.
https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.qb.upgrade.doc/doc/t0070016.html [Use method 2]
2. When you upgrade your db2, make sure TSAMP version should be upgrade along with, you may find the available TSAMP version details from "/<media>/server_t/db2/linuxamd64/tsamp"
3. If your installed TSAMP didn't match with bundled TSAMP version then you have to below procedure to update TSAMP in an automated Db2 high availability disaster recovery (HADR) environment.
4. On the standby node[node02], stop all Db2 processes by using:
-- deactivate db <database-name>. This command stops HADR, but retains the role.
-- db2stop force.
5. Stop the standby Node [node02]
-- Run the stoprpnode -f <standby node> command as root.
-- Run the stoprpnode -f <standby node> command as root.
6. Upgrade TSAMP Fix Pack by enter into TSAMP installation path.
cd <media path>/db2/linuxamx64/tsamp
7. Run "./db2installSAM" to upgrade TSAMP [this script will automatically installed required efixs as well along with TSAMP].
8. Once TSAMP upgrade done, check TSAMP version by using samversion command [o/p should be upgraded TSAMP]
9. On the primary node [node01], run the startrpnode <standby node> command as root.
10. On the standby node [node02], start all Db2 processes:
-- db2start.
-- activate db <database-name>. This command resumes HADR but retains the role.
-- activate db <database-name>. This command resumes HADR but retains the role.
11. Verify that the HADR pair has established PEER state via below command.
-- db2pd -hadr db <database-name>
12. On the node01, issue the below command to takeover resources to upgraded node02.
-- db2 takeover hadr on db <database-name>
13. On node1 , repeat steps 4-10 to apply the fix pack.
14. If required, migrate the TSAMP domain.[TSAMP domain migration is only required if the new Db2 fix pack includes a new TSAMP version. It is not always the case that the new Db2 fix pack includes a new TSAMP version.
TSAMP domain migration is required if the active version number (AVN) does not match the installed version number (IVN). These values can be listed by running the below command.
-- lssrc -ls IBM.RecoveryRM |grep VN
15. Verify that MixedVersions for the RSCT by running the below command, if you found MixedVersion = YES then you must complete the RSCT migration using next step.
-- lsrpdomain
16. To migrate TSAMP/RSCT domain, issue the following command as root:
-- export CT_MANAGEMENT_SCOPE=2
-- runact -c IBM.PeerDomain CompleteMigration Options=0 [To complete the RSCT migration]
-- samctrl -m # Type 'Y' to confirm migration [ To complete the TSAMP migration]
-- export CT_MANAGEMENT_SCOPE=2
-- runact -c IBM.PeerDomain CompleteMigration Options=0 [To complete the RSCT migration]
-- samctrl -m # Type 'Y' to confirm migration [ To complete the TSAMP migration]
17. Verify that the AVN and IVN values match using below command.
-- lssrc -ls IBM.RecoveryRM |grep VN command.
18. Verify that MixedVersions is set to No for the cluster manager by running the below command (this may take a minute or two after running the migration command).
lsrpdomain
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSRM2X","label":"Tivoli System Automation for Multiplatforms"},"ARM Category":[{"code":"a8m500000008c8FAAQ","label":"DB2"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"}],"Version":"All Version(s)","Line of Business":{"code":"LOB45","label":"Automation"}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"ARM Category":[{"code":"a8m500000008PknAAE","label":"Install\/Migrate\/Upgrade"}],"Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"}],"Version":"10.5.0;11.1.0;11.5.0","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Product Synonym
TSA;TSAMP
Was this topic helpful?
Document Information
Modified date:
01 July 2020
UID
ibm16221306