SQLLDR - load welsh character

Hello Experts,
Database 9.2.0.5 and character set is
NLS_CHARACTERSET- AL32UTF8
NLS_NCHAR_CHARACTERSET - AL16UTF16
Table Description
CREATE TABLE WELSHTRANSFORM
INTERFACE VARCHAR2(20 BYTE),
WELSHCHR CHAR(2 BYTE),
ANGLICHR CHAR(2 BYTE),
INSERTDT DATE,
UPDDT DATE
welshutf8.dat (saved as UTF-8)
A,Â,A
A,Ê,E
A,Î,I
Ctl file
LOAD DATA INFILE 'welshutf8.dat'
BADFILE 'welsh.bad'
DISCARDFILE 'welsh.dsc'
TRUNCATE INTO TABLE welshtransform
FIELDS TERMINATED BY "," OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
(interface,
welshchr,
anglichr,
insertdt sysdate
Log file
Table WELSHTRANSFORM, loaded from every logical record.
Insert option in effect for this table: TRUNCATE
TRAILING NULLCOLS option in effect
Column Name Position Len Term Encl Datatype
INTERFACE FIRST * , O(") CHARACTER
WELSHCHR NEXT * , O(") CHARACTER
ANGLICHR NEXT * , O(") CHARACTER
INSERTDT SYSDATE
Record 1: Rejected - Error on table WELSHTRANSFORM, column WELSHCHR.
ORA-01401: inserted value too large for column
Record 2: Rejected - Error on table WELSHTRANSFORM, column WELSHCHR.
ORA-01401: inserted value too large for column
Record 3: Rejected - Error on table WELSHTRANSFORM, column WELSHCHR.
ORA-01401: inserted value too large for column
Please can I get help on to insert with this welsh characters using sqlldr in a table. Manual Insert statement works fine.
insert into lang_transform (lang_rule,transform_from,transform_to,insertdate) values ('A','Â','A',sysdate);
insert into lang_transform (lang_rule,transform_from,transform_to,insertdate) values ('A','Ê','E',sysdate);
insert into lang_transform (lang_rule,transform_from,transform_to,insertdate) values ('A','Î','I',sysdate);
insert into lang_transform (lang_rule,transform_from,transform_to,insertdate) values ('A','Ô','O',sysdate);
Thanks.

Are you running manual INSERT and SQLLDR from the same OS session ?
What is the value of OS NLS_LANG setting in the OS session ?
If you are using a Unix session:
>
echo $NLS_LANG
>
If you are using a Windows session, check Windows Registry.
I suspect a NLS_LANG issue:
If NLS_LANG is not defined (default character set is US7ASCII)
select vsize(convert('Â','AL32UTF8')) from dual
SQL> /
VSIZE(CONVERT('??','AL32UTF8'))
                     4If NLS_LANG is set to AMERICAN_AMERICA.AL32UTF8
SQL> select vsize(convert('Â','AL32UTF8')) from dual
  2  ;
VSIZE(CONVERT('Â','AL32UTF8'))
                    2

Similar Messages

  • SQL Loader Multibyte character error, LENGTH SEMANTICS CHARACTER

    Hi,
    startet SQL Loader Multibyte character error
    {thread:id=2340726}
    some mod locked the thread, why?
    the solution for others:
    add LENGTH SEMANTICS CHARACTER to the controlfile
    LOAD DATA characterset UTF8 LENGTH SEMANTICS CHARACTER
    TRUNCATE                              
    INTO TABLE utf8file_to_we8mswin1252
      ID    CHAR(1)     
    , TEXT  CHAR(40)
    )Regards
    Michael

    Hi Werner,
    on my linux desktop:
    $ file test.dat
    test.dat: UTF-8 Unicode text, with very long lines
    my colleague is working on a windows system.
    On both systems exact the same error from SQL Loader.
    Btw, try with different number of special characters (german umlaute and euro) and there is no chance to load without the error
    when to many (?) special characters or data is long as column length and special characters included.
    Regards
    Michael

  • SQL Loader Multibyte character error

    Hello,
    Oracle Database 11g Release 11.2.0.2.0 - 64bit Production
    Database Characterset: WE8MSWIN1252
    To load an utf8 File (UTF-8 Unicode text) i use option characterset UTF8 in controlfile.
    All went fine until in textfile the column is filled up with 40 chars and
    german umlaute included (ÜÖÄüöä...)
    Loader stops (errors=0) and gives:
    Record 146466: Rejected - Error on table 'TableName', column 'ColumnName'.
    Multibyte character error
    * use CHAR(40) and POSITION(start-end) for field description - no help
    * modify column, from VC2(40 char) to VC2(50 char) - no help
    * without characterset UTF8 option i got wrong characters for german umlaute - no help
    * manual insert the data from this row with NO problems !
    any hint or workaround?
    Regards
    Michael

    Hi Werner,
    on my linux desktop:
    $ file test.dat
    test.dat: UTF-8 Unicode text, with very long lines
    my colleague is working on a windows system.
    On both systems exact the same error from SQL Loader.
    Btw, try with different number of special characters (german umlaute and euro) and there is no chance to load without the error
    when to many (?) special characters or data is long as column length and special characters included.
    Regards
    Michael

  • SQLLDR: Loading files with no extension

    Does the Sql*Loader mandates extensions in file? I'm providing data file in the argument like
    sqlldr CONTROL=test.ctl data=/whatever/AFileWithNoExtension
    It errors out with AFileWithNoExtension.dat not found.
    Thanks

    If you don't specify an extension sqlldr assumes as default extension .dat
    http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96652/ch04.htm#1004744
    You need to rename your file before running sqlldr

  • Urgent :SQL Loader Arabic Character Set Issue

    HI all,
    I am loading arabic characters into my database using SQL Loader using a fixed length data file. I had set my characterset and NLS_LANG set to UTF8.When I try to load the chararacter 'B' in arabic data i.e. ' لا ' , it gets loaded as junk in the table. All other characters are loaded correctly. Please help me in this issue and its very urgent.
    Thanks,
    Karthik

    Hi,
    Thanks for the responses.
    Even after setting the characterset to arabic and the problem continues to persist. This problem occurs only with the character "b".
    Please find my sample control file,input file and nls_parameters below:
    My control file
    LOAD DATA
    characterset UTF8
    LENGTH SEMANTICS CHAR
    BYTEORDER little endian
    INFILE 'C:\sample tape files\ARAB.txt'
    replace INTO TABLE user1
    TRAILING NULLCOLS
    name POSITION(1:2) CHAR(1),
    id POSITION (3:3) CHAR(1) ,
    salary POSITION (4:5) CHAR(2)
    My Input file - Fixed Format
    ?a01
    ??b02
    ?c03
    The ? indicates arabic characters.Arabic fonts must be installed to view them.
    NLS_PARAMETERS
    PARAMETER     VALUE
    NLS_LANGUAGE     ARABIC
    NLS_TERRITORY     UNITED ARAB EMIRATES
    NLS_CURRENCY     ?.?.
    NLS_ISO_CURRENCY     UNITED ARAB EMIRATES
    NLS_NUMERIC_CHARACTERS     .,
    NLS_CALENDAR     GREGORIAN
    NLS_DATE_FORMAT     DD/MM/RR
    NLS_DATE_LANGUAGE     ARABIC
    NLS_SORT     ARABIC
    NLS_TIME_FORMAT     HH12:MI:SSXFF PM
    NLS_TIMESTAMP_FORMAT     DD/MM/RR HH12:MI:SSXFF PM
    NLS_TIME_TZ_FORMAT     HH12:MI:SSXFF PM TZR
    NLS_TIMESTAMP_TZ_FORMAT     DD/MM/RR HH12:MI:SSXFF PM TZR
    NLS_DUAL_CURRENCY     ?.?.
    NLS_COMP     BINARY
    NLS_LENGTH_SEMANTICS     CHAR
    NLS_NCHAR_CONV_EXCP     FALSE

  • Loading international Character using Flat File

    Hi All,
    We have a requirement in which we want to load Japanese and German Characters using a Flat file. How can we go about it.
    When I change the file into CSV then only only ???? all displayed in place of the internatioanl character.
    Any help or document which tell that how we can load the internatioanl Characters would be appreciated and awarded in SDN.
    Regards,
    Samved

    Dear Samved Sinho,
    when u are creating the data source for  Flat file select the language dependent ..and in  the Text   table u have to include the corresponding language in SAP terminology
    Regards
    venu

  • Sqlldr Loading more rows than expected

    We are trying to load a child table that has the referential integrity constraint with its parent and some triggers on it that is used to change the case of data. We are using the bcp to create a text file that is having the 5 records. The text file generated from BCP is a kind of CSV (~ is used for ,) file. When we are trying to load the reords using sqlldr it is loading 10 records in the database. It happens when 2 last rows are violating the integrity constraint thus the first 3 records are being duplicated and violated records are also loaded. Strange thing is that the same record that was loaded is being pushed in the bad file also. When we disable the trigger everything works fine. To get your help following is the snap of trigger and ctl files along with sample data:
    CREATE OR REPLACE TRIGGER "CMD".RWC_SPCL_HANDLING_INSTRCTNS
    before insert or update on RWC_SPCL_HANDLING_INSTRCTNS
    REFERENCES NEW AS NEW
    for each row
    BEGIN
    :new.ORG_ROADMARK:=upper(:new.ORG_ROADMARK);
    :new.RWC_CD:=upper(:new.RWC_CD);
    :new.SPCL_HANDLING_CD:=upper(:new.SPCL_HANDLING_CD);
    EXCEPTION
    WHEN OTHERS THEN RETURN;
    END;
    ---------CTL FILE-------------
    load data
    infile 'data\rwc_spcl_handling_instrctns.txt'
    into table rwc_spcl_handling_instrctns truncate
    fields terminated by '~'
    trailing nullcols
    (ORG_ROADMARK ,
    RWC_CD ,
    SPCL_HANDLING_CD,
    RWC_SPCL_HNDLNG_INSTRCTN_ID "rwc_sqn.nextval"
    -SAMPLE DATA--------
    GSWR~CARCHTADO1~SLC
    GSWR~CARCHTBUO1~SLC
    GSWR~CARCHTCOO1~SLC
    GSWR~CARSTRCANO~SHL
    GSWR~CARSTRCANO~SLC
    Thanks,
    Ashok

    Why not include the UPPER in the control file
    load data
    infile 'data\rwc_spcl_handling_instrctns.txt'
    into table rwc_spcl_handling_instrctns truncate
    fields terminated by '~'
    trailing nullcols
    (ORG_ROADMARK "UPPER(:ORG_ROADMARK)" ,
    RWC_CD "UPPER(:RWC_CD)" ,
    SPCL_HANDLING_CD "UPPER(:SPCL_HANDLING_CD)" ,
    RWC_SPCL_HNDLNG_INSTRCTN_ID "rwc_sqn.nextval"

  • Master data loading special character issue in bw

    Hi ,
    while extracting Material master data from r/3 system due to special characters load is getting failed even after enabling in RSKC.
    is there any length restriction  in RSKC to enable special characters like 20 or 30 only.
    If i specify the "ALL_CAPITAL " in RSKC what exactly it will do .
    Regards
    Ravi

    Hi,
    No small letters are permitted for characteristic values (in the InfoObject maintenance). It depends, however, on the language being used as to whether a character is capitalized.
    It is guaranteed that the characters ' !"%&''()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ' are capitalized in all languages. Thus these characters are permitted for characteristic values.
    Expl:
    The bit combination, that stands for an 'Ö' in German, displays a small 'sch' in the Russian character set. In this way, a German 'Ö' is not capitalized in Russian.
    In the German character set, the bit combination shows a "pictured reflected P" for the Russian capitals "SCH". The conversion of small letters into capitals is, therefore, language-dependent.
    If you have a system, that delivers you permitted characters other than ' !"%&''()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ', you can enter these characters here. The system the checks whether these characters are capitalized in all of the installed languages in your system . If this is the case, then these characters are also accepted in characteristic values.
    You should only add additional characters to the permitted characters, if you have already installed all the languages that you wish to use later. All languages that you install subsequently are not checked.
    It is possible that the validity of these additional characters is then not guaranteed, and the selectability of the entire master data is, therefore, put at risk.
    Edited by: venu pawar on Jan 7, 2010 1:22 PM

  • Sqlldr loads just 4096 rows

    Hello, the command line is ...
    sqlldr user/pass control=control.ctl data=data.dat skip=1 streamsize=104857600 multithreading=TRUE errors=0 readsize=10485760 log=logfile.log bad=badfile.bad
    Indeed, it is being called from a shell script, but, anyway (also tried from command line), it hangs. To finishit, I have to issue a CTRL+C.
    In logfile.log is registered....
    [user@server log]$ more logfile.log
    SQL*Loader: Release 9.2.0.4.0 - Production on Thu Jul 22 11:46:11 2010
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    Number to load: ALL
    Number to skip: 1
    Errors allowed: 0
    Bind array: 64 rows, maximum of 256000 bytes
    Continuation: none specified
    Path used: Conventional
    Table TEST_TABLE, loaded from every logical record.
    Insert option in effect for this table: APPEND
    TRAILING NULLCOLS option in effect
    SQL*Loader-2028: load discontinued to user interrupt (Ctrl-C) [103]
    ORA-01013: user requested cancel of current operation
    SQL*Loader-605: Non-data dependent ORACLE error occurred -- load discontinued.
    Specify SKIP=4097 when continuing the load.
    Table TEST_TABLE:
    4096 Rows successfully loaded.
    0 Rows not loaded due to data errors.
    0 Rows not loaded because all WHEN clauses were failed.
    0 Rows not loaded because all fields were null.
    Also tried using a 10g client but the same happens. Can you help? Thanks!

    Hello BelMan. Here goes the control file
    LOAD DATA
    APPEND
    INTO TABLE TEST_TABLE
    FIELDS TERMINATED BY '|'
    TRAILING NULLCOLS
    COL01 "RTRIM(LTRIM(REPLACE(:COL01,chr(13),'')))",
    COL02 "RTRIM(LTRIM(REPLACE(:COL02,chr(13),'')))",
    COL03 "RTRIM(LTRIM(REPLACE(:COL03,chr(13),'')))",
    COL04 "RTRIM(LTRIM(REPLACE(:COL04,chr(13),'')))",
    COL05 "RTRIM(LTRIM(REPLACE(:COL05,chr(13),'')))",
    COL06 "RTRIM(LTRIM(REPLACE(:COL06,chr(13),'')))",
    COL07 "RTRIM(LTRIM(REPLACE(:COL07,chr(13),'')))",
    COL08 "F_FROM_TO(RTRIM(LTRIM(REPLACE(:COL03,chr(13),''))))",
    COL09 "TO_CHAR('N/A')",
    COL10 "RTRIM(LTRIM(REPLACE(:COL10,chr(13),'')))",
    COL11 "RTRIM(LTRIM(REPLACE(:COL11,chr(13),'')))"
    Details on it:
    1) COL08 is the return of a funtion over COL03
    2) COL09 is a constant string 'N/A'
    3) The table itself has 11 columns but the data file just 9 (the differences are due to mentioned columns above)
    This is a new version of a control file that used to work. It stopped after including the last to columns (COL10 and COL11) which are new in the test table. Even taking out the 2 new columns, sqlldr hangs at row 4096.
    Thanks for helping!

  • Load special character £ in node name

    Hi,
    I am importing the hierarchies with special character £ and once imported it shows as following before the node name:
    small square box in place of £ with UTF8 as character encoding while importing and
    ? mark in place of £ with ASCII or ANSI as character encoding while importing.
    Please let me know how to get the £ in the node name.
    Thanks,
    Ravi

    Got it,
    Save the text file itself in UTF format and then import with UTF8 encoding in DRM.
    Thanks,
    Ravi

  • Batch /exe file to convert dbf to csv for sqlldr loading..!

    Hi all,
    I am having a tough problem as below.
    I need to load a .dbf file into a oracle table by sql loader.
    Can to tell me the best way to convert .dbf file to .csv so that I can load it via sql loader.
    I need some batch file or exe file code to convert .dbf to .csv file.
    i was doing it manually as in below steps.
    1- open .dbf file in excel.
    2-save it as .csv option.
    3-use sql loaderfor converted .dbf file.
    I want to save my manual work of excel.Kindly help
    kindly light into it...
    rgds,
    pc

    There are lots of dbf to CSV converter available in net and you can find by Google!. In the Tom's package you can change a little bit to generate a CSV file.

  • Sqlldr load data

    HI
    I have a data file like this
    =================================================================
    Data File: /opt/oracle/dc/data/diff/tsn/rk.txt
    664632 Rows successfully loaded.
    0 Rows not loaded due to data errors.
    417 Rows not loaded because all WHEN clauses were failed.
    0 Rows not loaded because all fields were null.
    Data File: /opt/oracle/dc/data/diff/jkt/rk.txt
    2531666 Rows successfully loaded.
    0 Rows not loaded due to data errors.
    141925 Rows not loaded because all WHEN clauses were failed.
    0 Rows not loaded because all fields were null.
    Data File: /opt/oracle/dc/data/diff/del/rk.txt
    ORA-01401: inserted value too large for column
    ORA-01400: cannot insert NULL into (HBL)
    6931772 Rows successfully loaded.
    2 Rows not loaded due to data errors.
    1905 Rows not loaded because all WHEN clauses were failed.
    0 Rows not loaded because all fields were null.
    ===================================================================
    in this sample file i have three records , ineed to load in to table as a three
    records how i can do this.
    EACH RECORD CONTAINS MORE THAN 10 ROWS SOME TIMES
    always the new record start with -- Data File

    You can even use SQLLoader to load the output. It can be someting like
    I am assuming that you have table like indy_test (id number,loadOutput(4000))
    So try with something like. Please check the syntax
    CONTINUEIF this preserve (1:4) != 'Data'
    INTO TABLE indy_test (id SEQUENCE(MAX,1),loadOutput char(400))
    Hope this will help
    Indy
    http://www.datasoftech.com/library.html - Free Oracle 11g Training

  • Loaded Symbolic character from interface change into question mark (?) char

    what type of variable that could store SYMBOLIC character such as
    ® (registered), µM (Micro)?
    i create DFF (with CHAR format type) that suppose to store detail
    information that has any symbolic character.
    I create my data that have symbol character (the symbol display perfectly on
    my Microsoft Excell 2007 and Notepad++).
    Than save it as .csv, and import into interface table.
    after successfully imported, all symbolic character (like above) turn into
    "?" character
    on forms.
    does oracle e-business suite support using symbolic character on DFF?
    or there must be someway to turn my .csv into readable data for symbolic
    character?
    please help.

    Hi Sarah,
    There are some special characters hard coded in OIM as # character. In my case, I made a workaround and it is working for '#' character:
    1-If through “group to approver member mapping” recon we get a group that doesn’t exist in OIM, search if that group contains “#” sign.
    2-If yes, then convert that group name to some temporary name which doesn’t contain # sign and create the group.
    2.1-If not, follow the normal process.
    3-Just after it is created, use a sql query to update the group name to the original name.
    I wrote a code for implementing this and test is working fine with add, updates, delete.
    My suggestion is: Open a SR with Oracle and ask them about this special character (?). If it is hard coded or not.
    If it is you can create something like my idea above, but related of your password not group names.
    If not , if it is just enable special characters , please follow this steps: http://cn.forums.oracle.com/forums/thread.jspa?messageID=9670344
    I really hope this helps.
    Thiago L Guimaraes

  • Multibyte character error... (SQL*Loader)

    Hi,
    I am getting error while loading data via SQL*Loader:
    "Multibyte character error." while loading data from flat files comgin from mailframe into oracle 10g Rel2 with character set AL32UTF8
    here is my .ctl loader file
    OPTIONS (ERRORS=9999, ROWS=500, BINDSIZE=65536, SILENT=(FEEDBACK) )
    LOAD DATA
    APPEND
    INTO TABLE GLSTB270
          GLS27001_CONUMBER   POSITION(0001:0011)
        , GLS27002_STORE      POSITION(0012:0012)
        , GLS27003_STATUS     POSITION(0013:0013)
        , GLS27004_CUST_TYPE  POSITION(0014:0014)
        , GLS27005_EXTERN     POSITION(0015:0025)
        , GLS27006_ADD_DATE   POSITION(0026:0039) DATE "yyyymmddhh24miss"
        , GLS27007_EXTCUST    POSITION(0040:0071)
        , GLS27008_LPICKCHRO  POSITION(0072:0073)
        , GLS27009_LAST_ITEM  POSITION(0074:0075)
        , GLS27010_DLVADD1    POSITION(0076:0107)
        , GLS27011_DLVADD2    POSITION(0108:0139)
        , GLS27012_DLVADD3    POSITION(0140:0171)
        , GLS27013_DLVPOSTAL  POSITION(0172:0181)
        , GLS27014_DLVCOUNTY  POSITION(0182:0213)
        , GLS27015_DLVCNTRY   POSITION(0214:0215)
        , GLS27016_SPECADD    POSITION(0216:0216)
        , GLS27017_GROUPING   POSITION(0217:0217)
        , GLS27018_CO_TYPE    POSITION(0218:0218)
        , GLS27019_QUOTATION  POSITION(0219:0226) DATE "yyyymmdd"
             NULLIF (GLS27019_QUOTATION   = "00000000")
        , GLS27020_USHIP      POSITION(0227:0227)
        , GLS27021_CONFIRM    POSITION(0228:0228)
        , GLS27022_UNUDEMAND  POSITION(0229:0229)
        , GLS27023_FREECHARG  POSITION(0230:0230)
        , GLS27024_CONF_DATE  POSITION(0231:0238) DATE "yyyymmdd"
             NULLIF (GLS27024_CONF_DATE   = "00000000")
        , GLS27025_CONTACT    POSITION(0239:0270)
        , GLS27026_LICENCE    POSITION(0271:0290)
        , GLS27027_WARRANT    POSITION(0291:0291)
        , GLS27028_WARR_AUTH  POSITION(0292:0301)
        , GLS27029_CURRENCY   POSITION(0302:0304)
        , GLS27030_FSE        POSITION(0305:0310)
        , GLS27031_CARRIER    POSITION(0311:0320)
        , GLS27032_MANPRICIN  POSITION(0321:0321)
        , GLS27033_ADD_USER   POSITION(0322:0329)
        , GLS27034_AUTO_INV   POSITION(0330:0330)
        , GLS27035_PRIFACT    POSITION(0331:0338)
        , GLS27036_CRELETTER  POSITION(0339:0353)
       , GLS27025_CONTACT    POSITION(0239:0270)
        , GLS27026_LICENCE    POSITION(0271:0290)
        , GLS27027_WARRANT    POSITION(0291:0291)
        , GLS27028_WARR_AUTH  POSITION(0292:0301)
        , GLS27029_CURRENCY   POSITION(0302:0304)
        , GLS27030_FSE        POSITION(0305:0310)
        , GLS27031_CARRIER    POSITION(0311:0320)
        , GLS27032_MANPRICIN  POSITION(0321:0321)
        , GLS27033_ADD_USER   POSITION(0322:0329)
        , GLS27034_AUTO_INV   POSITION(0330:0330)
        , GLS27035_PRIFACT    POSITION(0331:0338)
        , GLS27036_CRELETTER  POSITION(0339:0353)
        , GLS27037_SHIPMENT   POSITION(0354:0354)
        , GLS27038_DIVISION   POSITION(0355:0356)
        , GLS27039_ACCREF     POSITION(0357:0365)
        , GLS27040_EXPENSE    POSITION(0366:0366)
        , GLS27041_ALREADY    POSITION(0367:0367)
        , GLS27042_SITE       POSITION(0368:0375)
        , GLS27043_SITE_DES   POSITION(0376:0395)
        , GLS27044_ADDTYPE    POSITION(0396:0396)
        , GLS27045_PROJECT    POSITION(0397:0406)
        , GLS27046_SITE_DOWN  POSITION(0407:0407)
        , GLS27047_QUOTATION  POSITION(0408:0408)
        , GLS27048_DELIVERY   POSITION(0409:0428)
        , GLS27049_CONSPERM   POSITION(0429:0429)
        , GLS27050_CHARACT    POSITION(0430:0432)
        , GLS27051_CONTRACT   POSITION(0433:0434)
        , GLS27052_FSE        POSITION(0435:0435)
        , GLS27053_SYSTEM     POSITION(0436:0445)
        , GLS27054_SYSTEM_D   POSITION(0446:0465)
        , GLS27055_JOBSTATUS  POSITION(0466:0468)
        , GLS27056_BO_L_CHRO  POSITION(0469:0470)
        , GLS27057_BUYER      POSITION(0471:0480)
        , GLS27058_SCREASON   POSITION(0481:0481)
        , GLS27059_L_M_DATE   POSITION(0482:0495) DATE "yyyymmddhh24miss"
        , GLS27061_L_M_USER   POSITION(0496:0503)
        , GLS27062_SCREEN     POSITION(0504:0507)
        , GLS27063_CUST_EXP   POSITION(0508:0508)
        , GLS270F1_GLS08001   POSITION(0509:0509)
        , GLS270F2_GLS08002   POSITION(0510:0511)
        , GLS270F3_GLS25001   POSITION(0512:0512)
        , GLS270F4_GLS25002   POSITION(0513:0522)
    )and here is the .log file containing error msg for sql*loader:
    SQL*Loader: Release 9.2.0.8.0 - Production on Thu Apr 5 15:35:21 2007
    Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
    Control File:   /opt/oracle/test/admin/glsdbt01/load/glstb270.ctl
    Data File:      /opt/oracle/test/admin/glsdbt01/download2/GLSTB270.ZZ.CRE
      Bad File:     /dblog02/glsdbt01/load/results/glsltb270zz.bad
      Discard File: /dblog02/glsdbt01/load/results/glsltb270zz.dis
    (Allow all discards)
    Number to load: ALL
    Number to skip: 0
    Errors allowed: 9999
    Continuation:    none specified
    Path used:      Direct
    Silent options: FEEDBACK
    Table GLSTB270, loaded from every logical record.
    Insert option in effect for this table: APPEND
       Column Name                  Position   Len  Term Encl Datatype
    GLS27001_CONUMBER                    1:11    11           CHARACTER
    GLS27002_STORE                      12:12     1           CHARACTER
    GLS27003_STATUS                     13:13     1           CHARACTER
    GLS27004_CUST_TYPE                  14:14     1           CHARACTER
    GLS27005_EXTERN                     15:25    11           CHARACTER
    GLS27006_ADD_DATE                   26:39    14           DATE yyyymmddhh24miss
    GLS27007_EXTCUST                    40:71    32           CHARACTER
    GLS27008_LPICKCHRO                  72:73     2           CHARACTER
    GLS27009_LAST_ITEM                  74:75     2           CHARACTER
    GLS27010_DLVADD1                   76:107    32           CHARACTER
    GLS27011_DLVADD2                  108:139    32           CHARACTER
    GLS27012_DLVADD3                  140:171    32           CHARACTER
    GLS27013_DLVPOSTAL                172:181    10           CHARACTER
    GLS27014_DLVCOUNTY                182:213    32           CHARACTER
    GLS27015_DLVCNTRY                 214:215     2           CHARACTER
    GLS27016_SPECADD                  216:216     1           CHARACTER
    GLS27017_GROUPING                 217:217     1           CHARACTER
    GLS27018_CO_TYPE                  218:218     1           CHARACTER
    GLS27019_QUOTATION                219:226     8           DATE yyyymmdd
        NULL if GLS27019_QUOTATION = 0X3030303030303030(character '00000000')
    GLS27020_USHIP                    227:227     1           CHARACTER
    GLS27020_USHIP                    227:227     1           CHARACTER
    GLS27021_CONFIRM                  228:228     1           CHARACTER
    GLS27022_UNUDEMAND                229:229     1           CHARACTER
    GLS27023_FREECHARG                230:230     1           CHARACTER
    GLS27024_CONF_DATE                231:238     8           DATE yyyymmdd
        NULL if GLS27024_CONF_DATE = 0X3030303030303030(character '00000000')
    GLS27025_CONTACT                  239:270    32           CHARACTER
    GLS27026_LICENCE                  271:290    20           CHARACTER
    GLS27027_WARRANT                  291:291     1           CHARACTER
    GLS27028_WARR_AUTH                292:301    10           CHARACTER
    GLS27029_CURRENCY                 302:304     3           CHARACTER
    GLS27030_FSE                      305:310     6           CHARACTER
    GLS27031_CARRIER                  311:320    10           CHARACTER
    GLS27032_MANPRICIN                321:321     1           CHARACTER
    GLS27033_ADD_USER                 322:329     8           CHARACTER
    GLS27034_AUTO_INV                 330:330     1           CHARACTER
    GLS27035_PRIFACT                  331:338     8           CHARACTER
    GLS27036_CRELETTER                339:353    15           CHARACTER
    GLS27037_SHIPMENT                 354:354     1           CHARACTER
    GLS27038_DIVISION                 355:356     2           CHARACTER
    GLS27039_ACCREF                   357:365     9           CHARACTER
    GLS27040_EXPENSE                  366:366     1           CHARACTER
    GLS27041_ALREADY                  367:367     1           CHARACTER
    GLS27042_SITE                     368:375     8           CHARACTER
    GLS27043_SITE_DES                 376:395    20           CHARACTER
    GLS27044_ADDTYPE                  396:396     1           CHARACTER
    GLS27045_PROJECT                  397:406    10           CHARACTER
    GLS27046_SITE_DOWN                407:407     1           CHARACTER
    GLS27047_QUOTATION                408:408     1           CHARACTER
    GLS27048_DELIVERY                 409:428    20           CHARACTER
    GLS27049_CONSPERM                 429:429     1           CHARACTER
    GLS27050_CHARACT                  430:432     3           CHARACTER
    GLS27051_CONTRACT                 433:434     2           CHARACTER
    GLS27052_FSE                      435:435     1           CHARACTER
    GLS27053_SYSTEM                   436:445    10           CHARACTER
    GLS27054_SYSTEM_D                 446:465    20           CHARACTER
    GLS27055_JOBSTATUS                466:468     3           CHARACTER
    GLS27056_BO_L_CHRO                469:470     2           CHARACTER
    GLS27057_BUYER                    471:480    10           CHARACTER
    GLS27058_SCREASON                 481:481     1           CHARACTER
    GLS27059_L_M_DATE                 482:495    14           DATE yyyymmddhh24miss
    GLS27061_L_M_USER                 496:503     8           CHARACTER
    GLS27062_SCREEN                   504:507     4           CHARACTER
    GLS27063_CUST_EXP                 508:508     1           CHARACTER
    GLS27063_CUST_EXP                 508:508     1           CHARACTER
    GLS270F1_GLS08001                 509:509     1           CHARACTER
    GLS270F2_GLS08002                 510:511     2           CHARACTER
    GLS270F3_GLS25001                 512:512     1           CHARACTER
    GLS270F4_GLS25002                 513:522    10           CHARACTER
    Record 20405: Rejected - Error on table GLSTB270, column GLS27043_SITE_DES.
    Multibyte character error.
    Record 20418: Rejected - Error on table GLSTB270, column GLS27043_SITE_DES.
    Multibyte character error.
    Record 20419: Rejected - Error on table GLSTB270, column GLS27043_SITE_DES.
    Multibyte character error.
    Record 20420: Rejected - Error on table GLSTB270, column GLS27043_SITE_DES.
    Multibyte character error.
    Record 20425: Rejected - Error on table GLSTB270, column GLS27043_SITE_DES.
    Multibyte character error.
    Record 20426: Rejected - Error on table GLSTB270, column GLS27043_SITE_DES.
    Multibyte character error.
    Record 20436: Rejected - Error on table GLSTB270, column GLS27043_SITE_DES.
    Multibyte character error.
    Record 20452: Rejected - Error on table GLSTB270, column GLS27043_SITE_DES.
    Multibyte character error.
    Record 20481: Rejected - Error on table GLSTB270, column GLS27043_SITE_DES.
    Multibyte character error.
    Record 20482: Rejected - Error on table GLSTB270, column GLS27043_SITE_DES.
    Multibyte character error.
    Record 20483: Rejected - Error on table GLSTB270, column GLS27043_SITE_DES.
    Multibyte character error.
    Record 20484: Rejected - Error on table GLSTB270, column GLS27043_SITE_DES.
    Multibyte character error.
    Record 20485: Rejected - Error on table GLSTB270, column GLS27043_SITE_DES.
    Multibyte character error.
    Record 20486: Rejected - Error on table GLSTB270, column GLS27043_SITE_DES.
    Multibyte character error.
    Record 20487: Rejected - Error on table GLSTB270, column GLS27043_SITE_DES.
    Multibyte character error.
    Record 20494: Rejected - Error on table GLSTB270, column GLS27043_SITE_DES.
    Multibyte character error.
    Record 20499: Rejected - Error on table GLSTB270, column GLS27043_SITE_DES.
    Multibyte character error.
    Record 20502: Rejected - Error on table GLSTB270, column GLS27043_SITE_DES.
    Multibyte character error.
    Record 20503: Rejected - Error on table GLSTB270, column GLS27043_SITE_DES.
    Multibyte character error.Can you pls help..?
    thanks

    Hi Werner,
    on my linux desktop:
    $ file test.dat
    test.dat: UTF-8 Unicode text, with very long lines
    my colleague is working on a windows system.
    On both systems exact the same error from SQL Loader.
    Btw, try with different number of special characters (german umlaute and euro) and there is no chance to load without the error
    when to many (?) special characters or data is long as column length and special characters included.
    Regards
    Michael

  • Sequel loader issue

    Hi Guys,
    I have to load data into the database through sequel loader.
    Following are the process I am using to load the data
    As my dataset contains data other than english also so I am saving the excel sheet in the unicode format and using characterset UTF8 in the control file.
    By this method I am able to load data perfectly . When I am checking in the table by sequel developer this particular record is there however when I am qeuring the table by putting that particular value ,the select clause is not able to fetch that record.
    The select statement is like this
    SELECT * FROM rev_dtls
    WHERE name='WIND ΕΛΛΑΣ ΤΗΛΕΠΙΚΟΙΝΩΝΙΕΣ Α.Ε.Β.Ε.';
    But the value 'WIND ΕΛΛΑΣ ΤΗΛΕΠΙΚΟΙΝΩΝΙΕΣ Α.Ε.Β.Ε.' is there in the database which is also visible thorugh the sequel developer tool
    Please help me out because I am not able to figure out the problem
    Lots of thanks in advance and any suggestion will be highly appreciated
    Thanks,
    Prafull

    Hi
    Check the NLS_LANG parameter of the client. It should support loading extended character set such as the characters you've got and also check your DB nls
    parameters; select * from nls_database_parameters; -- This should tell you what characterset your DB supports.
    If there are differences between the two, it is possible that your characters from the excel file are being loaded differently.
    You may find this useful: Sqlldr and special characters

Maybe you are looking for