Good morning,
While installing a database for Oracle Entreprise Manager Cloud Control (OEMCC) I can't login as sysdba, neither localy using sqlplus SYS@MYSID as sysdba
nor remotely using the OEMCC installer :
[oracle@myserver ~]$ sqlplus SYS@MYSID as sysdba SQL*Plus: Release 12.2.0.1.0 Production on Wed May 29 10:14:28 2019 Copyright (c) 1982, 2016, Oracle. All rights reserved. Enter password: ERROR: ORA-01017: invalid username/password; logon denied
I did some research :
Here : “ORA-01017: invalid username/password” while connecting to an instance remotely as sysdba
On oracle support : Troubleshooting ORA-1031 or ORA-1017 Errors When Connecting As SYSDBA (Doc ID 730067.1)
It seems to be a different case :
- Localy I can connect using the system user (not as sysdba) :
sqlplus system@MYSID
then enter password, it works. So tnsnames.ora is correct. (Either localy and remotely) - The password file is correctly created, using :
${ORACLE_HOME}/bin/orapwd file=${ORACLE_HOME}/dbs/orapwmysid password="*********" force=y
(just to be sure I connected usingsqlplus / as sysdba
then didalter user sys identified by "*********" account unlock;
) - The parameter
remote_login_passwordfile
is set toEXCLUSIVE
:
SQL> show parameter remote_login_passwordfile; NAME TYPE VALUE ------------------------- ------ --------- remote_login_passwordfile string EXCLUSIVE
- The orapw file rights are correct :
[oracle@myserver ~]$ ls -l $ORACLE_HOME/dbs/orapwmysid -rw-r-----. 1 oracle dba 6144 May 29 10:14 /opt/oracle/product/12.2.0/dbhome_1/dbs/orapwmysid
- Remote login using system works :
[oracle@anotherserver ~]$ sqlplus system@MYSID SQL*Plus: Release 12.2.0.1.0 Production on Wed May 29 13:18:52 2019 Copyright (c) 1982, 2016, Oracle. All rights reserved. Enter password: Last Successful login time: Tue May 28 2019 15:41:20 +02:00 Connected to: Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production SQL>
Do you have an idea, something I could investigate ?
Best Answer
Filenames (and Oracle instance names) on Linux are case sensitive. You keep using
MYSID
but you created the password file asorapwmysid
.MYSID
as a TNS alias is not case sensitive.MYSID
as an instance name is case sensitive and having the password file named lowercase will prevent logging in using SYS with the above error.Even if you change the SYS password with
ALTER USER...
, the password file will not be generated correctly in this case: