support/notes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

2026-05-03 08:47:40

Browse Source
This commit is contained in:
Valeriu PLESNILA
2026-05-03 10:47:40 +02:00
parent dea8469842
commit f06028c7e0
1 changed files with 21 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Golden_Gate/setup.md
+21 -8
View File
@@ -7,7 +7,7 @@ http://blog.data-alchemy.org/posts/oracle-goldengate-pluggable/
Databases: Databases:
- source: CDB: `NABOOPRD@togoria, PDB: EREP` - source: CDB: `NABOOPRD@togoria, PDB: EREP`
- target: CDB: `GENOSISPRD@wayland, PDB: GERISS` - target: CDB: `GENOSISPRD@wayland, PDB: GERISS
## Databases setup for Golden Gate ## Databases setup for Golden Gate
@@ -46,6 +46,14 @@ Create schemas for replicated tables on source and target PDB:
grant connect,resource to C3PO; grant connect,resource to C3PO;
connect C3PO/"Secret00!"@wayland/GERISS; connect C3PO/"Secret00!"@wayland/GERISS;
For both Golden Gate hosts (`exegol` and `helska`) `depl26ai` the password of Service Manager administrator has been defined:
- username: `oggadmin`
- password: `Alabalaportocala00_`
and `depl26ai` deployement has been created.
> Both username/password are case sensitive.
## Setup `exegol` Golden Gate deployment ## Setup `exegol` Golden Gate deployment
> My Root CA (added to truststore host) has not be recognized by `admincmient` resulting OGG-12982 error while `curl` works perfectly. > My Root CA (added to truststore host) has not be recognized by `admincmient` resulting OGG-12982 error while `curl` works perfectly.
@@ -57,19 +65,18 @@ Solution: define `OGG_CLIENT_TLS_CAPATH` environement variable to my root CA cer
Add in the credentialstore enteries for database connections: Add in the credentialstore enteries for database connections:
adminclient adminclient
connect https://exegol.swgalaxy:2000 deployment ogg_exegol_deploy as OGGADMIN password "Secret00!" connect https://exegol.swgalaxy:2000 deployment depl26ai as oggadmin password "Alabalaportocala00_"
Optionaly store credentials to connect to deployement: Optionaly store credentials to connect to deployement:
add credentials admin user OGGADMIN password "Secret00!" add credentials admin user oggadmin password "Alabalaportocala00_"
Now we can hide the password when conecting to deployement: Now we can hide the password when conecting to deployement:
connect https://exegol.swgalaxy:2000 deployment ogg_exegol_deploy as admin connect https://exegol.swgalaxy:2000 deployment depl26ai as admin
Add in the credentialstore enteries for database connections: Add in the credentialstore enteries for database connections:
create wallet
add credentialstore add credentialstore
alter credentialstore add user c##oggadmin@togoria/NABOOPRD password "Secret00!" alias NABOOPRD alter credentialstore add user c##oggadmin@togoria/NABOOPRD password "Secret00!" alias NABOOPRD
alter credentialstore add user c##oggadmin@togoria/EREP password "Secret00!" alias EREP alter credentialstore add user c##oggadmin@togoria/EREP password "Secret00!" alias EREP
@@ -86,6 +93,12 @@ To delete a user from credential store:
> IMPORTANT: in a database **MULTITENANT** architecture, Golden Gate is working at `CDB$ROOT` level. > IMPORTANT: in a database **MULTITENANT** architecture, Golden Gate is working at `CDB$ROOT` level.
In an Oracle Multitenant architecture (Oracle 19c through 23c), the placement of the Oracle GoldenGate checkpoint table depends on whether you are configuring the Extract (source) or the Replicat (target):
1. Target Side (Replicat): Inside the PDB
2. Source Side (Extract): Root Container (CDB$ROOT)
> Integrated Extracts store their recovery checkpoints primarily in the database's internal logmining server metadata and in .cpe checkpoint files on the GoldenGate file system. You do not manually create a standard "checkpoint table" for an Extract in the same way you do for a Replicat
Create the checkpoint table: Create the checkpoint table:
dblogin useridalias NABOOPRD dblogin useridalias NABOOPRD
@@ -104,15 +117,15 @@ Put:
## Setup `helska` Golden Gate deployment ## Setup `helska` Golden Gate deployment
adminclient adminclient
connect https://helska.swgalaxy:2000 deployment ogg_helska_deploy as OGGADMIN password "Secret00!" connect https://helska.swgalaxy:2000 deployment depl26ai as oggadmin password "Alabalaportocala00_"
Optionaly store credentials to connect to deployement: Optionaly store credentials to connect to deployement:
add credentials admin user OGGADMIN password "Secret00!" add credentials admin user oggadmin password "Alabalaportocala00_"
Now we can hide the password when conecting to deployement: Now we can hide the password when conecting to deployement:
connect https://helska.swgalaxy:2000 deployment ogg_helska_deploy as admin connect https://helska.swgalaxy:2000 deployment depl26ai as admin
Add in the credentialstore enteries for database connections: Add in the credentialstore enteries for database connections: