Solving the OSB 12c Oracle data source installation error for OCI

In the realm of data management and infrastructure, technical difficulties may often arise, one of which is an error message during the installation of a data source in Oracle Service Bus (OSB) 12c to an Oracle Database in Oracle Cloud Infrastructure (OCI).

The specific error in question reads: "weblogic.application.ModuleException:oracle.security.crypto.asn1.ASN1FormatException: Length is too big: takes 68 bytes" This blog post addresses this error with a six-step solution that worked in our case.

Solution

The process begins with a pre-requisite: ensuring you have the correct connection information for Database in the Domain_Credentials.properties file is crucial. Once this is guaranteed, the following steps could potentially help resolve the error.

1.

Download the appropriate Wallet for the correct environment. Example names for the different environments: Wallet_Test, Wallet_Prod

2.

Upload the Wallet to all nodes in your environment at their path, which could look like: /u01/app/oracle/product/fmw/wallets

3.
Two files need to be updated. The first file is sqlnet.ora:

Change the DIRECTORY to point to the correct Wallet folder. For example, for Wallet_Test, it would be: DIRECTORY="/u01/app/oracle/product/fmw/wallets/Wallet_Test"

Change SSL_SERVER_DN_MATCH from SSL_SERVER_DN_MATCH=no to SSL_SERVER_DN_MATCH=yes

4.

The next file to modify is tnsnames.ora:

Replace ssl_server_dn_match=no in security with the certificate's information. Example: Replace: (security=(ssl_server_dn_match=no)) To: (security=(ssl_server_cert_dn="CN=adwc.eucom-central-1.oraclecloud.com,O=Oracle Corporation,L=Redwood City,ST=California,C=US"))

5.

Run the script to install the data source or do it manually, depending on your preference.

6.

If you encounter errors, try rebooting the Admin and Managed servers.

Conclusion

By following these steps, you can address the ModuleException during the installation of a data source in OSB 12c to Oracle Database in OCI. Keep in mind that this is a technical solution that worked in our specific case. Different scenarios might require different solutions. In all cases, always ensure the integrity and security of your data and systems while attempting fixes.