Devart Forums

Hello out there,
I have a stored procedure that has a blob parameter. I can call this using client mode without problems with this code

procedure TIWUserSession.SchreibeBlob(const dateiname: string);
var
b :TOraLob;
begin
b := TOraLob.Create(OraSession.OCISvcCtx);
b.CreateTemporary(ltBLob);
b.LoadFromFile(dateiname);
b.WriteLob;
with OraStoredProcBlobNachDir do
begin
ParamByName('B').AsOraBlob := b;
ParamByName('DIR').AsString := 'ELO_IMPORT';
ParamByName('DATEI').AsString := ExtractFileName(dateiname);
Execute;
ParamByName('B').AsOraBlob.FreeLob;
end;
OraSession.Commit;
b.Free;
end;

But when I use direct mode, I get an ORA-00600 [kkxlrd csid mismatch], [0], [178], [0], [1], [], [], []

I suspect OraSession.OCISvcCtx is not valid in direct mode. Now the question is, how do I call a stored procedure with a blob parameter in direct mode?

I'm using ODAC 6.70.0.44 with Delphi2009 and Oracle 10.2.0.4.

Many thanks in Advance,
dhalek

OCISvcCtx can be used in the Direct mode. We could not reproduce the problem. Please send to odac*devart*com a complete small sample that demonstrates the problem, including the script for creating database objects.

Plash wrote:OCISvcCtx can be used in the Direct mode. We could not reproduce the problem. Please send to odac*devart*com a complete small sample that demonstrates the problem, including the script for creating database objects.

I just sent an example. Hope that helps solving the problem.

Regards,
dhalek

Hi Plash,

What is the current status for this bug? Did you manage to reproduce it using the sample code from dhalek. We seem to encounter a similar problem (but only in "OCIUnicode=true" mode) in 6.8.0.50. This is why we are wondering too...

Thanks a lot,
Александр

But we could not reproduce this problem.
Please send to odac*devart*com a complete small sample that demonstrates the problem, including the script for creating database objects.

Sent you an e-mail
Created: Tue, 15 Sep 2009 19:34:07 +0200
Subject: Sample code for #14385 and #15010
Attachments: TestODAC.rar

Sorry guys, but this is getting a bit pressing. You said that you managed to reproduce the BLOB problem using my sample app. Any update on this one?

We have fixed the problem with BLOB. The fix will be included in the next build of ODAC.