Hi,
I am using a older version of odac 5.8 and have come across a problem i hope someone can help with. I am posting to an oracle stored procedure with a clob that can contain some unicode characters. I can see the value of the vclob has changed after i run loadfromfile eg:
File contains=Jak Anioła głos
VClob contains=JAK ANIOÅ'#$81'A GÅ'#$81'OS
Is there anyway around this - do i need to encode the data or do i need to look at the latest version of odac?
thanks,
jp
ps. Here is my code just in case i've made a mistake:
with sp_Post do
begin
vClob := TOraLob.Create(dmIAPSNew.oraIAPS.OCISvcCtx);
vClob.CreateTemporary(ltClob);
vClob.LoadFromFile(ExtractFilePath(ParamStr(0)) + 'myfile.XML');
vClob.WriteLob;
ParamByName('MYDOC').AsOraClob := vClob;
ParamByName('DEBUGMODE').Clear;
ParamByName('OUTPUT').Clear;
Execute;
end;
vclob & unicode
vclob & unicode
Hi,
I have now installed the latest version of ODAC v6.8 and am getting an error with my previous code which was kind of working apart from the unicode bit. I now get an exception error on the line:
vClob.WriteLob;
Can anyone point me in the right direction on this?
thanks,
jp
I have now installed the latest version of ODAC v6.8 and am getting an error with my previous code which was kind of working apart from the unicode bit. I now get an exception error on the line:
vClob.WriteLob;
Can anyone point me in the right direction on this?
thanks,
jp
vclob & unicode
Hi,
When connected in direct mode i get an EAccessViolation error when executing the stored procedure. If I connect non direct i get an ORA-03113 after about 5 seconds of calling the store procedure.
Any ideas why i am seeign these problems. Let me know if there is anything I can try or of you can replicate the problem.
thanks,
jp
When connected in direct mode i get an EAccessViolation error when executing the stored procedure. If I connect non direct i get an ORA-03113 after about 5 seconds of calling the store procedure.
Any ideas why i am seeign these problems. Let me know if there is anything I can try or of you can replicate the problem.
thanks,
jp