Skip to Main Content

DevOps, CI/CD and Automation

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

ODBC call failed Error 63535

518591Jun 16 2006
I have a Ms-Access 2002 SP3 client and Oracle DB 9i in Solaris Unix. Through Access and by using ODBCDirect I post asynchronous queries to the Oracle Server.

Somewhere in the code I periodically check the value of the StillExecuting flag for the recordset bound to the posted query. The error will appear at no specific time by just checking the value of the StillExecuting. However by using the Toad Client by Quest, I have monitored the sessions and found out that:

1. The error will appear only if the Oracle optimiser did not break up the original query into multiple ones (using parallelism) thus executing as a single query.

2. When the single query reaches an amount of 7000000~11000000 physical reads.

3. The session remains paused until I kill the Access application.

However if the query is optimised by Oracle Optimiser then the results are fetched normally once the query is finished with no errors.

Is there any time, resources, connection, query limits set by Oracle? I have set to 0 all Ms-Access timeouts (query and connection). Queries sent by Toad if not optimised finish just fine. Does my ODBC driver has a problem since the Toad Client does not use ODBC? I use is the Oracle ODBC V.9.00.11.00 driver.
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jul 14 2006
Added on Jun 16 2006
0 comments
1,925 views