DB2 - Drop the DB2DETAILDEADLOCK event monitor

DB2DETAILDEADLOCK is created and activated by default when a database is created. When an activity activates the database the monitor starts up. When a deadlock occurs the diagnostic information is collected. There are circumstances where you need to either deactivate or DROP the monitor. For example , there may be resource constraints Deactivate the the event monitor db2 "set event monitor DB2DETAILDEADLOCK state 0" Drop the event monitor db2 "drop event monitor DB2DETAILDEADLOCK" Related Posts SQL0911N Reason Code 68 The current transaction has been rolled back because of a deadlock or timeout How to monitor a deadlock in DB2 Read more →

DB2 – How to pscp from the command line

PSCP is a command line secure file copy program. It’s part of the PuTTY suite of files, which also includes PuTTY – a Telnet and SSH client. Within the PuTTY suite is another program called : Plink – which is a command line interface to the PuTTY backend. The great thing about Plink is it can be used as part of a script for management of DB2 servers. For example, a script to log on securely to a server – run a series of commands. One of the limitation of Plink is you can’t download files. At this point PSCP... Read more →

Copyright-Disclaimer

Copyright © Jack Vamvas and dba-db2.com, 2008-2020. Unauthorized use and/or duplication of this material without express and written permission from this blog’s author and/or owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to Jack Vamvas and dba-db2.com with appropriate and specific direction to the original content. A link is compulsory. dba-db2.com provides a free feed. This MUST NOT be syndicated Disclaimer All content provided on this blog is for informational purposes only. The owner of this blog makes no representations as to the accuracy or completeness of any information on... Read more →

DB2 – Backup history

Question: How do I return DB2 BACKUP and DB2 RESTORE history? One requirement is to view the data for troubleshooting , the other requirement is to include in a daily report – for distribution to the DBA team Answer: Use either LIST HISTORY or or SYSIBMADM.DB_HISTORY Administrative View. Both methods have their benefits. The usage will depend on what information and in what format . I’ve included some simple examples. For full detail on all information returned and OPERATION \ OPERATION TYPES , refer to the DB2 documentation Method 1 Use the LIST HISTORY command Some examples: # Return history... Read more →