Favorite way: migrating to exadata
- At source database, enable the force logging, put it in archivelog mode, set secondary archive destination, add TNS entries and add standby redo logs etc.
- At Exadata, make sure ASM instances are up and running.
- At standby side, create a simple parameter file, make entries in TNS, and then start standby instance in nomount.
- Then from primary, in RMAN, connect to the source database and with target auxiliary standby and run duplicate target database for standby from active database.
- Then after making sure that standby is in sync with primary, switch-over to the standby.
- Using srvctl register this database to clusterware at all nodes of Exadata and configure database as RAC.
- Point your applications to the new Exadata database.
On this page
Share this
Share this
More resources
Learn more about Pythian by reading the following blogs and articles.
Lessons learned from debugging application performance in Cloud

Lessons learned from debugging application performance in Cloud
Jan 16, 2019 12:00:00 AM
4
min read
Migrating Oracle Workloads to Google Cloud - BMS
Migrating Oracle Workloads to Google Cloud - BMS
Dec 9, 2020 12:00:00 AM
2
min read
Import/export multiple SSIS packages
Import/export multiple SSIS packages
Sep 30, 2015 12:00:00 AM
1
min read
Ready to unlock value from your data?
With Pythian, you can accomplish your data transformation goals and more.