SQL> alter user system password expire container=all SQL> alter session set container=CDB$ROOT Įxpire SYSTEM's password for all containers. SQL> alter user hr identified by account unlock įor users like SYS or SYSTEM, it's a little bit complicated.įirst, go to the root container. Provide a new password for the user, an uppercase password is preferable for old clients. SQL> alter session set container=ORCLPDB1 You should expire user's password who is using old Oracle client. This is because the password of the PDB users must be expired before applying new logon protocol. Connect to Oracle 19cĪfter you set SQLNET.ALLOWED_LOGON_VERSION=8 in your 12c, 18c or 19c database server to overcome ORA-28040 for your users who may be using old releases like Oracle 9i clients, users still have a great chance to see ORA-01017, even though you use correct username / password to login. Normally, you don't have to care about case-sensitive problem on username, because username creation follows Oracle object naming rule that I have explained about the differences between quoted and non-quoted identifiers pretty much. Set SEC_CASE_SENSITIVE_LOGON to FALSE if the problem is becoming global.Change the password if there's no other way to solve it.Type the password in a text editor to make sure it's right.Check whether CAPS LOCK is enabled or not, this could ruin every password you typed.SQL> alter user hr identified by altered.īeside case-sensitive and special character problems, you can try the following things. If your password contains any special character, you have to double-quote it. That is, you have to use it case-sensitively. SQL> conn invalid username/password logon deniedĪs you can see, IDENTIFIED BY clause treats password as a case-sensitive string with or without quotation marks. SQL> conn alter user hr identified by HR By default, SEC_CASE_SENSITIVE_LOGON initialization parameter is set as TRUE which means that everything involves password are all case-sensitive, even though you didn't quote the password. Most password problem are case-sensitive problem. C:\Users\edchen>tnsping orclĪttempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = db.)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = ORCL))) So please check the connect identifier, and you can make some tests if necessary. Sometimes, your credentials are correct, you just went for the wrong destination. There're several errors patterns that throw ORA-01017.įor solving ORA-01017, you should inspect the following items carefully. SQL> conn invalid username/password logon denied ORA-01017 means that you either provided an incorrect pair of username and password, or mismatched authentication protocol, so the database that you tried to connect denied you to logon.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |