10g - Transportable Table Spaces Across Different Platforms [ID 243304.1]

8/2/2019 10g - Transportable Table Spaces Across Different Platforms [ID 243304.1]

http://slidepdf.com/reader/full/10g-transportable-table-spaces-across-different-platforms-id-2433041 1/3



Case 1

------

The source platform is Sun SPARC Solaris: endianness Big

The target platform is HP-UX (64-bit): endianness Big

SQL> select PLATFORM_ID , PLATFORM_NAME from v$database;

PLATFORM_ID PLATFORM_NAME

----------- ------------------------------

3 HP-UX (64-bit)

No conversion is needed for files that (1) do NOT contain UNDO/Rollback

segments and (2) have a source and target OS with the same endianness.

Refer to Note.415884.1 "Cross Platform Database Conversion

with same Endian" to determine which files contain UNDO/Rollback segments.

Case 2

------

The source platform is Microsoft WIndows NT: endianness Little

The target platform is HP-UX (64-bit): endianness Big

If we move the files and import the tablespace:

. importing SYS's objects into SYS

IMP-00017: following statement failed with ORACLE error 1565:

"BEGIN sys.dbms_plugts.beginImpTablespace('TBS_TTS',37,'SYS',1,0,8192,2,57"

"54175,1,2147483645,8,128,8,0,1,0,8,462754339,1,1,5754124,NULL,0,0,NULL,NULL"

"); END;"

IMP-00003: ORACLE error 1565 encountered

ORA-01565: error in identifying file '/database/db101b2/V101B2/datafile/reposit01.dbf'

ORA-27047: unable to read the header block of file

HP-UX Error: 2: No such file or directory

Additional information: 2

ORA-06512: at "SYS.DBMS_PLUGTS", line 1540ORA-06512: at line 1

IMP-00000: Import terminated unsuccessfully

You have to convert the files :

--> locally before the import step so that the files are endian compatible:

<Solaris> rman target=/

Recovery Manager: Release 10.1.0.1.0 - 64bit Beta

connected to target database: V101B2 (DBID=3287908659)

RMAN> convert tablespace 'REPOSIT'

2> to platform="Linux IA (32-bit)"

3> db_file_name_convert='/database/db101b2/V101B2/datafile/reposit01.dbf',

4> '/tmp/reposit01.dbf';

Starting backup at 24-NOV-03

using target database controlfile instead of recovery catalog

allocated channel: ORA_DISK_1

channel ORA_DISK_1: sid=8 devtype=DISK

channel ORA_DISK_1: starting datafile conversion

input datafile fno=00006 name=/database/db101b2/V101B2/datafile/reposit01.dbfconverted datafile=/tmp/reposit01.dbf

channel ORA_DISK_1: datafile conversion complete, elapsed time: 00:00:01

Finished backup at 24-NOV-03

The converted datafile is staged in /tmp directory until it is copied to the

target server.

--> remotely on the target server after having copied them on the server.

5. Move datafiles and export dump file

-----------------------------------

$ftp tts.dmp

+

/database/db101b2/V101B2/datafile/reposit01.dbf (no conversion)

or

/tmp/reposit01.dbf (converted file if conversion had been required)

6. Import metadata

---------------

$ imp userid=\'/ as sysdba\' TRANSPORT_TABLESPACE=Ydatafiles=/database/db101b2/V101B2/datafile/reposit01.dbf

(or /tmp/reposit01.dbf )

file=tts.dmp log=imp_tts.log

Import: Release 10.1.0.1.0 - Beta on Mon Nov 24 03:37:20 2003

Export file created by EXPORT:V10.01.00 via conventional path

About to import transportable tablespace(s) metadata...

...

. importing SYS's objects into SYS

. importing OMWB's objects into OMWB

. . importing table "MTG_COL_DEP_CHG"

...

. . importing table "SYBASE11_SYSUSERS"

Import terminated successfully without warnings.

Review the import log for warnings and errors and resolve issues

before continuing. Failure to do so can result in data loss.

7. Set the imported tablespace to READ WRITE

---------------------------------------SQL> alter tablespace reposit read write;

Tablespace altered.

of 3

11/02/2010https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=243304.1



RELATED DOCUMENTS

-----------------

Note:77523.1 Transportable Tablespaces -- An Example to setup and use

Note:100693.1 Getting Started with Transportable Tablespaces

Note.415884.1 Cross Platform Database Conversion with same Endian

Note.413586.1 How To Use RMAN CONVERT DATABASE for Cross Platform Migration:

Note 371556.1 How move tablespaces across platforms using Transportable Tablespaces with RMAN

Note 579136.1 IMPDP TRANSPORTABLE TABLESPACE FAILS for SPATIAL INDEX)

Related

Products

Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition•

Keywords

BIGFILE; TRANSPORTABLE

Errors

IMP-17; ORA-1565; ORA-27047

of 3

11/02/2010https://support oracle com/CSP/main/article?cmd=show&type=NOT&id=243304 1

10g - Transportable Table Spaces Across Different Platforms [ID 243304.1]

Documents

Transcript of 10g - Transportable Table Spaces Across Different Platforms [ID 243304.1]