Re: Oracle/Access ODBC Error

Yes, this is because the 8.0.5.x drivers now support query timeouts, which the older drivers did not. By default all queries created in Access have a 60-second timeout, and unless the designer of the query (or coder of the program) overrides it, that will be the case. Most times, re-running the query succeeds because most of the data required for the query is already in the cache, the SQL has already been parsed and an execution plan generated, etc., so it takes less time the second time around.

You can do one of two things:

1. Modify your queries to have proper timeouts, or timeouts of 0 (meaning never timeout).
2. Upgrade to the 8.0.5.5 ODBC driver, and use the DSN configuration option in the ODBC administrator to turn off query timeouts.

BTW, this issue is well covered in the online help with the ODBC drivers, and also on Metalink. If you look there first, you can find lots of useful information before going to the newsgroups :-)

Michael M <~okana_at_msn.com> wrote in message news:H2v73.95$MB.7120_at_news3.usenetserver.com...
> Question - it's not critical but annoying and I was wondering if anyone
else
> has seen this.
>
> Oracle 8.0.5 on NT - Client boxes on Win95/98
>
> Since updating to the 8.0.5.x ODBC drivers an error comes up infrequently
in
> Access queries against the Oracle tables.
>
> "ORA-01013: user requested cancel of current operation"
>
> It stops the current query - we can re-run it and watch the query finish
> without a problem. According to documentation that error means that the
> user used ctrl-C or another cancelling operation to stop the query. In
each
> case that is not true. The query has been suspended on it's own.
>
> We've noticed this since going to the 8.0.5 ODBC drivers, I think the
latest
> we have installed on any machine is 8.0.5.2
>
> Does anyone have any information on this?
>
> Michael Milliron
> mikem_at_msamail.com
> okana_at_msn.com
>
>
>
>
>
>
Received on Wed Jun 09 1999 - 19:49:53 CEST