ORA-12899: value too large for column (actual: 56, maximum: 14) after calling package function

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for Oracle
Post Reply
hansjoergp
Posts: 39
Joined: Wed 31 May 2017 14:33

ORA-12899: value too large for column (actual: 56, maximum: 14) after calling package function

Post by hansjoergp » Mon 15 Jul 2019 12:18

Hello,

after updating to the newest dotConnect for Oracle, I get the following exception:

Unhandled Exception: Devart.Data.Oracle.OracleException: ORA-12899: value too large for column "RADIX"."ARTICLE_TEST"."ARTID" (actual: 56, maximum: 14)

It seems that the error happens after Devart.Data.Oracle Version="9.6.621". v.9.6.646 is the first version in which I get the error.
It happens allways If you have an out parameter with CHAR, which is used inside the package to write some value to the database

Code: Select all

PACKAGE BODY PACKTESTHP
IS

   FUNCTION test
     ( artid OUT article_test.artid%TYPE)
     RETURN  NUMBER
    IS
   BEGIN 
      artid := getartid;
      INSERT INTO ARTICLE_TEST
         (ARTID)
         VALUES (artid);
      RETURN 1;   
   END;
   
   FUNCTION getartid
     RETURN  CHAR
   IS
     v_tonerartid   CHAR(14) := '00000000000001';
   BEGIN
      return v_tonerartid;
   END;

END;
I have send you with the contact form an example.

Shalex
Site Admin
Posts: 9543
Joined: Thu 14 Aug 2008 12:44

Re: ORA-12899: value too large for column (actual: 56, maximum: 14) after calling package function

Post by Shalex » Wed 17 Jul 2019 18:50

Thank you for your report. We will investigate the issue and notify you about the result.


Shalex
Site Admin
Posts: 9543
Joined: Thu 14 Aug 2008 12:44

Re: ORA-12899: value too large for column (actual: 56, maximum: 14) after calling package function

Post by Shalex » Mon 19 Aug 2019 10:16

The investigation is in progress. As soon as we have any results, we will notify you.

hansjoergp
Posts: 39
Joined: Wed 31 May 2017 14:33

Re: ORA-12899: value too large for column (actual: 56, maximum: 14) after calling package function

Post by hansjoergp » Mon 16 Sep 2019 11:34

We've been waiting two months for a solution to this problem. How long will it take?

Shalex
Site Admin
Posts: 9543
Joined: Thu 14 Aug 2008 12:44

Re: ORA-12899: value too large for column (actual: 56, maximum: 14) after calling package function

Post by Shalex » Fri 20 Sep 2019 18:13

Your function doesn't work with ODP.NET and Managed ODP.NET as well.

Our investigation is in progress:
* we have just supported your function in the OCI mode (via Oracle Client). Are you interested in the internal build with the fix?
* as soon as we have any result with the Direct mode, we will notify you

hansjoergp
Posts: 39
Joined: Wed 31 May 2017 14:33

Re: ORA-12899: value too large for column (actual: 56, maximum: 14) after calling package function

Post by hansjoergp » Thu 26 Sep 2019 05:36

Can I have the internal Build? Thank you

Shalex
Site Admin
Posts: 9543
Joined: Thu 14 Aug 2008 12:44

Re: ORA-12899: value too large for column (actual: 56, maximum: 14) after calling package function

Post by Shalex » Tue 01 Oct 2019 15:41

We have sent the internal build to your email.

Shalex
Site Admin
Posts: 9543
Joined: Thu 14 Aug 2008 12:44

Re: ORA-12899: value too large for column (actual: 56, maximum: 14) after calling package function

Post by Shalex » Thu 24 Oct 2019 16:54

The bug with executing stored procedure or function with Out/InOut parameter, when its type is CHAR and the parameter precision is determined by the length of a target column, is fixed: viewtopic.php?f=1&t=39475.

Post Reply