Default wallet password for Oracle Golden Gate Microservices

 GoldenGate Microservices Architecture (MA) allows you to configure and manage data replication over homogeneous or heterogeneous database environments using RESTful services. These microservices can be accessed using various interfaces including a web interface, command line interface, REST API, or any other service that allows accessing REST-based microservices.

                        

                   Image Reference:-https://docs.oracle.com/en/middleware/goldengate/core/21.3/coredoc/overview-oracle-goldengate-microservices-architecture.html#GUID-8079B9E7-3925-46AD-9C45-172C5A248798

Now, when we install Oracle Golden Gate microservices from OCI Marketplace, it basically creates default wallet files under /u02/deployment. The two files are ewallet.p12 and cwallet.sso. When we install the GG microservices, it doesn't prompt for any wallet password and thus we can't open the wallet.

To create a secure distribution path, in order to send the redo logs from existing extract to the target(example here-Golden Gate for Big data), the wallet password is required. We can get the password from:-

For the client wallet password, you will find a file init-ogg-deployment.py under /usr/local/bin. The client wallet password is in the file if you have not changed it after the instance is created.

For V19c GG Marketplace Microservices Architecture, that information is in /usr/local/bin/common.py

For V21c GG Marketplace Microservices Architecture, that information is in /usr/local/bin/init-ogg-deployment.py. However, for v21c, you don’t need to manipulate the wallet directly under shell. You can do this from the Service Manager WebUI, which is recommended practice.

Reference:-https://docs.oracle.com/en/middleware/goldengate/core/19.1/oggmp/provisioning-oracle-goldengate-microservices-oci-marketplace.html#GUID-ED0DD115-6AB2-424F-8DE4-7DE145B5992C

The Golden Gate Microservices Upgrade from 19c to 21c using GUI Method

Oracle GoldenGate Microservices Architecture (MA) allows you to configure and manage data replication over homogeneous or heterogeneous database environments using RESTful services. These microservices can be accessed using various interfaces including a web interface, command line interface, REST API, or any other service that allows accessing REST-based microservices.

The first part of any upgrade would be to get the binaries from OTN.

For 21c binaries installation, create the directories as below:-

New ORACLE_HOME=/u01/app/ogg/oracle21

Install using the runInstaller

Before:

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/u01/app/ogg/oracle19/lib

export ORACLE_HOME=/u01/app/ogg/oracle19/

export PATH=$PATH:$ORACLE_HOME/bin

export PATH=$PATH:/bin:$ORACLE_HOME/OPatch

NEW ORACLE_HOME= /u01/app/ogg/oracle21

Note down the extract and replicate trail file numbers and are in sync or not

e.g Extract-trail number- 579, Replicates-trail number-579

Stop the extract and replicate as they are in sync

 Go to the service manager console & check below services

Stop the respective deployments and go to the respective deployments and edit the respective environment variables

Now, do the changes in the Service manager and point it to new Oracle Home.

Do the changes and click apply.

Restart the service manager from service manager console.

If we get the 502 gateway error while accessing the service console page, then bounce the service manager from backend.

export OGG_ETC_HOME=/u02/deployments/ServiceManager/etc

export OGG_VAR_HOME=/u02/deployments/ServiceManager/var

export ORACLE_HOME= /u01/app/ogg/oracle21/

ps -ef|grep Service

Kill all the process from OS

start the service manager

cd $ORACLE_HOME/bin

./ServiceManager

ps -ef|grep Service

Access the service manager console page

Start the respective deployments one by one

Access the admin console page and start the extract & replicate.

References:-https://docs.oracle.com/en/middleware/goldengate/core/21.3/coredoc/overview-oracle-goldengate-microservices-architecture.html#GUID-8079B9E7-3925-46AD-9C45-172C5A248798

https://docs.oracle.com/cd/F44199_01/upgrading/upgrading-oracle-goldengate.pdf

Golden gate Extract is not starting because of ORA-28374: typed master key not found in wallet

We had an issue where all of a sudden after the DB bounce, extract was not coming up with errors ORA-28374: typed master key not found in wallet. This GG environment was acting a downstream mining and redo logs were coming from Source SaaS(Oracle Fusion). The first thing i did, is to go through the alert log. Found the trace file from the alert log and got the below warnings being reported.

kcrf_decrypt_redokey: dumping redo key 1344d0d94ad0a8347de7dda9e709dbff ======>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> DB is looking for this key as per trace file

kcrf_decrypt_redokey: dumping mkloc 1 mkid in log header 2f4219da61094fefbfc613ba4b51407a ======>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> DB is looking for this key as per trace file

kcrf_decrypt_redokey: dumping active kcbtsemkloc 1, kcbtsemkid 8655dd60aa2c4f6ebfd407dbecfd5e5b ======>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> DB is looking for this key as per trace file

Now from the information above, how can we know which keys does the DB is referring to

How we can decrypt it:-

SQL> select utl_raw.cast_to_varchar2( utl_encode.base64_encode('01'||'2f4219da61094fefbfc613ba4b51407a')) from dual;

UTL_RAW.CAST_TO_VARCHAR2(UTL_ENCODE.BASE64_ENCODE('01'||'2F4219DA61094FEFBFC613B

--------------------------------------------------------------------------------

AS9CGdphCU/vv8YTuktRQHo=

Run the below command to check existing keys present in wallet

SQL> select key_id from v$encryption_keys;

KEY_ID

------------------------------------------------------------------------------

ARBCnkv3lU/qv7MNJhC2AeAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

AYZV3WCqLE9uv9QH2+z9XlsAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

Thus, we can see that one key is missing and this is the reason why extract is not coming up. So, we got the keys from Source and imported it to our target database using the below command

ADMINISTER KEY MANAGEMENT IMPORT KEYS WITH SECRET "***" FROM 'path where key file have been placed' FORCE KEYSTORE IDENTIFIED BY "YOUR DB WALLET PASSWORD" with backup;

Upon importing the key to our wallet, we were able to successfully start the extract

Hope it helps someone

Oracle golden gate 19c microservices replication error

 We have a setup of Oracle Golden Gate 19c Microservices with source being Oracle SaaS DB. Thus downstream mining is running in Oracle VM DB system. We receive the redo logs from Source SaaS to our mining Database, where extract process runs. And we have 2 two instance for replication process. Everything was working fine, until the Source SaaS database was refreshed few days back

After the refresh, we had to setup the extract process again using Begin Now parameter and when we tried to start the replication, we got the below errors:-

Oracle GoldenGate Delivery for Oracle, REP33.prm: Error mapping from EKBN_DEV4_US6_GSI_F.FUSION.fnd_wls_active to SBXRPTDB_PDB1.FUSION.fnd_wls_active

We did not see any erros in gg logs and report file logs. So we took the logdump of the trail files and observed that the in the trail files the all the columns are not reported in before and after image.

Thus, we came to conclusion that after the refresh, one of our colleague did not enabled the trandata. Once we enabled the trandata, we were able to start the replicate with the required SCN number.

choose the option "start with options" and then provide the sequence number.

            

       syntax to enable trandata is:-

      ADD SCHEMATRANDATA DB_name.schema

       Hope this helps someone. Keep learning