"System as SysDba" password

Quote:

---

Originally Posted by dhar_kiran

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.

it is most likely because he is a priveleged os user, where you can type anything and get in as sysdba

Quote:

---

Originally Posted by davey23uk

how can you say that when you dont know what OS they are on? NTS is a windows only thing.

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.
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.