Skip Headers

Oracle® Objects for OLE Developer's Guide
10g Release 1 (10.1)

Part Number B10118-01
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Master Index
Master Index
Go to Feedback page

Limitations on Non-Blocking

The following are limitations on non-blocking mode:

· When a non-blocking operation is underway on an OraSqlStmt object, you cannot change the properties or attributes of this object as it can affect the execution that is in progress.

· You cannot create a OraSqlStmt in Non-Blocking mode if there are other objects that are already instantiated on the connection. In other words, creating an OraSqlStmt object to execute in Non-Blocking mode only succeeds if no other objects, such as OraDynaset and OraAQ, are currently active on the same database session. The only exceptions are OraParameter objects and OraObjects. These are permitted as they may be required for the non-blocking execution.

· While waiting for a non-blocking call to complete, the application cannot invoke any methods or properties on the OraDatabase instance that contains this OraSqlStmt. Applications can overcome this limitation by switching to a different server context. Refer to the example in Executing Multiple Queries in Asynchronous Mode.