Logging into Oracle Database using OraLogon functionality fails in Silk Performer 18.0
There is a known issue within Silk Performer 18.0 when upon the Oracle Database server, the sqlnet.ora file contains the following parameter and value:
The SQLNET.ALLOWED_LOGON_VERSION_SERVER variable represents the minimum authentication protocol allowed when connecting to the Oracle Database.
The value 12, means that "only clients which have applied critical patch update CPUOct2012 or later, or release 126.96.36.199 clients with an equivalent update can connect to the server".
We have seen with the value set to 12, the attempt to establish a connection with the server during replay fails when using the OraLogon functionality in the .bdf script.
If the value for the SQLNET.ALLOWED_LOGON_VERSION_SERVER variable is to 11, the connection is established, however there maybe security concerns why this value cannot be set.
A workaround to the problem would be to replace the Ora.bdh functionality in the script with the Ora8.bdh functionality, i.e. as opposed to OraLogon(), include Ora8Logon().
The connection problems when using the OraLogon functionality will be addressed in a future Silk Performer release.