How to check for DB2 Direct IO and FILE SYSTEM CACHING

Question : I’m running DB2 9.5 . How do I check the FILESYSTEM CACHING status on a DB2 tablespace? Answer: DB2 bufferpools and Linux filecache perform approximately the same function. Thefunction is : copy data from disk. DirectIO directs reads from disk into DB2 memory.DirectIO is set up on a tablespace by tablespace basis. The tablespace option is NO FILE SYSTEM CACHING Can be applied to: system tablespaces, temporary tablespaces Note: LOB and LONG VARCHAR doesn’t benefit – and continues to use file cache Check FILESYSTEM caching by db2 -v "get snapshot for tablespaces on myDB" | more Check for... Read more →

How to use Db2adutl delete logs

Question: How can I delete old archive logs from Tivoli Storage Manager (TSM) ? I’ve confirmed the TSM backup client configuration for DB2 on Linux is all OK Answer: The db2adutl command comes with DB2. The tool is located in the $HOME/sqllib/adsm directory of the instance owner. You can extract, loadcopies, verify backups , query and delete from TSM. The backup copies in TSM always active and never deleted by normal TSM file expiration processing. The db2adutl utility provides a way of deleting backups and log files that are no longer required This example code demonstrates the delete archive logs... Read more →

Running a Java Program from Command Prompt

Question: I’m receiving this message when attempting to compile some java code: 'javac' is not recognized as an internal or external command, operable program or batch file How can I fix this problem? Answer: If you installed the JDK in C:\jdk1.6.0. At the prompt you would type the following command and press Enter: C:\jdk1.6.0\bin\javac MyDB2.java If you choose this option, you'll have to precede your javac and java commands with C:\jdk1.6.0\bin\ each time you compile or run a program. If the system cannot find javac or java, check the set path command. It is possible to make the path setting... Read more →

SQL0911N Reason Code 68 The current transaction has been rolled back because of a deadlock or timeout

Question : I am seeing this SQL0911N Reason Code 68 message in my DB2 diaglog file: command : db2 backup db MYDB online use TSM include logs SQL0911N The current transaction has been rolled back because of a deadlock or timeout. Reason code "68". SQLSTATE=40001 How do I fix this SQL0911N error? Answer: The DB2 command line error utility shows this detailfor the SQL0911N Reason Code 68 error., indicating that the SQL0911N error is caused by a deadlock or locktimeout. A DB2 ONLINE backup attempts to obtain a IN lock on tables in SMS table spaces. DB2 tries to upgrade... Read more →