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