Which two migration will result in the least down time for a physical or logical migration of a database with active users during the migration?

Which two migration will result in the least down time for a physical or logical migration of a
database with active users during the migration?

Which two migration will result in the least down time for a physical or logical migration of a
database with active users during the migration?

A.
using GoldenGate

B.
using SQL Developer migration tools

C.
using Data Guard Physical Standby

D.
using cross-platform transportable tablespaces

E.
using incremental cross-platform RMAN restore

Explanation:
http://www.oracle.com/technetwork/middleware/goldengate/overview/ggzerodowntimed
atabaseupgrades-174928.pdf



Leave a Reply 7

Your email address will not be published. Required fields are marked *


Ranjit

Ranjit

Answer: A,C

OraDBA

OraDBA

It’s A & E. Below are the 3 Oracle HA migration options:

1. Cross Platform Incremental Backups
2. Oracle GoldenGate
3. Data Guard Transient Logical Standby

Eder Couto

Eder Couto

Dataguard would be required least downtime to migrate data after golden gate.
When using dataguard you simply need to switchover from primary to standby, which takes
only a few seconds. On the other hand, if you user cross-platform RMAN restore, before apply
any change on target database you need to convert backed up files, which is not that fast.

max

max

AC see Djamal’s pdf.

Ziad

Ziad

A,C
Data integration technologies such as Oracle GoldenGate or Oracle Data Integrator can
be used to migrate, and if necessary transform data. Typically, such environments
provide a high degree of flexibility, along with a productive way of defining and
implementing the required data integrations and transformations. Also, these
technologies are often used to facilitate data migration while the source system
continues to run.

If your application service-level agreements permit little or
no down time, you can use an Oracle Data Guard logical standby database to replicate
the database on Database Machine, and track and merge the changes while the source
database continues to run.