Configure Oracle GoldenGate Deployments
After you install Oracle GoldenGate Microservices, configure the deployment to connect to the source application database and communicate with the target environment. The tasks in this section create the required credentials, configure change data capture, create extract processes, and configure trail file distribution.
Create Database Credentials
Create credentials that Oracle GoldenGate uses to connect to the source application database. For more information, see Add Database Credentials to Connect to the Source Database.
Use the following recommended values when you create the database credentials.
| Credential Setting | Recommended Values |
|---|---|
|
Credential Domain |
OUDI_GG_SRC |
|
Credential Alias |
OUDI_SRC_C2M |
|
User ID |
C##GGADMIN@db_hostname:1521/CDB_NAME |
|
Password |
<Database PASSWORD for C##GGADMIN> |
|
Verify Password |
<Database PASSWORD for C##GGADMIN> |
Create Database Operator Credentials
Create operator credentials that Oracle GoldenGate uses to connect to the target Oracle GoldenGate environment. For more information, see Credential Store Tasks.
Use the following recommended values when you create the operator credentials.
| Credential Setting | Recommended Values |
|---|---|
|
Credential Domain |
OUDI_GG_CONN |
|
Credential Alias |
OUDI_GG_OPT |
|
User ID |
<TARGET OPERATOR USER> |
|
Password |
<TARGET OPERATOR USER PASSWORD> |
|
Verify Password |
<TARGET OPERATOR USER PASSWORD> |
Add TRANDATA Information
Add TRANDATA information so that Oracle GoldenGate can capture CDC information from the source application database. For more information, see Add TRANDATA, Heartbeat, and Checkpoint Tables.
Use the following values:
-
Table name: CISADM
-
Scheduling columns: No
-
All columns: No
-
Prepare CSN mode: None
If the Add TRANDATA Information in the Background? option is available, ensure that the option is set to Off.
Create an Extract Process
Create an extract process using the parameter file received from OUDI team. Use the Oracle GoldenGate documentation for detailed extract creation procedures.
To create the extract, see Add a Primary Extract.
To get started, see Step 3: Add an Extract.
Naming Conventions
Use the following naming conventions when you create Oracle GoldenGate connection aliases, extract processes, trail files, and trail subdirectories for each source application.
| Source Application | Connection Alias | Extract Process | Trail Name | Trail Subdirectory |
|---|---|---|---|---|
|
Customer Cloud Service (CCS) |
EW_SRC_CCS_1 EW_SRC_CCS_* |
CCS_EX1A CCS_EX2A CCS_EX** |
CA CB C* |
CCS1 CCS* |
|
Customer Care and Billing Cloud Service (CCBCS) |
EW_SRC_CCBCS_1 EW_SRC_CCBCS_* |
CCB_EX1A CCBC_EX** |
BA BB B* |
CCBCS1 CCBCS* |
|
Digital Assets Cloud Service (DACS) |
EW_SRC_WACS_1 EW_SRC_WACS_* |
DAC_EX1A DAC_EX2A DAC_EX** |
DA DB D* |
DACS1 DACS* |
|
Meter Solution Cloud Service (MSCS) |
EW_SRC_MSCS_1 EW_SRC_MSCS_* |
MSC_EX1A MSC_EX** |
MA MB M* |
MSCS1 MSCS* |
|
Work and Asset Cloud Service (WACS) |
EW_SRC_WACS_1 EW_SRC_WACS_* |
WAC_EX1A WAC_EX2A WAC_EX** |
WA WB W* |
WACS1 WACS* |
Required Extract Process Settings
Use the following settings when you create an extract process. These settings define the extract process configuration, database connectivity, trail file configuration, and restart behavior.
| Category | Setting | Value |
|---|---|---|
|
General |
Process Name |
<NAME UNDER 8 CHARS> |
|
General |
Description |
<Description of the extract process> |
|
General |
Intent |
High Availability |
|
General |
Begin |
Now |
|
Trail Configuration |
Trail Name |
Use the value defined in the naming conventions table. |
|
Credentials |
Credential Domain |
<Database credential domain created in the 'Create Database Credentials' step> |
|
Credentials |
Credential Alias |
<Database credential alias created in the 'Create Database Credentials' step> |
|
Exadata Configuration |
Register to PDBs |
(For Exadata and on-premises only) If the source environment uses Exadata, select the PDB name Register to PDBs: that appears after you select the database credentials. |
|
Managed Options |
Profile Name |
Custom |
|
Auto Restart |
Max retries |
9 |
|
Auto Restart |
Retry delay |
2 minutes |
|
Auto Restart |
Retries window |
5 minutes |
|
Auto Restart |
Restart on failure only |
Selected |
Update the Extract Parameter File
After you create the extract process, update the extract parameter file with the OUDI-specific configuration.
-
Open the extract parameter file.
-
Add the following parameter immediately before the
EXTTRAILparameter:ENCRYPTTRAIL AES256 -
Open the
EXTRACT_PARAMETER.prmfile provided by the OUDI team. -
Copy the contents of the OUDI parameter file into the extract parameter file.
-
If the source database uses a pluggable database (PDB), update the
SOURCECATALOGparameter to specify the source PDB name. Example:SOURCECATALOG <PDB_NAME> -
Save the parameter file.
-
Click on Create and Run to create and start the extract.
Example Extract Parameter File
EXTRACT CCS_EX1A
USERIDALIAS EW_SRC_CCS_1 DOMAIN EW_GG_SRC
ENCRYPTTRAIL AES256 <--- ADD this parameter to encrypt the trail
EXTTRAIL CCS1/CA
<CONTENT of PARAMETER FILE>
Configure Distribution Paths
Configure a distribution path to transfer trail files securely from the source environment to the target environment. For more information, see Add a Distribution Path.
Use the following settings when you create a distribution path. These settings define source and target connectivity, authentication, trail file configuration, encryption, and restart behavior.
| Setting | Value |
|---|---|
|
Reverse proxy enabled |
Cleared |
|
Source |
Select the extract process and specify the trail name. |
|
Target authentication method |
UserID Alias |
|
Target |
Enter the target connection details. |
|
Protocol |
WSS |
|
Target host |
|
|
Target port |
443 |
|
Trail subdirectory |
Leave blank |
|
Trail name |
Use the same value as the extract trail. |
|
Credential domain |
|
|
Credential alias |
|
|
Target encryption algorithm |
AES256 |
|
Configure trail format |
Leave blank. |
|
Enable network compression |
Leave blank. |
|
Trail size (MB) |
500 MB |
|
Begin |
Position in Log |
|
Source sequence number |
0 |
|
Source RBA offset |
0 |
|
Auto restart |
On |
|
Critical |
Off |
|
Retry count |
10 |
|
Retry delay |
2 minutes |
After you configure the distribution path settings, create the distribution path and start the path.
Create a Master key
Create a master key to encrypt Oracle GoldenGate trail files and credential information.
For more information, see the Oracle GoldenGate documentation:
-
Using the UI: Add a master key in the deployment console
After you create the master key wallet, upload the wallet file to object storage.
Example wallet location:
/<DEPLOYMENT_FOLDER>/var/lib/wallet/cwallet.sso
Monitor Oracle GoldenGate
Monitor Oracle GoldenGate extract processes and distribution paths continuously. Ensure that the processes remain operational and process data without interruption.
Oracle GoldenGate extract processes depend on archived redo logs to capture historical transactions. Archive log retention affects how far back an extract process can recover after an outage. If archive logs are removed before an extract process restarts, Oracle GoldenGate might not be able to recover all missed transactions.
For example, if archive logs are retained for 7 days, an extract process must restart within that 7-day period to recover missed transactions. Transactions older than the archive log retention period might not be available for recovery.