How to uninstall DB2

After you’ve installed the DB2 server – there may be a situation where you need to uninstall DB2. These notes will help db2_deinstall -F - Removes a feature from a DB2 database product in the current location. Execute the command from the DB2DIR/install directory db2_deinstall -a Removes all installed DB2 database products in the current location. Executes the command from the DB2DIR/install directory DB2DIR is the location specified in the DB2 server installation Example of Log created DB2 Uninstall log file started at: ============================================================ Operating system information: Linux 2.6.9-67.ELsmp.#1 SMP Wed Nov 7 13:58:04 EST 2007 i686 Previously Installed Components:... Read more →

nmon - tuning and benchmark tool

Nmon is a tuner and benchmark tool on Linux. Capture disk, cpu, memory , filesystem, resource usage, virtual memory As a DB2 DBA it's a very effective method of capturing different types of in data in one interface. nmon is useful in operation with DB2 and Linux IO testing tools Notes 1) Download nmon from http://nmon.sourceforge.net/pmwiki.php 2) tar –xvf filename.tar.gz on the target server 3) Locate the correct binary , in my case – nmon_linux_x86_64 4) Use to check if nmon is running : ps -ef | grep nmon 5) Use the file output option to Save the data file... Read more →

Linux multipath command

Q . How can I see the details of multipathing on a Red Had Enterprise Linux 5 server, using DM-Multipath? This is normally a prerequisite for a DB2 installation using SAN and Linux. The DBA can do a quick check A. Use the multipath command variations #find the paths to LUN multipath –l #Print multipathed paths showing which devices are multipathed multipath –v2 See Also Storage Monitoring : a quick guide Read more →

Troubleshooting SQL2219N and reason code 9

This DB2 error message SQL2219N reason code 9 appeared in the db2 db2diag file. The DB2 documentation details for reason code 9 are “START is not allowed as a prior paused table reorganization has not been stopped”. I discovered there was a scheduled maintenance of the databases – 1) REORG - managing reorg of tables (and indexes). 2) RUNSTATS It conflicted with the AUTO_REORG on the databases. Turning off AUTO_REORG stopped the error occurring. 2012-03-18-22.49.37.393468+000 E2273446E603 LEVEL: Error PID : 25077 TID : 189054052704 PROC : db2sysc INSTANCE: db2tdw NODE : 000 DB :MYDB APPHDL : 0-17413 APPID: *LOCAL.db2tdw.120319003038 AUTHID... Read more →

Troubleshooting ADM13001E IBMOSauthclient and db2secGetDefaultLoginContext

2012-03-14-21.59.22.121301+000 E1040722932E430 LEVEL: Severe PID : 26754 TID : 182956718112 PROC : db2bp INSTANCE: db2my NODE : 000 FUNCTION: DB2 UDB, bsu security, sqlexGetDefaultLoginContext, probe:150 MESSAGE : ADM13001E Plug-in "IBMOSauthclient" received error code "-2" from the DB2 security plug-in API "db2secGetDefaultLoginContext" with the error message " ". Determines the user associated with the default login context, in other words, determines the DB2 authid of the user invoking a DB2 command without explicitly specifying a user ID The db2secGetDefaultLoginContext API returns the user of the default login context. In the situation , where a DB2 command is executed , but a... Read more →