Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / June 2006

Tip: Looking for answers? Try searching our database.

Quiesce behavior

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
sethwai@yahoo.com - 19 Jun 2006 22:00 GMT
Hi,

  When executing a quiesce immediate on a database does the command
wait for all connections to be off the database before completing or
does it act asynchronously?  

Lew
Jayesh Thakrar - 20 Jun 2006 15:03 GMT
If you look up DB2 documentation, you will see that it has an option to
"force connections". If you do specify it, then it will force
connections. Your options are -
(1) wait for all transactions to commit
(2) wait a specified time for transactions to commit (if they do not
commit then force the connections)
(3) force them immediately

> Hi,
>
[quoted text clipped - 3 lines]
>
> Lew
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.