Ora 01438 ошибка

Following is my code, I dont understand what I’m doing wrong. Any help will be greatly appreciated

CREATE OR REPLACE
PROCEDURE COMP_LATE_FEE(LATE_APT_FINE IN NUMBER, LATE_GRG_FINE IN NUMBER)
AS
DIFF NUMBER;
TYPE MBCUR IS REF CURSOR RETURN MONTHLY_BILL%ROWTYPE;
MONBILL MBCUR;
MBREC MONTHLY_BILL%ROWTYPE;
BEGIN
--DIFF := FLOOR(SYSDATE - (TRUNC(SYSDATE,'MM')));
--DBMS_OUTPUT.PUT_LINE(DIFF);

OPEN MONBILL FOR
    -- checking the status of all last month's bills
    SELECT * FROM MONTHLY_BILL
    WHERE STATUS = 'PENDING' AND SYSDATE > ED_DT;
FETCH MONBILL INTO MBREC;
    -- adding the late fee amount for any bills that are past the due date
    -- due date = last day of the month
    DIFF := FLOOR(ABS(MBREC.ED_DT - (TRUNC(SYSDATE,'MM'))));
    UPDATE MONTHLY_BILL
    SET LATE_FEE = DIFF * LATE_APT_FINE
    WHERE BILL_NUM = MBREC.BILL_NUM;
    -- if a garage is rented by the resident then the respective additional fee is included
    IF (MBREC.GARAGE_RENT != 0) THEN
        UPDATE MONTHLY_BILL
        SET LATE_FEE = LATE_FEE + DIFF * LATE_GRG_FINE
        WHERE BILL_NUM = MBREC.BILL_NUM;
    END IF;

    COMMIT;
CLOSE MONBILL;
 END;
/

The procedure compiled without any err. But I get the following err when i call the proc

BEGIN
COMP_LATE_FEE(70,20);
END;
/

Error report:

ORA-01438: value larger than specified precision allowed for this column
ORA-06512: at "LALLURI.COMP_LATE_FEE", line 19
ORA-06512: at line 2
01438. 00000 -  "value larger than specified precision allowed for this column"
*Cause:    When inserting or updating records, a numeric value was entered
           that exceeded the precision defined for the column.
*Action:   Enter a value that complies with the numeric column's precision,
           or use the MODIFY option with the ALTER TABLE command to expand
           the precision.

— In the following example,
the inserted value should only have 2 digits, and both digits should be in
the decimal part of the number

SQL>
create table test (sal number(2,2));

Table
created.

SQL>
insert into test values(2.3333);

insert
into test values(2.3333)

                        *

ERROR
at line 1:

ORA-01438:
value larger than specified precision allowed for this column

SQL>
insert into test values(2.3);

insert
into test values(2.3)

                        *

ERROR
at line 1:

ORA-01438:
value larger than specified precision allowed for this column

SQL>
insert into test values(2);

insert
into test values(2)

                        *

ERROR
at line 1:

ORA-01438:
value larger than specified precision allowed for this column

SQL>
insert into test values(.2);

1
row created.

SQL>

— In the following example,
the inserted value should only have 2 digits for precision part only as no
decimal could be inserted in this column, although INSERT statement would
succeed if decimal value is mentioned.

SQL>
create table test (sal number(2));

Table
created.

SQL>
insert into test values(2.1);

1
row created.

SQL>
insert into test values(2.11);

1
row created.

SQL>
insert into test values(2.111);

1
row created.

SQL>
insert into test values(2.1110000);

1
row created.

SQL>
insert into test values(22.1110000);

1
row created.

SQL>
insert into test values(223.1110000);

insert
into test values(223.1110000)

                        *

ERROR
at line 1:

ORA-01438:
value larger than specified precision allowed for this column

SQL>
select * from test;

       SAL

———-

         2

         2

         2

         2

        22

— In the following example,
maximum 6 digits could be inserted in the column out of which 4 have to be
decimal part. As soon as we try to insert 3 digits in precision part,
ORA-01438 would be returned because 4 places have to be reserved for the decimal
part.

SQL>
create table test (sal number(6,4));

Table
created.

SQL>
insert into test values(25.65743);

1
row created.

SQL>
insert into test values(2534333.65743);

insert
into test values(2534333.65743)

                        *

ERROR
at line 1:

ORA-01438:
value larger than specified precision allowed for this column

SQL>
insert into test values(253433.65743);

insert
into test values(253433.65743)

                        *

ERROR
at line 1:

ORA-01438:
value larger than specified precision allowed for this column

SQL>
insert into test values(2534.65743);

insert
into test values(2534.65743)

                        *

ERROR
at line 1:

ORA-01438:
value larger than specified precision allowed for this column

SQL>
insert into test values(2.65743);

1
row created.

SQL>
insert into test values(22.65743);

1
row created.

SQL>
insert into test values(223.65743);

insert
into test values(223.65743)

                        *

ERROR
at line 1:

ORA-01438:
value larger than specified precision allowed for this column

SQL>
insert into test values(243.5);

insert
into test values(243.5)

                        *

ERROR
at line 1:

ORA-01438:
value larger than specified precision allowed for this column

SQL>
select * from test;

       SAL

———-

   25.6574

    2.6574

   22.6574

[{«Product»:{«code»:»SSLVY3″,»label»:»Initiate Master Data Service»},»Business Unit»:{«code»:»BU059″,»label»:»IBM Software w\/o TPS»},»Component»:»Not Applicable»,»Platform»:[{«code»:»PF025″,»label»:»Platform Independent»}],»Version»:»Version Independent»,»Edition»:»»,»Line of Business»:{«code»:»LOB10″,»label»:»Data and AI»}}]

Error Message

Using cov2sde command may generate the following error: SDE Error(-51) Underlying DBMS error Extended error code(1438): ORA-01438: value larger than specified precision allows for this column.

Cause

Attribute values of the coverage in one or more NUMBER fields are too large for the new fields created in the Oracle table.

Cov2sde first creates an Oracle table to receive the data. This new table’s NUMBER fields are defined from the output/display column and decimals fields specified for the coverage’s INFO table.

To illustrate, assume we have a single parcel coverage with an AREA field whose output/display width is 3, and its decimal column is set to 1 decimal place. When this AREA field is added to the new Oracle table it will be defined as NUMBER(3,1). The 3 indicates the maximum number of digits Oracle will store in this number field. The 1 means that one of those three digits is reserved for a position to the right of the decimal point. Thus, if the area value in the coverage is 12.3, it would be a legitimate number, but an area value of 123.4 would not be¹.
¹Koch, G., and K. Loney, «Creating, Dropping, and Altering Tables and Views,» Oracle: The Complete Reference, Electronic Edition (1997):383.

Solution or Workaround

Changing the output/display column width in the INFO table to a width larger than the attribute value before loading the coverage into the Oracle table eliminates the error, and should allow the data to load.

In the previous example, changing the column width from 3 to 4 or higher will correct the problem.
Find offending INFO column(s) and increase output/display width size using ArcCatalog™

or INFO

.

Note: ArcINFO™ Workstation refers to the column as Output width.
ArcInfo™ Desktop refers to the column as Display width.