itsonlyme4
asked on
Quiesce Database and deactivate/active Database to free memory
Occasionally we have DB backups fail because of insufficient memory (Db2 9.7 running on a 32bit OS)
What I would like to do is force all connections and Deactivate/Activate the Database like this:
db2 CONNECT TO MYDB;
db2 list applications for database MYDB show detail
# QUIESCE the database to force all connections
db2 QUIESCE DATABASE IMMEDIATE FORCE CONNECTIONS;
db2 CONNECT RESET
# DEACTIVATE the database
DB2 Attach to DB2
DB2 DEACTIVATE DB MYDB
# ACTIVATE the database
DB2 Attach to DB2
DB2 ACTIVATE DB MYDB
My question is.... is the QUIESCE necessary or will the Deactivate command force connections???????
What I would like to do is force all connections and Deactivate/Activate the Database like this:
db2 CONNECT TO MYDB;
db2 list applications for database MYDB show detail
# QUIESCE the database to force all connections
db2 QUIESCE DATABASE IMMEDIATE FORCE CONNECTIONS;
db2 CONNECT RESET
# DEACTIVATE the database
DB2 Attach to DB2
DB2 DEACTIVATE DB MYDB
# ACTIVATE the database
DB2 Attach to DB2
DB2 ACTIVATE DB MYDB
My question is.... is the QUIESCE necessary or will the Deactivate command force connections???????
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I just posted another question because I issued the db2 QUIESCE DATABASE IMMEDIATE FORCE CONNECTIONS and it is hanging.. this is what I'm seeing in the log:
MESSAGE : ADM2017C The Event Monitor "DB2DETAILDEADLOCK" has reached its file
capacity. Delete the files in the target directory
"C:\DB2\NODE0000\SQL00001\
another directory.
There are a bunch of .evt file and one .cnt file in the db2detaildeadlock folder.
not sure if I should move them ALL??