How to resolve the "ORA-01017 : Invalid Username/Password; Logon denied" error in an Oracle monitor
In Applications Manager, users might encounter the following error while attempting to add or monitor the Oracle database. This error indicates an issue with authentication credentials or other related configuration settings.
To troubleshoot this issue, users must first verify the username, password and SID/Service Name values provided in the Oracle monitor. Try connecting to the Oracle database directly using the same username and password used in Applications Manager to verify.
If the username and password are correct but the
ORA-01017: invalid username/password; logon denied error still occurs, follow the steps below to resolve the issue.Step 1: Verify Case Sensitivity
Begin by checking if case sensitivity is enabled for the Oracle login credentials. To do so, run the following command in the Oracle database:
SQL> SHOW PARAMETER SEC_CASE_SENSITIVE_LOGONA sample output of the query will look like this:
NAME TYPE VALUE
-------------------------------- --------- --------
sec_case_sensitivity_logon boolean TRUE
If the value is set to TRUE, the user has two options:
- Ensure that the password is entered with the correct case. (or)
- Disable case sensitivity for passwords
To disable case sensitivity, use the command given below. Note that in a multitenant architecture, this command should be executed on the container database, affecting all pluggable databases
SQL> ALTER SYSTEM SET SEC_CASE_SENSITIVE_LOGON=FALSE;
In most cases, disabling case sensitivity resolves the issue. If the error persists, check the compatibility mode of the client used to connect.
Step 2: Verify Client Compatibility Mode
If case sensitivity is disabled and the password is correct, a compatibility mismatch between the client and server versions (i.e: Applications Manager and the Oracle Database) could be causing the issue. To resolve this, users need to set the compatibility level in the sqlnet.ora file.
SQLNET.ALLOWED_LOGON_VERSION_SERVER=8 SQLNET.ALLOWED_LOGON_VERSION_CLIENT=8
After modifying and saving the file, restart Oracle listener service. This should allow the user to connect to the corresponding Oracle Database from Applications Manager.
Note: In Oracle versions prior to 11g, the compatibility mode is set using a single parameter.
SQLNET.ALLOWED_LOGON_VERSION=n
This parameter is deprecated from Oracle 12c onward.
New to ADSelfService Plus?
Related Articles
Troubleshooting URL Monitor
Here are few of the common errors you may come across in URL monitor, we have mentioned the steps you can follow to troubleshoot them. General troubleshooting for URL monitor Ensure that the URL is accessible from the server in which Applications ...REST API Monitor - FAQS
1. What should I do when Basic Authentication fails in REST API monitor? Verify if the credentials provided in the Applications Manager are correct. Try if sending username and password in Authorization request header works Get an BASE-64 encoded ...Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check prerequisites to be done Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...While trying to discover Oracle Database server, it fails and prompts some message.
1) Error: Failed. Oracle Server is down. Error Message: IO Error: The Network Adapter could not establish the connection Solution 1: The Oracle server is down, Please ensure whether the server is up and running fine. Solution 2: The Oracle server is ...The Oracle monitor is not working / The Oracle monitor is not collecting any data. What can I do?
Reason 1 - This could be because the Oracle user provided in Applications Manager does not have the necessary permission to run the query Go to <AppManager/logs> directory and check if you have an error print in stderr.txt / stderr.txt.1 / ...