Methods to find TSAMP error details and return codes

Question: How can I find details about TSAMP (Tivoli System Automation for Multiplatforms) failover details? I discovered that a failover occurred and need, what sources will give me details? I have a TSA single storage solution in place Answer: There are multiple methods to extract details about a failover details. If you troubleshooting , it may be necessary to correlate details from different sources. These sources of information are a good starting point for diagnostics. /var/ct/IBM.RecoveryRM.log Linux error logs on /var/logs/messages tail -f /var/log/messages Db2diag log files Instance_name.nfy file Read More on TSAMP TSAMP Cheat Sheet for DBA managing DB2... Read more →

HOW TO clear inactive DB2 LUW transaction log files

How to clear inactive DB2 LUW transaction log files is a solution to a common problem. Before we discuss how to prune the inactive transaction logs we’ll need to establish which log files are inactive. It is important to identify which logs to delete. If you delete an active transaction log file, you will cause an outage on the database Note: Log files located in the transaction log path cannot be removed with 'db2 prune history xxxxxxx and delet' if database configuration 'LOGARCHMETH1' is set to 'LOGRETAIN'. Before you start any activity , speak to the owners and users of... 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 →

TSAMP maintenance and diagnostics

You’ve set your TSAMP environment on Linux and DB2. Tested a few failover scenarios and everything is looking positive. One of the key things about TSAMP and DB2 is maintaining the environment. Finding any small problems before they become big problems. For example, monitoring message logs and backing up copies of configuration and state files can save you lots of work when troubleshooting. These are some guidelines to follow, which will give you a firm basis. There are different ways of using the information, but I like to create reports , which are reviewed and apply any fixes 1. Before... Read more →

ADM11001E DB2 did not create a memory segment for running fenced routines

Question:We are carrying out an application installation. The installation is failing with the following message in the .nfy file . ADM11001E DB2 did not create a memory segment for running fenced routines. This was specified by the use of DB2_FMP_COMM_HEAPSZ registry variable. How can I bypass these errors to allow the installation to finish? Answer: I’ve seen this problem plenty of times where a DBA has set the DB2 registry value : DB2_FMP_COMM_HEAPSZ=0. On many occasions , it is to force fenced routines such as the DB2 Health Monitor :Monitor health of instance and databases to not run. It is... Read more →