Possible charset conversion

Hi
My character set is :WE8ISO8859P1
Even I set NLS_LANG prior to export and import, (export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1 )
I still get below warning during import. Whats the reason for this? (I didnt get any warning during export)
import done in WE8ISO8859P1 character set and AL16UTF16 NCHAR character set
export client uses WE8MSWIN1252 character set (possible charset conversion)

ok thanks.
Regarding the standard export and import,
Suppose I take the export of a full schema: exp ../... owner=app file=....dmp
During import, user is not created automatically.
I have to create the user prior to import.
Is this same in datapump?

Similar Messages

Server uses WE8ISO8859P15 character set (possible charset conversion)

Hi,
when EXP in 9i I receive :
Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Export done in WE8PC850 character set and AL16UTF16 NCHAR character set
server uses WE8ISO8859P15 character set (possible charset conversion)What is the problem ?
Thank you.
I exported just a table, how to see if it is exported ?

Dear user522961,
You have not defined or misdefined the NLS_LANG environmental variable before trying to run the export command.
Here is a little illustration;
*$ echo $NLS_LANG*
*AMERICAN_AMERICA.WE8ISO8859P9*
$ exp system/password@opttest file=ogan.dmp owner=OGAN
Export: Release 10.2.0.4.0 - Production on Mon Jul 12 18:10:47 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
*Export done in WE8ISO8859P9 character set and AL16UTF16 NCHAR character set*
About to export specified users ...
. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user OGAN
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions for user OGAN
About to export OGAN's objects ...
. exporting database links
. exporting sequence numbers
. exporting cluster definitions
. about to export OGAN's tables via Conventional Path ...
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting referential integrity constraints
. exporting triggers
. exporting indextypes
. exporting bitmap, functional and extensible indexes
. exporting posttables actions
. exporting materialized views
. exporting snapshot logs
. exporting job queues
. exporting refresh groups and children
. exporting dimensions
. exporting post-schema procedural objects and actions
. exporting statistics
Export terminated successfully without warnings.
*$ export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P15*
$ exp system/password@opttest file=ogan.dmp owner=OGAN
Export: Release 10.2.0.4.0 - Production on Mon Jul 12 18:12:41 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
*Export done in WE8ISO8859P15 character set and AL16UTF16 NCHAR character set*
*server uses WE8ISO8859P9 character set (possible charset conversion)*
About to export specified users ...
. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user OGAN
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions for user OGAN
About to export OGAN's objects ...
. exporting database links
. exporting sequence numbers
. exporting cluster definitions
. about to export OGAN's tables via Conventional Path ...
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting referential integrity constraints
. exporting triggers
. exporting indextypes
. exporting bitmap, functional and extensible indexes
. exporting posttables actions
. exporting materialized views
. exporting snapshot logs
. exporting job queues
. exporting refresh groups and children
. exporting dimensions
. exporting post-schema procedural objects and actions
. exporting statistics
Export terminated successfully without warnings.Hope it Helps,
Ogan

Charset conversion of incoming XML documents

XML documents may contain data in other charsets than SAP's UTF-8. I'm using the ixml lib in ABAP. Using 'get_encoding', I can determine the incoming document's charset, but it seems only after having parsed it. I'd like to convert the entire document to the current SAP charset before processing. I didn't find a way in the ixml methods to do this, so I imagine I'll have to use CL_ABAP_CONV_IN_CE somehow.
What's the best way to handle non-SAP charsets in incoming XML documents?

ha that was just a joke. check the link below
http://livedocs.adobe.com/livecycle/es/sdkHelp/programmer/sdkHelp/wwhelp/wwhimpl/common/html/wwhelp.htm?context=sdkHelp&file=convertPDFToImage.64.3.html
Google - java api for converting pdf documents to images
Google - java api for converting xml documents to images etc

Charset conversation problem.

Hi!
I wanted to transform a ISO-8559-15 byte-Array into a valid Java String using
byte[] data = ...;
Charset iso_8559_15 = Charset.forName("ISO-8559-15");
String s = iso_8559_15.decode(ByteBuffer.wrap(data)).toString();s inclodes stranges byte-set which are neighter of UTF-8 nor ISO-8559-15 origin when writing them to a file using FileWriter.
It works perfectly well using
byte[] data = ...;
String s = new BufferedReader(new InputStreamReader(new ByteArrayInputStream(data))).readLine();Can you tell me whats wrong with using Charset/CharsetDecoder?

Probably you mean ISO-8859-15.
Check System.getProperty("file.encoding") - this is the default encoding.
I suppose it is different than ISO-8859-15 (if your second approach gives different results).
The simple way to convert byte array to string with desired charset is:
String str = new String(data, "ISO-8859-15");If you still do not achieve readable strings, check your input data.
Probably you have not-printable chars - for ISO-8859-15 in range 120-160 or most of these bellow 32.
(simple description and chars table can be found here: http://en.wikipedia.org/wiki/ISO_8859-15).

Charset conversion problem: JDriver/Ora 8.1.7/WLS 6.1

Hi. I'm having a problem with getting non-ASCII characters into an Oracle database
using the JDriver. I'm using CallableStatement.setString() to place a String with
Unicode \233 characters (accented e) in the database. The \233 shows up as a '?'
character (octal 77).
If I do the same thing from a simple Java app using the Oracle thin driver, the
character arrives properly.
I'd be grateful for any help.
Joe Humphreys

Hi Joe!
You have to set NLS_LANG parameter explicitely in your environement before starting
the server. That will resolve your problem.
Mitesh
Joe Humphreys wrote:
Hi. I'm having a problem with getting non-ASCII characters into an Oracle database
using the JDriver. I'm using CallableStatement.setString() to place a String with
Unicode \233 characters (accented e) in the database. The \233 shows up as a '?'
character (octal 77).
If I do the same thing from a simple Java app using the Oracle thin driver, the
character arrives properly.
I'd be grateful for any help.
Joe Humphreys

Is it possible to import and export dump between oracle 9 and oracle 11?

Is it possible to import and export dump between oracle 9 and oracle 11?
Source DB : Oracle 11g(unix0
Oracle client : Oracle 9(Windows)
Export import utility : Oracle 9's
Destination DB : oracle 9

I am getting the Following Error and export utility is not responding after this.
Export: Release 9.2.0.1.0 - Production on Thu Jul 15 14:37:01 2010
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
server uses AL32UTF8 character set (possible charset conversion)

NLS_LANG conversion

Hi All
Ihave problem with importin data
import done in AR8ISO8859P6 character set and AR8ISO8859P6 NCHAR character set
export client uses WE8ISO8859P1 character set (possible charset conversion)
export server uses WE8ISO8859P1 NCHAR character set (possible ncharset conversion)
my data writing in arabic , now I see it qutaion mark(??????????)

It look like while exporting you had western character set not arabic character set.
Set the nls_lang as per your requirement and take an export again. Then, do the import with the same nls_lang settings.
sjh
ocp dba

Conversions between character sets when using exp and imp utilities

I use EE8ISO8859P2 character set on my server,
when exporting database with NLS_LANG not set
then conversion should be done between
EE8ISO8859P2 and US7ASCII charsets, so some
characters not present in US7ASCII should not be
successfully converted.
But when I import such a dump, all characters not
present in US7ASCII charset are imported to the database.
I thought that some characters should be lost when
doing such a conversions, can someone tell me why is it not so?

Not exactly. If the import is done with the same DB character set, then no matter how it has been exported. Conversion (corruption) may happen if the destination DB has a different character set. See this example :
[ora102 work db102]$ echo $NLS_LANG
AMERICAN_AMERICA.WE8ISO8859P15
[ora102 work db102]$ sqlplus test/test
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Jul 25 14:47:01 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
TEST@db102 SQL> create table test(col1 varchar2(1));
Table created.
TEST@db102 SQL> insert into test values(chr(166));
1 row created.
TEST@db102 SQL> select * from test;
C
¦
TEST@db102 SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
[ora102 work db102]$ export NLS_LANG=AMERICAN_AMERICA.EE8ISO8859P2
[ora102 work db102]$ sqlplus test/test
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Jul 25 14:47:55 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
TEST@db102 SQL> select col1, dump(col1) from test;
C
DUMP(COL1)
©
Typ=1 Len=1: 166
TEST@db102 SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
[ora102 work db102]$ echo $NLS_LANG
AMERICAN_AMERICA.EE8ISO8859P2
[ora102 work db102]$ exp test/test file=test.dmp tables=test
Export: Release 10.2.0.1.0 - Production on Tue Jul 25 14:48:47 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Export done in EE8ISO8859P2 character set and AL16UTF16 NCHAR character set
server uses WE8ISO8859P15 character set (possible charset conversion)
About to export specified tables via Conventional Path ...
. . exporting table TEST 1 rows exported
Export terminated successfully without warnings.
[ora102 work db102]$ sqlplus test/test
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Jul 25 14:48:56 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
TEST@db102 SQL> drop table test purge;
Table dropped.
TEST@db102 SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
[ora102 work db102]$ imp test/test file=test.dmp
Import: Release 10.2.0.1.0 - Production on Tue Jul 25 14:49:15 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Export file created by EXPORT:V10.02.01 via conventional path
import done in EE8ISO8859P2 character set and AL16UTF16 NCHAR character set
import server uses WE8ISO8859P15 character set (possible charset conversion)
. importing TEST's objects into TEST
. importing TEST's objects into TEST
. . importing table "TEST" 1 rows imported
Import terminated successfully without warnings.
[ora102 work db102]$ export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P15
[ora102 work db102]$ sqlplus test/test
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Jul 25 14:49:34 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
TEST@db102 SQL> select col1, dump(col1) from test;
C
DUMP(COL1)
¦
Typ=1 Len=1: 166
TEST@db102 SQL>

ORA-03120: two-task conversion routine: integer overflow

Hello DB Gurus!!
Need your comments and help once again...
I am trying to import a DUMP file into My Local Database ie. Oracle Database 10g Enterprise Edition Release 10.2.0.4.0
The file exported was by different user on different Dabase of Oracle 10g i.e. Oracle Database 10g Enterprise Edition Release 10.2.0.3.0
but while I am trying to import, I getting the following error..
Please help.. and suggest the alternate..
Warning: the objects were exported by XYZABC , not by you
import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
import server uses WE8ISO8859P1 character set (possible charset conversion)
IMP-00008: unrecognized statement in the export file:
. importing NEXOS_ADMIN_OLTP_API's objects into SHRICHANDRA_ABC123
IMP-00003: ORACLE error 3120 encountered
ORA-03120: two-task conversion routine: integer overflow
. importing NEXOS_ADMIN_OLTP_TAB's objects into SHRICHANDRA_XYZ123
IMP-00003: ORACLE error 3120 encountered
ORA-03120: two-task conversion routine: integer overflow
Thanks in advance..

Thank Rajneesh,
I suspect the same issue as you did, But unfortunately I don't have much option available, as other side all are production DB so All I can do is pull from there that is export and import to my local where I am stuck!!!
Thanks..

Import error character set conversion

import done in US7ASCII character set and AL16UTF16 NCHAR character set
import server uses AL32UTF8 character set (possible charset conversion)
export client uses WE8ISO8859P1 character set (possible charset conversion)
Import terminated successfully without warnings.
how to resolve this
importinng into linux machine

import done in US7ASCII character set and AL16UTF16 NCHAR character set
import server uses AL32UTF8 character set (possible charset conversion)
export client uses WE8ISO8859P1 character set (possible charset conversion)
Import terminated successfully without warnings.Your import was successful. However, there are a few things you need to note from the top of the import log. It is advisable to use correct NLS settings when doing export/import to avoid data corruption/loss. That idea is to ensure you set the correct NLS setting (NLS_LANG) at the client before running exp or imp. In some cases, the setting does not matter because the different character sets can go together.
In this case, I would not worry about it.

Export/import character data conversion in NLS_LANG FAQ

The [OTN NLS_LANG FAQ|http://www.oracle.com/technology/tech/globalization/htdocs/nls_lang%20faq.htm#_Toc110410566] says:
>
In Oracle9i the Export utility always exports user data, including Unicode data, in the character set of the database. The Import utility automatically converts the data to the character set of the target database.
>
But I don't think this is correct for Oracle 9i. Example:
export NLS_LANG=AMERICAN_AMERICA.US7ASCII
sqlplus /
SQL*Plus: Release 9.2.0.6.0 - Production on Wed Jun 17 10:05:57 2009
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
JServer Release 9.2.0.6.0 - Production
SQL> select * from v$version;
BANNER
Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
PL/SQL Release 9.2.0.6.0 - Production
CORE    9.2.0.6.0       Production
TNS for HPUX: Version 9.2.0.6.0 - Production
NLSRTL Version 9.2.0.6.0 - Production
SQL> select * from nls_database_parameters where parameter like '%SET%';
PARAMETER                      VALUE
NLS_CHARACTERSET               WE8ISO8859P15
NLS_NCHAR_CHARACTERSET         AL16UTF16
SQL> exit
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
JServer Release 9.2.0.6.0 - Production
exp / owner=test file=test.dmp
Export: Release 9.2.0.6.0 - Production on Wed Jun 17 10:06:42 2009
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to: Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
JServer Release 9.2.0.6.0 - Production
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
server uses WE8ISO8859P15 character set (possible charset conversion)
About to export specified users ...Could you please:
- check and update NLS_LANG FAQ for Oracle 9i
- update NLS_LANG FAQ for Oracle 10g, Oracle 11g and Data Pump.
Thanks.
Edited by: P. Forstmann on Jun 17, 2009 10:14 AM

I was wrong and you are right like the OTN NLS_LANG FAQ.
I made the following test with Oracle 9.2.0.6 and with Oracle XE:
sqlplus test/test
SQL*Plus: Release 10.2.0.1.0 - Production on Ven. Juin 19 10:20:23 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connecté à :
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
SQL> create table t (x varchar2(10));
Table créée.
SQL> insert into t values(chr(233));
1 ligne créée.
SQL> select * from t;
X
é
SQL> select dump(x,1017) from t;
DUMP(X,1017)
Typ=1 Len=1 CharacterSet=WE8MSWIN1252: e9
SQL> exit
Déconnecté de Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
set NLS_LANG=AMERICAN_AMERICA.US7ASCII
exp test/test tables=t file=t.dmp
Export: Release 10.2.0.1.0 - Production on Fri Jun 19 10:21:54 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
server uses WE8MSWIN1252 character set (possible charset conversion)
About to export specified tables via Conventional Path ...
. . exporting table                              T          1 rows exported
Export terminated successfully without warnings.
sqlplus test/test
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Jun 19 10:22:07 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
SQL> drop table t;
Table dropped.
SQL> exit
Disconnected from Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
imp test/test tables=t file=t.dmp
Import: Release 10.2.0.1.0 - Production on Fri Jun 19 10:22:23 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
Export file created by EXPORT:V10.02.01 via conventional path
import done in US7ASCII character set and AL16UTF16 NCHAR character set
import server uses WE8MSWIN1252 character set (possible charset conversion)
. importing TEST's objects into TEST
. importing TEST's objects into TEST
. . importing table                            "T"          1 rows imported
Import terminated successfully without warnings.
sqlplus test/test
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Jun 19 10:22:32 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
SQL> select dump(x,1017) from t;
DUMP(X,1017)
Typ=1 Len=1 CharacterSet=WE8MSWIN1252: e9

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'

Oracle Export charset concern

Hi everyone,
Running Oracle 9i version 9.2.6.0 running on windows server 2003
I have run an export which completed sucessfully WITH warnings.
I figure I am getting this message due to the following line at the top of teh export log
"Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
server uses WE8ISO8859P1 character set (possible charset conversion)"
What is causing me concern is that when I check the the following table v$NLS_PARAMETERS it clearly shows NLS_CHARACTERSET = WE8ISO8859P1 and not WE8MSWIN1252.
I have no idea where it is getting this or why it is using it for the export.
Should I be foucing on setting NLS-LANGi in environment variable at the OS user level, it doesn't seem to have one set. Or should I be foucesd on the fact Oracle seems to be showing two different character sets. Bascially I am stumped.
So now I don't know how to resolve this issue, any advice would be greatly appreciated.
Thanks guys

For future reference, the Globalization forum: Globalization Support
user12243721 wrote:
I have run an export which completed sucessfully WITH warnings.
I figure I am getting this message due to the following line at the top of teh export logYou should have EXP-nnnnn messsages in the log.
If exp-91, then you should match client charset to server's. If that is not possible you might use STATISTICS=none for the export.
"Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character setThis is the (requested) export client and produced dump file character set. It's picked up from NLS_LANG, which defaults to WE8MSWIN1252 on western europe Windows' settings.
server uses WE8ISO8859P1 character set (possible charset conversion)"This matches database character set (NLS_CHARACTERSET).
Should I be foucing on setting NLS-LANGi in environment variable at the OS user level, it doesn't seem to have one set. Oracle Home on windows platform has a "default" NLS_LANG setting, implemented through the registry. (The char set part matches windows acp, ansi code page, I believe).
Or should I be foucesd on the fact Oracle seems to be showing two different character sets. It's one and the same.
For the "traditional" exp/imp tools, always care for NLS_LANG settings. For export sessions you should generally (always) match export client char set to that of the database character set. Note that this is sort of an exception to the rule, that you should not look to the database for the client side setting (see the NLS_LANG FAQ).
Seeing your database character set (NLS_CHARACTERSET) and that Windows (win-1252) is mentioned in your post, there might be a potential loss of character data considering db is a subset (character repertoire). If you have Windows based clients/apps, character data may be lost during proper conversion (replacement character used). Also the much too common pass-through scenario, data may be at risk due to incorrect setup. See e.g.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/ch2charset.htm#sthref165 (fig 2-6)
http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/ch11charsetmig.htm#i1005993
http://www.oracle.com/technetwork/database/features/globalization/nls-lang-099431.html

Export Scott Schema Conversion Error [SOLVED]

I'm trying to export default user SCOTT to DMP file.
But error occured. Some kind of character conversion error.
This is the log generated:
Connected to: Oracle9i Enterprise Edition Release 9.2.0.1.0 - 64bit Production
JServer Release 9.2.0.1.0 - Production
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
server uses AL32UTF8 character set (possible charset conversion)
EXP-00056: ORACLE error 942 encountered
ORA-00942: table or view does not exist
EXP-00000: Export terminated unsuccessfully
What is the solution for this case?
Thanks
Message was edited by:
user465837+++eric

>
How if I dont have 9.2 DB?You have attempted to export from one above...?
Can you skip the TOAD util and just log on to the server and run exp from there?
Another option would involve downloading the 9.2 Database Client (9i Downloads) and install on a nearby PC, or if you have one with 9.2 already installed, and export from there.
Any tricks to export user from different version of
DB instance? (Is it a must that having same version
of DB to exp-imp?)No tricks. The rule is: to export from lower to higher, you must use the lower versions exp tool. (Then use target version of imp for importing. The key is to get the exp dump of correct version and format.)
NB: while
C:\>dir c:\exp.exe / s
Volume in drive C is Disk_C
Volume Serial Number is 347F-B884
only return thatIt's searching, give it (plenty of) time.
Message was edited by:
orafad

CHARACTER SET CONVERSION PROBLEM BETWEEN WIN XP (SOURCE EXPORT) AND WIN 7

Hi colleagues, please assist:
I have a laptop running win 7 professional. Its also running oracle database 10g release 10.2.0.3.0. I need to import a dump into this database. The dump originates from a client pc running win XP and oracle 10g release 10.2.0.1.0 When i use the import utility in my database(on the laptop), the following happens:
Import: Release 10.2.0.3.0 - Production on Tue Nov 9 17:03:16 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Username: system/password@orcl
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options
Import file: EXPDAT.DMP > F:\uyscl.dmp
Enter insert buffer size (minimum is 8192) 30720>
Export file created by EXPORT:V08.01.07 via conventional path
Warning: the objects were exported by UYSCL, not by you
import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
export client uses WE8ISO8859P1 character set (possible charset conversion)
export server uses WE8ISO8859P1 NCHAR character set (possible ncharset conversion)
List contents of import file only (yes/no): no >
when i press enter, the import windows terminates prematurely without completing the process. What should i do to fix this problem?

Import: Release 10.2.0.3.0 - Production on Fri Nov 12 14:57:27 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Username: system/password@orcl
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options
Import file: EXPDAT.DMP > F:\Personal\DPISIMBA.dmp
Enter insert buffer size (minimum is 8192) 30720>
Export file created by EXPORT:V10.02.01 via conventional path
import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
List contents of import file only (yes/no): no >
Ignore create error due to object existence (yes/no): no >
Import grants (yes/no): yes >
Import table data (yes/no): yes >
Import entire export file (yes/no): no >
Username:

Possible charset conversion

Similar Messages

Maybe you are looking for