- 论坛徽章:
- 0
|
问个关于权限设置方面的问题
我把ROOT加入到DBA中也应该继承到属主的权限吧?? \r\n照着书上说是该这样的\r\nUsing Operating System (OS) Authentication\r\nThis section describes how to authenticate an administrator using the operating system.\r\n\r\nPreparing to Use OS Authentication\r\nTo enable authentication of an administrative user using the operating system you must do the following:\r\n\r\nCreate an operating system account for the user. \r\nAdd the user to the OSDBA or OSOPER operating system defined groups. \r\nEnsure that the initialization parameter, REMOTE_LOGIN_PASSWORDFILE, is set to NONE. This is the default value for this parameter. \r\n************************************************\r\nOSDBA and OSOPER\r\nTwo special operating system groups control database administrator connections when using OS authentication. These groups are generically referred to as OSDBA and OSOPER. The groups are created and assigned specific names as part of the database installation process. The specific names vary depending upon your operating system and are listed in the following table:\r\n\r\nOperating System Group UNIX Windows \r\nOSDBA dba ORA_DBA\r\n OSOPER oper ORA_OPER\r\n \r\n\r\nThe default names assumed by the Oracle Universal Installer can be overridden. How you create the OSDBA and OSOPER groups is operating system specific.\r\n\r\nThe following describes how membership in the OSDBA or OSOPER group affects your connection to Oracle:\r\n\r\nIf you are a member of the OSDBA group, and specify AS SYSDBA when you connect to the database, you are granted the SYSDBA system privilege. \r\nIf you are a member of the OSOPER group, and specify AS SYSOPER when you connect to the database, you are granted the SYSOPER system privilege. \r\nIf you are not a member of the associated operating system group for SYSDBA or SYSOPER system privileges, the CONNECT command fails. |
|