Results 1 to 2 of 2
  1. #1
    Join Date
    Jun 2009
    Posts
    1

    Unanswered: Character set encoding in Oracle 10g XE

    Hi everybody!

    This is my first post and, first of everything, I want to apologize about my poor English... So, let's go!

    I've instaled Oracle 10g XE Server on an Ubuntu linux and I need to configure it to support spanish tipical chars (, , ...). I've searched in this forum and I have found this post: http://www.dbforums.com/oracle/11152...racterset.html but I haven't fixed my problem.

    I have a table with a column defined as VARCHAR2(8) (this table is defined by our client: I can't change anything). They sent us an script to load data and all rows have 8 characters in that column. Some of them have an '' and oracle doesn't like it:

    ERROR en lnea 1:
    ORA-12899: el valor es demasiado grande para la
    columna "DESEXTERNO"."CEN"."CENCXU" (real: 9,
    mximo: 8)
    if I execute "select * from v$NLS_PARAMETERS;" the result is:

    Code:
    PARAMETER					VALUE
    ---------------------------------------------------------------------------------------------------------
    NLS_LANGUAGE 					SPANISH
    NLS_TERRITORY					SPAIN
    NLS_CURRENCY					
    NLS_ISO_CURRENCY				SPAIN
    NLS_NUMERIC_CHARACTERS			,.
    NLS_CALENDAR					GREGORIAN
    NLS_DATE_FORMAT					DD/MM/RR
    NLS_DATE_LANGUAGE				SPANISH
    NLS_CHARACTERSET				AL32UTF8
    NLS_SORT						SPANISH
    NLS_TIME_FORMAT					HH24:MI:SSXFF
    NLS_TIMESTAMP_FORMAT			DD/MM/RR HH24:MI:SSXFF
    NLS_TIME_TZ_FORMAT				HH24:MI:SSXFF TZR
    NLS_TIMESTAMP_TZ_FORMAT			DD/MM/RR HH24:MI:SSXFF TZR
    NLS_DUAL_CURRENCY				
    NLS_NCHAR_CHARACTERSET			AL16UTF16
    NLS_COMP						BINARY
    NLS_LENGTH_SEMANTICS			BYTE
    NLS_NCHAR_CONV_EXCP				FALSE
    I've created a table for testing with a column defined as VARCHAR2(2) and I can insert "" there but I get the same error if I try to insert "a". I'm using sql*plus for this...

    Could somebody help me?

    Thank you very much

  2. #2
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    Code:
    12899, 00000, "value too large for column %s (actual: %s, maximum: %s)"
    // *Cause: An attempt was made to insert or update a column with a value
    //         which is too wide for the width of the destination column.
    //         The name of the column is given, along with the actual width
    //         of the value, and the maximum allowed width of the column.
    //         Note that widths are reported in characters if character length
    //         semantics are in effect for the column, otherwise widths are
    //         reported in bytes.
    // *Action: Examine the SQL statement for correctness.  Check source
    //          and destination column data types.
    //          Either make the destination column wider, or use a subset
    //          of the source column (i.e. use substring).
    Some characters consume more than 1 byte.
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •