By TOM LASZEWSKI JASON WILLIAMSON
Read Online or Download Oracle 11g Streams Implementers Guide PDF
Best databases books
This ebook brings the entire components of database layout jointly in one quantity, saving the reader the time and fee of creating a number of purchases. It consolidates either introductory and complex subject matters, thereby overlaying the gamut of database layout method ? from ER and UML options, to conceptual information modeling and desk transformation, to storing XML and querying relocating items databases.
Oracle Call Interface. Programmer's Guide
The Oracle name Interface (OCI) is an software programming interface (API) that enables functions written in С or C++ to engage with a number of Oracle database servers. OCI provides your courses the aptitude to accomplish the entire variety of database operations which are attainable with an Oracle database server, together with SQL assertion processing and item manipulation.
Oracle Warehouse Builder 11g: Getting Started
This easy-to-understand instructional covers Oracle Warehouse Builder from the floor up, and faucets into the author's extensive event as a software program and database engineer. Written in a calm kind with step by step motives, plenty of screenshots are supplied in the course of the publication. there are various guidance and worthwhile tricks all through that aren't present in the unique documentation.
Extra info for Oracle 11g Streams Implementers Guide
Sample text
Destination (HUB) Source 1 (SPOKE) Source 2 (SPOKE) Bi-directional Spoke-to-Hub Source 3 (SPOKE) This configuration is just an extension of uni-directional Spoke-to-Hub that allows the HUB to send its changes to each spoke. This means that at least one Capture process and queue must be configured on the HUB, and a Propagation process configured to each SPOKE. Note here that the HUB processes should be configured so that the HUB does not send the same change back to the SPOKE that originated it.
This is controlled by checkpointing. The Capture process will conduct checkpoints in which it coordinates its SCNs. By default these checkpoints happen with the capture of 10 MB of redo and the checkpoint metadata is retained in the database for 60 days. You can also force a checkpoint if the need arises. These checkpointing options are all controlled by the following capture parameters: • _CHECKPOINT_FREQUENCY: The number of megabytes captured which • CHECKPOINT_RETENTION_TIME: Number of days to retain • _CHECKPOINT_FORCE: This will force a Capture checkpoint.
About those Queues Throughout our discussion on the Streams processes, we mention the Advanced Queues used by Streams to transport changes. These queues are either in-memory (buffered queues) or tables on disk (persistent queues). Oracle Streams uses both buffered queues and persistent queues. A buffered queue can only be an ANYDATA queue, while a persistent queue can be an ANYDATA or a TYPED queue. ANYDATA and TYPED refer to the payload datatype of the message handled by the queue. ANYDATA datatype.