oracle实用笔记（国外英文资料）.docVIP

oracle实用笔记（国外英文资料） User management: Sys user: the sys program stores the base table and the dynamic view of the data dictionary, which has a dba database administrator, sysdba system administrator, sysoper system operator, These roles also have the authority to have these roles, which is the most privileged of sysdba, which is a lot more than sysoper to create a delete database that can be fully and partially restored Sysoper can only recover fully. The dba authority is the smallest of the three that does not have the permission to turn off the data You can only log in as sysdba or sysoper, and you cant log in as normal. System user: storing the secondary data, having the dba, the sysdba role, can log in as normal Authorization (system authority, object permissions), if you want to allow the user to continue to assign permissions to the user to add ... Grant connect (dba, resource) to user name with admin option Grant select (insert, update, all...) The on table name is to the user name (which is logged in to the user with another user) with grant option Connect: alter session, create clustr, database link, session, table, view, sequence Dba: has all the system permissions and the with admin option Resource: create cluster, indextype, table, sequence, type, procedure, trigger, unlimit database Object permissions: select, update, insert, delete, all, create index... Roles: connect, dba, resource (which can be built in the table space) Recover the permissions Revoke authority on table name from user System authority does not cascade collection, object authority will cascade recovery The custom roles Create role name not identified; The create role role name identified by the user name; The role is removed from the role in the custom role and the appropriate permissions are removed The relationship between the user and the schema: the schema is the same as the user name, and oracle manages the data object as a schema Create a user The create user user name identif