Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Unknown cause of Transportable Tablespace charset problem

Posted on 2014-03-17
1
Medium Priority
?
1,091 Views
Last Modified: 2014-05-02
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
Comment
Question by:Ralph
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 29

Accepted Solution

by:
MikeOM_DBA earned 1500 total points
ID: 39936944
. . .  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

[Webinar] Lessons on Recovering from Petya

Skyport is working hard to help customers recover from recent attacks, like the Petya worm. This work has brought to light some important lessons. New malware attacks like this can take down your entire environment. Learn from others mistakes on how to prevent Petya like worms.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article started out as an Experts-Exchange question, which then grew into a quick tip to go along with an IOUG presentation for the Collaborate confernce and then later grew again into a full blown article with expanded functionality and legacy…
Truncate is a DDL Command where as Delete is a DML Command. Both will delete data from table, but what is the difference between these below statements truncate table <table_name> ?? delete from <table_name> ?? The first command cannot be …
This video explains at a high level with the mandatory Oracle Memory processes are as well as touching on some of the more common optional ones.
Via a live example show how to connect to RMAN, make basic configuration settings changes and then take a backup of a demo database

610 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question