We have noticed failure when MDM is configured using Oracle Database 12c Release 2 as the database with the below exception:
test_datasource:
Running ODBC SQL statement [select 1 from dual;]...
Executing <MDM_INSTALL_DIR>/mds/bin/madsql.exe
<MDM_INSTALL_DIR>/mds/scripts../bin/madsql.exe: STATE=HY000, CODE=28040, MSG=[InitiateSystems][ODBC Oracle Wire Protocol driver][Oracle]ORA-28040: No matching authentication protocol
Result: 1
To overcome this exception, perform the below steps on Oracle configuration:
1. Set the value of property SQLNET.ALLOWED_LOGON_VERSION_SERVER to a value below 12 in file sqlnet.ora. The recommended value is 8
2. Restart the Oracle Service corresponding to the database
3. Change the password using the ALTER USER command
The above steps can also be found at SQLNET.ALLOWED_LOGON_VERSION_SERVER
Note: MDM uses ojdbc6.jar for JDBC communication with Oracle during installation, configuration and runtime, hence please ensure that ojdbc6.jar is available at <ORACLE_HOME>/jdbc/lib folder.
test_datasource:
Running ODBC SQL statement [select 1 from dual;]...
Executing <MDM_INSTALL_DIR>/mds/bin/madsql.exe
<MDM_INSTALL_DIR>/mds/scripts../bin/madsql.exe: STATE=HY000, CODE=28040, MSG=[InitiateSystems][ODBC Oracle Wire Protocol driver][Oracle]ORA-28040: No matching authentication protocol
Result: 1
To overcome this exception, perform the below steps on Oracle configuration:
1. Set the value of property SQLNET.ALLOWED_LOGON_VERSION_SERVER to a value below 12 in file sqlnet.ora. The recommended value is 8
2. Restart the Oracle Service corresponding to the database
3. Change the password using the ALTER USER command
The above steps can also be found at SQLNET.ALLOWED_LOGON_VERSION_SERVER
Note: MDM uses ojdbc6.jar for JDBC communication with Oracle during installation, configuration and runtime, hence please ensure that ojdbc6.jar is available at <ORACLE_HOME>/jdbc/lib folder.
No comments:
Post a Comment