Database Backup and Recovery (MOSC)

MOSC Banner

Transportable tablespaces and cross platform incremental backup procedures

edited Oct 28, 2018 5:00AM in Database Backup and Recovery (MOSC) 1 commentAnswered

Hello,

I'm currently migrating an 11g database from Solaris 10 to Red Hat 4.8.5-28, following instructions documented in 11G - Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup (Doc ID 1389592.1).

The process described in the above article are moving along well; however, it's been a while since I've done the final step involving importing the remaining database accounts and objects. 

Once I'm complete importing each tablespace's metadata, I believe I can take a full datapump export of the source database with no data, and then perform a full datapump import in which I set object_exists_action to skip since the tables of interest will already be available for use. At this point, I will have the additional accounts from the source database in the new one, plus any additional objects such as triggers, PL/SQL code, materialized views, etc...

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center