Cutover Went Perfectly. The First New Order Failed With ORA-00001.
Lab Row counts matched 10,000 to 10,000, and the first new order still failed: the target sequence was handing out 9,001 while the table already went up to 10,000.
Oracle Cloud & Migration
OCI, Azure, Exadata, 23ai/26ai, on-prem → cloud
Moving Oracle to the cloud is less about the destination than the method — and the method decides your downtime, your risk, and whether you can roll back. ZDM, GoldenGate, Data Pump, Data Guard, and RMAN each trade cutover time against complexity and cost, and the right choice depends on your database size, version, and tolerance for downtime. These guides cover the decisions across OCI and Microsoft Azure — including Oracle Database@Azure, Autonomous, Exadata, and 23ai/26ai — vendor-neutral, with the trade-offs spelled out rather than glossed.
Guides in this pillar
-
-
The Migration Completed Successfully. Half the Names Are Now Question Marks.
Lab Every migration 'succeeded' with 10 rows and 0 errors. Only the Unicode target kept every name intact.
-
Oracle Data Pump, Done Right: A Migration You Can Prove
Lab Counted, not assumed: the export and re-import brought back exactly the same 5,000 + 20,000 rows.
-
OCI vs Oracle Database@Azure: Where Should Your Oracle Database Live?
Lab The same chatty workload went from 868 ms to 12,101 ms as injected latency rose from 0 to 10 ms. The batched version took 274 ms even at 10 ms.
-
Your First Oracle Autonomous Database on OCI Always Free
Lab Asked for the rows most similar to 'cat', VECTOR_DISTANCE put 'kitten' closest and 'airplane' farthest, on Oracle Database Free with no OCI account.
-
Migrating Oracle to the Cloud: Which Method, and When
Lab In all six scenarios, the method followed from four checks: the target, the endian or version boundary, the downtime budget, and the edition.