Oracle Database Discussions

How big is the source database ? How much downtime can you afford ? A less complicated approach may be using simple expdp/impdp

http://docs.oracle.com/cd/E11882_01/server.112/e23633/expimp.htm

HTH
Srini

Hello;

Checked my notes and I did this from AIX 9 years ago. Thoughts :

On your Step 1 - Will Archive be off on the new database until the data is moved? If yes at what point will you turn it on?

On your Step 2 - Would consider using restrict mode instead.

On your Steps 5 and 6 - How are you moving? SCP? How much time did you budget for transfer?

On Step 10 - Will Data Pump skip empty tables and break something? ( How will you deal with invalid objects in general on the new system ? )

On Step 11 - Are there addition users to create on Linux system?

Questions

1. Are there any scripts which need to move which can tested in advance?

2. Are there Jobs/Crons which need to be account for on the old and new system? ( Off on old and ON on new )

3. Was Linux setup with LVM? ( Given your large size might save headache down the road )

4. What method will be used to compare objects between the old and the new?

5. Does you checklist have a start and stop time for each item?

6. Has the net80 been tested in advance?

( Would keep Linux and Oracle on separate partitions if possible, then you could reinstall the OS without touching Oracle )

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Notes :

( Migration of an Oracle Database Across OS Platforms [ID 733205.1] )


How To Use RMAN CONVERT DATABASE on Source Host for Cross Platform Migration [ID 413586.1]

Cross-Platform Migration on Destination Host Using Rman Convert Database [ID 414878.1]


Creating a Duplicate Database on a New Host. [ID 388431.1]


Best Regards

mseberg

Why are you doing both transportable tablespaces and import ? You just need to import metadata if you are planning to use transportable tablespace.
Follow MOS notes:
733205.1
243304.1

I guess you can not use rman convert database because of different endianness.

So either use transportable tablespace or expdp/impdp.

The database is 1.5TB..That's the reason why I'm going for TTS. We can tolerate a downtime of 2 days.

Hi

I'm having to move a 3.4TB database from a big to a little endian platform (HPUX -> RHEL5) both using ASM. I was planning to do the following as the RMAN convert command does not work at database level with different platform endians and the XTTS / NFS method isn't going to work so well when using ASM with 100s of tablespaces.

1. Use whichever of these import methods proves to be quicker... parallel expdp then use dbms_file_transfer.PUT_FILE to move the dump files to the target ASM instance then use impdp for the imports. Or use impdp over a network link using the NETWORK_LINK parameter.

2. Use a PL/SQL script to do a insert /* APPEND */ over a db link to insert all of the rows added to the source database since the database was exported.

Will let you know if this is any good.

Steve