Oracle Foundation Rights Management

I. Classification of database permissions

A permission is a user's right to have execution on a feature. In Oracle, permissions are divided into system permissions and object permissions.

1. System permissions

The system specifies the user's permission to use the database. For example, create a table space, create a table, and delete a table right. These all belong to system permissions.

2. Object permissions

Access to a table or view of another user by a privileged user.

Ii. Delegation of authority

Oracle has two ways to authorize users:

1, the administrator directly to the user to grant permissions.

2. The administrator grants permissions to the role and then grants the role to one or more users.

Since the use of roles can be more convenient and funny to manage permissions, it is generally recommended to take this approach to authorization.

Third, the role

Many roles are pre-defined in Oracle.

　　 DBA: Has full privileges, is the highest system privilege, and only the DBA can create the database structure. RESOURCE: A user with RESOURCE permission can only create entities and cannot create a database structure. Connect: A user with connect permission can only log on to Oracle, not create an entity, and cannot create a database structure. For normal users: Grant Connect, Resource role.
For DBA administration users: Grant Connect,resource, DBA role.iv. Authorization Syntax:GRANT Permissions | Role to User name example:

GRANT  to Shop_user     -- grant the Connect,resource role to the user Shop_user

Multiple permissions are used, separated.

v. Revocation of authorization:REVOKE Permissions | Role from user name example:　　

REVOKE  from Shop_user           -- cancel shop_user  connect permission, will not log in to the database

Oracle Foundation Rights Management