1. Oracle GoldenGate Microservices Documentation
  2. Extract
  3. Downstream Extract for Downstream Database Mining
  4. Configure Extract for a Downstream Deployment
  5. Evaluate Extract Options for a Downstream Deployment

Evaluate Extract Options for a Downstream Deployment

To configure an Extract on the downstream mining database side, consider the following guidelines:

  • Multiple source databases can send their redo data to a single downstream database; however the downstream mining database can accept online redo logs from only one of those source databases. The rest of the source databases must ship archived logs.
  • When online logs are shipped to the downstream database, real-time capture by Extract is possible. Changes are captured as though Extract is reading from the source logs. In order to accept online redo logs from a source database, the downstream mining database must have standby redo logs configured.
  • When using a downstream mining configuration, the source database and mining database must be the same endian and same bitsize, which is 64 bits. For example, if the source database was on Linux 64-bit, you can have the mining database run on Windows 64-bit, because they have the same endian and bitsize.