If the network or the target system becomes unavailable, Extract could run out of memory and abend. Protection against network and target failures: In a basic Oracle GoldenGate configuration, with only a trail on the target system, there is nowhere on the source system to store the data operations that Extract continuously extracts into memory. Some reasons for using a data pump include the following: Though configuring a data pump is optional, Oracle recommends it for most configurations. Pass-through mode increases the throughput of the Data Pump, because all of the functionality that looks up object definitions is bypassed. Perform no data manipulation: Data Pump can be configured in pass-through mode, where data is passively transferred as-is, without manipulation. Perform data manipulation: Data Pump can be configured to perform data filtering, mapping, and conversion. The data pump can be configured in two ways: In general, a data pump can perform data filtering, mapping, and conversion The data pump adds storage flexibility and also serves to isolate the primary Extract process from TCP/IP activity. The data pump reads this trail and sends the data operations over the network to a remote trail on the target. In a typical configuration with a data pump, however, the primary Extract group writes to a trail on the source system. If a data pump is not used, the Extract process must streams all the captured operations to a trail file on the remote target database. Though configuring a data pump is optional, it is highly recommended for most configurations. The data pump reads the trail file on the source database and sends the data operations over the network to the remote trail file on the target database. If you configure a data pump, the Extract process writes all the captured operations to a trail file on the source database. Support system managed database sharding to deliver fine-grained, multi-master replication where all shards are writable, and each shard can be partially replicated to other shards within a shardgroup.ĭata pump is a secondary Extract group within the source Oracle GoldenGate configuration. Simpler management of multiple implementations of Oracle GoldenGate environments and control user access for the different aspects of Oracle GoldenGate setup and monitoring. Large scale and cloud deployments with fully-secure HTTPS interfaces and Secure WebSockets for streaming data. Oracle GoldenGate can be installed and configured to use the Oracle GoldenGate Microservices Architecture for the following purposes: Oracle GoldenGate can be installed and configured to use the Oracle GoldenGate classic architecture for the following purposes:Ī static extraction of data records from one database and the loading of those records to another database.Ĭontinuous extraction and replication of transactional Data Manipulation Language (DML) operations and Data Definition Language (DDL) changes (for supported databases) to keep source and target data consistent.Įxtraction from a database and replication to a file outside the database.Ĭapture from heterogeneous database sources. The REST-enabled services provide remote configuration, administration, and monitoring through HTML5 web pages, command line, and APIs. Oracle GoldenGate Microservices Architecture is a new microservices architecture that provides REST-enabled services as part of the Oracle GoldenGate environment. These processes and files form the main components of the classic architecture and was the product design until this release. Oracle GoldenGate classic architecture provides the processes and files required to effectively move data across a variety of topologies.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |