CSV loader error Character String Buffer Too Small


Product(s):Exor Asset Manager
Version(s):04.07.00.01
Environment:N\A
Area:CSV Loader
Subarea:N\A

Problem Description

When user tries to load data using CSV Loader

----------------------------
---------------------------------------------------------------
X - Error in transfer to holding table       : 1
H - In Holding Table                                : 0
E - Error in Validation or Insert               : 1161
V - Validation Completed                         : 0
I - Record Inserted                                    : 0
------------------------------------------------------------------
-------------------------
Record Num Bad File # St Error Text
---------- ---------- -- ---------------------------------------------
---------------------
         1          1 X  PL/SQL: numeric or value error: character to number conversion error:LINK_NUM

         2          2 E  PL/SQL: numeric or value error: character string buffer too small
         3          3 E  PL/SQL: numeric or value error: character string buffer too small
         4          4 E  PL/SQL: numeric or value error: character string buffer too small
         5          5 E  PL/SQL: numeric or value error: character string buffer too small
         6          6 E  PL/SQL: numeric or value error: character string buffer too small
         7          7 E  PL/SQL: numeric or value error: character string buffer too small
         8          8 E  PL/SQL: numeric or value error: character string buffer too small
         9          9 E  PL/SQL: numeric or value error: character string buffer too small
        10         10 E  PL/SQL: numeric or value error: character string buffer too small

other errors:

      26              1 E  Record Failed To Update.  Check Log files For Details
      1001          3 E  Inspection/Parent ID combination is invalid

Steps to Resolve

This issue is related to the data size of one field/column in uploaded CSV file, it was greater than specified in the Definition Table (on HIG2020 form) in Database, resulting in a mismatch. For instance,

Column "GEO_ID" in the CSV file was given values like "10001" (which was 5 character value) and "nm_elements_all.ne_owner column" was defined as "varchar(4)" type.

1001 error, in the very end of the errors list.The last record/line in the uploaded csv file is empty or has no data included in (only commas are there). - Solution: delete that empty line from csv file.

26 error, the error appeared because there is a latest Inspection for the specific asset in the system and the inspection whose creation date is earlier was canceled on loading csv file.

See Also

ba13ced047b94e509091861f536d43f4-file-loading-fails

 Original Author:Jyoti Patil