Examples with "single-database capture and apply example" and their translation in Japans
We konden deze vermelding niet vinden. Er worden benaderende resultaten weergegeven. Controleer je spelling of stel voor deze term aan het woordenboek toe te voegen.
Overview of the Single-Database Capture and Apply Example
単一データベースの取得および適用の例の概要
32 Single-Database Capture and Apply Example
32 単一データベースの取得および適用の例
The following topics describe configuring an example single-database capture and apply example
次の項では、単一データベースの取得および適用例の構成について説明します。
For more information about this configuration, see Chapter 32, "Single-Database Capture and Apply Example".
この構成の詳細は、第32章単一データベースの取得および適用の例を参照してください。
Chapter 32, "Single-Database Capture and Apply Example" for a sample environment that explicitly dequeues messages
This chapter illustrates an example of a single database that captures changes to a table with a capture process, reenqueues the captured changes into a queue, and then uses a DML handler during apply to insert a subset of the changes into a different table.
Sample Configuration That Performs Capture and Apply in a Single Database
単一データベースで取得および適用を実行する構成の例
Figure 1-16 Sample Single Database Capture and Apply Configuration
図1-16 単一データベースの取得および適用構成の例
This example specifies the other parameters to show that you can choose the name for the capture process, capture process's queue table, capture process's queue, apply process, apply process's queue table, and apply process's queue. If you do not specify these parameters, then system-generated names are used.
In some cases, you might want to capture, propagate, apply, or dequeue only changes that contain specific types of example, you might want to apply changes containing only insert operations for a particular table, but not other operations, such as update and delete.
You can transform a message during capture, propagation, apply, or dequeue, or during any combination of capture, propagation, apply, and dequeue. For example, if you want to hide sensitive data from all recipients, then you can transform a message during capture. If some recipients require additional custom transformations, then you can transform the previously transformed message during propagation, apply, or dequeue.
The examples in this chapter are independent of Oracle Streams. That is, no Oracle Streams capture processes, propagations, apply processes, or messaging clients are clients of the rules engine in these examples, and no queues are used.
A capture process, an apply process, or a messaging client can be associated with only one user. However, one user can be associated with multiple Oracle Streams clients, including multiple capture processes, apply processes, and messaging clients. For example, an apply process cannot have both hr and oe as apply users, but hr can be the apply user for multiple apply processes.
Er worden alleen voorbeelden gegeven om u te helpen het woord of de woordcombinatie waarop u hebt gezocht, te vertalen. Deze worden niet door ons geselecteerd of gevalideerd en kunnen ongepaste taal bevatten. Wij vragen u melding te maken van voorbeelden die dienen te worden aangepast of verwijderd. Vertalingen met grof of informeel taalgebruik worden meestal rood of oranje gemarkeerd.