Transportable tablespace across diff platform

Hello experts
Source platform is Solaris (64bit)
Target platform Linus IA (32-bit)
Database in both platform is 10.2
Steps what I am following
1. Ensure the tablespaces are self-contained.
Ans: the tablespaces are self contained
2. Make the tablespaces read-only.
Ans: I made the tablespaces read only
3. Export the metadata using Data Pump Export.
Ans: I have exported the tablespaces and dumfile name=trans.dmp
$ expdp system/pwd DUMPFILE=trans.dmp DIRECTORY=DATA_PUMP_DIR TRANSPORT_TABLESPACES=SESSION_DATA TRANSPORT_FULL_CHECK=Y
4. Convert the data files to match the endian format.
Ans: RMAN> CONVERT DATAFILE '\opt\oracle\session_data.dbf'
TO PLATFORM ="Linux IA (32-bit)"
FROM platform=”Solaris [tm] OE (64-bit)”
FORMAT'\opt\oracle';
This was also done successfully ,its generated converted file like system define name: “data_D-UMR2_I-1977123235_TS-SESSION_DATA_FNO-5_1rk8r180”
5. Copy the files to the target system.
Then I have copied the exported trans.dmp file and converted datafile to target location like linux server.
6. Use the Data Pump Import utility to import the metadata
Impdp system/pwd DUMPFILE=trans.dmp DIRECTORY_PUMP_DIR
TRANSPORT_DATAFILES=/opt/oracle/data_D-UMR2_I-1977123235_TS-SESSION_DATA_FNO-5_1rk8r180
While importing I am getting this error :
ORA-29345 : cannot plug a tablespace into a database using an incompatible character ser

Whats the character set of Solaris Database? and whats the character set of Linux database. It looks they are different and thats reason for this error

Similar Messages

  • Transport Tablespace Issues

    hi.. i'm trying to use transport tablespace across the same platforms rather than performing export/import . i'm following the steps in Note:371556.1to exp/imp ASM files.
    i have finished all the steps and successfully transport the tablespace. this process involved only 2 TBS, CC_DATA and CC_INDEXES and the schema is CC. i choose to check the full containment before the export done. but when i count the objects before export and after the import, the count is different. the question is how to make the count of objects is same before and after transport.
    before export
    SQL> select count(*), object_type from user_objects group by object_type;
    COUNT(*) OBJECT_TYPE
    33 SEQUENCE
    3 DATABASE LINK
    55 TABLE
    82 INDEX
    19 SYNONYM
    39 VIEW
    6 rows selected.
    after import
    SQL> select count(*), object_type from user_objects group by object_type;
    COUNT(*) OBJECT_TYPE
    82 INDEX
    55 TABLE
    thanks in advance.
    -julie-
    Edited by: gunit on Nov 17, 2008 7:35 PM

    It's a limitation on transportable tablespace (http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/tspaces.htm#i1007233)
    You cannot transport the SYSTEM tablespace or objects owned by the user SYS. Some examples of such objects are PL/SQL, Java classes, callouts, views, synonyms, users, privileges, dimensions, directories, and sequences.So you need to transfer the views, sequences,etc., one method is using exp/imp.
    [source]$ exp cc/<pwd> file=cc.dmp rows=no
    [target]$ imp cc/<pwd> file=cc.dmp ignore=yes HTH
    Enrique

  • 11i Migration to Linux - Using transportable tablespace of 10g to move DB

    Hi there,
    We are planning to move 11i from HP-UX to Linux. Our Oracle EBS 11i database version is 10g R2. Does anyone know if its possible to use the "Transportable" tablespace feature of 10g to move the entire database to Linux rather than using Export/Import?
    Since 10g offers to move the tablespaces across the platforms using its transportable tablespace feature, I just wanted to poll this group to see if anyone has any experience on doing this for Oracle E-Business suite's database.
    Thanks,
    Ashish

    Consider the limitations of Transportable Tablespaces, Objects with underlying objects (such as materialized views) or contained objects (such as partitioned tables) are not transportable unless all of the underlying or contained objects are in the tablespace set.
    Most database entities, such as data in a tablespace or structural information associated with the tablespace, behave normally after being transported to a different database but there are some exceptions:
    Transporting Tablespaces Between Databases
    http://download-west.oracle.com/docs/cd/B13789_01/server.101/b10739/tspaces.htm#i1007233

  • Why transportable tablespace for platform migration of same endian format?

    RDBMS Version : 10.2.0.4
    We are planning to migrate our DB to a different platform. Both platforms are of BIG endian format. From googling , I came across the following link
    http://levipereira.files.wordpress.com/2011/01/oracle_generic_migration_version_1.pdf
    In this IBM document, they are migrating from Solaris 5.9 (SPARC) to AIX 6 . Both are of BIG endian format.Since they both are of same endian format can't they use TRANSPORTABLE DATABASE ? Why are they using RMAN COVERT DATAFILE (Transportable tablespace ) ?

    In this IBM document, they are migrating from Solaris 5.9 (SPARC) to AIX 6 . Both are of BIG endian format.Since they both are of same endian format can't they use TRANSPORTABLE DATABASE ? Why are they using RMAN COVERT DATAFILE (Transportable tablespace ) ?they are using transportable database - they are not importing data to dictionary, not creating users... - instead of using convert database, they used convert datafile to avoid of converting all datafiles (you need to convert only undo + system tablespace) - there's MOS note: Avoid Datafile Conversion during Transportable Database [ID 732053.1].
    Basic steps for convert database:
    1. Verify the prerequisites
    2. Identify any external files and directories with DBMS_TDB.CHECK_EXTERNAL.
    3. Shutdown (consistent) and restart the source database in READ ONLY mode.
    4. Use DBMS_TDB.CHECK_DB to make sure the database is ready to be transported.
    5. Run the RMAN convert database command.
    6. Copy the converted files to the target database. Note that this implies that you will need 2x the storage on the source database for the converted files.
    7. Copy the parameter file to the target database.
    8. Adjust configuration files as required (parameter, listener.ora, tnsnames, etc).
    9. Fire up the new database!
    All other details are in:
    http://docs.oracle.com/cd/B19306_01/backup.102/b14191/dbxptrn.htm#CHDFHBFI
    Lukas

  • Steps to create Cross-Platform Transportable Tablespaces

    hi
    what is the steps to do Cross-Platform Transportable Tablespaces.
    i want to perform this in my pc, i have linux and windows in same PC, i want to migrate from linux to windows and vice versa.
    so can i know complete steps and commands to perform Cross-Platform Transportable Tablespaces. to get complete knowledge i am doing this so i can implement this in my office when any migrate issues comes. so once i do this i will get confidence so that i can do the same in my office which saves my time.
    veeresh s
    oracle-dba
    [email protected]

    Hi, also you can review the Note:413586.1 into metalink site.
    Good luck.
    Regards.

  • Cross Platform migration employing Incremental Transportable Tablespaces

    We have a VLDB that needs to be converted from a Sparc T3 Solaris Big endian to Linux small endian and there are over 6000 tables and the GoldenGate method to reduce downtime was attempted n dev and was an utter failure.  Then I read in several places including metalink ( My Oracle Support ) in DOC ID 1644693.1 Entitiled "How to restore a pre 12c database backup to a cross platform cross endian 12c database", Bug 13335722 and many Oracle 12c Brochures all state that the cross platform cross endian method of using Incremental Transportable Tablespaces which used to be only supported for Exadata is now supported for ALL 12c platforms.  Can anyone veriffy this and has employed this technique to migrate from Sun to Linux by first upgrading the source database to 12c then employing Incremental Transportable Tablespaces capabilities of 12c to migrate cross platform cross endian from Sun Sparc big endian 64 bit word  to Linux Intel little endian 64 word.  Otherwise if we migrate from 11GR2 Sun to Intel we are looking at least 5 days of Read Only downtime.
    Thanks

    You can also refer to Metalink note
    Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup (Doc ID 1389592.1)

  • Transportable tablespace Windows to Linux different character sets

    Hi,
    Is it absolutely necessary to have the same character set when doing a cross platform transport tablespace from Windows to Linux? We are trying to do it on Oracle10gR2 from Windows to Linux.
    Thank you.

    Hi, yes is necessary that your databases have the same chracter set, please review the limitations into the Note:291024.1.
    Luck.
    Have a good day.
    Regards.

  • Transport Tablespace via RMAN

    Hii all
    I configured control file autobackup on and take a backup whole database with "backup database;" command and
    RMAN> transport tablespace users tablespace destination 'c:\Transport' auxiliary destination 'c:\Auxi';
    I am receiving ;
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06026: some targets not found - aborting restore
    RMAN-06024: no backup or copy of the control file found to restore
    In begining lines of rman command I saw that "control_files=c:\Auxi/cntrl_tspitr_ST1_dFcB.f" looks like using unix path format in windows? Have you any idea ?
    Best Regards
    Oracle 10.2.0.3 on Vista Sp2

    hi
    Yes it is on besides I take backup with "backup database include current controlfile" nothing has changed
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\
    NCFST1.ORA'; # default
    also I have just tested same command on aix platform it works well I think this is related windows platform ?
    Edited by: EB on Sep 25, 2009 4:56 PM

  • Transportable tablespaces for migration and upgrade

    Hello All,
    I'm trying to find out some theory about transportable tablespace and upgrade in a single step. I've to move a DB from a Windows server to a Linux server. Win is running 10.1 and Linux 10.2 . It's possible to use RMAN to migrate the whole database and then on new node run startup upgrade and catupgrd.sql to upgrade catalog ?
    Should work?
    Thanks
    Raj

    The following doc for TDB says :-
    "Note: TDB requires the same Oracle Database software version on the source and target systems; hence, a database upgrade cannot be accomplished simultaneous with the platform migration. However, best practices for a database upgrade, as documented in the Oracle Upgrade Companion, also apply to any planned database maintenance activity, including platform migration."
    http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10gR2_PlatformMigrationTDB.pdf
    There is also an Oracle Whitepaper called "Database Upgrade Using Transportable Tablespaces: Oracle Database 11g Release 1" but I am still trying to find a copy.

  • 10gR2 Transportable Tablespaces Certified for EBS 11i for Migration

    Guys,
    Good news is Now 10gR2 Transportable Tablespaces Certified for EBS 11i,
    Here is Steven chan blog link, I know personally how much i struggled with expdp and impdp on linux, it sounds good news who is migrating 11i .
    http://blogs.oracle.com/stevenChan/2010/04/10gr2_xtts_ebs11i.html?utm_source=feedburner&utm_medium=email&utm_campaign=Feed%3A+OracleE-BusinessSuiteTechnology+%28Oracle+E-Business+Suite+Technology%29

    To migrate the database you can either use Transportable tablespaces or export/import.
    Transportable Tablespaces
    New Source Database Added for EBS 12 + 11gR2 Transportable Tablespaces
    https://blogs.oracle.com/stevenChan/entry/new_source_database_added_for
    New Source Databases Added for Transportable Tablespaces + EBS 11i
    https://blogs.oracle.com/stevenChan/entry/new_source_databases_added_for
    Database Migration using 11gR2 Transportable Tablespaces Now Certified for EBS 12
    https://blogs.oracle.com/stevenChan/entry/database_migration_using_11gr2_transportable
    Export/Import
    Export/import process for 12.0 or 12.1 using 11gR1 or 11gR2 (Doc ID 741818.1)
    Export/import notes on Applications 11i Database 11g (Doc ID 557738.1)
    If your application will remain on the same OS (which is different than the target database OS) then please also see:
    Oracle EBS R12 with Database Tier Only Platform on Oracle Database 11.2.0 (Doc ID 456347.1)
    Using Oracle EBS with a Split Configuration Database Tier on 11gR2 (Doc ID 946413.1)
    Oracle E-Business Suite Upgrades and Platform Migration (Doc ID 1377213.1)
    Thanks,
    Hussein

  • What is the best way to copy Oracle Transportable Tablespace datafiles betw

    Hi All,
    We are planning to implement Oracle Transportable Tablespace feature to copy huge data (around 900 GB) between the DBs.
    Our plan is to:
    1. Offline the tablespace 1 and tablespace 2 on Linux BOX1.
    2. Take export of these two tablespaces using TTS on Linux BOX1.
    3. zip datafiles of tablespace1 & 2 on Linux BOX1.
    4. Copy the zipped datafiles and dump file to Linux BOX2.
    5. Unzip datafiles of tablespace1 & 2 on Linux BOX1.
    6. Make the tablespaces online on Linux BOX1.
    7. Unzip datafiles of tablespace1 & 2 on Linux BOX2.
    8. Import the dump file to DB on Linux BOX2.
    9. Online the tablespace1 & 2 on Linux BOX2.
    However I do have below queries before I proceed.
    1. Do you see any issue with the above approach?
    2. To improve the copying speed across the network, Do you suggest any solution than rcp and ftp
    Our Environment: Oracle 9.2.0.8 running on Linux 2.6.5-7.308-bigsmp #1 SMP
    Please share your experiences.
    Thanks in advance for your time and suggestions :)
    Krishna Bussu.

    Take a look at Note:77523.1.
    Hope this Helps
    Regards

  • Transportable tablespace /imp problem

    Dear all ,
    please i need to correct me if i am wrong
    transportable tablespace can you done of different version of oracle database
    (means can do that task from lower to upper ex:10g.2 to 11g.2) take in your consideration the limitation of this taks.???
    1. when i do this task in same platform unix to unix and same edians big to big
    there is no way to convert datafile or tablespace
    the take is done by take tablespace read only and then exp this tablespace and ftp the datafile and dmp file
    to new server and switch tablespace read write thus imp the dmp ???
    2. when this taks is done from win to unix from 10g.2 to 11g.2
    check the self_contained this in the two and take tablespace read only and convert and exp and ftp the datafile and dmp file
    to new server thus convert the datafile and then imp and the last one switch the tablespace in read write???
    please i need your opinion obout this ?????
    and i need your advice in import
    imp USERID=\'sys/iti_ICON_sys as sysdba\' \ tablespaces=USERS transport_tablespace=y FROMUSER=sys@TABSTST as sysdba TOUSER=sys@PRODICON as sysdba file=/icon/appl/oracle/trans.dmp datafiles='/icon/appl/oracle/USERS01.dbf'oraicon@billdb03 $ imp USERID=\'sys/iti_ICON_sys as sysdba\' \ tablespaces=USERS transport_tablespace=y FROMUSER=sys@TABSTST as sysdba TOUSER=sys@PRODICON as sysdba file=/icon/appl/oracle/trans.dmp datafiles='/icon/appl/oracle/USERS01.dbf'
    Import: Release 10.2.0.3.0 - Production on Tue Dec 20 12:11:34 2011
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
    Export file created by EXPORT:V10.02.01 via conventional path
    About to import transportable tablespace(s) metadata...
    import done in AL32UTF8 character set and AL16UTF16 NCHAR character set
    export client uses US7ASCII character set (possible charset conversion)
    IMP-00017: following statement failed with ORACLE error 29342:
    "BEGIN sys.dbms_plugts.checkUser('ORAESB'); END;"
    IMP-00003: ORACLE error 29342 encountered
    ORA-29342: user ORAESB does not exist in the database
    ORA-06512: at "SYS.DBMS_PLUGTS", line 1895
    ORA-06512: at line 1
    IMP-00000: Import terminated unsuccessfully
    oraicon@billdb03 $ imp USERID=\'sys/iti_ICON_sys as sysdba\' \ tablespaces=USERS transport_tablespace=y file=trans.dmp datafiles='/icon/appl/oracle/USERS01.dbf'
    Import: Release 10.2.0.3.0 - Production on Tue Dec 20 12:28:50 2011
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
    Export file created by EXPORT:V10.02.01 via conventional path
    About to import transportable tablespace(s) metadata...
    import done in AL32UTF8 character set and AL16UTF16 NCHAR character set
    export client uses US7ASCII character set (possible charset conversion)
    . importing SYS's objects into SYS
    . importing SYS's objects into SYS
    IMP-00017: following statement failed with ORACLE error 29342:
    "BEGIN sys.dbms_plugts.checkUser('ORAESB'); END;"
    IMP-00003: ORACLE error 29342 encountered
    ORA-29342: user ORAESB does not exist in the database
    ORA-06512: at "SYS.DBMS_PLUGTS", line 1895
    ORA-06512: at line 1
    IMP-00000: Import terminated unsuccessfully
    oraicon@billdb03 $
    MANY THANKS

    1 read documentation. You can use rman to convert the files
    2 read documentation. You can use rman to convert the files.
    3 the error message is self explanatory
    4 the error message is self explanatory
    Please do your own research prior to posting.
    Please include only 1 question per post.
    Sybrand Bakker
    Senior Oracle DBA

  • Error in Transport Tablespace from linux to windows

    I am testing the cross-Platform Transport Tablespace. As per the oracle, we can transport tablespace from linux to windows without conversion because both are using same endian (Little).
    But i am fail to do Transport Tablespace from Linux to Windows.
    I am performing Transport Tablespace process as following:
    from Source Oracle Database server(red had linux as 4 32-bit oracle version:10.2)
    Sql> alter tablespace TEST read only;
    $ expdp system/pass dumpfile=test.dmp directory=export_dir transport_tablespaces=test transport_full_check=y
    after this i am coping test.dmp and data file (test.dbf) to the target machine (ms windows xp 32-bit with oracle 10.1) .
    on Target Machine (with Ms windows xp os) here i am giving the following command:
    impdp system dumpfile=test.dmp directory=exp_dir transport_datafiles=/exp_dir/test.dbf
    but it is giving following error:
    ora-39001: invalid argument value
    ora-39000: bad dump file specification
    ora-31619: invalid dump file "c:\pks\1103.dmp"
    what may by ...
    Prabhaker

    now for version compatibility i am inclusding version option with expdp
    edpdp scott dumpfile=1103.dmp directory=pks transport_tablespaces=prabhu version=10.1.0.2.0
    but now it is giving following error:
    Import: Release 10.1.0.2.0 - Production on Saturday, 11 March, 2006 19:07
    Copyright (c) 2003, Oracle. All rights reserved.
    Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
    With the Partitioning, OLAP and Data Mining options
    Master table "SCOTT"."SYS_IMPORT_TRANSPORTABLE_01" successfully loaded/unloaded
    Starting "SCOTT"."SYS_IMPORT_TRANSPORTABLE_01": scott/******** DUMPFILE=1103.DMP DIRECTORY=PKS TRANSPORT_DATAFILES=C:\PKS\PRABHU version=10.1.0
    Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
    ORA-39123: Data Pump transportable tablespace job aborted
    ORA-06550: line 2, column 2:
    PLS-00306: wrong number or types of arguments in call to 'BEGINIMPORT'
    ORA-06550: line 2, column 2:
    PL/SQL: Statement ignored
    Job "SCOTT"."SYS_IMPORT_TRANSPORTABLE_01" stopped due to fatal error at 19:07
    regards
    Prabhu

  • Transportable tablespace between 10.1 and 11.1 database

    Platform: Solaris
    From: 10.2.0.4
    To: 11.1.0.7
    I did some google searches and I don't see anything about transporting tablespaces between a 10.1 database and an 11.1 database
    Edited by: user11990507 on Oct 19, 2010 4:24 AM

    user11990507 wrote:
    Platform: Solaris
    From: 10.2.0.4
    To: 11.1.0.7
    I did some google searches and I don't see anything about transporting tablespaces between a 10.1 database and an 11.1 database
    It should work fine. check MOS :
    Compatibility and New Features when Transporting Tablespaces with Export and Import *[ID 291024.1]*
    Regards
    Rajesh

  • Transportable Tablespace in ASM

    Hi all,
    I want to move one tablespace from a database to another database using the 10g cross platform transportable tablespace.
    My source database is running on Linux 32 bit (Little endian format) and the target database is running on AIX (Big endian format). However both databases use the ASM diskgroup as a storage option.
    Do I need to convert the endian format of the source tablespace datafile to transport to the target database?
    Thanks,

    Because ASM diskgroup consists of one or more raw
    partitions or raw devices, I am wondersing if I still
    have to convert the endian format of datafiles..Interesting question.
    As you said earlier:
    - Linux natively uses Little endian
    - AIX natively uses Big endian
    You imply that perhaps Linux's ASM 'converts' to an 'Oracle neutral-endian' format whenever something is stored in the ASM disk group. Which would make it identical to AIX's ASM format, also 'converted'.
    (I use 'convert' in quotes, as one or the other would not need to get switched, if a specific endian form is maintained.)
    Worth investigating further. Although I am not sure why Oracle would introduce the overhead of conversion to-and-from every storage call.

Maybe you are looking for