A single apply process can apply user-enqueued messages that originated at multiple databases. However, a single apply process can apply captured messages. Similarly, a single apply process can apply synchronous messages from only one source database. Applying these LCRs requires knowledge of the dependencies, meaningful transaction ordering, and transactional boundaries at the source database.
Captured messages and synchronous messages from multiple databases can be sent to a single destination queue. However, if a single queue contains messages from multiple source databases, then there must be multiple apply processes retrieving these LCRs. Each of these apply processes should be configured to receive messages from exactly one source database using rules. Oracle recommends that you use a separate ANYDATA queue for messages from each source database.
Captured LCRs from multiple databases may be sent to a single destination queue. However, if a single queue contains captured LCRs from multiple source databases, then there must be multiple apply processes retrieving these LCRs. Each of these apply processes should be configured to receive captured LCRs from exactly one source database using rules. Regarding user-enqueued messages containing LCRs (not captured messages), a single apply process can apply these user-enqueued messages, even if they are from multiple source databases.
An apply process either can apply captured LCRs or user-enqueued LCRs, but not both. Regarding captured LCRs, an apply process can apply captured LCRs from only one source database, because processing these LCRs requires knowledge of the dependencies, meaningful transaction ordering, and transactional boundaries at the source a captured LCR, the source database is the database where the change encapsulated in the LCR was generated in the redo log.
It is not possible to do an in place compact, that is, one in which the source database and destination database are the same, using this method. An error will occur if the provider does not support compacting Access databases.
These procedures configure two databases at a time, and they require you to specify one database as the source database and the other database as the destination can be used to configure a replication environment with more than two databases by running them multiple times.
Suppose a source queue is propagating messages captured by a capture process or synchronous capture to multiple destination queues, and one or more destination databases acknowledge successful propagation of messages much more slowly than the other queues. In this case, the source queue can increase because the slower destination databases create a backlog of messages that have already been acknowledged by the faster destination such an environment, consider creating more than one capture process or synchronous capture to capture changes at the source database. Doing so lets you use one source queue for the slower destination databases and another source queue for the faster destination databases.
This example configures an Oracle Streams replication environment that replicates DML changes to all of the tables in the hr schema at two example shows you how to configure the environment for one-way replication, where changes to the replicated database objects are only allowed at one source configuration uses a downstream capture process at a destination database to capture the changes that were made to these database objects at the source database objects are read-only at the destination database.
The ability to configure at one or more downstream databases multiple capture processes that capture changes from a single source database provides more flexibility and can improve scalability.
Exemplele au rolul de a te ajuta să traduci cuvinte sau expresii corect si adaptat la context. Nu sunt selectate sau validate manual, așadar pot conține termeni inadecvați. Te rugăm să raportezi exemplele pe care le consideri inadecvate. Traducerile vulgare sau colocviale sunt în general marcate cu roșu sau cu portocaliu.