R12 Characterset conversion to UTF8 on 11 G R2 Database

We are doing Characterset conversion to UTF8, i ran csscan its complaning lot of lossy chars and Convertible chars,do i need to take export below all tables..?
ata Dictionary Tables:
Datatype Changeless Convertible Truncation Lossy
VARCHAR2 117,133,414 0 0 0
CHAR 17,402 0 0 0
LONG 8,074,421 0 0 0
CLOB 4,348,695 22,903 0 0
VARRAY 42,001 0 0 0
Total 129,615,933 22,903 0 0
Total in percentage 99.982% 0.018% 0.000% 0.000%
The data dictionary can be safely migrated using the CSALTER script
XML CSX Dictionary Tables:
Datatype Changeless Convertible Truncation Lossy
VARCHAR2 501 0 0 0
CHAR 0 0 0 0
LONG 0 0 0 0
CLOB 0 0 0 0
VARRAY 0 0 0 0
Total 501 0 0 0
Total in percentage 100.000% 0.000% 0.000% 0.000%
[Application Data Conversion Summary]
Datatype Changeless Convertible Truncation Lossy
VARCHAR2 118,182,641 0 103 1,260,883
CHAR 265 0 0 0
LONG 61,948 0 0 0
CLOB 129,455 827 0 0
VARRAY 32,797 0 0 0
Total 118,407,106 827 103 1,260,883
Total in percentage 98.946% 0.001% 0.000% 1.054%
Data Dictionary Tables:
USER.TABLE Convertible Truncation Lossy
MDSYS.OPENLS_NODES 17 0 0
MDSYS.SDO_COORD_OP_PARAM_VALS 200 0 0
MDSYS.SDO_GEOR_XMLSCHEMA_TABLE 1 0 0
MDSYS.SDO_STYLES_TABLE 78 0 0
MDSYS.SDO_XML_SCHEMAS 3 0 0
ORDDATA.ORDDCM_CT_PRED_OPRD 51 0 0
ORDDATA.ORDDCM_DOCS 9 0 0
ORDDATA.ORDDCM_MAPPING_DOCS 1 0 0
SYS.METASTYLESHEET 178 0 0
SYS.REGISTRY$ERROR 2 0 0
SYS.RULE$ 21 0 0
SYS.SCHEDULER$_EVENT_LOG 182 0 0
SYS.WRH$_SQLTEXT 2,099 0 0
SYS.WRH$_SQL_PLAN 1,736 0 0
SYS.WRI$_ADV_ACTIONS 5,452 0 0
SYS.WRI$_ADV_DIRECTIVE_META 5 0 0
SYS.WRI$_ADV_OBJECTS 2,278 0 0
SYS.WRI$_ADV_RATIONALE 9,594 0 0
SYS.WRI$_ADV_SQLT_PLANS 455 0 0
SYS.WRI$_ADV_SQLT_PLAN_STATS 288 0 0
SYS.WRI$_DBU_FEATURE_METADATA 188 0 0
SYS.WRI$_DBU_FEATURE_USAGE 16 0 0
SYS.WRI$_DBU_HWM_METADATA 20 0 0
SYS.WRI$_REPT_FILES 27 0 0
XDB.XDB$DXPTAB 2 0 0
XML CSX Dictionary Tables:
USER.TABLE Convertible Truncation Lossy
Application Data:
USER.TABLE Convertible Truncation Lossy
APPLSYS.BISM_OBJECTS 4 0 0
APPLSYS.DR$FND_LOBS_CTX$I 0 103 1,260,883
APPLSYS.FND_CONC_PROG_ANNOTATIONS 272 0 0
APPLSYS.FND_OAM_CONTEXT_FILES 15 0 0
APPLSYS.FND_OAM_DOC_LINK 1 0 0
APPS.FND_OAM_CONTEXT_FILES_1 6 0 0
AZ.AZ_APIS 11 0 0
AZ.AZ_SELECTION_SET_ENTITIES_B 48 0 0
ECX.ECX_DTDS 205 0 0
ECX.ECX_FILES 91 0 0
IBC.IBC_ATTRIBUTE_BUNDLES 41 0 0
JTF.JTF_HEADER_DTD 1 0 0
JTF.JTF_MESSAGE_OBJECTS 82 0 0
JTF.JTY_TRANS_USG_PGM_SQL 29 0 0
ODM.ODM_PMML_DTD 1 0 0
OKC.OKC_REPORT_SQL_B 3 0 0
OKC.OKC_REPORT_SQL_TL 2 0 0
OKC.OKC_REPORT_XSL_TL 5 0 0
XDP.XDP_PROC_BODY 10 0 0
[Distribution of Convertible, Truncated and Lossy Data by Column]
Data Dictionary Tables:
USER.TABLE|COLUMN Convertible Truncation Lossy
MDSYS.OPENLS_NODES|SYS_NC00004$ 17 0 0
MDSYS.SDO_COORD_OP_PARAM_VALS|PARAM_VALUE_FILE 200 0 0
MDSYS.SDO_GEOR_XMLSCHEMA_TABLE|XMLSCHEMA 1 0 0
MDSYS.SDO_STYLES_TABLE|DEFINITION 78 0 0
MDSYS.SDO_XML_SCHEMAS|XMLSCHEMA 3 0 0
ORDDATA.ORDDCM_CT_PRED_OPRD|SYS_NC00004$ 51 0 0
ORDDATA.ORDDCM_DOCS|SYS_NC00005$ 9 0 0
ORDDATA.ORDDCM_MAPPING_DOCS|SYS_NC00007$ 1 0 0
SYS.METASTYLESHEET|STYLESHEET 178 0 0
SYS.REGISTRY$ERROR|MESSAGE 1 0 0
SYS.REGISTRY$ERROR|STATEMENT 1 0 0
SYS.RULE$|CONDITION 21 0 0
SYS.SCHEDULER$_EVENT_LOG|ADDITIONAL_INFO 182 0 0
SYS.WRH$_SQLTEXT|SQL_TEXT 2,099 0 0
SYS.WRH$_SQL_PLAN|OTHER_XML 1,736 0 0
SYS.WRI$_ADV_ACTIONS|ATTR5 2,726 0 0
SYS.WRI$_ADV_ACTIONS|ATTR6 2,726 0 0
SYS.WRI$_ADV_DIRECTIVE_META|DATA 5 0 0
SYS.WRI$_ADV_OBJECTS|ATTR4 2,278 0 0
SYS.WRI$_ADV_RATIONALE|ATTR5 9,594 0 0
SYS.WRI$_ADV_SQLT_PLANS|OTHER_XML 455 0 0
SYS.WRI$_ADV_SQLT_PLAN_STATS|OTHER 288 0 0
SYS.WRI$_DBU_FEATURE_METADATA|INST_CHK_LOGIC 21 0 0
SYS.WRI$_DBU_FEATURE_METADATA|USG_DET_LOGIC 167 0 0
SYS.WRI$_DBU_FEATURE_USAGE|FEATURE_INFO 16 0 0
SYS.WRI$_DBU_HWM_METADATA|LOGIC 20 0 0
SYS.WRI$_REPT_FILES|SYS_NC00005$ 27 0 0
XDB.XDB$DXPTAB|SYS_NC00006$ 2 0 0
XML CSX Dictionary Tables:
USER.TABLE|COLUMN Convertible Truncation Lossy
Application Data:
USER.TABLE|COLUMN Convertible Truncation Lossy
APPLSYS.BISM_OBJECTS|SYS_NC00023$ 4 0 0
APPLSYS.DR$FND_LOBS_CTX$I|TOKEN_TEXT 0 103 1,260,883
APPLSYS.FND_CONC_PROG_ANNOTATIONS|PROGRAM_ANNOTAT 272 0 0
APPLSYS.FND_OAM_CONTEXT_FILES|TEXT 15 0 0
APPLSYS.FND_OAM_DOC_LINK|DOC_LINK_INFO 1 0 0
APPS.FND_OAM_CONTEXT_FILES_1|TEXT 6 0 0
AZ.AZ_APIS|FILTERING_PARAMETERS 11 0 0
AZ.AZ_SELECTION_SET_ENTITIES_B|FILTERING_PARAMETE 48 0 0
ECX.ECX_DTDS|PAYLOAD 205 0 0
ECX.ECX_FILES|PAYLOAD 91 0 0
IBC.IBC_ATTRIBUTE_BUNDLES|ATTRIBUTE_BUNDLE_DATA 41 0 0
JTF.JTF_HEADER_DTD|HEADER_DTD 1 0 0
JTF.JTF_MESSAGE_OBJECTS|BUS_OBJ_DTD 41 0 0
JTF.JTF_MESSAGE_OBJECTS|BUS_OBJ_SQL 41 0 0
JTF.JTY_TRANS_USG_PGM_SQL|BATCH_DEA_SQL 1 0 0
JTF.JTY_TRANS_USG_PGM_SQL|BATCH_INCR_SQL 5 0 0
JTF.JTY_TRANS_USG_PGM_SQL|BATCH_TOTAL_SQL 6 0 0
JTF.JTY_TRANS_USG_PGM_SQL|INCR_REASSIGN_SQL 5 0 0
JTF.JTY_TRANS_USG_PGM_SQL|REAL_TIME_INSERT 6 0 0
JTF.JTY_TRANS_USG_PGM_SQL|REAL_TIME_SQL 6 0 0
ODM.ODM_PMML_DTD|DTD 1 0 0
OKC.OKC_REPORT_SQL_B|SQL_TEXT 3 0 0
OKC.OKC_REPORT_SQL_TL|HELP_TEXT 2 0 0
OKC.OKC_REPORT_XSL_TL|HELP_TEXT 2 0 0
OKC.OKC_REPORT_XSL_TL|XSL_TEXT 3 0 0
XDP.XDP_PROC_BODY|PROC_BODY 10 0 0
[Indexes to be Rebuilt]
USER.INDEX on USER.TABLE(COLUMN)
APPLSYS.DR$FND_LOBS_CTX$X on APPLSYS.DR$FND_LOBS_CTX$I(TOKEN_TEXT)
APPLSYS.DR$FND_LOBS_CTX$X on APPLSYS.DR$FND_LOBS_CTX$I(TOKEN_TYPE)
APPLSYS.DR$FND_LOBS_CTX$X on APPLSYS.DR$FND_LOBS_CTX$I(TOKEN_FIRST)
APPLSYS.DR$FND_LOBS_CTX$X on APPLSYS.DR$FND_LOBS_CTX$I(TOKEN_LAST)
APPLSYS.DR$FND_LOBS_CTX$X on APPLSYS.DR$FND_LOBS_CTX$I(TOKEN_COUNT)
IBC.IBC_ATTRIBUTE_BUNDLES_CTX on IBC.IBC_ATTRIBUTE_BUNDLES(ATTRIBUTE_BUNDLE_DATA)
-----------------------------------------------------------------------------------------

Sawwan,
I am getting below error
[oracle@uat nls]$ exp file=exp_utf8.dmp parfile=exp.par
Export: Release 11.2.0.1.0 - Production on Wed Apr 20 18:43:11 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Username: system
Password:
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Export done in UTF8 character set and AL16UTF16 NCHAR character set
server uses US7ASCII character set (possible charset conversion)
About to export specified tables via Conventional Path ...
Current user changed to APPLSYS
. . exporting table BISM_OBJECTS 4 rows exported
EXP-00011: APPLSYS.DR$FND_LOBS_CTX$I does not exist ( do i need to procced with truncation of convertable objects..?, please confirm me, i am confusing here)
http://www.oracle-latest-technology.com/2011/02/how-to-convert-character-set-of-oracle.html
. . exporting table FND_CONC_PROG_ANNOTATIONS 290 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table FND_OAM_CONTEXT_FILES 15 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table FND_OAM_DOC_LINK 1 rows exported
EXP-00091: Exporting questionable statistics.
Current user changed to APPS
. . exporting table FND_OAM_CONTEXT_FILES_1 6 rows exported
EXP-00091: Exporting questionable statistics.
Current user changed to AZ
. . exporting table AZ_APIS 356 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table AZ_SELECTION_SET_ENTITIES_B 490 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
Current user changed to ECX
. . exporting table ECX_DTDS 205 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table ECX_FILES 91 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
Current user changed to IBC
EXP-00011: IBC.IBC_ATTRIBUTE_BUNDLES_DATA does not exist
. . exporting table IBC_ATTRIBUTE_BUNDLES 41 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
Current user changed to JTF
. . exporting table JTF_HEADER_DTD 1 rows exported
EXP-00091: Exporting questionable statistics.
. . exporting table JTF_MESSAGE_OBJECTS 41 rows exported
EXP-00091: Exporting questionable statistics.
. . exporting table JTY_TRANS_USG_PGM_SQL 7 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00010: MDSYS is not a valid username
EXP-00010: MDSYS is not a valid username
EXP-00010: MDSYS is not a valid username
EXP-00010: MDSYS is not a valid username
EXP-00010: MDSYS is not a valid username
EXP-00010: MDSYS is not a valid username
Current user changed to ODM
. . exporting table ODM_PMML_DTD 1 rows exported
EXP-00091: Exporting questionable statistics.
Current user changed to OKC
. . exporting table OKC_REPORT_SQL_B 3 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table OKC_REPORT_SQL_TL 3 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table OKC_REPORT_XSL_TL 3 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
EXP-00010: XDB is not a valid username
Current user changed to XDP
. . exporting table XDP_PROC_BODY 10 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
Current user changed to ORDDATA
. . exporting table ORDDCM_CT_PRED_OPRD 51 rows exported
. . exporting table ORDDCM_DOCS 9 rows exported
. . exporting table ORDDCM_MAPPING_DOCS 1 rows exported
EXP-00091: Exporting questionable statistics.
Export terminated successfully with warnings.
[oracle@uat nls]$ exp file=exp_fnd_lobs.dmp table=APPLSYS.DR$FND_LOBS_CTX$I
LRM-00101: unknown parameter name 'table'

Similar Messages

Characterset Conversion

Hi,
I would like to change the characterset of my E-Business Suite R12.1.3 with database 10.2.0.4 from US7ASCII to UTF8. Which is the best document to follow and what all are the things I need to take care of?
Expecting expert's advice.
Sony

Sony,
Please see the docs referenced in these threads.
MLS Data Character Set Conversion
MLS Data Character Set Conversion
Oracle E-Biz Applications Database characterset conversion
Re: Oracle E-Biz Applications Database characterset conversion
Thanks,
Hussein

Convert characterset WE8MSWIN1252 to UTF8

Hi all
I am using Oracle 10g Database. Now the Characterset as WE8MSWIN1252. I want to change my CharacterSet to UTF8. It is possible.
Can anyone please post me the steps involved.
Very Urgent !!!!!!!
Regds
Nirmal

Subject: Changing WE8ISO8859P1/ WE8ISO8859P15 or WE8MSWIN1252 to (AL32)UTF8
Doc ID: Note:260192.1 Type: BULLETIN
Last Revision Date: 24-JUL-2007 Status: PUBLISHED
Changing the database character set to (AL32)UTF8
=================================================
When changing a Oracle Applications Database:
Please see the following note for Oracle Applications database
Note 124721.1 Migrating an Applications Installation to a New Character Set
If you have any doubt log an Oracle Applications TAR for assistance.
It might be usefull to read this note, even when using Oracle Applications
seen it explains what to do with "lossy" and "truncation" in the csscan output.
Scope:
You can't simply use "ALTER DATABASE CHARACTER SET" to go from WE8ISO8859P1 or
WE8ISO8859P15 or WE8MSWIN1252 to (AL32)UTF8 because (AL32)UTF8 is not a
binary superset of any of these character sets.
You will run into ORA-12712 or ORA-12710 because the code points for the
"extended ASCII" characters are different between these 3 character sets
and (AL32)UTF8.
This note will describe a method of still using a
"ALTER DATABASE CHARACTER SET" in a limited way.
Note that we strongly recommend to use the SAME flow when doing a full
export / import.
The choise between using FULL exp/imp and a PARTIAL exp/imp is made in point
7)
DO NOT USE THIS NOTE WITH ANY OTHER CHARACTERSETS
WITHOUT CHECKING THIS WITH ORACLE SUPPORT
THIS NOTE IS SPECIFIC TO CHANGING:
FROM: WE8ISO8859P1, WE8ISO8859P15 or WE8MSWIN1252
TO: AL32UTF8 or UTF8
AL32UTF8 and UTF8 are both Unicode character sets in the oracle database.
UTF8 encodes Unicode version 3.0 and will remain like that.
AL32UTF8 is kept up to date with the Unicode standard and encodes the Unicode
standards 3.0 (in database 9.0), 3.1 (database 9.2) or 3.2 (database 10g).
For the purposes of this note we shall only use AL32UTF8 from here on forward,
you can substitute that for UTF8 without any modifications.
If you use 8i or lower clients please have a look at
Note 237593.1 Problems connecting to AL32UTF8 databases from older versions (8i and lower)
WE8ISO8859P1, WE8ISO8859P15 or WE8MSWIN1252 are the 3 main character sets that
are used to store Western European or English/American data in.
All standard ASCII characters that are used for English/American do not have to
be converted into AL32UTF8 - they are the same in AL32UTF8. However, all other
characters, like accented characters, the Euro sign, MS "smart quotes", etc.
etc., have a different code point in AL32UTF8.
That means that if you make extensive use of these types of characters the
preferred way of changing to AL32UTF8 would be to export the entire database and
import the data into a new AL32UTF8 database.
However, if you mainly use standard ASCII characters and not a lot else (for
example if you only store English text, maybe with some Euro signs or smart
quotes here and there), then it could be a lot quicker to proceed with this
method.
Please DO read in any case before going to UTF8 this note:
Note 119119.1 AL32UTF8 / UTF8 (unicode) Database Character Set Implications
and consider to use CHAR semantics if on 9i or higher:
Note 144808.1 Examples and limits of BYTE and CHAR semantics usage
It's best to change the tables and so to CHAR semantics before the change
to UTF8.
This procedure is valid for Oracle 8i, 9i and 10g.
Note:
* If you are on 9i please make sure you are at least on Patch 9204, see
Note 250802.1 Changing character set takes a very long time and uses lots of rollback space
* if you have any function-based indexes on columns using CHAR length semantics
then these have to be removed and re-created after the character set has
been changed. Failure to do so will result in ORA-604 / ORA-2262 /ORA-904
when the "alter database character set" statement is used in step 4.
Actions to take:
1) install the csscan tool.
1A)For 10g use the csscan 2.x found in /bin, no need to install a newer version
Goto 1C)
1B)For 9.2 and lower:
Please DO install the version 1.2 or higher from TechNet for you version.
http://technet.oracle.com/software/tech/globalization/content.html
and install this.
copy all scripts and executables found in the zip file you downloaded
to your oracle_home overwriting the old versions.
goto 1C).
Note: do NOT use the CSSCAN of a 10g installation for 9i/8i!
1C)Run csminst.sql using these commands and SQL statements:
cd $ORACLE_HOME/rdbms/admin
set oracle_sid=<your SID>
sqlplus "sys as sysdba"
SQL>set TERMOUT ON
SQL>set ECHO ON
SQL>spool csminst.log
SQL> START csminst.sql
Check the csminst.log for errors.
If you get when running CSSCAN the error
"Character set migrate utility schema not compatible."
then
1ca) or you are starting the old executable, please do overwrite all old files with the files
from the newer version from technet (1.2 has more files than some older versions, that's normal).
1cb) or check your PATH , you are not starting csscan from this ORACLE_HOME
1cc) or you have not runned the csminst.sql from the newer version from technet
More info is in Note 123670.1 Use Scanner Utility before Altering the Database Character Set
Please, make sure you use/install csscan version 1.2 .
2) Check if you have no invalid code points in the current character set:
Run csscan with the following syntax:
csscan FULL=Y FROMCHAR=<existing database character set> TOCHAR=<existing database character set> LOG=WE8check CAPTURE=Y ARRAY=1000000 PROCESS=2
Always run CSSCAN with 'sys as sysdba'
This will create 3 files :
WE8check.out a log of the output of csscan
WE8check.txt a Database Scan Summary Report
WE8check.err contains the rowid's of the rows reported in WE8check.txt
At this moment we are just checking that all data is stored correctly in the
current character set. Because you've entered the TO and FROM character sets as
the same you will not have any "Convertible" or "Truncation" data.
If all the data in the database is stored correctly at the moment then there
should only be "Changeless" data.
If there is any "Lossy" data then those rows contain code points that are not
currently stored correctly and they should be cleared up before you can continue
with the steps in this note. Please see the following note for clearing up any
"Lossy" data:
Note 225938.1 Database Character Set Healthcheck
Only if ALL data in WE8check.txt is reported as "Changeless" it is safe to
proceed to point 3)
NOTE:
if you have a WE8ISO8859P1 database and lossy then changing your WE8ISO8859P1 to
WE8MSWIN1252 will most likly solve you lossy.
Why ? this is explained in
Note 252352.1 Euro Symbol Turns up as Upside-Down Questionmark
Do first a
csscan FULL=Y FROMCHAR=WE8MSWIN1252 TOCHAR=WE8MSWIN1252 LOG=1252check CAPTURE=Y ARRAY=1000000 PROCESS=2
Always run CSSCAN with 'sys as sysdba'
For 9i, 8i:
Only if ALL data in 1252check.txt is reported as "Changeless" it is safe to
proceed to the next point. If not, log a tar and provide the 3 generated files.
Shutdown the listener and any application that connects locally to the database.
There should be only ONE connection the database during the WHOLE time and that's
the sqlplus session where you do the change.
2.1. Make sure the parallel_server parameter in INIT.ORA is set to false or it is not set at all.
If you are using RAC see
Note 221646.1 Changing the Character Set for a RAC Database Fails with an ORA-12720 Error
2.2. Execute the following commands in sqlplus connected as "/ AS SYSDBA":
SPOOL Nswitch.log
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
ALTER SYSTEM ENABLE RESTRICTED SESSION;
ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0;
ALTER SYSTEM SET AQ_TM_PROCESSES=0;
ALTER DATABASE OPEN;
ALTER DATABASE CHARACTER SET WE8MSWIN1252;
SHUTDOWN IMMEDIATE;
STARTUP RESTRICT;
SHUTDOWN;
The extra restart/shutdown is necessary in Oracle8(i) because of a SGA
initialization bug which is fixed in Oracle9i.
-- a alter database takes typically only a few minutes or less,
-- it depends on the number of columns in the database, not the amount of data
2.3. Restore the parallel_server parameter in INIT.ORA, if necessary.
2.4. STARTUP;
now go to point 3) of this note of course your database is then WE8MSWIN1252, so
you need to replace <existing database character set> with WE8MSWIN1252 from now on.
For 10g and up:
When using CSSCAN 2.x (10g database) you should see in 1252check.txt this:
All character type data in the data dictionary remain the same in the new character set
All character type application data remain the same in the new character set
and
The data dictionary can be safely migrated using the CSALTER script
IF you see this then you need first to go to WE8MSWIN1252
If not, log a tar and provide all 3 generated files.
Shutdown the listener and any application that connects locally to the database.
There should be only ONE connection the database during the WHOLE time and that's
the sqlplus session where you do the change.
Then you do in sqlplus connected as "/ AS SYSDBA":
-- check if you are using spfile
sho parameter pfile
-- if this "spfile" then you are using spfile
-- in that case note the
sho parameter job_queue_processes
sho parameter aq_tm_processes
-- (this is Bug 6005344 fixed in 11g )
-- then do
shutdown immediate
startup restrict
SPOOL Nswitch.log
@@?\rdbms\admin\csalter.plb
-- Csalter will aks confirmation - do not copy paste the whole actions on one time
-- sample Csalter output:
-- 3 rows created.
-- This script will update the content of the Oracle Data Dictionary.
-- Please ensure you have a full backup before initiating this procedure.
-- Would you like to proceed (Y/N)?y
-- old 6: if (UPPER('&conf') <> 'Y') then
-- New 6: if (UPPER('y') <> 'Y') then
-- Checking data validility...
-- begin converting system objects
-- PL/SQL procedure successfully completed.
-- Alter the database character set...
-- CSALTER operation completed, please restart database
-- PL/SQL procedure successfully completed.
-- Procedure dropped.
-- if you are using spfile then you need to also
-- ALTER SYSTEM SET job_queue_processes=<original value> SCOPE=BOTH;
-- ALTER SYSTEM SET aq_tm_processes=<original value> SCOPE=BOTH;
shutdown
startup
and the 10g database will be WE8MSWIN1252
now go to point 3) of this note of course your database is then WE8MSWIN1252, so
you need to replace <existing database character set> with WE8MSWIN1252 from now on.
3) Check which rows contain data for which the code point will change
Run csscan with the following syntax:
csscan FULL=Y FROMCHAR=<your database character set> TOCHAR=AL32UTF8 LOG=WE8TOUTF8 CAPTURE=Y ARRAY=1000000 PROCESS=2
Always run CSSCAN with 'sys as sysdba'
This will create 3 files :
WE8TOUTF8.out a log of the output of csscan
WE8TOUTF8.txt a Database Scan Summary Report
WE8TOUTF8.err a contains the rowid's of the rows reported in WE8check.txt
+ You should have NO entries under Lossy, because they should have been filtered
out in step 2), if you have data under Lossy then please redo step 2).
+ If you have any entries under Truncation then go to step 4)
+ If you only have entries for Convertible (and Changeless) then solve those in
step 5).
+ If you have NO entry's under the Convertible, Truncation or Lossy,
and all data is reported as "Changeless" then proceed to step 6).
4) If you have Truncation entries.
Whichever way you migrate from WE8(...) to AL32UTF8, you will always have to
solve the entries under Truncation.
Standard ASCII characters require 1 byte of storage space under in WE8(...) and
in AL32UTF8, however, other characters (like accented characters and the Euro
sign) require only 1 byte of storage space in WE8(...), but they require 2 or
more bytes of space in AL32UTF8.
That means that the total amount of space needed to store a string can exceed
the defined column size.
For more information about this see:
Note 119119.1 AL32UTF8 / UTF8 (unicode) Database Character Set Implications
and
"Truncation" data is always also "Convertible" data, which means that whatever
else you do, these rows have to be exported before the character set is changed
and re-imported after the character set has changed. If you proceed with that
without dealing with the truncation issue then the import will fail on these
columns because the size of the data exceeds the maximum size of the column.
So these truncation issues will always require some work, there are a number of
ways to deal with them:
A) Update these rows in the source database so that they contain less data
B) Update the table definition in the source database so that it can contain
longer data. You can do this by either making the column larger, or by using
CHAR length semantics instead of BYTE length semantics (only possible in
Oracle9i).
C) Pre-create the table before the import so that it can contain 'longer' data.
Again you have a choice between simply making it larger, or switching from BYTE
to CHAR length semantics.
If you've chosen option A or B then please rerun csscan to make sure there is no
Truncation data left. If that also means there is no Convertible data left then
proceed to step 6), otherwise proceed to step 5).
To know how much the data expands simply check the csscan output.
you can find that in the .err file as "Max Post Conversion Data Size"
For example, check in the .txt file wich table has "Truncation",
let's assume you have there a row that say's
-- snip from WE8TOUTF8.txt
[Distribution of Convertible, Truncated and Lossy Data by Table]
USER.TABLE Convertible Truncation Lossy
SCOTT.TESTUTF8 69 6 0
-- snip from WE8TOUTF8.txt
then look in the .err file for "TESTUTF8" until the
"Max Post Conversion Data Size" is bigger then the column size for that table.
User : SCOTT
Table : TESTUTF8
Column: ITEM_NAME
Type : VARCHAR2(80)
Number of Exceptions : 6
Max Post Conversion Data Size: 81
-> the max size after going to UT8 will be 81 bytes for this column.
5) If you have Convertible entries.
This is where you have to make a choice whether or not you want to continue
on this path or if it's simpler to do a complete export/import in the
traditional way of changing character sets.
All the data that is marked as Convertible needs to be exported and then
re-imported after the character set has changed.
6) check if you have functional indexes on CHAR based columns and purge the RECYCLEBIN.
select OWNER, INDEX_NAME , INDEX_TYPE, TABLE_OWNER, TABLE_NAME, STATUS,
FUNCIDX_STATUS from ALL_INDEXES where INDEX_TYPE not in
('NORMAL', 'BITMAP','IOT - TOP') and TABLE_NAME in (select unique
(table_name) from dba_tab_columns where char_used ='C');
if this gives rows back then the change will fail with
ORA-30556: functional index is defined on the column to be modified
if you have functional indexes on CHAR based columns you need to drop the
index and recreate after the change , note that a disable will not be enough.
On 10g check ,while connected as sysdba, if there are objects in the recyclebin
SQL> show recyclebin
If so do also a PURGE DBA_RECYCLEBIN; other wise you will recieve a ORA-38301 during CSALTER.
7) Choose on how to do the actual change
you have 2 choices now:
Option 1 - exp/imp the entire database and stop using the rest of this note.
a. Export the current entire database (with NLS_LANG set to <your old
database character set>)
b. Create a new database in the AL32UTF8 character set
c. Import all data into the new database (with NLS_LANG set to <your old database character set>)
d. The conversion is complete, do not continue with this note.
note that you do need to deal with truncation issues described in step 4), even
if you use the export/import method.
Option 2 - export only the convertible data and continue using this note.
For 9i and lower:
a. If you have "convertible" data for the sys objects SYS.METASTYLESHEET,
SYS.RULE$ or SYS.JOB$ then follow the following note for those objects:
Note 258904.1 Convertible data in data dictionary: Workarounds when changing character set
make sure to combine the next steps in the example script given in that note.
b. Export all the tables that csscan shows have convertible data
(make sure that the character set part of the NLS_LANG is set to the current
database character set during the export session)
c. Truncate those tables
d. Run csscan again to verify you only have "changeless" application data left
e. If this now reports only Changeless data then proceed to step 8), otherwise
do the same again for the rows you've missed out.
For 10g and up:
a. Export all the USER tables that csscan shows have convertible data
(make sure that the character set part of the NLS_LANG is set to the current
database character set during the export session)
b. Fix any "convertible" in the SYS schema, note that the 10g way to change
the characterset (= the CSALTER script) will deal with any CLOB data in the
sys schema. All "no 9i only" fixes in
Note 258904.1 Convertible data in data dictionary: Workarounds when changing character set
should NOT be done in 10g
c. Truncate the exported user tables.
d. Run csscan again to verify you only have "changeless" application data left
e. If this now reports only Changeless data then proceed to step 8), otherwise
do the same again for the rows you've missed out.
When using CSSCAN 2.x (10g database) you should see in WE8TOUTF8.txt this:
The data dictionary can be safely migrated using the CSALTER script
If you do NOT have this when working on a 10g system CSALTER will NOT work and this
means you have missed something or not followed all steps in this note.
8) Perform the character set change:
Perform a backup of the database.
Check the backup.
Double-check the backup.
For 9i and below:
Then use the "alter database" command, this changes the current database
character set definition WITHOUT changing the actual stored data.
Shutdown the listener and any application that connects locally to the database.
There should be only ONE connection the database during the WHOLE time and that's
the sqlplus session where you do the change.
1. Make sure the parallel_server parameter in INIT.ORA is set to false or it is not set at all.
If you are using RAC see
Note 221646.1 Changing the Character Set for a RAC Database Fails with an ORA-12720 Error
2. Execute the following commands in sqlplus connected as "/ AS SYSDBA":
SPOOL Nswitch.log
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
ALTER SYSTEM ENABLE RESTRICTED SESSION;
ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0;
ALTER SYSTEM SET AQ_TM_PROCESSES=0;
ALTER DATABASE OPEN;
ALTER DATABASE CHARACTER SET INTERNAL_USE AL32UTF8;
SHUTDOWN IMMEDIATE;
-- a alter database takes typically only a few minutes or less,
-- it depends on the number of columns in the database, not the amount of data
3. Restore the parallel_server parameter in INIT.ORA, if necessary.
4. STARTUP;
Without the INTERNAL_USE you get a ORA-12712: new character set must be a superset of old character set
WARNING WARNING WARNING
Do NEVER use "INTERNAL_USE" unless you did follow the guidelines STEP BY STEP
here in this note and you have a good idea what you are doing.
Do NEVER use "INTERNAL_USE" to "fix" display problems, but follow Note 225938.1
If you use the INTERNAL_USE clause on a database where there is data listed
as convertible without exporting that data then the data will be corrupted by
changing the database character set !
For 10g and up:
Shutdown the listener and any application that connects locally to the database.
There should be only ONE connection the database during the WHOLE time and that's
the sqlplus session where you do the change.
Then you do in sqlplus connected as "/ AS SYSDBA":
-- check if you are using spfile
sho parameter pfile
-- if this "spfile" then you are using spfile
-- in that case note the
sho parameter job_queue_processes
sho parameter aq_tm_processes
-- (this is Bug 6005344 fixed in 11g )
-- then do
shutdown
startup restrict
SPOOL Nswitch.log
@@?\rdbms\admin\csalter.plb
-- Csalter will aks confirmation - do not copy paste the whole actions on one time
-- sample Csalter output:
-- 3 rows created.
-- This script will update the content of the Oracle Data Dictionary.
-- Please ensure you have a full backup before initiating this procedure.
-- Would you like to proceed (Y/N)?y
-- old 6: if (UPPER('&conf') <> 'Y') then
-- New 6: if (UPPER('y') <> 'Y') then
-- Checking data validility...
-- begin converting system objects
-- PL/SQL procedure successfully completed.
-- Alter the database character set...
-- CSALTER operation completed, please restart database
-- PL/SQL procedure successfully completed.
-- Procedure dropped.
-- if you are using spfile then you need to also
-- ALTER SYSTEM SET job_queue_processes=<original value> SCOPE=BOTH;
-- ALTER SYSTEM SET aq_tm_processes=<original value> SCOPE=BOTH;
shutdown
startup
and the 10g database will be AL32UTF8
9) Reload the data pump packages after a change to AL32UTF8 / UTF8 in Oracle10
If you use Oracle10 then the datapump packages need to be reloaded after
a conversion to UTF8/AL32UTF8. In order to do this run the following 3
scripts from $ORACLE_HOME/rdbms/admin in sqlplus connected as "/ AS SYSDBA":
For 10.2.X:
catnodp.sql
catdph.sql
catdpb.sql
For 10.1.X:
catnodp.sql
catdp.sql
10) Reimporting the exported data:
If you exported any data in step 5) then you now need to reimport that data.
Make sure that the character set part of the NLS_LANG is still set to the
original database character set during the import session (just as it was during
the export session).
11) Verify the clients NLS_LANG:
Make sure your clients are using the correct NLS_LANG setting:
Regards,
Chotu,
Bangalore

R12 Customer Conversion by using TCA API OR Standard interface table ?

R12 Customer Conversion should be done via TCA API OR Standard interface table? Why ?
Which approach is more suitable kindly let us know your thoughts.

We have used interface tables just to have better control and reprocessing abilities. You may need to be little careful about the TCA tables.

R12 Supplier Conversion by using API OR Standard interface table ?

R12 Supplier Conversion should be done via API OR Standard interface table? Why ?
Which approach is more suitable kindly let us know your thoughts.
Thanks in advance

We have used interface tables just to have better control and reprocessing abilities. You may need to be little careful about the TCA tables.

G Performing database characterset conversion adsvdcnv.cmd

hi,
i m installing 11.5.9 EBS on windows XP and getting stuck on some point on this point everytime, no messege nothing just it hangs there for hours
Step 3 of 5
100%
status
g Performing database characterset conversion adsvdcnv.cmd
everything was fine installed everything required,
all checks were passed but it always stucks here
if anybody can help me since i m stuck with this for last whole week.....
Edited by: FarhatKayani on Apr 22, 2009 7:47 AM

I had the same error and it turned out to be an issue with the domain name specification. I have a single node install on a computer not on a network. But it had been part of a domain earlier. I took it out of the domain and followed the instructions posted by Srinath Nanduri in his post 'Steps for **SUCCESSFUL** installation of 11.5.9 on Windows' - Steps for **SUCCESSFUL** installation of 11.5.9 on Windows

Database Characterset Conversion from AMERICAN to JAPANESE

Hello
We are creating a test environment from a database with NLS_LANG = AMERICAN_AMERICA.WE8ISO8859P1. This needs to be converted into Japanese characterset with NLS_LANG = JAPANESE_JAPAN.JA16EUC
As per my understanding, I need to first export the database, then create a new database with Japanese NLS_LANG, and then re-import it
Could someone please confirm the steps please
1. Do I need to change NLS_LANG before exporting the database?
2. Can I run a database characterset conversion check before exporting db?
3. Is there any other pre-cautions that I need to take
Oracle Version: Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
OS Version: HP-UX B.11.11
Regards
Sudhanshu

Hello,
I have used the Character Set Scan utility (csscan) Version 1.2. I have attached the report results below.
To convert the character set instead of export/import, can I simply do
ALTER DATABASE CHARACTER SET ja16euc;
I would appreciate feedback on this if anyone has worked on this conversion before.
Parameter Value
CSSCAN Version v1.2
Database Version 9.2.0.6.0
Scan type Full database
Scan CHAR data? YES
Database character set WE8ISO8859P1
FROMCHAR WE8ISO8859P1
TOCHAR JA16EUC
Scan NCHAR data? NO
Array fetch buffer size 10240
Number of processes 20
Capture convertible data? NO
[Scan Summary]
Some character type data in the data dictionary are not convertible to the new character set
Some character type application data are not convertible to the new character set
[Data Dictionary Conversion Summary]
Datatype Changeless Convertible Truncation Lossy
VARCHAR2 3,303,684 386 0 8
CHAR 5 0 0 0
LONG 219,988 1 0 0
CLOB 0 58 0 0
Total 3,523,677 445 0 8
Total in percentage 100% 0% 0% 0%
[Application Data Conversion Summary]
Datatype Changeless Convertible Truncation Lossy
VARCHAR2 3,316,273,097 8,517 56 2,675
CHAR 6,954 0 0 0
LONG 197,690 0 0 0
CLOB 0 0 0 0
Total 3,316,477,741 8,517 56 2,675
Total in percentage 100% 0% 0% 0%
Convertible Truncation Lossy
1 0 0
4 0 0
28 0 6
2,792 43 20
55 1 0
45 0 0
3 0 0
39 0 0
978 0 0
69 0 0
36 0 0
16 0 0
45 0 0
21 0 0
102 4 0
195 4 0
205 0 2
102 4 0
61 0 470
2 0 0
6 0 0
67 0 487
0 0 1
1 0 0
3 0 0
8 0 0
1 0 0
3,115 0 1,689
261 0 0
4 0 0
230 0 0
5 0 0
4 0 0
4 0 0
6 0 0
3 0 0
1 0 0
58 0 0
386 0 8
Convertible Truncation Lossy
1 0 0
4 0 0
28 0 6
2,792 43 20
55 1 0
45 0 0
3 0 0
20 0 0
11 0 0
2 0 0
4 0 0
2 0 0
978 0 0
69 0 0
16 0 0
10 0 0
4 0 0
4 0 0
2 0 0
10 0 0
4 0 0
2 0 0
45 0 0
21 0 0
4 0 0
4 0 0
0 4 0
59 0 0
27 0 0
8 0 0
4 0 0
93 0 0
4 0 0
0 4 0
59 0 0
27 0 0
8 0 0
102 0 1
58 0 1
35 0 0
10 0 0
4 0 0
4 0 0
0 4 0
59 0 0
27 0 0
8 0 0
61 0 470
2 0 0
6 0 0
67 0 487
0 0 1
1 0 0
3 0 0
8 0 0
1 0 0
3,115 0 1,689
261 0 0
4 0 0
73 0 0
115 0 0
37 0 0
5 0 0
2 0 0
3 0 0
4 0 0
4 0 0
6 0 0
2 0 0
1 0 0
1 0 0
58 0 0
386 0 8
---------------- ---------------- ----------------

Re: g Performing database characterset conversion adsvdcnv.cmd

Hi,
I am trying to install oracle applications 11i on Windows XP Professional on Toshiba laptop centrino 1.743 GHz) and for some reason the process is getting stuck at :
Step 3 of 5, 40 % done
And shows 100% of step 3 complete
Shows this error
g Performing database characterset conversion adsvdcnv.cmd
I have tried several times and everytime it is getting stuck at this stage only.
I am installing in language English only... and selected most of the options defaulted by the system.
Pls. find below my log file. Pls. advise how to fix this problem.
The system doesnot give any error message but get stuck at this point for hours. Couldn't figure out the problem... Please throw in some ideas... Thanks in advnance...
Environment variables:
ORACLE_HOME =
PATH = D:\11iStage\startCD\Disk1\rapidwiz\unzip\NT;C:\mks\bin;C:\mks\bin\X11;C:\mks\mksnt;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft Visual Studio\Common\Tools\WinNT;C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin;C:\Program Files\Microsoft Visual Studio\Common\Tools;c:\vc\vc98\bin;C:\vc\VC98\bin;C:\WINDOWS\SYSTEM32;C:\make-3.79.1\winrel\gnumake.exe; C:\Windows;C:\vc\VC98\bin ;C:\vc\Tools\WinNT;C:\vc\MSDev98\Bin;C:\vc\Tools;C:\VC98\bin;C:\Program Files\Microsoft Visual Studio\Common\Tools\WinNT;C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin;C:\Program Files\Microsoft Visual Studio\Common\Tools;c:\vc\vc98\bin;C:\vc\VC98\bin;C:\MKS\bin;C:\MKS\bin\X11;C:\MKS\mksnt;C:\WINDOWS\SYSTEM32;C:\make-3.79.1\winrel\gnumake.exe; C:\Windows;C:\vc\VC98\bin
CLASSPATH =
Username is: applmgr
Unable to read the list of homes from the inventory.
Unable to read c:\Program Files\Oracle\Inventory/Contents/OracleHomesList.ser. Some inventory information may be lost.
Unable to read c:\Program Files\Oracle\Inventory/Contents/CompsList0.ser. Some inventory information may be lost.
Unable to read c:\Program Files\Oracle\Inventory/Contents/PatchesList0.ser. Some inventory information may be lost.
Unable to read c:\Program Files\Oracle\Inventory/Contents/LibsList.ser. Some inventory information may be lost.
Unable to read c:/Program Files/Oracle/Inventory/ContentsXML/comps.xml. Some inventory information may be lost.
Current Inventory:
Independent Products:
Oracle Home: APPS9I_PROD
Oracle9i Database 9.2.0.1.0
Oracle 9iR2 Patch Set 9.2.0.3.0
JDBC Common Files 9.2.0.1.0
Oracle JDBC Thin Driver for JDK 1.1 9.2.0.1.0
JDBC/OCI Common Files 9.2.0.1.0
Sun JDK extensions 9.2.0.1.0
RDBMS Required Support Files 9.2.0.1.0
Oracle Trace Required Support Files 9.2.0.1.0
Oracle JDBC Thin Driver for JDK 1.2 9.2.0.1.0
Oracle Client Required Support Files 9.2.0.1.0
Agent Required Support Files 9.2.0.1.0
SSL Required Support Files 9.2.0.1.0
Oracle JDBC Thin Driver for JDK 1.4 9.2.0.1.0
Oracle JDBC/OCI Driver for JDK 1.1 9.2.0.1.0
Bali Share 1.1.17.0.0
Parser Generator Required Support Files 9.2.0.1.0
Oracle Extended Windowing Toolkit 3.4.13.0.0
Installation Common Files 9.2.0.1.0
Oracle Ice Browser 5.06.8.0.0
Enterprise Manager Minimal Integration 9.2.0.1.0
LDAP Required Support Files 9.2.0.1.0
PL/SQL Required Support Files 9.2.0.1.0
Platform Required Support Files 9.2.0.1.0
Oracle Code Editor 1.2.1.0.0A
Oracle Core Required Support Files 9.2.0.1.0
Oracle JFC Extended Windowing Toolkit 4.1.10.0.0
XML Parser for Java 9.2.0.1.0
Oracle Help For Java 4.1.13.0.0
Oracle Help For Java 3.2.13.0.0
Documentaion Required Support Files 9.2.0.1.0
Precompiler Required Support Files 9.2.0.1.0
Oracle Net Required Support Files 9.2.0.1.0
Precompiler Common Files 9.2.0.1.0
Oracle9i Globalization Support 9.2.0.1.0
DBJAVA Required Support Files 9.2.0.1.0
XDK Required Support Files 9.2.0.1.0
Enterprise Manager Shared Libraries 9.2.0.1.0
Enterprise Manager Win32 App Translated Files 9.2.0.1.0
Enterprise Manager Expert Common Files 9.2.0.1.0
Enterprise Manager Win32 Application Common Files 9.2.0.1.0
Enterprise Manager Translated Files 9.2.0.1.0
SQLServer Monitoring Option 9.2.0.1.0
Enterprise Manager Win32 Apps Bridge 9.2.0.1.0
Index Tuning Wizard 9.2.0.1.0
Expert 9.2.0.1.0
Trace DataViewer 9.2.0.1.0
SQL Analyze 9.2.0.1.0
Performance Manager 9.2.0.1.0
Capacity Planner 9.2.0.1.0
Enterprise Manager Events 9.2.0.1.0
Enterprise Manager Base Classes 9.2.0.1.0
Required Support Files 9.2.0.1.0
Enterprise Manager Installation Prerequisite Checks 9.2.0.1.0
Utilities Common Files 9.2.0.1.0
Enterprise Manager Quick Tours 9.2.0.1.0
Oracle Display Fonts 9.0.2.0.0
regexp 2.0.20.0.0
Oracle OLAP Worksheet 9.2.0.1.0
Oracle OLAP API 9.2.0.1.0
Oracle Developer Server Forms Manager 9.2.0.1.0
Oracle Intelligent Agent Base Component Files 9.2.0.1.0
Oracle Internet Directory Client Common Files 9.2.0.1.0
Sun JDK 1.3.1.0.1a
Oracle Directory Manager 9.2.0.1.0
Visigenics ORB 3.4.0.0.0
Assistant Common Files 9.2.0.1.0
Enterprise Manager Paging and OMS Common Files 9.2.0.1.0
XML Parser for C 9.2.0.1.0
Oracle Net Configuration Assistant 9.2.0.1.0
Character Set Migration Utility 9.2.0.1.0
Enterprise Manage Website Translated Files 9.2.0.1.0
Oracle Net Manager 9.2.0.1.0
Oracle Net 9.2.0.1.0
Oracle Perl Interpreter 5.00503.0.0.0c
Apache Web Server files 1.3.22.0.0a
Database Configuration Assistant 9.2.0.1.0
Oracle JDBC/OCI Driver for JDK 1.2 9.2.0.1.0
Oracle INTYPE File Assistant 9.2.0.1.0
SQLJ Runtime 9.2.0.1.0
Advanced Queueing (AQ) API 9.2.0.1.0
Oracle Caching Service for Java 2.1.0.0.0a
Recovery Manager 9.2.0.1.0
JSDK 2.0.0.0.0d
Apache JServ 1.1.0.0.0g
Oracle interMedia Java Client 9.2.0.1.0
Oracle Java Layout Engine 2.0.1.0.0
Oracle XML SQL Utility 9.2.0.1.0
SQLJ Translator 9.2.0.1.0
Enterprise Login Assistant 9.2.0.1.0
Enterprise Manager Paging Server 9.2.0.1.0
Oracle Java Tools 9.2.0.1.0
Oracle ODBC Driver 9.2.0.1.0
Authentication and Encryption 9.2.0.1.0
Oracle Wallet Manager 9.2.0.1.0
Pro*COBOL 1.8.77.0.0
Oracle Database User Interface 2.2.11.0.0
Pro*COBOL 9.2.0.1.0
Oracle SNMP Agent 9.2.0.1.0
Oracle C++ Call Interface 9.2.0.1.0
Oracle OLAP Cube Viewer 9.2.0.1.0
Oracle OLAP CWM Lite 9.2.0.1.0
Object Type Translator 9.2.0.1.0
SQL*Plus 9.2.0.1.0
Oracle Call Interface (OCI) 9.2.0.1.0
SQL*Loader 9.2.0.1.0
Secure Socket Layer 9.2.0.1.0
Oracle Internet Directory Client 9.2.0.1.0
Oracle Net Listener 9.2.0.1.0
Advanced Replication 9.2.0.1.0
Oracle Complete DSS Starter Database 9.2.0.1.0
Oracle Complete OLTP Starter Database 9.2.0.1.0
Oracle Starter Database 9.2.0.1.0
Oracle Message Gateway Common Files 9.2.0.1.0
Oracle Common Schema Demos 9.2.0.1.0
Change Management Common Files 9.2.0.1.0
Oracle UIX 2.0.20.0.0
Oracle Help for the Web 1.0.7.0.0
XML Class Generator for C++ 9.2.0.1.0
XML Parser for C++ 9.2.0.1.0
XML Parser for Oracle JVM 9.2.0.1.0
XML Transx 9.2.0.1.0
XML Transviewer Beans 9.2.0.1.0
XML Class Generator for Java 9.2.0.1.0
XSQL Servlet 9.2.0.1.0
XML Parser for PL/SQL 9.2.0.1.0
Oracle SQLJ 9.2.0.1.0
Enterprise Manager Common Files 9.2.0.1.0
Common Files For Generic Connectivity Using OLEDB 9.2.0.1.0
Oracle SOAP Client 2.0.0.0.0a
Oracle Workflow Manager 9.2.0.1.0
Oracle Net Integration 9.2.0.1.0
Oracle XML Runtime Components 9.2.0.1.0
Enterprise Manager Database Applications 9.2.0.1.0
Oracle SOAP Server 2.0.0.0.0a
Oracle Database Demos 9.2.0.1.0
Oracle Ultra Search Common Files 9.2.0.1.0
Enterprise Manager Console 9.2.0.1.0
Enterprise Manager Integrated Applications 9.2.0.1.0
Enterprise Manager Client 9.2.0.1.0
Database Workspace Manager 9.2.0.1.0
Oracle interMedia Java Advanced Imaging 9.2.0.1.0
Oracle interMedia Client Compatibility Files 9.2.0.1.0
Oracle interMedia Java Media Framework Client 9.2.0.1.0
Oracle interMedia Client Demos 9.2.0.1.0
Oracle interMedia Web Client 9.2.0.1.0
BC4J Runtime for Database 9.0.2.692.1
Oracle Change Management Pack 9.2.0.1.0
Oracle interMedia Annotator 9.2.0.1.0
Data Management Services Common Files 9.2.0.1.0
Oracle interMedia Common Files 9.2.0.1.0
Oracle interMedia Image 9.2.0.1.0
Oracle interMedia Audio 9.2.0.1.0
Oracle interMedia Video 9.2.0.1.0
Database Upgrade Assistant 9.2.0.1.0
Oracle Intelligent Agent Config Tool 9.2.0.1.0
Oracle Intelligent Agent 9.2.0.1.0
PL/SQL Embedded Gateway 9.2.0.1.0
Oracle HTTP Server Extensions 9.2.0.1.0
Oracle eBusiness Management Extensions 9.2.0.1.0
Oracle EMD Agent Extensions 9.2.0.1.0
Oracle interMedia Client Option 9.2.0.1.0
Oracle SOAP for JServ 2.0.0.0.0a
MIcrosoft SQLServer(TM) Extensions 9.2.0.1.0
Oracle Management Pack for Oracle Applications 9.2.0.1.0
Export/Import 9.2.0.1.0
Microsoft SQL Server 7.0 Plugin 9.2.0.1.0
Microsoft SQL Server 6.5 Plugin 9.2.0.1.0
Microsoft SQL Server 2000 Plugin 9.2.0.1.0
Microsoft Access Plugin 9.2.0.1.0
Informix7 Plugin 9.2.0.1.0
DB2400V4R5 Plugin 9.2.0.1.0
MySQL Plugin 9.2.0.1.0
Sybase Adaptive Server 12 Plugin 9.2.0.1.0
Sybase Adaptive Server 11 Plugin 9.2.0.1.0
Apache Configuration for Oracle XML Developer's Kit 9.2.0.1.0
Oracle Tuning Pack 9.2.0.1.0
Oracle Forms Extensions 9.2.0.1.0
Oracle XML Developer's Kit 9.2.0.1.0
Oracle Java Server Pages 1.1.3.1.0
Oracle Diagnostics Pack 9.2.0.1.0
Oracle Ultra Search Middle-Tier 9.2.0.1.0
Oracle Dynamic Services Server 9.2.0.1.0
Oracle Mod PL/SQL Gateway 3.0.9.8.3b
Apache Configuration for Oracle Java Server Pages 1.1.2.3.0
Pro*C/C++ 9.2.0.1.0
Oracle Text 9.2.0.1.0
Generic Connectivity Common Files 9.2.0.1.0
New Database ID 9.2.0.1.0
Database SQL Scripts 9.2.0.1.0
Generic Connectivity Using OLEDB - SQL 9.2.0.1.0
Oracle HTTP Server 9.2.0.1.0
XML 9.2.0.1.0
Generic Connectivity Using OLEDB - FS 9.2.0.1.0
Generic Connectivity Using ODBC 9.2.0.1.0
Enterprise Manager Webserver Integration 9.2.0.1.0
Reporting Framework 9.2.0.1.0
Oracle interMedia Locator 9.2.0.1.0
Oracle Transparent Gateways 9.2.0.1.0
Oracle Management Server 9.2.0.1.0
Oracle Ultra Search Server 9.2.0.1.0
Oracle interMedia 9.2.0.1.0
Oracle Trace 9.2.0.1.0
Oracle9i Syndication Server 9.2.0.1.0
Enterprise Manager Web Site 9.2.0.1.0
Oracle Applications Extensions 9.2.0.1.0
Oracle Intelligent Agent Extensions 9.2.0.1.0
Oracle Programmer 9.2.0.1.0
Migration Utility 9.2.0.1.0
Oracle Enterprise Manager Products 9.2.0.1.0
Oracle9i Development Kit 9.2.0.1.0
Oracle Advanced Security 9.2.0.1.0
Oracle JVM 9.2.0.1.0
Oracle Migration Workbench 9.2.0.1.0
Database Verify Utility 9.2.0.1.0
PL/SQL 9.2.0.1.0
Oracle Database Utilities 9.2.0.1.0
Oracle9i 9.2.0.1.0
Oracle Net Services 9.2.0.1.0
Oracle Data Mining 9.2.0.1.0
Oracle OLAP 9.2.0.1.0
Oracle Spatial 9.2.0.1.0
Oracle Partitioning 9.2.0.1.0
Enterprise Edition Options 9.2.0.1.0
MIcrosoft SQLServer(TM) Extensions Patch 9.2.0.3.0
Data Management Services Common Files Patch 9.2.0.3.0
Oracle eBusiness Management Extensions Patch 9.2.0.3.0
Oracle EMD Agent Extensions Patch 9.2.0.3.0
Oracle Applications Extensions Patch 9.2.0.3.0
Oracle Intelligent Agent Base Component Files Patch 9.2.0.3.0
Generic Connectivity Using OLEDB - SQL Patch 9.2.0.3.0
Generic Connectivity Using OLEDB - FS Patch 9.2.0.3.0
XSQL Servlet 9.2.0.3.0
Oracle Net Configuration Assistant Patch 9.2.0.3.0
Oracle SQLJ Patch 9.2.0.3.0
Oracle JDBC Thin Driver for JDK 1.1 Patch 9.2.0.3.0
Oracle Java Core Patch 9.2.0.3.0
Oracle Internet Directory Client Common Files Patch 9.2.0.3.0
Assistant Common Files Patch 9.2.0.3.0
XML Parser for PL/SQL Patch 9.2.0.3.0
XML Parser for C Patch 9.2.0.3.0
XML Parser for C++ Patch 9.2.0.3.0
Oracle interMedia Client Demos Patch 9.2.0.3.0
Oracle XML Developer's Kit Patch 9.2.0.3.0
Oracle Call Interface (OCI) Patch 9.2.0.3.0
Oracle Ultra Search Server Patch 9.2.0.3.0
Oracle JDBC Thin Driver for JDK 1.4 Patch 9.2.0.3.0
Oracle Java Tools Patch 9.2.0.3.0
DBJAVA Required Support Files Patch 9.2.0.3.0
Oracle Ultra Search Middle-Tier Patch 9.2.0.3.0
Oracle Ultra Search Common Files Patch 9.2.0.3.0
Oracle Spatial Patch 9.2.0.3.0
Oracle JDBC Thin Driver for JDK 1.2 Patch 9.2.0.3.0
XML 9.2.0.3.0
SQLJ Runtime Patch 9.2.0.3.0
Oracle XML SQL Utility Patch 9.2.0.3.0
Oracle JVM Patch 9.2.0.3.0
Oracle Database Demos Patch 9.2.0.3.0
Secure Socket Layer Patch 9.2.0.3.0
PL/SQL Required Support Files Patch 9.2.0.3.0
Oracle Net Manager Patch 9.2.0.3.0
Oracle Partitioning Patch 9.2.0.3.0
Oracle OLAP API Patch 9.2.0.3.0
Oracle Net Patch 9.2.0.3.0
Utilities Common Files Patch 9.2.0.3.0
Database Verify Utility Patch 9.2.0.3.0
Oracle Net Listener Patch 9.2.0.3.0
Oracle Common Schema Demos Patch 9.2.0.3.0
Oracle Internet Directory Client Patch 9.2.0.3.0
XML Parser for Oracle JVM Patch 9.2.0.3.0
XML Parser for Java Patch 9.2.0.3.0
Oracle Database Utilities Patch 9.2.0.3.0
XDK Required Support Files Patch 9.2.0.3.0
SSL Required Support Files Patch 9.2.0.3.0
RDBMS Required Support Files Patch 9.2.0.3.0
Precompiler Required Support Files Patch 9.2.0.3.0
Oracle Trace Required Support Files Patch 9.2.0.3.0
Oracle Core Required Support Files Patch 9.2.0.3.0
Oracle9i Globalization Support Patch 9.2.0.3.0
Oracle Net Required Support Files Patch 9.2.0.3.0
LDAP Required Support Files Patch 9.2.0.3.0
Oracle Client Required Support Files Patch 9.2.0.3.0
Agent Required Support Files Patch 9.2.0.3.0
SQL*Plus Patch 9.2.0.3.0
SQL*Loader Patch 9.2.0.3.0
Recovery Manager Patch 9.2.0.3.0
PL/SQL Patch 9.2.0.3.0
Oracle Trace Patch 9.2.0.3.0
Oracle C++ Call Interface Patch 9.2.0.3.0
New Database ID Patch 9.2.0.3.0
Migration Utility Patch 9.2.0.3.0
Generic Connectivity Using ODBC Patch 9.2.0.3.0
Generic Connectivity Common Files Patch 9.2.0.3.0
Export/Import Patch 9.2.0.3.0
Database SQL Scripts Patch 9.2.0.3.0
Advanced Queueing (AQ) API Patch 9.2.0.3.0
Oracle9i Patch 9.2.0.3.0
Pro*COBOL Patch 1.8.77.3.0
Pro*COBOL Patch 9.2.0.3.0
Pro*C/C++ Patch 9.2.0.3.0
Precompiler Common Files Patch 9.2.0.3.0
Object Type Translator Patch 9.2.0.3.0
Oracle OLAP CWM Lite Patch 9.2.0.3.0
Oracle OLAP Patch 9.2.0.3.0
Oracle interMedia Java Advanced Imaging Patch 9.2.0.3.0
Oracle interMedia Common Files Patch 9.2.0.3.0
Oracle interMedia Client Compatibility Files Patch 9.2.0.3.0
Oracle Wallet Manager Patch 9.2.0.3.0
Authentication and Encryption Patch 9.2.0.3.0
JDBC/OCI Common Files Patch 9.2.0.3.0
Oracle interMedia Locator Patch 9.2.0.3.0
Oracle Text Patch 9.2.0.3.0

Hi there.
I had encountered the same hanging problem at "Performing database characterset conversion adsvdcnv.cmd" (On Microsoft Windows Server 2003 - - XEON PROCESSOR - a staging area installation - rapidwiz ver 11.5.9.22 - . ).
What i did is that i installed the JDK version : 1.4.2.04 instead of 1.3.1 and reinstalled the product. So the installation completed successfully..

Characterset conversion from WE8ISO8859P1 to UTF8

Hi All,
While running CSSCAN utility from WE8ISO8859P1 to UTF8 after running 8-9H, the process is going to sleep state.
We need to complete this task in next 1week of time.Can any one share why this is happening.
Thanks,
Sekhar

There is a Metalink note on [Bug 6460895 - CSSCAN may hang / run slowly|https://metalink.oracle.com/CSP/ui/flash.html#tab=Home(page=Home&id=fm2z4pjj()),(page=KBNavigator&id=fm2z4vd6(&viewingMode=1141&userQuery=csscan%20sleep&searchControl=1146))] that looks to be vaguely related. This indicates that the bug was fixed in 10.2.0.4, but unfortunately the bug itself isn't published, so it is rather hard to know if this is your problem or not. It would probably be worth logging a support request to see if Oracle support can determine whether or not you're being affected by this bug.
Meanwhile, can you apply the 10.2.0.4 patchset and see if that solves the problem?
Justin

Conversion of UTF8 to WE8DEC

First, I'm a newer for DB related topics.
I have two oracle DBMS.
Sys1 : Oracle 8.X UTF-8 for Web Application
Sys2 : Oracle 8.X WE8DEC for SAP R/3
For some reason,
With Sys2, I have to view the table contents of Sys1.
DBA set up DB-link between two systems.
With DB-LINK, Any Alphabetic characters can be seen,
but some characters(2byte Korean,Japanese character) doesn't look properly.
I can find out for some PL/SQL conversion function
which convert from one character set to another character set.
But not for my case. from UTF8 to WE8DEC.
Can anybody give me some help..

Hi,
Use function module 'idoc_xml_transform' .
U can use transaction 'WE60' to convert it.
convert IDOC data to XML format.
best Regards,
Brijesh

Characterset conversion from WE8MSWIN1252 to AL32UTF8

DB Version:11g
Is it possible to convert a DB of WE8MSWIN1252 characterset to AL32UTF8?

Yes it can be done..
Please refer below metalink notes:
Changing the Database Character Set ( NLS_CHARACTERSET ) [ID 225912.1]
AL32UTF8 / UTF8 (Unicode) Database Character Set Implications [ID 788156.1]
Changing the NLS_CHARACTERSET to AL32UTF8 / UTF8 (Unicode) [ID 260192.1]
Regards
Rajesh

Character Set Conversion AL24UTFFSS - UTF8

Gents,
we are currently migrating our customers from 8.0.5 to 8.1.6 including charset conversion from AL24UTFFSS to UTF8 using export/import.
There4s been one case where imp.exe just hung (no messages) at a certain table. It was found, that it hold a string value that ended with the character i. The whole entry was deleted from the export file and imp.exe went through.
Tests showed that i in the middle of a string is not a problem, only if it4s at the end.
Can someone explain why that happens or, even better, has an idea how to prevent this from the beginning?
Thanks
Stefan

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Stefan Marx ([email protected]):
Gents,
we are currently migrating our customers from 8.0.5 to 8.1.6 including charset conversion from AL24UTFFSS to UTF8 using export/import.
There4s been one case where imp.exe just hung (no messages) at a certain table. It was found, that it hold a string value that ended with the character i. The whole entry was deleted from the export file and imp.exe went through.
Tests showed that i in the middle of a string is not a problem, only if it4s at the end.
Can someone explain why that happens or, even better, has an idea how to prevent this from the beginning?
Thanks
Stefan<HR></BLOCKQUOTE>
Sorry, this is probably the wrong Discussion Group. I moved this to 'Oracle 8i Globalization and NLS'.
null

How to convert characterset VN8VN3 into UTF8??

Hi all,
My database is using character set VN8VN3, I want to convert into UTF8. I use tool: csscan. Then:
SVRMGR> connect sys as sysdba;
SVRMGR> shutdown immediate
SVRMGR> startup mount
SVRMGR> alter system enable restricted session;
SVRMGR> alter system set job_queue_processes = 0;
SVRMGR> alter database open;
SVRMGR> alter database character set utf8;
but command at the end line, I see error: " new character set is not superset old character set"
So, what should I do now ??

thx
paste values from the edit menu works !

Language Text Conversion to UTF8 -

Hi ,
I am trying to convert the Loaded Frech Text into UTF8,
My Database NLS_CHARACTERSET is UTF8.
The desired output of the text is "Réforme institutionnelle"
However I had loaded the data into my table. I find this is the value before applying the Convert on that Value - "Riforme institutionnelle".
I tried converting the same using the Character set
update tan_test set value = convert(value,'UTF8','WE8ISO8859P1');
update tan_test set value = convert(value,'UTF8','WE8ISO8859P9');
update tan_test set value = convert(value,'UTF8','WE8ISO8859P15');
None of the above helps me in converting the same to the desired Output
"Réforme institutionnelle"
Can anyone help me in giving the right Character set to convert it to French appropriately.
Thanks,
Narayanan.

With Refered the ID 124721.1, we need to take necessary steps until the scanner reports no exceptions. i.e. truncate tables.Even SYS, APPLSYS schema tables need to truncate.
Now the question is There are few Tables which are not exported as follows:
APPLSYS.DR$FND_LOBS_CTX$I
CTXSYS.DR$SQE
MDSYS.OPENLS_NODES
MDSYS.SDO_COORD_OP_PARAM_VALS
MDSYS.SDO_GEOR_XMLSCHEMA_TABLE
MDSYS.SDO_STYLES_TABLE
MDSYS.SDO_XML_SCHEMAS
ORDSYS.ORDDCM_CT_PRED_OPRD
ORDSYS.ORDDCM_DOCS
ORDSYS.ORDDCM_MAPPING_DOCS
Error is :EXP-00010: ORDSYS/MDSYS/ORDSYS is not a valid username
EXP-00011: APPLSYS.DR$FND_LOBS_CTX$I does not exist
Do we still go ahead truncation of these tables. But then How to get the data back in target.
Do We need to set NLS_LANG=American_America.US7ASCII while export and also same while import?
Please advice.

Characterset conversion from P15 to WE8MSWIN1252

I have a database with the P15 characterset.
How can I make a charactersetconversion to WE8MSWIN1252-characterset.
WhatÂ´s the most eassyiest way to do this?
Could someone please help me?

Start here:
http://www.oracle.com/technology/tech/globalization/pdf/TWP_Character_Set_Migration_Best_Practices_10gR2.pdf
Also, consider migrating to WE8MSWIN1252 in place of WE8ISO8859P1. If you have Windows clients, then WE8MSWIN1252 should be used anyway. Even if you do not have Windows clients, WE8MSWIN1252 is a binary superset of WE8ISO8859P1 and can hold all WE8ISO8859P1 codes + ca. 15 characters more. It is better to use it in case Windows clients are used in future.
-- Sergiusz

R12 Characterset conversion to UTF8 on 11 G R2 Database

Similar Messages

Maybe you are looking for