Re: password files

First question:
The password file used depends on which instance is started. e.g. startup pfile=initPROD.ora or initTEST.ora

Second question:
exclusive settings requires a dedicated server configuration. meaning a single instance is connecting to the database. In this case, you grant SYSDBA to multiple users. Remember, SYSDBA is automatically granted to both the
SYS and INTERNAL users.

SHARED settings assumes that multiple instances will be accessing a single database. In this case, SYSDBA can only be used by SYS and INTERNAL users. You cannot grant SYSDBA to other users.

hope that helps
wozi_at_dhc.net

Jonathan Gennick wrote in message
<3742c5b9.4262128_at_netnews.worldnet.att.net>...
>I've been researching the use of Oracle password files, and
>I have a question about the REMOTE_LOGIN_PASSWORDFILE=SHARED
>setting. Actually, I have several questions. In what
>scenario would you use it? Since the SID name forms part of
>the password file name (e.g. orapwPROD), how do you get
>multiple databases to point to just one password file.
>Presumably, if I have two databases named TEST and PROD,
>they will look for two password files named orapwTEST and
>orapwPROD. How then do you "share" a file?
>
>My last question involves remote authentication. When I use
>the exclusive setting, I can connect to a database as
>INTERNAL from a client PC. However, when I use the shared
>setting, I can't. Why is that? What does the use of shared
>buy you.
>
>I'm sure there is some scenario that I'm not thinking of
>where shared makes sense. Can anyone enlighten me on this?
>
>Jonathan
>
>Jonathan Gennick
>mailto:jonathan_at_gennick.com
>http://gennick.com
>Brighten the Corner Where You Are
>
Received on Thu May 20 1999 - 05:06:39 CDT