Cloud migration
Migrate to Oracle Cloudfor database performance and cost efficiency
OCI moves usually start with an Oracle Database. Here is how Oracle's VM service and Zero Downtime Migration work, and what your database edition rules out.
Why teams move to OCI at all
The usual reason is an Oracle Database. If yours is at the centre of the estate, its migration methods, licensing and Exadata options drive the decision, and the application servers follow. If you don't run Oracle Database, compare OCI against the other clouds on your own workloads. There may be no reason to single it out.
Moving virtual machines
Oracle Cloud Migrations automates moving VMs to OCI, and Oracle lists two sources: VMware virtual machines and AWS EC2 instances. Anything else needs another route. The flow is specific:
- Install and register a remote agent appliance, a sealed VM that connects to the source environment. It needs IPv4 addressing, static or DHCP.
- Create a source environment and an asset source, then run discovery.
- Create a migration project and add assets. An asset can belong to only one project, which shapes how you divide the work.
- Replicate on a schedule or manually, then create a migration plan and configure the target assets.
- Generate a Resource Manager stack from the plan, deploy it to create the instances, validate, and mark the project complete.
A shortcut with a cost
You can import assets from CSV files without setting up a source environment, but imported assets can't use automated discovery or replication. That is fine for planning and cost comparison, and it doesn't move any data.
Moving Oracle databases
Oracle's Zero Downtime Migration tool, ZDM, offers physical and logical methods, each online or offline. The name refers to how the online methods are configured to keep the source available while data moves. The switch itself still needs a planned window.
Physical methods use Data Guard and RMAN. Online physical sets up a standby on the target from a source backup, then switches over. Logical methods use Data Pump, plus GoldenGate for online moves, with the source open to clients while data transfers. Logical methods can convert a non-multitenant source to a multitenant target.
Edition matters. Oracle states that offline physical is the only method supported for Standard Edition databases, so a Standard Edition estate can't plan on an online move with ZDM. Find that out before you promise anyone a short outage.
What to check around the database
- Your Oracle licensing and what it permits on OCI. Have your licensing contact confirm this in writing.
- Database links, scheduled jobs and external tables pointing at servers or paths that won't exist after the move.
- Character set and version differences between source and target, which decide which methods are open to you.
- Application connection strings and how quickly clients reconnect after the switch.
What we can show you
We have no published Oracle Cloud or Oracle Database migration. Our published database work is on MySQL. For an Oracle estate of any size, you should involve an Oracle DBA, and we can work alongside one on the application side: connection handling, SQL changes and testing against the new environment.
Oracle Cloud migration questions
Does ZDM really mean no downtime?
It means online methods keep the source available while data moves, followed by a switch you still have to plan for. Standard Edition sources are limited to the offline physical method.
Can we move from Azure to OCI with Oracle Cloud Migrations?
Oracle lists VMware and AWS EC2 as its sources, so Azure VMs aren't covered by that service. They would need a different route.
Which edition and version are you running?
Tell us the database edition and version and what connects to it. We will tell you which parts we can help with and where you need an Oracle specialist.
We reply within one business day (IST).