Can anyone explain the difference betweeen synchronous and asynchronous mode in designer in detail or at least point me to any source which will give me this information?
How do these modes affect query performance?
Asynchrorous mode allows our user base to use the ESC key to cancel queries. Where as synchronous mode waits for the thread to complete before ESC responds.
Using MVS/DB2 via IBM/CAE middleware. Hope this helps.
Christopher J. Pohl
Mellon Financial Corporation
Corporate Information Systems Group/SED
EMail: pohl.cj@mellon.com
Good explanation. If you look at the BO database guide for whatever database you are using, there is a good explanation. Also, it doesn’t have an effect on query performance. I prefer Asynchronous for the reason below. It also seems to make your PC more useable during a query.
SQL*Net 2.2 is not interruptable. If you upgrade your server so 2.3, and change the connection to ASYNC, I believe it will solve the problem on the sever and client.
Chris,
we are using Oracle 7.3 and SQL*NET 2.2 as middleware. Our universe has been defined with a synchronous mode. While running a query through Web I, if we try to stop the query by clicking on cancel query button, Web i does come back to the query panel, but the query keeps on running on the database.We can know this via Oracle performance monitor on the database server.Is there a way to stop the query on the database side as well. Does asynchronous mode stop the query on the database when the escape key is pressed.
Thanks
Saket
Chris wrote :
Asynchrorous mode allows our user base to use the ESC key to cancel queries. Where as synchronous mode waits for the thread to complete before ESC responds.
Using MVS/DB2 via IBM/CAE middleware. Hope this helps.
Christopher J. Pohl
Mellon Financial Corporation
Corporate Information Systems Group/SED
EMail: pohl.cj@mellon.com
Asynchronous mode should cancel the query on the server as well. I’ve always tried to use asynchronous mode but I believe (and it may have been fixed since now since I haven’t worked with it in a bit but…) that there is a problem with LOV’s in WebI when you use asynchronous mode so we had to switch back to synchronous.
Julie
Chris,
we are using Oracle 7.3 and SQL*NET 2.2 as middleware. Our universe has been defined with a synchronous mode. While running a query through Web I, if we try to stop the query by clicking on cancel query button, Web i does come back to the query panel, but the query keeps on running on the database.We can know this via Oracle performance monitor on the database server.Is there a way to stop the query on the database side as well. Does asynchronous mode stop the query on the database when the escape key is pressed.
We will soon be migrating our database to Oracle 8.1 .Hope SQL NET 8/OCI are interruptable.
Thanks,
Saket
steve wrote :
SQL*Net 2.2 is not interruptable. If you upgrade your server so 2.3, and change the connection to ASYNC, I believe it will solve the problem on the sever and client.
Wow,I would like to know more about problems with LOV’s while using asynchronous mode, could you please elaborate. Thanks in advance,
Saket
Asynchronous mode should cancel the query on the server as well. I’ve always tried to use asynchronous mode but I believe (and it may have been fixed since now since I haven’t worked with it in a bit but…) that there is a problem with LOV’s in WebI when you use asynchronous mode so we had to switch back to synchronous.
Julie
Chris,
we are using Oracle 7.3 and SQL*NET 2.2 as middleware. Our universe has been defined with a synchronous mode. While running a query through Web I, if we try to stop the query by clicking on cancel query button, Web i does come back to the query panel, but the query keeps on running on the database.We can know this via Oracle performance monitor on the database server.Is there a way to stop the query on the database side as well. Does asynchronous mode stop the query on the database when the escape key is pressed.
There are probs and BusObj recommend synchronous connections for Webi even though it’s a pain. I think this is because they haven’t fixed the bugs yet(they wouldn’t say this!) especially since they recommend asynch connections for client-server!
Regards
Jonathan
Project Leader
Group Medical, Regulatory and Product Strategy IS.
Wow,I would like to know more about problems with LOV’s while using asynchronous mode, could you please elaborate. Thanks in advance,
Saket
Asynchronous mode should cancel the query on the server as well. I’ve always tried to use asynchronous mode but I believe (and it may have been fixed since now since I haven’t worked with it in a bit but…) that there is a problem with LOV’s in WebI when you use asynchronous mode so we had to switch back to synchronous.
Julie
Chris,
we are using Oracle 7.3 and SQL*NET 2.2 as middleware. Our universe has been defined with a synchronous mode. While running a query through Web I, if we try to stop the query by clicking on cancel query button, Web i does come back to the query panel, but the query keeps on running on the database.We can know this via Oracle performance monitor on the database server.Is there a way to stop the query on the database side as well. Does asynchronous mode stop the query on the database when the escape key is pressed.