Shulou(Shulou.com)06/01 Report--

User creation:

Today to create an Oracle user, and then found that sql does not remember, and then can only look for information, found that this efficiency is not very high, so record as a blog, if necessary, copy directly from the blog.

The following is my simple arrangement, you can refer to if you need it.

-create tablespace

CREATE TABLESPACE WORKFLOW01 LOGGING DATAFILE'D:\ oracle\ admin\ oa\ WORKFLOW01.dbf'SIZE 100m AUTOEXTEND ON NEXT 32m MAXSIZE 500m EXTENT MANAGEMENT LOCAL

-create temporary tablespace

Create temporary tablespace TEMP11 tempfile'D:\ oracle\ admin\ oa\ TEMP11.dbf'size 100m autoextend on next 32m maxsize 500m extent management local

-create a user

CREATE USER t_base IDENTIFIED BY t_base DEFAULT TABLESPACE WORKFLOW01 TEMPORARY TABLESPACE TEMP11

-user authorization

Grant connect,resource,dba to tasking Baseport grant create session to t_base

-Delete tablespace

Drop tablespace WORKFLOW01 including contents and datafiles cascade constraints

-Delete user information

Drop user t_base cascade

Oracle Authorization Table permissions to the user:

Syntax: grant [permission name (select | insert | update | delete | all)] on [table name] to [user name]

Example: give user1 authorization to query table1 permissions: grant select on table1 to user1

However, the above is a bit troublesome. If there are many tables, you may be able to experiment with cursors. If the user table permissions are not very strict, you can authorize users to query the table permissions of all users: grant select any table to gd_user with admin option.

However, when querying, you still need to add a user name to query, for example: select * from user.table1

The above is the way to assign permissions with sql, and you can also authorize them through roles. First, give permissions to roles, and then assign roles to users.

Oracle main system roles:

DBA: has all privileges, is the highest privilege of the system, and only DBA can create the database structure. RESOURCE: users with Resource permissions can only create entities, not database structures. CONNECT: users with Connect permission can only log in to Oracle, cannot create entities, and cannot create database structures. Ordinary users: connect, resource permissions are generally granted. DBA administrative user: grant connect,resource, dba permissions.

Sometimes you can directly authorize Oracle's system roles, or you can create your own roles and then authorize them.

Set up through PLSQL

Summary

The above is the whole content of this article. I hope the content of this article has a certain reference and learning value for everyone's study or work. Thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.