Oracle database--creation and management of users and solutions

I. Related content

1. Master the basic concepts of user, program and authority.

2. Master the command of user operation.

Second, the specific operation

(a) Select the title:

1. Description of the programme which one of the following is incorrect? C

A. Objects such as tables or indexes must belong to a particular scenario

B. In the Oracle database, the scenario is one by one corresponding to the database user

C. A table can belong to multiple scenarios

D. A scenario can have multiple tables

2. Which of the following objects belong to the schema object? C

A. Data segment

B. Disk Area

C. Table

D. Table Space

3. Which of the following commands is used to connect to an Oracle database? B

A.create

B.connect

C.alter

D.select

(b) Brief answer:

1. Briefly describe the relationship between the programme and the user?

A: Oracle users, in layman's words, are "people" who access the Oracle database. Each user has a password and the appropriate permissions. A scenario is a collection of logical data structures or objects that can be understood as namespaces or packages. A scheme can only be owned by a database user, and the name of the scheme is the same as the name of the user, and when a new user is created, the system automatically creates a schema for that user. The schema object created by the user is saved in its own schema by default.

2. What is the purpose of the various options in the Create user command? What is necessary?

A: The various options in the CREATE User command are as follows:

(1) CREATE User Username---username

(2) identified by password---password

(3) [default tablespace tablespace]---The default tablespace, where the user-created object is stored by default.

(4) [temporary tablespace tablespace]---The default temporary tablespace used by the user

(5) [QUOTA [integer k[m]][unlimited] on tablespace_name---the user allows the use of k[m] bytes in the tablespace

(6) [PROFILES profile_name]---the name of the profile. Restrict the resources that users are able to use.

(7) [PASSWORD EXPIRE]---immediately set the password to an expired state, the user must change the password before logging in.

(8) [Account Lock or UNLOCK]---whether the user is locked out.

Among them, (1) CREATE USER username and (2) identified by password are required and the remainder are optional.

(c) Operation questions:

1. Create the user ora_temp, the password is TEM.

Use system/orcl1234 to connect to Sql*plus first, create a user using the following statement

2. Change the user ora_temp password to ora.

3. User Ora_temp account lock.

4. Unlock the user ora_temp account.

5. Grant the user Ora_temp permission to establish a session (create session).

6. Connect to the database using Ora_temp identity.

7. Disconnect the Ora_temp user and connect to the database using the system identity.

8. Delete the ora_temp user.

9. Use the OEM tool to unlock the built-in user account Scott and view all the tables for the Scott user scenario.

(1) Enter the URL address in the browser: http://localhost:1158/em Enter the OEM login interface

(2) in the "admin" interface to find "user", click Open User

(3) After entering "user", select "Scott" user

(4) Edit "Scott" user information, the status is "unlocked", and then click "Apply" to save.

(5) on the "Administration" tab, click on "Table", click on the option, select "Scott"

(6) Select "Scott",

(7) View all the tables of the Scott user scenario

Oracle database--creation and management of users and solutions