Hi all
If you try
sqlplus "system as sysdaba"
system asks for the password.
whatever password you type Oracle allows you to log in
Why ?????
Printable View
Hi all
If you try
sqlplus "system as sysdaba"
system asks for the password.
whatever password you type Oracle allows you to log in
Why ?????
try this,
/ as sysdba
it will log u on the database
When you connect as SYSDBA privilege, you are connecting as SYS schema and not the schema associated with your username. And the schema SYS will accept any password if your OS username, through which you are logged into the machine, belongs to DBA(unix) or ORA_DBA(windows) group on the machine where Oracle database is installed.Quote:
Originally Posted by gsmathew
HTH
Hi
To enable authentication of an administrative user using password file authentication you must do the following:
Create an operating system account for the user.
If not already created, Create the password file using the ORAPWD utility:
ORAPWD FILE=filename PASSWORD=password ENTRIES=max_users
Set the REMOTE_LOGIN_PASSWORDFILE initialization parameter to EXCLUSIVE.
Connect to the database as user SYS (or as another user with the administrative privilege).
If the user does not already exist in the database, create the user. Grant the SYSDBA or SYSOPER system privilege to the user:
GRANT SYSDBA to scott;
This statement adds the user to the password file, thereby enabling connection AS SYSDBA.
Regards,
Sasikumar
the password file has NOTHING to do with the issue hereQuote:
Originally Posted by sasikumar
Do we need we need to recreate the instance for changing the password of sys on Windows OS; is it true?
If no, how can we change?
Obviously it's false
Just alter user sys identified by whatever
Yes ur right, then what about ORAPWD which we use on UNIX systems??
Thanks to this forum, am really learning alot here than in any institutes
orapwd is used just to create password files to support remote sysdba/sysoper logins, everytime you change your sysdba passwords look how the modification date in the password file changes
When u connect through system, u connect as public schema.
Now the reason behind allowing system to connect while entering wrong password is that
1. u are using OS authentication.(u can check it from SQLNET.ora file...
SQLNET.AUTHENTICATION_SERVICES= (NTS))
and there is no password file created.
Possible Solutions are:
1. Make SQLNET.AUTHENTICATION_SERVICES= (NONE)
or
2. Create a password file.
how can you say that when you dont know what OS they are on? NTS is a windows only thing.Quote:
Originally Posted by dhar_kiran
it is most likely because he is a priveleged os user, where you can type anything and get in as sysdba
we can use sqlnet.authentication=(NTS) in windows.Quote:
Originally Posted by davey23uk
yes u are right. it is a privileged user and the authetication it is using is OS authentication, and for OS authentication one of the options we use is sqlnet.authentication=(NTS) in windows or that user should be a member of ORADBA on windows and DBA in unix group and REMOTE_LOGIN_PASSWORDFILE=none if passwordfile is used.