Dbvisit Software limited has released its Dbvisit Replicate version 2.5, which supports a near zero downtime migration path to Oracle’s recently released Oracle 12c.

The traditional approach to migrating data involves locking the legacy database in a known state by stopping the application while the data is copied, then connecting the application to the new migrated database before restarting it.

To ensure that all changes are reflected in the new replacement database, data migration traditionally involves an application outage for the period of time it takes to copy the legacy data to the new database.

This is an increasingly infeasible approach as larger data volumes mean that the migration process becomes more time consuming, difficult and risky. Meanwhile, around-the-clock demand for systems significantly reduces the availability of batch windows and planned system outages, which would typically be leveraged for this process.

This approach has a number of limitations. The most significant is that the application must remain offline for the full duration of the data copying process. For large databases, this means it can take a very long time to physically copy the data.

For many companies this outage is no longer acceptable. Companies need to use an alternative strategy for migration of databases from one version to another or from one platform to another.

Customers can now carry out their much-needed migrations of Oracle database versions (or of hardware and operating systems) without spending enormous sums and losing valuable production up time.

Different Editions for Different Needs
When it comes to Oracle database replication one size does not fit all. Dbvisit’s Replicate version 2.5 offers different product editions and pricing plans to align with current replication requirements, and can grow along with these requirements.

For more information about Dbvisit Replicate editions: