Hi

I'm experiencing problems when freeing a temporary TLobLocator at certain times.

My TOracleQuery calls a stored proc which has a CLOB parameter for saving data. The stored proc then calls another stored proc and passes the CLOB parameter through.

It would appear that when the parameter in the second stored proc is declared as a CLOB, an exception is generated in Delphi when I come to free the temporary TLobLocator.

If the second stored proc uses a long parameter, there is no problem. However, we really need it to be a CLOB because of the amount of data we are sending.

Can you please help?

(Using DOA 4.0.3)

Many thanks
Chris

What exactly is the exception message?

It's very strange. There is an exception, it is captured by the exception handler, however there is NO message. (i.e. E.message="")

1. Have downloaded DOA 4.0.5 - Same problem occurs.

2. Although exception message is blank, if I use EOracleError the exception numbers raised are:-
32550540, 33070844, 32554684, 32553312
If I "unload" my delphi app from IIS and try again I get the same sequence of error numbers(!)

These numbers don't seem right. What is the Exception class (EOracleError or something else)?

Here is my code:

try
myCLOB.Free;
except
on E: EOracleError do
begin
LogAction('Save Dealer Exception - Unable to free Temporary CLOB'+#13#10+
'mess='+e.Message+' num='+FloatToStr(E.ErrorCode));
end;
end;

and here is an extract from my log file:

29/06/2004 10:42:57 Save Dealer Exception - Unable to free Temporary CLOB
mess= num=32550540
29/06/2004 10:42:58 Save Dealer Exception - Unable to free Temporary CLOB
mess= num=33070844
29/06/2004 10:43:17 Save Dealer Exception - Unable to free Temporary CLOB
mess= num=32554684
29/06/2004 10:43:18 Save Dealer Exception - Unable to free Temporary CLOB
mess= num=32553312

If the exception was not an EOracleError surely this handler will not capture the exception(?)

It is indeed an EOracleError. The bogus error code makes me wonder if the session is still connected at this time. Can you verify this?

Yes. The TOracleQuery.Session.Connected property is still true at this point.

Okay. Can you send me a little demo project that reproduces the issue?

Demo project and stored procs sent as requested.

To summarise: Delphi would appear to be unable to free the temporary LOB, only when all the following are true:-
1) OracleQuery calls a stored proc which calls another
2) Both stored procs have a CLOB input parameter
3) Both stored procs evaluate the CLOB as XML

I eagerly await your comments.