DB2 Archived Log Compression

Question: Can I compress DB2 LUW archived logs? How can I configure a DB2 database to apply compression to the archived logs automatically? Answer: It is possible to configure a DB2 LUW database to compress Archived Logs. The two primary database configurables are to use Primary log archive compression (logarchcompr1) and secondary log archive compression (logarchcompr2). By simply changing the default value of NO to YES , does not automatically mean there will be archival logging compression. LOGARCHMETH1 must be set to either DISK, TSM, or VENDOR. If these values are not used there will be no compression of archivedlog... Read more →

DB2 Archived Log Compression

Question: Can I compress DB2 LUW archived logs? How can I configure a DB2 database to apply compression to the archived logs automatically? Answer: It is possible to configure a DB2 LUW database to compress Archived Logs. The two primary database configurables are to use Primary log archive compression (logarchcompr1) and secondary log archive compression (logarchcompr2). By simply changing the default value of NO to YES , does not automatically mean there will be archival logging compression. LOGARCHMETH1 must be set to either DISK, TSM, or VENDOR. If these values are not used there will be no compression of archivedlog... Read more →

How to block database connections

During a recent consultation there was a requirement to block DB2 LUW database connections. The purpose was to test monitoring alerts and assess the correct response when a database connection could not be established. The requirement was to maintain the DB2 instance active and all the other databases as online An easy way to block database connections is to use the MAXAPPLS database configurable. This parameter specifies the maximum number of concurrent applications that can be connected (both local and remote) to a database. The trick is to set the DB2 LUW database MAXAPPLS configurable to 1, and ensure that... Read more →

Cannot drop database SQL1035N The operation failed because the specified database cannot be connected to in the mode requested. SQLSTATE=57019

I cannot drop the database and getting the error message SQL1035N The operation failed because the specified database cannot be connected to in the mode requested. SQLSTATE=57019 What is the safest way to work around this problem? Answer: The DB2 error message appears because the current database is not a valid state for the DROP DATABASE command you’re attempting to commit. From the IBM DB2 LUW documentation “The database must not be in use; all users must be disconnected from the database before the database can be dropped”. Before you deactivate the database , speak with the application owner and... Read more →

How to check DB2 LUW database write suspend state with db2pd

DB2 LUW write suspend state is commonly checked during a splitting of mirrored database.I’d like the flexibility of checking via the db2pd monitoring tool, How can I get the output in db2pd to check if a DB2 database is in the write suspend state? Answer: There’s a couple of different things you can check in this situation. The db2pd tool will allow you to check and report on the database configuration and to identify if the database is in write suspend state. This command will return the relevant information. Check for the item “database is in write suspend state” db2pd... Read more →