Devart Forums

I am using last OraDirect.Net release 3.55.18. Connection parameters Direct=true, Unicode=true. I am calling function with varchar output states in Oracle package. Function always return the same output string.
I am using Oracle command to call function. First call works well. When I am calling this function in loop on 10 or 15 call function starts to return on 1 character less every call. And at the end I am recieving an exception:

CoreLab.Oracle.OracleException occurred
Message="ORA-06502: PL/SQL: numeric or value error: character string buffer too small\nORA-06512: at line 2"
Source="CoreLab.Oracle"
Code=6502
Offset=0
StackTrace:
at CoreLab.Oracle.OracleCommand.a(CommandBehavior A_0, IDisposable A_1, Int32 A_2, Int32 A_3)
at CoreLab.Common.DbCommandBase.c(CommandBehavior A_0)
at System.Data.Common.DbCommand.ExecuteReader()
at CoreLab.Common.DbCommandBase.ExecuteNonQuery()
at Opengaming.UnifiedWizard.WinGroupControl.readBasketFromDB(Group grp, Decimal basketCost, Int32 basketID) in D:\4GCasino\UW\Development\Opengaming.UnifiredWizard\UserControls\WinGroupControl.cs:line 379

Please investigate this problem and fix it as well.
Regards Leonid

Please send me test project to reproduce this problem including the definition of your database objects.

The test project was send to support email.
Also I found that Ora.Direct components fill stored procedure parameters incorrectly when connection works in Unicode=true mode. In this test project when I set OraConnection partameters Direct=true and Unicode = true and then I am tring to set in OraDirect designer from OraCommand stored proc parameters they will be defined incorrectly. Application will be crash on ExecuteNonQuerty. In order to fix problem I must set Unicode=false and reset stored proc parameters and return to Unicode=true. In case when stored proc parameter name is long (20 or 30 chars) and Unicode = true OraCommand designer return parameters cutted.
I waitng for fix ASAP.
Regards, Leonid

We are investigating your test project.
Look forward to hearing from us soon.

We have fixed the problem. Look forward to the next build.

Do you fix probem with fetching stored proc parameters in design time in unicode mode too?

Not yet. We are going to fix this in OraDirect .NET 3.55.20.
I'll expressly inform you.

The problem is fixed. Look forward to the build.