1700: Could not connect with username/password ‘abc/pqr@database’ (‘ORA-28040: Message 28040 not found; product=RDBMS; facility=ORA’) error is specific to Oracle Workflow when you try to connect Workflow builder client to remote Oracle Database.
Why this error is coming?
That is what we are going to brainstorm in this article.
What is 1700: Could not connect with username/password and solution?
The latest version of the Oracle Workflow Builder client is 2.6.3.0.1. This still uses Oracle client version 9 to connect to remote Oracle Database Server. Whereas the current database version is 21c at the time of writing this article.
Oracle did changes to restricts the client version which can connect to the remote Oracle Database from version 12C onward.
Below are the parameters in the sqlnet.ora file that controls which version of the client is allowed to connect to the database.
As per the Database Net Services Reference document,
- SQLNET.ALLOWED_LOGON_VERSION_SERVER – To set the minimum authentication protocol allowed when connecting to Oracle Database instances.
- SQLNET.ALLOWED_LOGON_VERSION_CLIENT – To set the minimum authentication protocol allowed for clients, and when a server is acting as a client, such as connecting over a database link, when connecting to Oracle Database instances.
When Oracle Workflow tries to connect the database using client 9, the remote server rejects the connection as the client version is not allowed to connect.
Set up the SQLNET.ALLOWED_LOGON_VERSION_SERVER and SQLNET.ALLOWED_LOGON_VERSION_CLIENT parameter value to 8 in sqlnet.ora file in the remote server to resolve ‘ORA-28040: Message 28040 not found; product=RDBMS; facility=ORA’ error as shown below.
SQLNET.ALLOWED_LOGON_VERSION_SERVER=8 SQLNET.ALLOWED_LOGON_VERSION_CLIENT=8
This says that even clients with version 8 are also allowed to connect to the database.
This may not work if your remote server is on the cloud database(OCI). In that case, add or update the same entry in the sqlnet_ifile.ora file.
Note:- Make sure to restart the listener after changing the parameters.
I hope this small tip helped you solve the connection issue. Please share and subscribe.
You can also refer to the Metalink notes give below in the reference section for additional information.
Reference
- Workflow Builder 2.6.3.0.1 Fails To Connect To 12c Database With ORA-28040: Message 28040 not found (Doc ID 2049667.1)
- How to Allow Login to Database Based on the Client Version (Doc ID 402193.1)
- Database Net Services Reference
