Troubleshooting
Problem
During the initial post-installation configuration of InfoSphere MDM deployments with an Oracle 12cR2 database, the Configure_MasterDataManagement madconfig target can fail due to an incorrect default database protocol version.
Symptom
This issue results in the following error message in the madconfig logs for both the Configure_MasterDataManagement target and the test_datasource target:
- MSG=[InitiateSystems][ODBC Oracle Wire Protocol driver][Oracle]ORA-28040: No matching authentication protocol
Cause
In Oracle 12cR2, the default protocol version has changed to 12.
Environment
Oracle 12c R2
Diagnosing The Problem
This message is shown in the madconfig logs either when the test_datasource target or the Configure_MasterDataManagement target is run. The result is a failure in the target execution.
Resolving The Problem
To resolve this issue:
-
- Edit the sqlnet.ora file to change the value for the default protocol value to be 11 or lower. For example: SQLNET.ALLOWED_LOGON_VERSION_SERVER= 8 sqlnet.ora location = <ORACLE_HOME>/network/admin/
- Restart the Oracle services identified by OracleService<DB_NAME>.
- Update the Oracle schema password to a new value using the following sqlplus command: ALTER USER <USER_NAME> IDENTIFIED BY <NEW_PASSWORD>;
- Edit the sib.properties file and add the below entry
- sib.msgstore.jdbcPerformColumnChecks=false
sib.properties location = <WAS_HOME>/properties/
If you wish to take advantage of Oracle 12 Authentication, please review this document.
[{"Product":{"code":"SSWSR9","label":"IBM InfoSphere Master Data Management"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"11.5;11.6;11.6.0.1;11.6.0.2;11.6.0.3;11.6.0.4","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Was this topic helpful?
Document Information
Modified date:
27 April 2022
UID
swg22009929