Hi everybody !
Does anybody can explain me how does the remote_login_passwordfile parameter work exactly ?
Here is the problem :
On one NT server, with 8.1.7 Oracle release, I would like to create a new database :
- I've created a new init.ora file (with remote_login_passwordfile to EXCLUSIVE),
- I've created the Oracle Service and the password file (with ORADIM),
- I lauched server manager and connect internal to startup nomount the instance and then execute the create database statement.
What I'm wondering, is how Oracle knows that we need a password for internal (which is in the password file because the remote_login_passwordfile is set to EXCLUSIVE) when we are connected if the init.ora file is not opened yet (we have just launched svrmgrl) .....
The init.ora is read as soon as you start your database.
I think you are getting confused between the init.ora and the 'mounting' of the control file.
the name of the file parameter "remote_......" suggests this is only for remote connections
or connections through listener if on the same box.
so if u want to connect from remote machine as sys or internal or system, and want to use
password file authentication, this is useful.
OR if u need to start the database with a OS user which is not part of DBA group u can use
connect internal/password as sysdba and start the database.
I'm agree with you.
But if the database is closed and I want to startup it from a client side with Server Manager. I do the following :
1 : on the client side, execute svrmgrl.exe
2 : connect internal/password@my_instance
3 : startup the database.
But how does the connect phase (phase 2) know about the remote_login_passwordfile value when the database is not opened yet ! How does Oracle know that the password reside is the password file ?
Again, you are confused over the init.ora file.
It is read when you issue your connect / as sysdba
It is not mounted like the control file.
The database is closed.
I've renamed the init.ora file.
I've initialized the oracle_sid with the instance name.
I've started svrmgrl.
I'va tried to connect with internal : it was succeful !
So the init.ora file is not read when you just connect internal ...
If Oracle kernel finds that there is password file
for the SID (note password file name is a standard with SID name in it)
It shall allow remote connection with internal and if the privileges are there
for internal, it shall connect.
u already moved init.ora , create another password file for the same instance with different password
, move this new file to some other name, copy back the old password file and now try to connect.
Click Here to Expand Forum to Full Width