1.NONE
Setting this parameter to NONE causes Oracle to behave as if the password file does not exist. That is, no privileged connections are allowed over non-secure connections. NONE is the default value for this parameter.
EXCLUSIVE
An EXCLUSIVE password file can be used with only one database. Only an EXCLUSIVE file can contain the names of users other than SYS. Using an EXCLUSIVE password file allows you to grant SYSDBA and SYSOPER system privileges to individual users and have them connect as themselves.
SHARED
A SHARED password file can be used by multiple databases. However, the only user recognized by a SHARED password file is SYS. You cannot add users to a SHARED password file. All users needing SYSDBA or SYSOPER system privileges must connect using the same name, SYS, and password. This option is useful if you have a single DBA administering multiple databases.
2.grant sysdba (sysoper) to Hr(user name)
but must exclusive3.
if 9i "connect / as sysdba " can connect database as sysdba ,OS authentication
if only "connect sys/sys's password as sysdba" can connect database as sysdba,password file authenticationthat is all!
Setting this parameter to NONE causes Oracle to behave as if the password file does not exist. That is, no privileged connections are allowed over non-secure connections. NONE is the default value for this parameter.
EXCLUSIVE
An EXCLUSIVE password file can be used with only one database. Only an EXCLUSIVE file can contain the names of users other than SYS. Using an EXCLUSIVE password file allows you to grant SYSDBA and SYSOPER system privileges to individual users and have them connect as themselves.
SHARED
A SHARED password file can be used by multiple databases. However, the only user recognized by a SHARED password file is SYS. You cannot add users to a SHARED password file. All users needing SYSDBA or SYSOPER system privileges must connect using the same name, SYS, and password. This option is useful if you have a single DBA administering multiple databases.
2.grant sysdba (sysoper) to Hr(user name)
but must exclusive3.
if 9i "connect / as sysdba " can connect database as sysdba ,OS authentication
if only "connect sys/sys's password as sysdba" can connect database as sysdba,password file authenticationthat is all!
解决方案 »
- 修改oracle字段数据类型
- oracle 从unix上备份 在window下恢复
- Oracle行转列的问题。急求解答
- 求租 一个连续日期多记录的报表sql!
- ora-12500 : TNS:监听程序无法启动专用服务器进程
- 一个简单的问题:请问在Linux中如何停止和启动Oracle HTTP Server???
- 分区表的导入导出!
- ORACLE的异常处理为啥不执行
- oracle 11g impdp 导入 错误ORA-39126,ORA-31603
- oracle ORA-01033
- 关闭数据库shutdown normal和shutdown immediate有什么区别?
- oracle里面的MICROSOFTDTPROPERTIES表是干什么用的?
Setting this parameter to NONE causes Oracle to behave as if the password file does not exist. That is, no privileged connections are allowed over non-secure connections. NONE is the default value for this parameter.Does this mean this authentication is same with OS authentication ?
3.
if 9i "connect / as sysdba " can connect database as sysdba ,OS authentication
if only "connect sys/sys's password as sysdba" can connect database as sysdba,password file authenticationIf I login the system with administrator account, any of "connect / as sysdba", "connect hr/hr as sysdba", "connect scott/tiger as sysdba" can connect database as sysdba.
If I login the system with another account, only "connect sys/change_on_install as sysdba" can connect database as sysdba. The results likeSQL> connect scott/tiger as sysdba;
Not logged on
SQL> connect system/manager as sysdba;
Not logged on
SQL> connect sys/change_on_install as sysdba;
Connected to Oracle9i Enterprise Edition Release 9.0.1.1.1
Connected as SYSIs this right?
OS authentication is not care of username and password,so ……