Home » RDBMS Server » Security » ORAPWD Utility
ORAPWD Utility [message #273576] Thu, 11 October 2007 00:25 Go to next message
Messages: 26
Registered: July 2007
Location: Hyderabad
Junior Member

I 've created a user & provided the roles as follow:
Grant connect,resource,sysdba to U10 identified by U10;

And the remote_login_passwordfile parameter value is EXCLUSIVE

I 've executed the following command at
as follows:
orapwd file=orapwpwdorcl.ora password=pass1234 force=y

Select username From v$pwfile_users;

On my client machine
I 've connected using U10 user with following :
u10/u10@orcl as sysdba
sys/anypassword@orcl as sysdba

After this I 've executed as follows:
>Shut Immediate

The DB is shut downed

But what is the usage of "Password" "which is created using ORAPWD" utility..
Without that same password(which is generated using ORAPWD utility..) also am able to connecting the server if I 've specified "as sysdba"

Problem might be what can u please explain..?

Thanks In Advance

Re: ORAPWD Utility [message #273579 is a reply to message #273576] Thu, 11 October 2007 00:31 Go to previous messageGo to next message
Mohammad Taj
Messages: 2412
Registered: September 2006
Location: Dubai, UAE
Senior Member

because database connection made through OS authentication instead of PASSWORD file authentication.
either your member of DBA group or SQLNET.AUTHENTICATION_SERVICES=NTS.

Re: ORAPWD Utility [message #274080 is a reply to message #273576] Sat, 13 October 2007 09:30 Go to previous message
Messages: 1
Registered: September 2006
Junior Member
dba_giri wrote on Thu, 11 October 2007 08:25

On my client machine
I 've connected using U10 user with following :
u10/u10@orcl as sysdba

You're connecting using the password file authentication here.

sys/anypassword@orcl as sysdba

As I assume you're running sqlplus command as the user who created the database.
You're connecting here using the OS authentication here, since the user you created the database with in Windows is added to the ORA_DBA group by default. So any username and password you type followed by "as sysdba" will be ignored and it won't be checked, and you'll be authenticated as the user sys.
You can make sure with this example:
SQL> conn sysys/asasa as sysdba
SQL> show user
SQL> select username From v$pwfile_users; -- You can see here that the user sysys doesn't even exist


Remember that the authentication precedence is as follows:

  1. Operating system authentication.
  2. Password file authentication.
  3. Data dictionary authentication.
Previous Topic: system privilege
Next Topic: ALL_TABLES is showing incorrect information
Goto Forum:

Current Time: Thu Dec 01 08:37:26 CST 2022