Before we get started, I need to share that this is for informational purposes only and is covered by this guidance.
Scope of changes:*Hardware example:from E25k to M5*Operating system example:-from MS Windows to Linux, from HP-UX Itanium to SPARC Solaris*Database version example:From 18.104.22.168 to 22.214.171.124. Even „simple” database upgrade may also be considered as a migration for example, if the availability requirements are very strict and near zero downtime conditions have to be met.*Location:-For example the database needs to be placed in another data center*Storage method or technology:-For example: from raw devices managed by Veritas VxVM to ASM, from one filesystem to another.
Oracle to Oracle is the best method when:The technical capabilities of software and infrastructure fit acceptable downtime conditionIt needs to be as simple as possible or we need to migrate tens or hundreds of databases. This is true for physical migration methods specifically.Go for O3 when:It is not possible to meet downtime requirements with any of O2 methods.It may mean long preparation and migration process time. It may also mean lots of $$$ spent by the customer.
* Exception: TTS combined with TTS incremental backup may allow to use a fuzzy tablespace backup. Going to be used in 12c, 11gR2 -> migration scenarios to Exadata only.
1 CPU License for Golden Gate is 17.5k$ per CPU in list price. 1-year Premier Support is 3.85k$ for list price.If using 1-year Golden Gate term license, total cost (license + support) per 1 CPU license will be 7.35k$ (list price).
„Modernizacja infrastruktury baz danych okiem ACS” – Piotr Kołodziej, Advanced Customer Support Architect, Oracle Polska