OGG DB2 i: After Goldengate Upgrade Encryption Method Not Working?
(Doc ID 2887819.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle GoldenGate - Version 19.1.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
User recently upgraded Goldengate for DB2 i from version 12.3.0.1 to 19.1.0.0
After upgrade extract was not starting up , while investigating they found the dblogin is failing :
> dblogin SOURCEDB DBNAME USERID XXXXX, PASSWORD AACAAAAAAAAAAAIATEJCHBUEAHOBXDOC ENCRYPTKEY KEYNAME
ERROR: Error (-12) decrypting string: .
The dblogin was only working while explicitly we are using the encryption method as BLOWFISH :
> dblogin SOURCEDB DBNAME USERID XXXXX, PASSWORD AACAAAAAAAAAAAIATEJCHBUEAHOBXDOC, BLOWFISH ENCRYPTKEY KEYNAME
2022-05-27 14:01:29 INFO OGG-03036 Database character set identified as UTF-8. Locale: en_GB.
2022-05-27 14:01:29 INFO OGG-03037 Session character set identified as UTF-8.
Successfully logged into database.
But BLOWFISH is not approved encryption method in the organization.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |