Parameter getting truncated when being passed into procedure call.

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for Oracle
Post Reply
DarrenColes
Posts: 51
Joined: Mon 28 Aug 2006 11:07

Parameter getting truncated when being passed into procedure call.

Post by DarrenColes » Tue 12 Jun 2007 11:21

I'm passing a long parameter (2500 characters in my example) and it gets truncated to 2002 characters when i am running with Unicode=true. However it works fine when Unicode=False. This is using version 3.55.21 of the component.

Here is the package definition im using (just a simple example that returns the lengh of the parameter passed in)


CREATE OR REPLACE PACKAGE BODY PKG_app_test AS

procedure proc_test3(
v_value IN varchar2,
v_result OUT number)
as
begin
select length(v_value) into v_result from dual;
end proc_test3;


END PKG_app_test;

and the C# code im calling it with..

private void button6_Click(object sender, EventArgs e)
{
String ParamValue = "";
OracleConnection oc = new OracleConnection();
oc.ConnectionString = "pooling = false";
oc.Unicode = true;
oc.AutoCommit = true;
oc.Server = "development";
oc.UserId = "schema";
oc.Password = "schema";
oc.Open();

OracleCommand o2 = oc.CreateCommand();
o2.ParameterCheck = true;
o2.CommandType = CommandType.StoredProcedure;
o2.CommandText = "pkg_app_test.proc_test3";
o2.Prepare();
ParamValue = ParamValue.PadLeft(2500, 'A');
o2.Parameters["v_value"].Value = ParamValue;
o2.ExecuteNonQuery();
MessageBox.Show(o2.Parameters["v_result"].Value.ToString());

}

All pretty simple stuff, I hope this allows you to recreate the problem.

Thanks

Darren

DarrenColes
Posts: 51
Joined: Mon 28 Aug 2006 11:07

Post by DarrenColes » Tue 12 Jun 2007 13:50

Also tried upgrading to the latest release and that doesnt resolve the issue.

Alexey
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Post by Alexey » Wed 13 Jun 2007 06:22

I've reproduced this problem. We will investigate it. Look forward to hearing from me again.

Alexey
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Post by Alexey » Thu 14 Jun 2007 13:18

This problem is fixed.
Look forward to the next build.

DarrenColes
Posts: 51
Joined: Mon 28 Aug 2006 11:07

Post by DarrenColes » Thu 14 Jun 2007 13:27

I will, we have a product due to go live quite shortly. Could you suggest how long this might be?

Alexey
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Post by Alexey » Thu 14 Jun 2007 14:03

Hopefully, we will provide the build in two weeks.

DarrenColes
Posts: 51
Joined: Mon 28 Aug 2006 11:07

Post by DarrenColes » Wed 27 Jun 2007 11:32

Any update on when a fix is likely to be released for this?

DarrenColes
Posts: 51
Joined: Mon 28 Aug 2006 11:07

Post by DarrenColes » Mon 02 Jul 2007 08:36

Any news on this yet?

Alexey
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Post by Alexey » Mon 02 Jul 2007 11:08

New version is going to be released this week.
Thanks for your patience.

DarrenColes
Posts: 51
Joined: Mon 28 Aug 2006 11:07

Post by DarrenColes » Wed 04 Jul 2007 14:13

Thanks, based on the limited testing weve done so far, the new build released today appears have resolved it.

Alexey
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Post by Alexey » Thu 05 Jul 2007 06:56

Good news.

Post Reply