SQL*LOADER Character set

Hi,
I am trying to load data created on IBM OS/390 into Oralce on Solaris using SQL*LOADER CHARACTER SET option. I am currently using the character set WE8EBCDIC500 and everything is working fine except that '!' are being converted to ']'. I am wondering if I am using the right character set or not. Any help is appreciated.
thanks!

MY character set from database is
PARAMETER VALUE
NLS_CHARACTERSET AL32UTF8
NLS_NCHAR_CHARACTERSET AL16UTF16
My oracle is under linux and version is 11g R2
I am running loader from windows xp.

Similar Messages

  • Character set supported by post and util.zip

    hi friends
    in my application i was sending a file(in client) using post method and in server getting using servlets.i what that file to be compressed using util.zip in client and uncompresed in server but i was unsucessful .i think the file before post (compressed one) and retrieving one are not same. is it problem different character set supported by http and zip files? or any thing else?
    plz help me.......

    Just ran into this myself yester day.
    There is a Metalink Note on it.
    http://metalink.oracle.com/metalink/plsql/ml2_documents.showFrameDocument?p_database_id=NOT&p_id=190281.1
    Problem Description
    You are using OC4J and trying to connect to a database using JDBC OCI and
    are getting:
    "java.sql.SQLException: Character Set Not Supported !!: DBConversion"
    Solution Description
    Replace the <OC4J_HOME>\jdbc\lib\classes12dms.jar with
    <ORACLE_HOME>\jdbc\lib\classes12.jar and rename it with classes12dms.jar.
    Explanation
    It seems there is a mismatch of classes12.zip supplied with OC4J 9.0.2
    and the Oracle9i client libraries ocijdbc8.dll or ocijdbc8.so.
    OC4J 9.0.2 does not use jdbc\lib\classes12.jar instead it uses
    jdbc\lib\classes12dms.jar. So, in order to use the 9.0.1 client with OC4J, you
    will need to make a copy of classes12.jar and rename it to classes12dms.jar
    References
    [NOTE:108876.1] Creating Connection gives "No ocijdbc8 in java.library.path"
    [NOTE:174808.1] JDev9i and OCI Connections
    I copied and renamed the jar (classes12.jar) as they stated.
    Note: It should be in the directory you set in the JDev.conf, mine is
    AddNativeCodePath D:\OraNT\9iDS\bin
    Didn't try the other reply's suggestion of setting an environment variable.

  • SQL Loader error number 1 in OWB 9.0.4

    I'm trying to execute a flat-file to database table mapping (using SQL*Loader), having set up my locations & connectors. When I execute the mapping, I get the following message:
    Starting Execution COM_COM_MT_STG
    Starting Task COM_COM_MT_STG
    RPE-1013-SQL_LOADER_ERROR SQL Loader reported error condition, number 1.
    Completing Task COM_COM_MT_STG
    Completing Execution COM_COM_MT_STG
    What does that mean and how do I fix it?
    Also, is there any detailed documentation on building such a mapping, that can take you through all the steps, from creating the flat file module to deployment?
    Thanks,
    Carey

    Carey,
    Use the runtime audit browser to access the error log. It will show you what went wrong. You may have to re-register your flat file location with a folder separator at the end... This is a bug.
    Thanks,
    Mark.

  • Character Set not supported

    Hi,
    I use Repository Administrative to create a new repository, but i got a error: "process aborted"
    Then i checked the log file, which is Character Set not support from type 31 to type 852
    anybody knows any solution about that
    Thanks in advance

    Just ran into this myself yester day.
    There is a Metalink Note on it.
    http://metalink.oracle.com/metalink/plsql/ml2_documents.showFrameDocument?p_database_id=NOT&p_id=190281.1
    Problem Description
    You are using OC4J and trying to connect to a database using JDBC OCI and
    are getting:
    "java.sql.SQLException: Character Set Not Supported !!: DBConversion"
    Solution Description
    Replace the <OC4J_HOME>\jdbc\lib\classes12dms.jar with
    <ORACLE_HOME>\jdbc\lib\classes12.jar and rename it with classes12dms.jar.
    Explanation
    It seems there is a mismatch of classes12.zip supplied with OC4J 9.0.2
    and the Oracle9i client libraries ocijdbc8.dll or ocijdbc8.so.
    OC4J 9.0.2 does not use jdbc\lib\classes12.jar instead it uses
    jdbc\lib\classes12dms.jar. So, in order to use the 9.0.1 client with OC4J, you
    will need to make a copy of classes12.jar and rename it to classes12dms.jar
    References
    [NOTE:108876.1] Creating Connection gives "No ocijdbc8 in java.library.path"
    [NOTE:174808.1] JDev9i and OCI Connections
    I copied and renamed the jar (classes12.jar) as they stated.
    Note: It should be in the directory you set in the JDev.conf, mine is
    AddNativeCodePath D:\OraNT\9iDS\bin
    Didn't try the other reply's suggestion of setting an environment variable.

  • SQLException Character Set Not Supported

    I'm at wit's end.
    I have the following versions:
    Win2k
    JDeveloper 9i R2
    Oracle9iAS 9.0.3.0.0
    Oracle 9i client 9.0.1.1
    Sun J2SDK 1.3.1
    Oracle 9i Enterprize Edition 9.0.1.3.0
    I'm trying to get a JDBC connection from a DataSource in a servlet. The result is the following error: java.sql.SQLException: Character Set Not Supported !!: DBConversion.
    I get the same problem just trying a simple JDBC connection in JDeveloper. I can fix this problem by forcing JDeveloper to use classes12.jar from the Oracle client directory BEFORE oc4j.jar in the JDeveloper libraries.
    Unfortunately, I can't get the external 9iAS server to make this switch. It's (naturally) using its copy of oc4j.jar.
    Any ideas on:
    1) How to properly avoid the Character Set error.
    2) How to force 9i AS to use different libraries before it looks in oc4j.
    Any help is greatly appreciated

    I have tried the embedded server in JDeveloper with the same results. Currently, I am using the external one.
    I believe the data source is valid. I can duplicate this problem by just using a plain JDBC connection from DriverManager. Also, I switched to the 1.0.2 version of oc4j, replaced the Oracle stuff with 8i versions and was able to connect using the same data-sources.xml.
    This problem also goes away when using the thin driver but we're reluctant to use the thin driver for performance reasons.
    Thanks for the response,
    TG

  • Character set not supported!! DBConversion error. Need Help!

    I installed JDeveloper9.2 on windows 2000. When I try to make a database server connection by using OCI8 driver, it gives me a "Character set not supported DBConversion error". After that I tried to connect database by using Thin driver, everything is OK. I really need your help.
    I used database connection wizard to make the connection. Connection type I selected ORACLE(JDBC) and drive I selected OCI8. After that I tried to test connection, it gave me above error. I noticed that JDeveloper did not talked with database server at all, I tried to connect with a database server which does not exist, it still gave me the same error.

    Just ran into this myself yester day.
    There is a Metalink Note on it.
    http://metalink.oracle.com/metalink/plsql/ml2_documents.showFrameDocument?p_database_id=NOT&p_id=190281.1
    Problem Description
    You are using OC4J and trying to connect to a database using JDBC OCI and
    are getting:
    "java.sql.SQLException: Character Set Not Supported !!: DBConversion"
    Solution Description
    Replace the <OC4J_HOME>\jdbc\lib\classes12dms.jar with
    <ORACLE_HOME>\jdbc\lib\classes12.jar and rename it with classes12dms.jar.
    Explanation
    It seems there is a mismatch of classes12.zip supplied with OC4J 9.0.2
    and the Oracle9i client libraries ocijdbc8.dll or ocijdbc8.so.
    OC4J 9.0.2 does not use jdbc\lib\classes12.jar instead it uses
    jdbc\lib\classes12dms.jar. So, in order to use the 9.0.1 client with OC4J, you
    will need to make a copy of classes12.jar and rename it to classes12dms.jar
    References
    [NOTE:108876.1] Creating Connection gives "No ocijdbc8 in java.library.path"
    [NOTE:174808.1] JDev9i and OCI Connections
    I copied and renamed the jar (classes12.jar) as they stated.
    Note: It should be in the directory you set in the JDev.conf, mine is
    AddNativeCodePath D:\OraNT\9iDS\bin
    Didn't try the other reply's suggestion of setting an environment variable.

  • 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. ' &#1604;&#1575; ' , 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

  • SQL*Loader-282: Unable to locate character set handle for character set ID

    How do I fix this error that i'm getting when running SQL Loader and connecting to an Oracle 10g database. I'm on 10g client.
    SQL*Loader-282: Unable to locate character set handle for character set ID (46).
    Here's the NLS parameter settings in database: select * from v$nls_parameters
    PARAMETER     VALUE
    NLS_LANGUAGE     AMERICAN
    NLS_TERRITORY     AMERICA
    NLS_CURRENCY     $
    NLS_ISO_CURRENCY     AMERICA
    NLS_NUMERIC_CHARACTERS     .,
    NLS_CALENDAR     GREGORIAN
    NLS_DATE_FORMAT     DD-MON-RR
    NLS_DATE_LANGUAGE     AMERICAN
    NLS_CHARACTERSET     WE8ISO8859P15
    NLS_SORT     BINARY
    NLS_TIME_FORMAT     HH.MI.SSXFF AM
    NLS_TIMESTAMP_FORMAT     DD-MON-RR HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT     HH.MI.SSXFF AM TZR
    NLS_TIMESTAMP_TZ_FORMAT     DD-MON-RR HH.MI.SSXFF AM TZR
    NLS_DUAL_CURRENCY     $
    NLS_NCHAR_CHARACTERSET     AL16UTF16
    NLS_COMP     BINARY
    NLS_LENGTH_SEMANTICS     CHAR
    NLS_NCHAR_CONV_EXCP     TRUE
    Message was edited by:
    evo

    Yep that's it, thanks, I found out about V$NLS_PARAMETERS:
    SQL> select * from v$nls_parameters;
    PARAMETER                  VALUE
    NLS_LANGUAGE               AMERICAN
    NLS_TERRITORY              AMERICA
    NLS_CURRENCY               $
    NLS_ISO_CURRENCY           AMERICA
    NLS_NUMERIC_CHARACTERS     .,
    NLS_CALENDAR               GREGORIAN
    NLS_DATE_FORMAT            DD-MON-RR
    NLS_DATE_LANGUAGE          AMERICAN
    NLS_CHARACTERSET           WE8ISO8859P1
    NLS_SORT                   BINARY
    NLS_TIME_FORMAT            HH.MI.SSXFF AM
    NLS_TIMESTAMP_FORMAT       DD-MON-RR HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT         HH.MI.SSXFF AM TZR
    NLS_TIMESTAMP_TZ_FORMAT    DD-MON-RR HH.MI.SSXFF AM TZR
    NLS_DUAL_CURRENCY          $
    NLS_NCHAR_CHARACTERSET     AL16UTF16
    NLS_COMP                   BINARY
    NLS_LENGTH_SEMANTICS       BYTE
    NLS_NCHAR_CONV_EXCP        FALSEGiven that 9i is not available for Solaris x86,
    how do I change NLS_NCHAR_CHARACTERSET to something that
    will work, like UTF-8?
    Thanks
    Ed

  • SQL*Loader-266: Unable to locate character set handle for None

    Hi All,
    I am getting "SQL*Loader-266: Unable to locate character set handle for None" through sql loader.
    NLS Parameters are :
    NLS_LANGUAGE AMERICAN
    NLS_TERRITORY AMERICA
    NLS_CURRENCY $
    NLS_ISO_CURRENCY AMERICA
    NLS_NUMERIC_CHARACTERS .,
    NLS_CALENDAR GREGORIAN
    NLS_DATE_FORMAT DD-MON-RR
    NLS_DATE_LANGUAGE AMERICAN
    NLS_CHARACTERSET AL32UTF8
    NLS_SORT BINARY
    NLS_TIME_FORMAT HH.MI.SSXFF AM
    NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
    NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
    NLS_DUAL_CURRENCY $
    NLS_NCHAR_CHARACTERSET UTF8
    NLS_COMP BINARY
    NLS_LENGTH_SEMANTICS BYTE
    NLS_NCHAR_CONV_EXCP FALSE
    Kindly help
    Thanks in advance

    Please, provide the exact value of the NLS_LANG environment variable, if defined in the shell environment of SQL*Loader, and the NLS_LANG Registry setting, if on Windows. Please, provide the SQL*Loader control file.
    -- Sergiusz

  • ORA-12709: error while loading create database character set after upgrade

    Dear All
    i m getting ORA-12709: error while loading create database character set, After upgraded the database from 10.2.0.3 to 11.2.0.3 in ebusiness suit env.
    current application version 12.0.6
    please help me to resolve it.
    SQL> startup;
    ORACLE instance started.
    Total System Global Area 1.2831E+10 bytes
    Fixed Size 2171296 bytes
    Variable Size 2650807904 bytes
    Database Buffers 1.0133E+10 bytes
    Redo Buffers 44785664 bytes
    ORA-12709: error while loading create database character set
    -bash-3.00$ echo $ORA_NLS10
    /u01/oracle/PROD/db/teche_st/11.2.0/nls/data/9idata
    export ORACLE_BASE=/u01/oracle
    export ORACLE_HOME=/u01/oracle/PROD/db/tech_st/11.2.0
    export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$PATH
    export PERL5LIB=$ORACLE_HOME/perl/lib/5.10.0:$ORACLE_HOME/perl/site_perl/5.10.0
    export ORA_NLS10=/u01/oracle/PROD/db/teche_st/11.2.0/nls/data/9idata
    export ORACLE_SID=PROD
    -bash-3.00$ pwd
    /u01/oracle/PROD/db/tech_st/11.2.0/nls/data/9idata
    -bash-3.00$ ls -lh |more
    total 56912
    -rw-r--r-- 1 oracle oinstall 951 Jan 15 16:05 lx00001.nlb
    -rw-r--r-- 1 oracle oinstall 957 Jan 15 16:05 lx00002.nlb
    -rw-r--r-- 1 oracle oinstall 959 Jan 15 16:05 lx00003.nlb
    -rw-r--r-- 1 oracle oinstall 984 Jan 15 16:05 lx00004.nlb
    -rw-r--r-- 1 oracle oinstall 968 Jan 15 16:05 lx00005.nlb
    -rw-r--r-- 1 oracle oinstall 962 Jan 15 16:05 lx00006.nlb
    -rw-r--r-- 1 oracle oinstall 960 Jan 15 16:05 lx00007.nlb
    -rw-r--r-- 1 oracle oinstall 950 Jan 15 16:05 lx00008.nlb
    -rw-r--r-- 1 oracle oinstall 940 Jan 15 16:05 lx00009.nlb
    -rw-r--r-- 1 oracle oinstall 939 Jan 15 16:05 lx0000a.nlb
    -rw-r--r-- 1 oracle oinstall 1006 Jan 15 16:05 lx0000b.nlb
    -rw-r--r-- 1 oracle oinstall 1008 Jan 15 16:05 lx0000c.nlb
    -rw-r--r-- 1 oracle oinstall 998 Jan 15 16:05 lx0000d.nlb
    -rw-r--r-- 1 oracle oinstall 1005 Jan 15 16:05 lx0000e.nlb
    -rw-r--r-- 1 oracle oinstall 926 Jan 15 16:05 lx0000f.nlb
    -rw-r--r-- 1 oracle oinstall 1.0K Jan 15 16:05 lx00010.nlb
    -rw-r--r-- 1 oracle oinstall 958 Jan 15 16:05 lx00011.nlb
    -rw-r--r-- 1 oracle oinstall 956 Jan 15 16:05 lx00012.nlb
    -rw-r--r-- 1 oracle oinstall 1005 Jan 15 16:05 lx00013.nlb
    -rw-r--r-- 1 oracle oinstall 970 Jan 15 16:05 lx00014.nlb
    -rw-r--r-- 1 oracle oinstall 950 Jan 15 16:05 lx00015.nlb
    -rw-r--r-- 1 oracle oinstall 1.0K Jan 15 16:05 lx00016.nlb
    -rw-r--r-- 1 oracle oinstall 957 Jan 15 16:05 lx00017.nlb
    -rw-r--r-- 1 oracle oinstall 932 Jan 15 16:05 lx00018.nlb
    -rw-r--r-- 1 oracle oinstall 932 Jan 15 16:05 lx00019.nlb
    -rw-r--r-- 1 oracle oinstall 951 Jan 15 16:05 lx0001a.nlb
    -rw-r--r-- 1 oracle oinstall 944 Jan 15 16:05 lx0001b.nlb
    -rw-r--r-- 1 oracle oinstall 953 Jan 15 16:05 lx0001c.nlb
    Starting up:
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options.
    ORACLE_HOME = /u01/oracle/PROD/db/tech_st/11.2.0
    System name: SunOS
    Node name: proddb3.zakathouse.org
    Release: 5.10
    Version: Generic_147440-19
    Machine: sun4u
    Using parameter settings in server-side spfile /u01/oracle/PROD/db/tech_st/11.2.0/dbs/spfilePROD.ora
    System parameters with non-default values:
    processes = 200
    sessions = 400
    timed_statistics = TRUE
    event = ""
    shared_pool_size = 416M
    shared_pool_reserved_size= 40M
    nls_language = "american"
    nls_territory = "america"
    nls_sort = "binary"
    nls_date_format = "DD-MON-RR"
    nls_numeric_characters = ".,"
    nls_comp = "binary"
    nls_length_semantics = "BYTE"
    memory_target = 11G
    memory_max_target = 12G
    control_files = "/u01/oracle/PROD/db/apps_st/data/cntrl01.dbf"
    control_files = "/u01/oracle/PROD/db/tech_st/10.2.0/dbs/cntrl02.dbf"
    control_files = "/u01/oracle/PROD/db/apps_st/data/cntrl03.dbf"
    db_block_checksum = "TRUE"
    db_block_size = 8192
    compatible = "11.2.0.0.0"
    log_archive_dest_1 = "LOCATION=/u01/oracle/PROD/db/apps_st/data/archive"
    log_archive_format = "%t_%s_%r.dbf"
    log_buffer = 14278656
    log_checkpoint_interval = 100000
    log_checkpoint_timeout = 1200
    db_files = 512
    db_file_multiblock_read_count= 8
    db_recovery_file_dest = "/u01/oracle/fast_recovery_area"
    db_recovery_file_dest_size= 14726M
    log_checkpoints_to_alert = TRUE
    dml_locks = 10000
    undo_management = "AUTO"
    undo_tablespace = "APPS_UNDOTS1"
    db_block_checking = "FALSE"
    session_cached_cursors = 500
    utl_file_dir = "/usr/tmp"
    utl_file_dir = "/usr/tmp"
    utl_file_dir = "/u01/oracle/PROD/db/tech_st/10.2.0/appsutil/outbound"
    utl_file_dir = "/u01/oracle/PROD/db/tech_st/10.2.0/appsutil/outbound/PROD_proddb3"
    utl_file_dir = "/usr/tmp"
    plsql_code_type = "INTERPRETED"
    plsql_optimize_level = 2
    job_queue_processes = 2
    cursor_sharing = "EXACT"
    parallel_min_servers = 0
    parallel_max_servers = 8
    core_dump_dest = "/u01/oracle/PROD/db/tech_st/10.2.0/admin/PROD_proddb3/cdump"
    audit_file_dest = "/u01/oracle/admin/PROD/adump"
    db_name = "PROD"
    open_cursors = 600
    pga_aggregate_target = 1G
    workarea_size_policy = "AUTO"
    optimizer_secure_view_merging= FALSE
    aq_tm_processes = 1
    olap_page_pool_size = 4M
    diagnostic_dest = "/u01/oracle"
    max_dump_file_size = "20480"
    Tue Jan 15 16:16:02 2013
    PMON started with pid=2, OS id=18608
    Tue Jan 15 16:16:02 2013
    PSP0 started with pid=3, OS id=18610
    Tue Jan 15 16:16:03 2013
    VKTM started with pid=4, OS id=18612 at elevated priority
    VKTM running at (10)millisec precision with DBRM quantum (100)ms
    Tue Jan 15 16:16:03 2013
    GEN0 started with pid=5, OS id=18616
    Tue Jan 15 16:16:03 2013
    DIAG started with pid=6, OS id=18618
    Tue Jan 15 16:16:03 2013
    DBRM started with pid=7, OS id=18620
    Tue Jan 15 16:16:03 2013
    DIA0 started with pid=8, OS id=18622
    Tue Jan 15 16:16:03 2013
    MMAN started with pid=9, OS id=18624
    Tue Jan 15 16:16:03 2013
    DBW0 started with pid=10, OS id=18626
    Tue Jan 15 16:16:03 2013
    LGWR started with pid=11, OS id=18628
    Tue Jan 15 16:16:03 2013
    CKPT started with pid=12, OS id=18630
    Tue Jan 15 16:16:03 2013
    SMON started with pid=13, OS id=18632
    Tue Jan 15 16:16:04 2013
    RECO started with pid=14, OS id=18634
    Tue Jan 15 16:16:04 2013
    MMON started with pid=15, OS id=18636
    Tue Jan 15 16:16:04 2013
    MMNL started with pid=16, OS id=18638
    DISM started, OS id=18640
    ORACLE_BASE from environment = /u01/oracle
    Tue Jan 15 16:16:08 2013
    ALTER DATABASE MOUNT
    ORA-12709 signalled during: ALTER DATABASE MOUNT...

    ORA-12709 signalled during: ALTER DATABASE MOUNT...Do you have any trace files generated at the time you get this error?
    Please see these docs.
    ORA-12709: WHILE STARTING THE DATABASE [ID 1076156.6]
    Upgrading from 9i to 10gR2 Fails With ORA-12709 : Error While Loading Create Database Character Set [ID 732861.1]
    Ora-12709 While Trying To Start The Database [ID 311035.1]
    ORA-12709 when Mounting the Database [ID 160478.1]
    How to Move From One Database Character Set to Another at the Database Level [ID 1059300.6]
    Thanks,
    Hussein

  • 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

  • How to review implication of database character set change on PL/SQL code?

    Hi,
    We are converting WE8ISO8859P1 oracle db characterset to AL32UTF8. Before conversion, i want to check implication on PL/SQL code for byte based SQL functions.
    What all points to consider while checking implications on PL/SQL code?
    I could find 3 methods on google surfing, SUBSTRB, LENGTHB, INSTRB. What do I check if these methods are used in PL/SQL code?
    What do we check if SUBSTR and LENGTH functions are being used in PL/SQl code?
    What all other methods should I check?
    What do I check in PL/SQL if varchar and char type declarations exist in code?
    How do i check implication of database characterset change to AL32UTF8 for byte bases SQL function.
    Thanks in Advance.
    Regards,
    Rashmi

    There is no quick answer.  Generally, the problem with PL/SQL code is that once you migrate from a single-byte character set (like WE8ISO8859P1) to a multibyte character set (like AL32UTF8), you can no longer assume that one character is one byte. Traditionally, column and PL/SQL variable lengths are expressed in bytes. Therefore, the same string of Western European accented letters may no longer fit into a column or variable after migration, as it may now be longer than the old limit (2 bytes per accented letter compared to 1 byte previously). Depending on how you dealt with column lengths during the migration, for example, if you migrated them to character length semantics, and depending on how relevant columns were declared (%TYPE vs explicit size), you may need to adjust maximum lengths of variables to accommodate longer strings.
    The use of SUBSTR, INSTR, and LENGTH and their byte equivalents needs to be reviewed. You need to understand what the functions are used for. If the SUBSTR function is used to truncate a string to a maximum length of a variable, you may need to change it to SUBSTRB, if the variable's length constraint is still declared in bytes.  However, if the variable's maximum length is now expressed in characters, SUBSTR needs to be used.  However, if SUBSTR is used to extract a functional part of a string (e.g. during parsing), possibly based on result from INSTR, then you should use SUBSTR and INSTR independently of the database character set -- characters matter here, not bytes. On the other hand, if SUBSTR is used to extract a field in a SQL*Loader-like fixed-format input file (e.g. read with UTL_FILE), you may need to standardize on SUBSTRB to make sure that fields are extracted correctly based on defined byte boundaries.
    As you see, there is universal recipe on handling these functions. Their use needs to be reviewed and understood and it should be decided if they are fine as-is or if they need to be replaced with other forms.
    Thanks,
    Sergiusz

  • Data load uses wrong character set, where to correct? APEX bug/omission?

    Hi,
    I created a set of Data Load pages in my application, so the users can upload a CSV file.
    But unlike the Load spreadsheet data (under SQL Workshop\Utilities\Data Workshop), where you can set the 'File Character Set', I didn't see where to set the Character set for Data Load pages in my application.
    Now there is a character set mismatch, "m³/h" and "°C" become "m�/h" and "�C"
    Where to set?
    Seems like an APEX bug or at least omission, IMHO the Data Load page should ask for the character set, as clients with different character sets could be uploading CSV.
    Apex 4.1 (testing on the apex.oracle.com website)

    Hello JP,
    Please give us some more details about your database version and its character set, and the character set of the CSV file.
    >> …But unlike the Load spreadsheet data (under SQL Workshop\Utilities\Data Workshop), where you can set the 'File Character Set', I didn't see where to set the Character set for Data Load pages in my application.
    It seems that you are right. I was not able to find any reference to the (expected/default) character set of the uploaded file in the current APEX documentation.
    >> If it's an APEX omission, where could I report that?
    Usually, an entry on this forum is enough as some of the development team members are frequent participants. Just to be sure, I’ll draw the attention of one of them to the thread.
    Regards,
    Arie.
    &diams; Please remember to mark appropriate posts as correct/helpful. For the long run, it will benefit us all.
    &diams; Author of Oracle Application Express 3.2 – The Essentials and More

  • Help : error while loading create database character set

    SQL> startup
    ORACLE instance started.
    Total System Global Area 599785472 bytes
    Fixed Size 2022600 bytes
    Variable Size 180355896 bytes
    Database Buffers 411041792 bytes
    Redo Buffers 6365184 bytes
    ORA-12709: error while loading create database character set

    ORA-12709 error while loading create database character set
    Cause: This is an internal error.
    Action: Contact Oracle Support Services.

  • Character Set Error in PL/SQL

    Hi,
    While connecting to PL/SQL Developer I am getting this following error.
    Database character set (AL32UTF8) and client character set (WE8MSWIN1252) are different.
    Character set conversion may cause unexpected results.
    Note: you can set the client character set through the NLS_LANG registry key in
    HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_XE.
    Please help me avoid this error.
    Thanks.

    That is presumably a PL/SQL Developer error. You may want to contact the vendor of that particular product to understand that warning because it makes no sense to me.
    It is perfectly appropriate, and quite normal, for the client character set to be a subset of the database character set. Setting the client character set to match the database character set can create a host of problems that lead to invalid data being stored in the database. This appears designed to increase the odds that this particular tool will work correctly while decreasing the odds that everything else in your environment will work correctly. That seems like a relatively poor trade-off to me.
    Justin

Maybe you are looking for