Error ORA-1003

[khang]

I use an TOracleDataset to make a query. Ramdomly I got ORA-1003 error when I open my dataset. I mean with the same query and the same parameters my query work and suddenly I got the ORA-1003 error once and if I try to reopen my query again, it work.
I use ORACLE 8.1.7 standard Edition server.
My oracle client is an old oracle 7.3.4 SQL*NET client.

I question Oracle about this problem. They explain me that one possible cause is that the OCI parse procedure return an error but DOA didn't report it so I got this message when I open my query.

Hase anyone any suggestion to solve the problem or to trace my execution to point out the exact error.

Thank you

 

[Marco Kalter]

I have not had any problem reports about this before, so I can't give you any immediate hints. Theoretically this should not happen. Can you use the Oracle Monitor to capture some information when this error occurs? Or is it too random?

------------------
Marco Kalter
Allround Automations

 

[khang]

This problem is very random, but once it occurs it remain until you quit the application. So, I will try to trace with oracle monitor.

Thank you for your quick reply.

 

[khang]

One possible logical reason of this error is that the OParse function return an error that isn't trap. So you got the error when you open the query . So my question are:
1- Do DOA ALLWAYS make an OParse before opening the query ?
2- When DOA call the OParse function does it trap any error an raise an exception for it ?
3- to summary, are you sure that you got a valid cursor before opening it.

 

[Marco Kalter]

Originally posted by khang:
1- Do DOA ALLWAYS make an OParse before opening the query ?

Yes, unless it involves a TOracleQuery that is assigned to a otCursor variable (see Cursor Variables in the help file). Executing a TOracleQuery for a cursor variable that is not opened can lead to ORA-01003. I'm sure that this is not the case here though.

Originally posted by khang:
2- When DOA call the OParse function does it trap any error an raise an exception for it ?

Yes.

Originally posted by khang:
3- to summary, are you sure that you got a valid cursor before opening it.

Yes, with the exception of cursor variables, which need to be opened by the application.

------------------
Marco Kalter
Allround Automations