The delay between the time a DML change is applied at the originating database and the time the transaction reaches the destination databases is called as

Options
- Propagation
- Propagation latency
- Conflict
- Conflict latency

CORRECT ANSWER : Propagation latency

Discussion Board
Propagation latency

When Oracle propagates an update to destination tables, it expects the current data for the row at the destination to match the data at the originating site prior to the update.

If the data is not the same, an update conflict results.

Similarly, if an insert fails because of a primary key violation (i.e., a unique constraint violation) the result is a uniqueness conflict or violation.

If the target row of a delete does not exist at the destination site, a delete conflict results.

Unless you are propagating changes among master sites synchronously, there is a delay between the time a DML change is applied at the originating database and the time the transaction reaches the destination databases.

This lag is known as propagation latency.

Prajakta Pandit 02-16-2017 01:19 AM

Write your comments


Enter the code shown above:

(Note: If you cannot read the numbers in the above image, reload the page to generate a new one.)


Related Content

Advertisement
 
▲