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!
解决方案 »
- MDF文件如何导入到oracle数据库?
- 今天面试题,项目中,怎么处理sql效率问题??
- 求助该如何写这个期初至今累计的语句?
- oracle的clob对象查询起来好慢啊,有什么方法可以解决吗?
- 求教一个查询语句
- 关于PRO*C获取索引名的问题,急!!!在线等待!
- 函数转换
- 分析一下这个ORA-01747: invalid user.table.column, table.column, or column specification
- navicat 链接oracle的问题
- 存储过程编码找出物料编码为“1”或“5”开头的物料对应的成本对象/产品为“8”或字母开头的成品关系;一共需出具2014-2017年4年对应清单
- 关闭数据库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 ……