What is the best approach for releasing persistent database connection so that a database recycle can be done.  Currently we are taking done the application server, but is there a way to clear or change the perisistent connection to allow the database to be clear for a recycle without a complete shutdown.    The connections can be forced off on the database (DB2) side but the immediately reconnect.

------------------------------
Jim Shelton
------------------------------

Hello Jim,
you can try the following step to run the backup:
--- snip ---
db2 force application all
db2 deactivate database <db>
db2 backup database <db> to <dir> // or whatever your backup command is
db2 activate db <db>
--- snip ---

Of course the applications will suffer an impact as they can't connect while the database is deactivated but they should reconnect as soon as the db2 activate db is done .

Hope that helps .... Hermann

------------------------------
Hermann Huebler

#IBMChampion
------------------------------

You can either purge the connection pool
or
pause and then restart it

https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.javadoc.doc/web/mbeanDocs/ConnectionFactory.html?view=embed

neither will require the application server to be recycled 

If you're not familiar with using wsadmin to obtain an Mbean reference you can refer to https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.multiplatform.doc/ae/rrun_app_config_conflicts.html

though in your case you'll obtain a reference to the ConnectionFactory Mbean not the ConfigService Mbean as illustrated in the link above

------------------------------
Tom Alcott
Senior Technical Staff Member
IBM
------------------------------