How To Contact Jack Vamvas

Jack Vamvas is a full time DBA with in depth experience of DB2 LUW, SQL Server, MongoDB and PostgresQL . In the meantime , You can find Jack on twitter.com/jackvamvas, LinkedIn , http://www.dba-db2.com , http://www.dba-ninja.com , http://sqlserver-dba.com Improve SQL Server and DB2 performance. I identify and solve bottlenecks fast. Cut through the complexity with proven solutions to problems. Don't waste money on expensive hardware upgrades. I've posted a list of Frequently Asked Questions . Check to see if your question is answered otherwise use the methods listed below to contact me. I enjoy marathon training and running marathons Post a... Read more →

TSM losing connection with DB2

Platform ------------------------------- OS = RedHat Linux ESE 4.6 32 bits DB2 versiion = v9.1.0.3 DB2 code release = SQL09013 Tivoli Storage Automation (TSA) = SAFMP V310 Problem -------------------------------- Assumption - installed OK - and system has been running OK i.e scheduled backups and archived logging working OK . The problem can be created with the following step: 1)Upon issuing a db2_kill TSA restarts the instance - which it does so successfully. But at that point : a)issuing a "backup database MYDB online use TSM" b)archival logging both return a (in db2diaglog): TSM RC=0x0000006A=106 -- see TSM API Reference for meaning.... Read more →

DM1823E - Log file has reached its saturation point

This set of messages appeared as separate , but in a row - which indicates it's one underlying problem ADM1822W The active log is being held by dirty pages. DM1823E The active log is full and is held by application handle "79". Terminate this application by COMMIT, ROLLBACK or FORCE APPLICATION. Log File has reached its saturation point" DIA8309C Log file was full. There is an DB2 error message indicating that the transaction log for the database is full. Cause: The LOGFILSIZ_DB2 parameter is set too low. Solution: Increase the LOGFILSIZ_DB2 parameter using the following command: db2 update database configuration... Read more →

DB2 Indoubt transactions

DB2 9.1.3 ESE I had a crash recovery on DB2 and found the database to not be in a valid state, with the following message: In-doubt transaction(s) exists at the end of crash recovery. The main reason is log file size not large enough I resolved this situation by 1)Connect to relevant database: 2)Issue the following command: db2 list indoubt transactions with prompting 3)decide an action - Ref:Jack Vamvas(http://www.dba-db2.com) Read more →

ADM1823E active log file full

I found this message in the db2diag.log : ADM1823E The active log is full and is held by application handle "371". Terminate this application by COMMIT, ROLLBACK or FORCE APPLICATION. Doing some research there were a couple of potential causes 1.Potentially long running query - not commiting i.e database configured to run 12 log files on a circular. If the transaction has not been commited and you go through the 12 log files - then try to write to log file 1 again - which is still holding the open transaction, then you've got a problem. This is one possible... Read more →