PL/SQL: digital or value error: character number conversion in the TRG error

Hello
I have a strange problem with a trigger that, during the update of the table of reports (DB is 9.2.0.8):

ORA-06502: PL/SQL: numeric or value error: character to number conversion error
ORA-06512: at "UDR_LOG", line 345
ORA-04088: error during execution of trigger 'UDR_LOG'

but the 345 line is:
END IF;

This kind of strange

the code looks like

343 IF nvl(to_char(:old.PKD_ID),'''') <> nvl(to_char(:new.PKD_ID),'''') THEN
344     v_zmn := v_zmn || 'PKD_ID''' || to_char(:old.PKD_ID) || '''' || to_char(:new.PKD_ID) || '''';
345    END IF;

so its concatenation not to_number usage .

error is raised by the update on a column.

I'm sorry that I can't provide you with the code in the trigger everything.
So, if you could recommend only whole method of inquiry that would be great.
Concerning
Greg

Hi, Greg.

When there is an error in a trigger, the line numbers in error messages are compared to the first statement DECLARE or BEGIN; often, it is a few lines after CREATE OR REPLACE TRIGGER. Post a few lines after what you have already posted.

If you do not find the error, then create another table to test this and create a small trigger on that table, who did just enough to cause the error. Then, you will be able to post the complete relaxation, and the code needed to recreate the problem.

Tags: Database

Similar Questions

ORA-06502: PL/SQL: digital or value error: character of error number

Hello gurus,

I get the following error:
ORA-06502: PL/SQL: digital or value error: character of number conversion error

It happens on wizard generated in a table.

DECLARE
v_venue_prsntd_qtr varchar2(3);
v_venue_prsntd_fy  number;

BEGIN
FOR i IN 1 .. apex_application.g_f02.COUNT
  LOOP
    IF apex_application.g_f05 (i) IS NOT NULL THEN 
        v_venue_prsntd_qtr := 
         Case WHEN TO_CHAR(apex_application.g_f05 (i), 'MON') IN ('OCT','NOV','DEC') THEN '1'
              WHEN TO_CHAR(apex_application.g_f05 (i), 'MON') IN ('JAN','FEB','MAR') THEN '2'
              WHEN TO_CHAR(apex_application.g_f05 (i), 'MON') IN ('APR','MAY','JUN') THEN '3'
              ELSE '4'
              END;
  -- INTO v_venue_prsntd_qtr
  -- FROM venue_prsntd
  -- WHERE venue_prsntd_seqno = apex_application.g_f02 (i) 
  -- AND dfcy_seqno = apex_application.g_f03 (i)
  -- AND apex_application.g_f05 (i) IS NOT NULL; 
----fiscal year
 --    v_venue_prsntd_fy := 
 --       CASE WHEN TO_CHAR(TO_NUMBER(TO_CHAR(apex_application.g_f05(i), 'MMDD'))) < 1001 THEN --------TO_CHAR(apex_application.g_f05 (i),'YYYY')
--        ELSE TO_CHAR(TO_NUMBER(TO_CHAR(apex_application.g_f05 (i),'YYYY')) + 1) 
--      END;

   --  INTO v_venue_prsntd_fy
   --  FROM venue_prsntd
   --  WHERE venue_prsntd_seqno = apex_application.g_f02 (i) 
   --  AND dfcy_seqno = apex_application.g_f03 (i) 
   --  AND apex_application.g_f05 (i) IS NOT NULL; 
   --  
---END IF;
  --- IF apex_application.g_f02 (i) IS NULL AND apex_application.g_f05 (i) IS NOT NULL Then 
          -- INSERT INTO venue_prsntd(venue_prsntd_qtr, venue_prsntd_fy)
          --                   VALUES(v_venue_prsntd_qtr, v_venue_prsntd_fy);
             UPDATE VENUE_PRSNTD
                  SET VENUE_PRSNTD_QTR = to_number(v_venue_prsntd_qtr)
                     -- VENUE_PRSNTD_FY = v_venue_prsntd_fy
             WHERE VENUE_PRSNTD_SEQNO = APEX_APPLICATION.G_F03(i);
END IF;
END LOOP;
END;

I'm trying to update venue_prsntd_qtr. I commented all the rest to see if I can limit the error is coming from.

QTR is a numeric field in the database. I have gone back and forth with the variable type in the code and still get the same error.

I use oracle db 10g, apex 3.2.1

Thank you
Mary

Hi, I don't think it's possible to integrate with the routine auto mru. What you can do is to use a trigger to insert database after the cessation of the to do.

Otherwise, you will still need a separate process Apex which runs after the SRM process.

Luis

ORA-06502: PL/SQL: digital or value error: character buffer t string

I understand the error, but I don't know where is the case,
The error
Exception: ORA-06502: PL/SQL: digital or value error: character buffer t string
Little OO

I know that to be here: but it makes no sense I got anought space, I got same increse VARCHAR2 (42); for VARCHAR2 (100);
I guess my question is is there a way to debug, so I can see exactly which variable creates the problem.
There is a lot of code, I hate to put all the code here, please help I'm stuck!

 PROCEDURE process2 (
      v_aidy_code   IN   faismgr.rorstat.rorstat_aidy_code%TYPE
   )
   IS
      v_filename1          VARCHAR2 (42);
      v_filename2          VARCHAR2 (42);
      v_path               VARCHAR2 (26);
      v_file_out1          UTL_FILE.file_type;
      v_file_out2          UTL_FILE.file_type;
      w_pidm               faismgr.rorstat.rorstat_pidm%TYPE;
      w_match1_no          NUMBER;
      w_match2_no          NUMBER;
      w_match3_no          NUMBER;
      w_match4_no          NUMBER;
      w_match5_no          NUMBER;
      w_match6_no          NUMBER;
      w_match7_no          NUMBER;
      w_match8_no          NUMBER;
      w_pidm_check         faismgr.rorstat.rorstat_pidm%TYPE;
      w_ssn_check          saturn.spbpers.spbpers_ssn%TYPE;
      w_idoc_id_no_check   NUMBER;
      w_pidm_no            NUMBER;
      w_comment            ryridoc_cover.nomatch_comment%TYPE;
      w_ryridoc_insert     VARCHAR2 (1);
      w_tgrp_code          faismgr.rorstat.rorstat_tgrp_code%TYPE;
      w_ntf                VARCHAR2 (1);
      d_space5             VARCHAR2 (5);
      w_no_recs            NUMBER;
      w_no_1recs           NUMBER;
      w_no_2recs           NUMBER;
      w_no_notprocessed    NUMBER;
      w_no_questionable    NUMBER;
      w_no_subsequent      VARCHAR2 (1);  

BEGIN
           --v_path := '/' || SUBSTR (database_name, 1, 4)
      ----          || '/u02/sct/banner/bandev2/middlebury/dat_files';
       v_path     :=        'MIDD_DATA' ;
      v_filename1 :=
              'idoc_nomatch' || TO_CHAR (SYSDATE, 'yyyymonddhhmiss')
              || '.lis';
      v_filename2 :=
                'idoc_error' || TO_CHAR (SYSDATE, 'yyyymonddhhmiss')
                || '.lis';
      v_file_out1 := UTL_FILE.fopen (v_path, v_filename1, 'w');
      v_file_out2 := UTL_FILE.fopen (v_path, v_filename2, 'w');
      d_space5 := '     ';
      w_no_recs := 0;
      w_no_1recs := 0;
      w_no_2recs := 0;
      w_no_notprocessed := 0;
      w_no_questionable := 0;
      w_match1_no := 0;
      w_match2_no := 0;
      w_match3_no := 0;
      w_match4_no := 0;
      w_match5_no := 0;
      w_match6_no := 0;
      w_match7_no := 0;
      w_match8_no := 0;

Certainly an improvement, you are now thank yourself.

You are welcome, regardless of the problem.

Concerning
Peter

not able to seeds and release - error report: 06502: PL/SQL: digital or value error: character string buffer too small.

Hello
After an upgrade of 4.2.4 5.0.0 we aren't able to seeds and publish the translation.
There is report error: ORA-06502: PL/SQL: digital or value error: character string buffer too small.
DB version is 11.2.0.3.0.
Main language 'fr', translation 'sk '.
APEX day language is "en".
Any thoughts?

Hello

Fortunately, we have solved the problem.

After upgrading a default sort to the report was to 'language '.

If report error, that is fair enough to click on a prompt different orders of the report to change the sorting of the report.

(the blank report is displayed at the bottom of the page, and you can see the guests)

After the click the report updates and looks OK.

Good day.

ORA-06502: PL/SQL: digital or value error: character string buffer too small in the functions

Hi all
FUNCTION to CREATE or REPLACE fnc_two (p_in_job IN VARCHAR2)
RETURN VARCHAR2
AS
CUR CURSOR
IS
SELECT ename
WCP
WHERE job = p_in_job;
v_first_name emp.ename%TYPE;
BEGIN
FOR my heart IN rec
LOOP
IF v_first_name IS NULL
THEN
v_first_name: = rec.ename;
ON THE OTHER
v_first_name: = v_first_name | ',' || Rec.Ename;
END IF;
END LOOP;
RETURN v_first_name;
END;
SQL > SELECT fnc_two ('CLERK')
2 FROM dual;
SELECT fnc_two ('CLERK')
*
ERROR on line 1:
ORA-06502: PL/SQL: digital or value error: character string buffer too small
ORA-06512: at the 'APPS '. FNC_TWO', line 17
SQL > select distinct work of emp
2.
JOB
---------
CLERK
SELLER
PRESIDENT
MANAGER
ANALYST

v_first_name: = v_first_name | ',' || Rec.Ename;

The above statement is the original error. The value has been assinged to v_first_name is larger than the computer can handle.

Increase the size of the variable v_first_name to avoid the error example

v_first_name varchar2 (100);

ORA-06502: PL/SQL: digital or value error: character string buffer too smal
Hi experts,

Please check my query

DECLARE
f utl_file.file_type;
s NVARCHAR2 (32000);
VARCHAR2 (10) F1;
F2 char (1);
F3 VARCHAR2 (100);
F4 VARCHAR2 (100);
F5 VARCHAR2 (100);
F6 DATE;
F7 DATE;
F8 DATE;
F9 DATE;
F10 DATE;
F11 char (1);
BEGIN
DBMS_OUTPUT. ENABLE (100000);
f: = utl_file.fopen ('MID5010_DOC1TP', 'OPT_CM_BASE.txt', 'R');

LOOP
BEGIN
UTL_FILE. GET_LINE (f, s);

F1: = REGEXP_SUBSTR (s, "[^ |]") +', 1, 1);
F2: = REGEXP_SUBSTR (s, "[^ |]") +', 1, 2);
F3: = REGEXP_SUBSTR (S, "[^ |]") +', 1, 3);
F4: = REGEXP_SUBSTR (S, "[^ |]") +', 1, 4);
F5: = REGEXP_SUBSTR (S, "[^ |]") +', 1, 5);
F6: = REGEXP_SUBSTR (S, "[^ |]") +', 1, 6);
F7: = REGEXP_SUBSTR (S, "[^ |]") +', 1, 7);
F8: = REGEXP_SUBSTR (S, "[^ |]") +', 1, 8);
F9: = REGEXP_SUBSTR (S, "[^ |]") +', 1, 9);
F10: = REGEXP_SUBSTR (S, "[^ |]") +' 1, 10);
F11: = REGEXP_SUBSTR (s, "[^ |]") +', 1.11);

insert into OPTUM_ICD10CM_BASE
(OF THE CODE
STATUS,
SHORT_DESCRIPTION,
LONG_DESCRIPTION,
FULL_DESCRIPTION,
CODE_EFFECTIVE_DATE,
CHANGE_EFFECTIVE_DATE,
TERMINATION_DATE,
RELEASE_DATE,
CREATION_DATE,
VALIDITY)
VALUES (F1,
F2,
F3,
F4,
F5,
F6,
F7,
F8,
F9,
F10,
F11);
EXCEPTION
WHEN NO_DATA_FOUND THEN
EXIT;
END;
END LOOP;

UTL_FILE. FCLOSE (F);
END;
------------

and format text as below

A50.0 | Short | Long | Full | 01/01/2009 | / 01/2009 | 01/01/2013. 18/09/2012 | C |
A50.1 | Short | Long | Full | 01/01/2009 | 01/01/2009 | 001-2013 | 18/09/2012 | C |
A50.2 | Short | Long | Full|01-01-2009|01-01-2009|67|01-01-2013|09-18-2012| C |
A50.3 | Short | Long | Full | 011-2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A50.4 | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | 5.
A50.5 | R | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A50.6 | Short | Long | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A50.7 | Short | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
2345. Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A60.0 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A60.1 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A60.2 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A60.3 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A60.4 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A60.5 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A60.6 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A60.7 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A60.8 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A60.9 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A70.0 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A70.1 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A70.2 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A70.3 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A70.4 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
B222 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A4.1 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A4.2. N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A4.3 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A4.4 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A4.5 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A4.6 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A4.7 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A4.8 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A4.9 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A5.0 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A5.1. N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A5.2. B: Short | Long | Full|01-01-2009|01-01-2009|01-10-2013|01-01-2013|09-18-2012| C |
A5.3 | B: Short | Long | Full|01-01-2009|01-01-2009|01-10-2013|01-01-2013|09-18-2012| C |
D642 | B: Short | Long | Full|01-01-2009|01-01-2009|01-10-2013|01-01-2013|09-18-2012| C |
A5.5 | B: Short | Long | Full|01-01-2009|01-01-2009|01-10-2013|01-01-2013|09-18-2012| C |
A5.6 | B: Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A5.7 | C | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A001 | C | Short update | Long update | Full update | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A009 | C | Short update | Long update | Full update | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A5.10. C | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A0109 | C | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
F10.0 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
F10.1 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
F10.2 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
F10.3 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
F10.4 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
F10.5 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
F10.6 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
F10.7 | N | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A30 | C | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A316 | C | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |
A317 | C | Short | Long | Full | 01/01/2009 | 01/01/2009 | 01/01/2013. 18/09/2012 | C |

but I make an error such as ORA-06502: PL/SQL: digital or value error: character string buffer too small

Please help me
See now, you really have to think carefully, the code of operation step by step. Then you could help you.

I told you to use a when others share to block emergency inside the LOOP and you that has changed in the external main block! Why?

Simply change and recheck.

ORA-06502: PL/SQL: digital or value error: character string too small buffer
Dear gurus, I'm generation mail format html from oracle 10 g database.

Display the data in html format message body are superior to more than 32 k.

can you please guide me how to handle this error?

ORA-06502: PL/SQL: digital or value error: character string too small buffer

I use the long data type for message body data.
http://asktom.Oracle.com/pls/asktom/f?p=100:11:4325516854017254:P11_QUESTION_ID:1739411218448

see you soon

Text editor enriched ORA-06502: PL/SQL: digital or value error: character string buffer too small

Hello
I have apex user 4.2.3 with enterprise database edition 11, I page include RICH TEXT EDITOR, when I add data to this text and save it will record successfully and when I try to view this information in another page I see all the data, as expected, the problem when I try to go to the same page as RICH TEXT EDITOR error message apper ORA-06502 : PL/SQL: digital or value error: buffer string too small, I see this link https://forums.oracle.com/thread/2461151?tstart=0 but I don't know how it solve it, the problem is made data at the point of the rich text editor.

Any suggestion?

Thank you

Thanks for the reply,

Its standard form with text rich field, my question she same as link above I added before

PL/SQL: digital or value error: string buffer too small characters - LOV?
Environment:

APEX 3.1.1.00.09 under AIX 5.3 10.2.0.2 in

Problem sample on apex.oracle.com:

Workspace: GALWAY
ID: GWICKE
Password: GWICKE

Application ID: 43172 (BUILDERPL) NOTE: there are three 3 applications with the same name, but this one is currently broken

I get the dreaded "" ORA-06502: PL/SQL: digital or value error: character string buffer too small "when you try to create a new line."

To reproduce the error:

1 run page 3
2 - Select any agency
3 - Click on the button "create a new contract.
4 - Select the start and end dates in the DATE picker
5 - Click on the button "Add contract".

If the line is added successfully if please go to Indianapolis and run the app for me since you obviously have the 'touch '! ;-) >

But seriously folks,

I've read many threads about this error and for the most part, they seem to point to large LOV. I have three 3 LOV on the page but only a 1 is dynamic and display and back elements are the same, a description in this case. There are 400 lines in the LOV table and the description is defined as VARCHAR2 (75), so we're not talking a huge amount of data.

To further complicate the issue, this application was working just a couple of days. What changes I've made since a few days, you might ask?

The only thing that comes to mind is I did go through the definitions of element and change the values of maximum size equal to the size of the columns in the target table, using a value of 22 for the NUMBER of columns.

Since then I went back and changed at a much greater value than their corresponding column definitions, but nothing helped.

Another interesting fact is that if an existing contract is selected on the page (Page 3 in my case) by selecting an agency that produces values in the second select list (selection of contract) and then clicking on "change this contract." After you change any value or fill in one of the missing values, click "Apply Changes" and he should have success.

The new contract page and the page of modification of the contract are the same (Page 2) just with different buttons.

Thanks a lot for any assistance. Indeed, it is greatly appreciated.

-gary

PS I also tried to change the LOV both given a popup and a standard text box I typed in, both received the same message.
Gary - I deleted then recreated your DML process and it seems to have solved the problem. Export page reveals something odd in the process definition:
```
declare  p varchar2(32767) := null;  l_clob clob;  l_length number := 1;beginp:=p||'F|#OWNER#:BUILDERPL_CONTRACT:P2_CONTRACT_SEQ:CONTRACT_SEQ|I';

wwv_flow_api.create_page_process( ...
```
That the assignment statement must not have ' F | "as the first two characters. There must be a bug in one of the wizards who created the process. Have you used a wizard to create the page?

Scott

ORA-06502: PL/SQL: digital or value error: character conversion number e
Hi all
I work with DBLOCALE , which is
```
Oracle Database 10g Release 10.2.0.3.0 - 64bit Production
PL/SQL Release 10.2.0.3.0 - Production
CORE     10.2.0.3.0     Production
TNS for IBM/AIX RISC System/6000: Version 10.2.0.3.0 - Productio
NLSRTL Version 10.2.0.3.0 - Production
```
and DBREMOTE
```
Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
PL/SQL Release 9.2.0.8.0 - Production
CORE     9.2.0.8.0     Production
TNS for IBM/AIX RISC System/6000: Version 9.2.0.8.0 - Production
NLSRTL Version 9.2.0.8.0 - Production
```
Leave a procedure on DBLOCALE I run SCHEMA. MYPROCEDURE@dbremote (NUMBER, stringPar VARCHAR2, datePar DATE numberPar)

I use this procedure only to call a function in a package of DBREMOTE with education booleanresult: = MYPACKAGE. MYFUNC (NUMBER, stringPar VARCHAR2, datePar DATE numberPar)

In the service, I try to INSERT IN MYTABLE (numberPar, stringPar, datePar) and the error
```
ORA-06502: PL/SQL: numeric or value error: character to number conversion error
```
is triggered.

I missed something basic? Where is my mistake?

I have check all types of past data and types of data in the table, that I have to insert.

Any help or suggestion will be appreciated. Feel free to ask me any questions that need me to explain or for more details.

Best regards
Alex
OraclePSP wrote:

It starts with a page of APEX who call a procedure in DBLOCALE.

Apex point (page) variables are all text - and bind as text variables when used in PL/SQL and SQL code.

In this procedure, ii assess the past, then insert into a few tables@DBREMOTE without errors.
The end of it, I'm calling the remote packaged function.
In the function I use parameters to open a cursor and insert into MYTABLE.

That you pass as parameters? The variable element of Apex (e.g. : P1_DATE) or do you attribute the object variable to a PL/SQL variable and the neck of the PL/SQL variable as a parameter?

Even if I agree with you on the copy & paste I don't know what part of the process, I can speak to you.

Well, you can try the following. Create a dynamic PL/SQL region on the page. This region should be implemented and made that the page has been sent (in other words, element variables used in the page need value for this region, for the record). You can create a condition for this region that must be met to be made - and this can check the QUERY variable, or to check if the relevant variables have values.

In this dynamic PL/SQL code for the region block, use HTP.prn () as you would use DBMS_OUTPUT.put_line () in client-server test normal (using TOAD or SQL * more). And in this block of code, call the remote procedure.

For example
```
--// dynamic PL/SQL region code block:
HTP.prn( 'Item P1_DATE = ['||:P1_DATE||'] 
' );
HTP.prn( 'Item P1_NUMBER = ['||:P1_NUMBER||'] 
' );
..etc..

HTP.prn( 'Calling remote procedure:
' );
begin
  RemoteProc@RemoteDB( param1=>:P1_DATE, param2=>:P1_NUMBER );
  HTP.prn( 'Call was successful
' );
exception when OTHERS then
  HTP.prn( 'Call failed with: '||SQLERMM(SQLCODE)||'
');
end;
..etc..
```

ORA-06502: PL/SQL: digital or value error: character string buffer too small

Hello
I am facing infinity listagg that 4000 bytes in listagg issue, so I created a defined user aggregate function suggested by asking tom team,
https://asktom.Oracle.com/pls/Apex/f?p=100:11:0% 3A % 3A % 3A % 3aP11_QUESTION_ID: 2196162600402
But I am facing the error as "digital or value error: character string buffer too small" in the Type on line 27 when questioning this way
Select stragg (val) in the dummy_tab;
My table has a column and the data type is varchar2 (50) and he has more than 300 documents,.
can someone here help me to solve this problem.
Thanks and greetings
Guru

Now if you followed this link, so I hope that you:

(a) set the attribute of the object type to be a CLOB

(b) sets the return value of your Mapper function to be a CLOB

and not as in the example (which is the time before the existence of LISTAGG) as a Varchar2...

HTH

ORA-06502: PL/SQL: digital or value error ORA-06512: at the 'APPS '. WF_NOTIFICATION', line 5754 ORA-06512: at line 5

Hello
I have a l_body variable in my pl/sql code with varchar2 (32767).
It displays maximum 44 lines, more than 44 lines he gives buffer size error.
If I use the clob data type then it gives value or digital erro on 44 lines.
code is below
concerning

l_clob CLOB.
l_body varchar2 (32767);
BEGIN
Dbms_lob. CreateTemporary (l_clob,TRUE);

l_body: = null;

l_body: = "< Html >";

l_body: = l_body | "< Body >" ;

-l_body: = l_body | "< do Face ="Verdana, Arial, Helvetica"Color ="#000000"> ';

-l_body: = l_body | "< BR > < BR > < BR > ' | l_str | "< Br >".

l_body: = l_body | "< BR >" || "Please note that receipt number < B > ' " || Trans_Id | ' with amount: ' | Trim (to_char (total_amount,'999G999G999G999D99')): ' < /B > has been sent for approval. Detail is given below:' | ' < Br BR > > < ' ;

--------------------------

l_body: = l_body | ' < / table > < Br > < Br > ' ;

l_body: = l_body | '< table Border = 1 ">' ;

-l_body: = l_body | "< Tr Bgcolor = rgb (0,154,61) > ';

l_body: = l_body | "< Tr Bgcolor = rgb (162,202,230) >" ;

l_body: = l_body | '< e > < P > < Font Size = 2 Face = "Verdana, Arial, Helvetica" > < div align = left > Date' ;

l_body: = l_body | ' < e > < P > < Font Size = 2 Face = "Verdana, Arial, Helvetica" > < div align = left > name of the seller ' ;

l_body: = l_body | '< e > < P > < Font Size = 2 Face = "Verdana, Arial, Helvetica" > < div align = left > number of PO' ;

l_body: = l_body | ' < e > < P > < Font Size = 2 Face = "Verdana, Arial, Helvetica" > < div align = left > number ' ;

l_body: = l_body | '< e > < P > < Font Size = 2 Face = "Verdana, Arial, Helvetica" > < div align = left > line' ;

l_body: = l_body | '< e > < P > < Font Size = 2 Face = "Verdana, Arial, Helvetica" > < div align = left > Description of the object' ;

l_body: = l_body | ' < e > < P > < Font Size = 2 Face = "Verdana, Arial, Helvetica" > < div align = left > quantity ' ;

l_body: = l_body | ' < e > < P > < Font Size = 2 Face = "Verdana, Arial, Helvetica" > < div align = left > unit ' ;

l_body: = l_body | ' < e > < P > < Font Size = 2 Face = "Verdana, Arial, Helvetica" > < div align = left > unit price PO' ;

l_body: = l_body | ' < e > < P > < Font Size = 2 Face = "Verdana, Arial, Helvetica" > < div align = left > currency " " ;

l_body: = l_body | ' < e > < P > < Font Size = 2 Face = "Verdana, Arial, Helvetica" > < div align = left > amount ' ;

l_body: = l_body | '< e > < P > < Font Size = 2 Face = "Verdana, Arial, Helvetica" > < div align = left > Code combination' ;

l_body: = l_body | "< /Tr >" ;

FOR x in C LOOP

l_body: = l_body | "< Tr >" ;

l_body: = l_body | '< td > < P > < Font Size = 2 > < div align = left >' | x.transaction_date | "< Table >" ;

l_body: = l_body | '< td > < P > < Font Size = 2 > < div align = left >' | x.VENDOR_NAME | "< Table >" ;

l_body: = l_body | '< td > < P > < Font Size = 2 > < div align = left >' | x.po_number | "< Table >" ;

l_body: = l_body | '< td > < P > < Font Size = 2 > < div align = left >' | x.release_num | "< Table >" ;

l_body: = l_body | '< td > < P > < Font Size = 2 > < div align = left >' | x.line_num | "< Table >" ;

l_body: = l_body | '< td > < P > < Font Size = 2 > < div align = left >' | x.item_description | "< Table >" ;

l_body: = l_body | '< td > < P > < Font Size = 2 > < div align = right >' | x.Quantity | "< Table >" ;

l_body: = l_body | '< td > < P > < Font Size = 2 > < div align = left >' | x.unit_of_measure | "< Table >" ;

l_body: = l_body | '< td > < P > < Font Size = 2 > < div align = right >' | x.po_unit_price | "< Table >" ;

l_body: = l_body | '< td > < P > < Font Size = 2 > < div align = left >' | x.currency_code | "< Table >" ;

l_body: = l_body | '< td > < P > < Font Size = 2 > < div align = right >' | x.amount | "< Table >" ;

l_body: = l_body | '< td > < P > < Font Size = 2 > < div align = left >' || x.cc|| "< Table >" ;

l_body: = l_body | "< /Tr >" ;

END LOOP;

l_body: = l_body | ' < / table > < Br > < Br > ' ;

l_body: = l_body | "< / body >" || CHR(10);

l_body: = l_body | ' < / html > ' || CHR(10);

DBMS_LOB. WriteAppend (l_clob, length (l_body), l_body);

RETURN L_Clob;

END Format_Notification_Msg;

The maximum size allowed for l_body is 32767 who as varchar2 (32767)

Even if the CLOB has no size limit, you store the actual data in "l_body", it throws the error when the "l_body" increases of 32,767 characters.

Call the dbms_lob.writeappend () API in the for loop and cancel l_body after the API call, so that the 'l_body' will not go beyond the specified limit.

ERROR at line 1: ORA-06502: PL/SQL: digital or value error ORA-06512: at line 10

Hi all
DECLARE
TYPE (t1) IS RENDERING
v_ename emp.ename%TYPE,
v_sal emp.sal%TYPE
);
TNom TYPE IS an ARRAY OF t1
INDEX OF DIRECTORY;
v_tname tNom;
BEGIN
BECAUSE me IN v_tname. FIRST... v_tname. LAST
LOOP
Dbms_output.put_line (v_tname (i) .v_ename |) '' || .v_sal v_tname (i));
END LOOP;
END;

You want to ask why I used the SLIDER? -We can use in BULK COLLECT with LIMIT clause with the cursor

We also directly in bulk collect into collections as below:

DECLARE

TYPE (t1) IS RENDERING

v_ename emp.ename%TYPE,

v_sal emp.sal%TYPE

);

TNom TYPE IS an ARRAY OF t1

INDEX OF DIRECTORY;

v_tname tNom;

BEGIN

SELECT ename, sal BULK COLLECT INTO v_tname FROM emp;

BECAUSE me IN v_tname. FIRST... v_tname. LAST

LOOP

Dbms_output.put_line (v_tname (i) .v_ename |) ' ' || .v_sal v_tname (i));

END LOOP;

END;

/

PL/SQL error: digital or value error: character string buffer too small

HI gurus of the oracle,.
I'm new to PL/SQL,
my version of oracle's oracle 11g.
I create a procedure to insert data from flat file to a table using UTL_FILE.
The table is

CREATE TABLE EXT_PERSON_INFO

(

ID_PERSON NUMBER (38),

ID_BATCH NUMBER (38),

ID_PERSON_NBR VARCHAR2 (3 BYTE),

ID_AREA VARCHAR2 (5 BYTE),

NM_FINAL VARCHAR2 (20 BYTE),

NM_START VARCHAR2 (20 BYTE),

DATE OF DT_DOB,

ID_SERIAL VARCHAR2 (BYTE 9),

DATE OF DT_RESPONSE,

TRANS_TYPE VARCHAR2 (2 BYTE),

REG_RESPONSE VARCHAR2 (1 BYTE),

TM_RX TIMESTAMP (6)

)

My procedure is

CREATE OR REPLACE PROCEDURE PROC_PERSON

IS

f_line VARCHAR2 (2000);

f utl_file.file_type;

f_dir VARCHAR2 (250);

fname VARCHAR2 (50);

F_ID_PERSON EXT_PERSON_INFO.ID_PERSON%type: = 1;

F_ID_BATCH EXT_PERSON_INFO.ID_BATCH%type: = 1;

F_ID_PERSON_NBR EXT_PERSON_INFO.ID_PERSON_NBR%type;

F_ID_AREA EXT_PERSON_INFO.ID_AREA%type;

F_NM_FINAL EXT_PERSON_INFO. Type of NM_FINAL %;

F_NM_START EXT_PERSON_INFO. Type of NM_START %;

F_DT_DOB EXT_PERSON_INFO. Type of DT_DOB %;

F_ID_SERIAL EXT_PERSON_INFO.ID_SERIAL%type;

F_DT_RESPONSE EXT_PERSON_INFO. Type of DT_RESPONSE %;

F_TRANS_TYPE EXT_PERSON_INFO. Type of TRANS_TYPE %;

F_REG_RESPONSE EXT_PERSON_INFO. Type of REG_RESPONSE %;

BEGIN

fname: = "D:\raj\raj.txt";

f: = utl_file.fopen('RAJ',fname,'r');

loop

Start

UTL_FILE.get_line (f, f_line);

exception

When no_data_found then

"exit";

end;

F_ID_PERSON: = 1;

F_ID_BATCH: = 1;

F_ID_PERSON_NBR: = substr (f_line, 1, 3);

F_NM_FINAL: = substr (f_line, 4, 22);

F_NM_START: = substr (f_line, 23, 34);

F_DT_DOB: = substr (f_line, 35, 44);

F_ID_SERIAL: = substr (f_line, 45, 48);

F_DT_RESPONSE: = substr (f_line, 49, 58);

F_TRANS_TYPE: = substr (f_line, 59, 60);

F_REG_RESPONSE: = substr (f_line, 61, 61);

F_ID_AREA: = substr (f_line, 62, 64);

insert into EXT_PERSON_INFO VALUES (F_ID_PERSON, F_ID_BATCH, F_ID_PERSON_NBR, F_ID_AREA, F_NM_FINAL, F_NM_START, F_DT_DOB, F_ID_SERIAL, F_DT_RESPONSE, F_TRANS_TYPE, F_REG_RESPONSE);

end loop;

UTL_FILE.fclose (f);

commit;

end;

/

am getting error

ORA-06502: PL/SQL: digital or value error: character string buffer too small

Please help me in this regard. Impossible to trace the issue.
Thanks in advance
Kind regards
REDA

The error message should include a line number to reference your code to see what line the error occurred on.

That said, look at the documentation for SUBSTR as you incorrectly use the third parm. It's length, no end of race. That's your problem.

ORA-06502: digital or value error: character of number conversion error
I met the following error when I ran function to_number_or_null PL/SQL of Donald. Someone here could help me find the solution? Thank you!

SQL > create or replace FUNCTION to_number_or_null)
2 aiv_number in varchar2)
3 return number is
4 / *
5 to_number_or_null.fun
6 by Donald J. Bales on 12/15/2006
(7. a method of to_number without error)
8 * /
9 start
10 return to_number (aiv_number);
exception 11
12 when INVALID_NUMBER then
13 return NULL;
14 end to_number_or_null;
15.

The function is created.

SQL > select to_number_or_null('A') from double;
Select to_number_or_null ('A') of double
*
ERROR on line 1:
ORA-06502: PL/SQL: digital or value error: character of number conversion error
ORA-06512: at "CAROL. TO_NUMBER_OR_NULL', line 10
It seems that Donald must have handled VALUE_ERROR instead of INVALID_NUMBER.

http://download.Oracle.com/docs/CD/B19306_01/AppDev.102/b14261/errors.htm#LNPLS00703

PL/SQL: digital or value error: character number conversion in the TRG error

Similar Questions

Maybe you are looking for