In 11g – Passwords are case
sensitive but this can be controlled by an init.ora parameter -
SQL> show parameter
SEC_CASE_SENSITIVE_LOGON ;
NAME TYPE VALUE
———————————— ———– ——————————
sec_case_sensitive_logon boolean TRUE
———————————— ———– ——————————
sec_case_sensitive_logon boolean TRUE
SQL> create user arjun identified
by ARJUN; – Password in Upper Case.
User created.
SQL> grant create session to
arjun;
Grant succeeded.
SQL> conn arjun/arjun; – Tried to
connect with lower case password – FAILS.
ERROR:
ORA-01017: invalid username/password; logon denied
ERROR:
ORA-01017: invalid username/password; logon denied
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 – 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 – 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> conn arjun/ARJUN – CONNECTS
–
Connected.
SQL>exit
Connected.
SQL>exit
Sqlplus “sys as sysdba”
? drop user arjun cascade;
Now alter the parameter to FALSE –
so case sensitive passwords are not required.
SQL> alter system set sec_case_sensitive_logon=false;
System altered.
SQL> create user arjun identified
by ARJUN;
User created.
SQL> grant create session to
arjun;
Grant succeeded.
SQL> conn arjun/arjun; – Connects
with lower case password although password at time of creation was in UPPER case.
No comments:
Post a Comment