• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1126
  • Last Modified:

Unknown cause of Transportable Tablespace charset problem

Noting tricky here, just following an exercise.
Exporting a small TS from one DB to another using OS file copy and metadata xfer.

The "TTS" tablespace has been copied from the ORCL to the OMF DB, and as SYSDBA on OMF, I issued:
SQL> alter session set db_file_name_convert =  '/disk1/orcl/TTS.dbf', '/disk1/omf/OMF/datafile/TTS.dbf';

User U1 exists on both DBs.

The two DBs are on the same machine, both created via `dbca`.  I don't recall setting any non-default character sets.

Can someone elucidate this for me?
Thanks!

-- ---------------------------------------
On the SOURCE:

[oracle@rhel 00:17:11 ~]orcl$ exp file=tts.dmp log=tts.log tablespaces=TTS transport_tablespace=y

Export: Release 11.2.0.1.0 - Production on Mon Mar 17 00:40:46 2014

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.


Username: / as sysdba

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 US7ASCII character set and AL16UTF16 NCHAR character set
server uses WE8MSWIN1252 character set (possible charset conversion)
Note: table data (rows) will not be exported
About to export transportable tablespace metadata...

For tablespace TTS ...
. exporting cluster definitions
. exporting table definitions
. . exporting table                      U1_T1_TTS
. exporting referential integrity constraints
. exporting triggers
. end transportable tablespace metadata export
Export terminated successfully without warnings.

-- -------------------------------------------------
On the DESTINATION:

[oracle@rhel 19:23:39 ~]omf$ imp file=tts.dmp transport_tablespace=y datafiles='/disk1/omf/OMF/datafiles/TTS.dbf'

Import: Release 11.2.0.1.0 - Production on Mon Mar 17 19:23:56 2014

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

Username: / as sysdba

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 file created by EXPORT:V11.02.00 via conventional path
About to import transportable tablespace(s) metadata...
import done in US7ASCII character set and AL16UTF16 NCHAR character set
. importing SYS's objects into SYS
. importing SYS's objects into SYS
IMP-00017: following statement failed with ORACLE error 29345:
 "BEGIN   sys.dbms_plugts.beginImport ('11.2.0.1.0',178,'2000',13,'Linux x86 "
 "64-bit',75329,1072051,1,0,0,0); END;"
IMP-00003: ORACLE error 29345 encountered
ORA-29345: cannot plug a tablespace into a database using an incompatible character set
ORA-06512: at "SYS.DBMS_PLUGTS", line 2561
ORA-06512: at "SYS.DBMS_PLUGTS", line 2070
ORA-06512: at line 1
IMP-00000: Import terminated unsuccessfully
0
Ralph
Asked:
Ralph
1 Solution
 
MikeOM_DBACommented:
. . .  server uses WE8MSWIN1252 character set (possible charset conversion)
Change your NLS_LANG environment variable to something compatible with US7ASCII  or perhaps AL16UTF16.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now