23 March,2013 by Jack Vamvas
Taking a OFFLINE DB2 backup requires shutdown of all database connections . Often you'll see the SQL1035N The database is currently in use mesage. There are a number of workarounds to achieve the outcome of starting the OFFLINE backup, such as :
db2 force applications all --or QUIESCE DATABASE IMMEDIATE FORCE CONNECTIONS
Sometimes the required outcome does not occur., particularly with very persistent connection attempts.
One method of blocking connections to the DB2 database server instance is to change the SVCENAME configuration parameter. This forces the attempted connections to all databases on the instance to fail. If you don’t want all connections to the database server instance to be blocked, do not use this method.
Once you’ve completed the OFFLINE backup , change the SVCENAME back to the original value .
db2 UPDATE DBM CFG USING SVCENAME 50006