This blog discusses how to configure a downstream capture for an Oracle multi-tenant database. The configuration is useful for cloud applications because the cloud databases limit the new processes that can be installed on the production systems. In the example, we use Oracle GoldenGate integrated remote capture and delivery.
1. Scenario
In the example scenario shown as follows, Oracle GoldenGate replication is configured to replicat data from a Oracle multi-tenant database in the Cloud to an Oracle database on premises. Only one pluggable database, the CRM database, is replicated. Because limited new processes are allowed on the source database, a mining database is set up in the cloud for Oracle GoldenGate Cloud Service (GGCS) or Oracle GoldenGate to capture remotely and then deliver the data to the on-premise database via remote delivery.
1. Scenario
In the example scenario shown as follows, Oracle GoldenGate replication is configured to replicat data from a Oracle multi-tenant database in the Cloud to an Oracle database on premises. Only one pluggable database, the CRM database, is replicated. Because limited new processes are allowed on the source database, a mining database is set up in the cloud for Oracle GoldenGate Cloud Service (GGCS) or Oracle GoldenGate to capture remotely and then deliver the data to the on-premise database via remote delivery.
Oracle GoldenGate need to connect to both the source and mining database's container database for the capture. Because Oracle GoldenGate capture is configured at the container database level, Oracle GoldenGate connection to the source database (with alias ggadmins) and the connection to the mining database (with alias ggadminm) need to use the common database user connecting to the container database.
Why do I get the " OGG-08217 A root container connection is required when registering or unregistering Extract for a container database. " error?
Answer: When implementing the downstream capture, both the connection to the source database and the connections to the mining database need to use the root container.
Answer: When implementing the downstream capture, both the connection to the source database and the connections to the mining database need to use the root container.
2. Configuration
The configuration includes the following steps:
The configuration includes the following steps:
- Enabling the log shipping from the source database to the ming database.[1]
- Configuring the SQL*Net connection from Oracle GoldenGate to both the source and mining database.
- Configuring the Oracle GoldenGate extract with the downstream capture.
- Configuring the Oracle GoldenGate replicat with the remote delivery.
Why do I get the "OGG-08234 ERROR: Database container DMPDB1 does not exist." error?
Details: When registering extract to the mining database, I got the "OGG-08234 ERROR: Database container DMPDB does not exist" error". My source DB PDB name is CRM and my mining DB PDB is CRMDM How to resolve this?
Answer: You have to use the source DB PDB name. So please change to CRM.
Details: When registering extract to the mining database, I got the "OGG-08234 ERROR: Database container DMPDB does not exist" error". My source DB PDB name is CRM and my mining DB PDB is CRMDM How to resolve this?
Answer: You have to use the source DB PDB name. So please change to CRM.
Note that you need to register the integrated extract when logging into the mining database but you need to define the extract parameter file as follows:
extract extdm01 useridalias ggadmins TRANLOGOPTIONS MININGUSERALIAS ggadminm TRANLOGOPTIONS INTEGRATEDPARAMS (downstream_real_time_mine Y) exttrail ./dirdat/et SOURCECATALOG CRM table oggsr.*;
The ggadmins is the connection alias to the source database. The The ggadminm is the connection alias to the mining database. If the PDB name on the source and mining database are different. You need to use the source PDB name when registering the extract. In the extract parameter file, you can see the SOURCECATALOG parameter uses the CRM, which is the source PDB name.
Resources
- Oracle GoldenGate Best Practices: Configuring Downstream Integrated Extract ( Doc ID 1485620.1 )