"Go" uses Navicat for Oracle to create new tablespace, user, and permissions to assign

First, let's create a new table space. Open Navicat for Oracle and enter the relevant connection information. Such as:

Fill in the correct information, after the connection. We click on the "Table space" option under "Other" on the panel, such as:

Into the table space interface, we can go through the panel of "new table space", or by the right mouse button in the space, new table space, such as:

In the Popup interface, we enter the name of the table space we need to store in Oracle on the physical disk, as well as the initial size and unit of the table space. In the path option, fill in the Physical disk path where the tablespace resides. "On" in the auto-expand option allows you to expand the table space yourself. If "Off" is selected, the tablespace is fixed size and is not allowed to be extended. Specific examples, such as:

The following is the SQL language that creates the tablespace:

After filling out the rest of the information, we simply click on the "Save" button. The system pops up an interface that lets us fill in the name of this tablespace, such as:

After the new build, we can look at the disk in the House to see if there are table space files, such as:

When the table space is new, we're going to create a new user. Click the "User" option on the panel, such as:

There are two ways to create a new user, one is the new User button on the Control Panel, and the other is to empty the right key, such as. After clicking on "New User", the screen pops up and fills in the relevant information. Such as:

One of the things we need to be aware of is that the username must be capitalized in the user name. keep in mind that it must be capitalized, and if it is lowercase, the user cannot connect to the Oracle database. specifically why this, I think this may be a bug in this software. In "Default Tablespace", we select our new table space in front of the science department. If we do not choose, the system default Tablespace users will be used.

In member of, we have selected DBA permission. In fact, for the general user, we only need to give connect, resource, create view these permissions can be. But here we choose "DBA" for the convenience of demonstration. For a few permissions on Connect, resource, create view, it is visible:

Once the above operation is complete, we can switch to the SQL Preview option to view the relevant SQL statements, such as:

Once the user is established, we can use this database. Let's start with the test, whether the user can connect to the Oracle database properly.

Through, it is obvious to see that we have just created a new user to connect to the database is normal.

However, the database is established correctly and cannot be used more than normal. This requires a practical validation of the project.

Ok, I have a project on the OA system on hand now. Now let's import the database with the relevant import statements as follows:

Imp ilanni/[email protected]:/xe fromuser=jy touser=ilanni file=d:\jy.dmp buffer=102400

Open "Start"-"Run"-CDM, then paste the statement in.

Once the operation is complete, we can start the system. The specific boot method in the compression package has the relevant instructions. How is the interface after normal startup:

This is the prompt to enter the system normally.

"Go" uses Navicat for Oracle to create new tablespace, user, and permissions to assign