The introduction
role is a command set of related permissions. The main purpose of using roles is to simplify the management of permissions. It is assumed that there are users a, b, and c in order to allow them to have the following permissions
1) Connect to the database
2 ) If the direct authorization operation is used for select, insert, and update on the scott.emp table, 12 authorizations are required. Therefore, at this time, a role is established to have these permissions, and then all these users have this role, so that they can be granted All have those permissions, and only authorized 3 times. Roles are divided into two types: predefined roles and custom roles : 1. Predefined roles: Predefined roles refer to the roles provided by oracle. Each role is used to perform some specific management tasks. Below we introduce the commonly used predefined roles Role connect, resource, dba
1) connect role
The connect role has most of the permissions required by general application developers. When a user is established, in most cases, it is enough to grant the connect and resource roles to the user. What system permissions does the connect role have?
alter session //modify session
create cluster //create cluster
create database link //create database connection
create session //create session
create table //create table
create view //create view
create sequence //create sequence
2) resource role
resource role Has other permissions required by application developers, such as creating stored procedures, triggers, etc. It should be noted here that the resource role implies unlimited tablespace system permissions.
The resource role includes the following system permissions:
create cluster //create cluster
create indextype
create table //create table
create sequence //create sequence
create type
create procedure
create trigger
3) dba role
The dba role has all system permissions and with admin option , the default dba users are sys and system, they can grant any system permissions to other users, but it should be noted that the dba user does not have the privileges of sysdba and sysoper (start and close the database)