http://iotn.co.kr ¿¬¶ôó: gilho.kr@gmail.com [ The Japanese government should apologize to Japanese Military Sexual Slavery victim. / ìíÜâïÙݤªÏìíÜâÏÚªÎàõîÜÒ¿ÖË?ßåíºªËÞóñªª¹ªÙª. ]
IMP-00058: ORACLE error 1461 encountered
ORA-01461: can bind a LONG value only for insert into a LONG column
IMP-00028: partial import of previous table rolled back: 2679 rows rolled back
doc id: 788156.1 AL32UTF8 / UTF8 (Unicode) Database Character Set Implications
-----------------------------------------------------------------------------
In this Document
Purpose
Scope and Application
AL32UTF8 / UTF8 (Unicode) Database Character Set Implications
A) Often asked questions:
A.1) Do I need to use Nchar, Nvarchar2 or Nclob?
A.2) Does my Operating System need to support Unicode?
A.3) What are the Unicode charactersets and the Unicode versions in Oracle RDBMS?
A.4) Is -insert your preferred language here- supported in an Oracle Unicode database?
B) Server side implications.
B.1) Storage.
B.2) How much will my database grow when going to AL32UTF8?
B.3) Codepoints for characters may change in AL32UTF8.
B.4) The meaning of SP2-0784, ORA-29275 and ORA-600 [kole_t2u], [34] errors / losing characters when using convert.
B.5) Going to AL32UTF8 from another characterset.
B.6) ORA-01401 / ORA-12899 while importing data in an AL32UTF8 database.
B.6) Object and user names using non-US7ASCII characters.
B.6) The password of an user can only contain single byte data in 10g and below.
B.7) When using DBMS_LOB.LOADFROMFILE
B.8) When using UTL_FILE
B.9) When using sqlldr or external tables
B.10) Make sure you do not store "binary" (Encrypted) data in character datatypes (CHAR,VARCHAR2,CLOB).
B.11) String functions work with characters not byte (length,like,substr ...).
B.12) LPad and Rpad count in "display units" not characters.
B.13) Using LIKE and INSTR.
B.14) Character functions that are returning character values might silently truncate data.
B.15) Column size triple/quadruple when using Materialized Views / CTAS trough database link.
B.16) When fetching data from non-AL32UTF8 databases using cursors (PL/SQL)
B.17) When using HTMLDB.
B.18) When using non-US7ASCII names in directory's or file names.
B.19) When using XDB (xmltype).
C) The Client side.
C.1) Common misconceptions about NLS_LANG.
C.2) Configuring your UNIX client to be an UTF8 (Unicode) client.
C.3) Configuring your Windows client to be an UTF8 (Unicode) client.
C.4) The default column width of output in sqlplus will change.
C.5) Configuring your web based client to be a Unicode client.
C.6) Using Sqlplus to run scripts in UTF-8 encoding
C.7) Using Oracle Applications.
C.8) Using Portal.
C.9) Oracle Forms PDF and Unicode
C.10) Changing a database to AL32UTF8 hosting an OracleAS 10g Metadata Repository.
References