Open the file and check that this information is correct, such as the service name and ID. You could be getting this ORA-01017 error if the information in that file is incorrect. Your TNSNAMES.ORA file contains a list of service ID information for your databases. So, check these things for your database connection string. CONNECT TO order_database IDENTIFIED BY bob USING "DatabaseStar"
To resolve it, put your password inside double quotes. This is then checked against the stored value of DatabaseStar, and is found to be different. This is because the password of DatabaseStar is converted to uppercase, which will be DATABASESTAR. Using the earlier example, if you specify your password in the connection string as DatabaseStar, you’ll get an error. It’s related to the database you’re connecting to, not from. If you’re connecting to an Oracle 11g database but running the query from a 10g or earlier version, the case sensitivity still applies. You can then check the connection string to make sure that the user is correct, and that the password is case sensitive (if you’re using an Oracle 11g database). To check the database link, you can run a simple query against it to see if it works.
If you’re getting this error while running a query, but you’ve already logged in to the database, it might be because your query uses a database link, and the connection details for the database link are incorrect. To resolve this error, specify the password in double quotes: CONN bob/"DatabaseStar" To fix this, you can specify your password inside double quotes when connecting to the database.įor example, if your password is “DatabaseStar”, and you’re connecting to a database like this, you’ll get an error: CONN bob/databasestar It’s a database setting that can be turned on and off, but if it’s on, you’ll need to treat your connection string differently. This was a new feature introduced in Oracle 11g. If you’re connecting to an Oracle 11g database, the passwords are case sensitive. If you have them stored somewhere else, make sure you’re looking up the right password.Īlso, try entering the username and password manually instead of copying and pasting (or vice versa) to make sure there are no issues with carriage returns or strange characters. It seems like an obvious step, but make sure that the username and password you’re entering is correct. Check the database link setup if you’re using a database linkĮnsure that the Username and Password are Correct.Oracle 11g passwords are case sensitive, so ensure that your connection string caters for this.Check the username and password are correct.There are a few ways to resolve the ORA-01017 error: Now, let’s look at the solution to this error. The database configuration is not correct ( tnanames.ora, $ORACLE_SID parameter).Your username or password is actually incorrect.There are a few reasons that you can get this error: ORA-01017: invalid username/password logon denied So you’re trying to connect to a database, or run a query across a database link, and you get this message: Have you gotten an ORA-01017 error in your Oracle database? Learn what caused it and how you can resolve it in this article.