How to put TSAMP into maintenance mode

A common problem for managing TSMAMP DB2 high availability is how to deal with non DB2 maintenance. An example is OS patching. Let's say there is a 2 node clustering architecture set up. The OS administrators will want to patch the servers, but there is a requirement to maintain uptime on the DB2. If using TSAMP a straightforward plan, could be based on these steps The basic idea is to change the Automation mode to manual mode . Step 1 : Manually move the DB2 instance to the required node. Use the rgreq command . Read more on TSAMP Cheat... Read more →

The case of the missing numeric ip format in TSM TCPCLIENTADDRESS

As part of the DB2 clustering solution using Tivoli Storage Automation(TSA) there were some customisations required to make the monitoring and backup procedures “cluster aware”. One of the customisations was to facilitate TSM scheduler to point to the active DB2 node. Read more on How to customise TSAMP start and stop scripts to make monitoring ... Therefore if there is a DB2 failover from Server 1 to Server 2 , with all the associated resources failing over, such as ip address, DB2 instance and storage , TSM scheduler can point to the current active node and continue with backups as... Read more →

The great Windows or Linux debate for DB2 LUW

I manage large DB2 servers on Windows and Linux , so I’m confident both OS platforms can support installations with large data sets and high end throughput. But believing DB2 will perform exactly the same on both Windows and Linux without some analysis is a recipe for problems. There are some considerations when planning switching or deciding between DB2 or Linux or Windows. Scriptability of DB2 on Linux versus Windows. If migrating from Linux – you may have a large shell script library which manage Linux and commit the flow control . There may be considerable work to adapt these... Read more →