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

Blogger QQ:819594300

Blog address: http://zpf666.blog.51cto.com/

Friends who have any questions can contact the blogger, the blogger will help you answer, thank you for your support!

In addition to command operation, oracle can also be managed graphically by OEM. Daily management can be done through OEM operations, including the creation of database objects, the management of user rights, the configuration of data files and parameters, backup and recovery operations, and so on.

1. OEM knowledge points

1. Introduction to OEM

OEM is a tool set that uses intuitive and convenient graphical interface to control and manage ORACLE database. It contains a large number of useful tools for DBA. In oracle, database management and operations can be done using OEM, such as creating users and roles, permission assignment, creating scheme objects, storage management, and so on.

2. OEM architecture

OEM can manage not only local database instances, but also database instances in network and RAC environments. OEM accesses the database through HTTP/HTTPS, whether it is managing the database locally or on the network. Its architecture is shown below:

1) Management repository: stores the management data and status information of the database to be monitored.

2) OMS management service: monitor and manage the database with management agent installed, and store the management information in management repository.

3) Oracle HTTP Server: built-in apache server.

4) OC4J/J2EE: an application server that conforms to J2EE standards.

5) Oracle web cache: used to quickly access web.

6) Management agent: installed on the managed data server to monitor the running status of the database, resource usage, information changes, etc., transfer the information to OMS,OMS and store the information in repository.

3. Two versions of OEM

There are two different versions of OEM: database control and grid control. Databasecontrol is typically used to monitor and manage a local single database or RAC database. Grid control is used to manage large-scale and complex system environment, it can manage the entire infrastructure, including hosts, databases, web servers, listeners, services and so on.

With databasecontrol, you usually don't have to configure anything, and when you've created the database using DBCA or oracle universal installer, databasecontrol is ready to use. Of course, if you manually created the database through the create database statement, you need to configure database control through EMCA (enterprise manager configurationassistant). Gridcontrol needs to be installed separately from the database, and the installation process and configuration are more complicated.

II. The use of OEM

1. Installation and configuration of OEM

When installing an oracle database through oracle universal install, if you choose to create the database (or create the database directly through DBCA), OEM database control is installed by default. After the database is created, the relevant information of OEM will be displayed, and database control URL is the access address of OEM.

(the above picture refers to the Oracle series of blog posts (1): installation of oracle)

1) use DBCA to configure OEM

DBCA provides a way to create an OEM graphically, starting DBCA first.

In this way, using OEMdatabase control to manage the database is configured, which is very simple and all done visually through DBCA.

1) manually configure using EMCA

If you create the database manually through the createdatabase statement, you need to configure OEM through EMCA. EMCA can set all aspects related to OEM, such as the reconstruction and deletion of repository storage, the creation and deletion of configuration files, and so on. The following are common EMCA commands.

Emca-config dbcontroldb: configure OEM database control.

Emca-deconfig dbcontroldb: delete the OEM database control configuration file.

Emca-repos drop: delete the repository store.

Emca-repos create: create a new repository store.

Emca-repos recreate: rebuilds the repository store.

Let's reconfigure OEM using emca. Execute the emca-config dbcontrol db-reposrecreate command, which configures OEM database control and rebuilds the repository store.

Note: if OEM has not been configured, use the emca-config dbcontrol db-repos create command to configure it.

2. Use EMCTL to control OEM

You must make sure that the dbconsole process is started before using OEM, and oracle provides EMCTL tools to start and shut down the dbconsole process and view its status.

1) View OEM status

By executing the emctl status dbconsole command, you can get whether the OEM is running, the access address of the OEM, and the location of the log. The implementation results are as follows:

2) close OEM

Execute the emctl stop dbconsole command.

3) start OEM

Execute emctl start dbconsole

3. Use OEM to monitor and manage databases

OEM provides very powerful monitoring and management capabilities, and here are a few common operations.

1) use OEM to start and shut down the database

First, make sure that the monitor is running.

2) check the status of OEM

3) access the URL of OEM, and click the "start" button

4) enter the main interface, click "start", enter the following interface, and click "OK" in the upper right corner after filling in.

5) enter the main interface

6) OEM monitoring database running

After OEM starts, you can use OEM to manage, monitor, and maintain the database. First visit OEM. And log in using a SYS or SYSTEM account.

There are two roles for OEM users: administrator privileges and non-administrator privileges. Administrators have high privileges, such as monitoring, modifying settings, database audit, upgrade, backup and recovery, etc. Non-administrator permissions can only view information and cannot modify any settings. After logging in, you can see the main interface of OEM, which is divided into seven function tags for users to choose from, namely, home directory, performance, availability, server, scheme, data mobility, software and support. Their functions are described below.

7) Home directory

The home directory section presents the overall state of the database instance, which is presented graphically, while more specific metrics and contents can be obtained by clicking the corresponding content. For example, to get the details of CPU, click the underlined data under the CPU diagram. Other situations are similar, as shown in the following figure:

Click the listener in the image above and pop up the interface below

8) performance

The performance part mainly provides host monitoring, user connection monitoring and iCompo performance, as well as other related connection options to assist in judgment.

Host monitoring: monitor whether there is a cpu bottleneck. It shows the curve of cpu utilization and clearly shows the level of cpu utilization in different periods. If you find that cpu usage is extremely high in a certain period of time, and there have been performance problems, such as the end user reporting that the application system is slow, then you need to analyze the user session to see which sql is consuming cpu resources.

Average active session monitoring: this is a key part of analyzing performance issues, showing which events the session is waiting for during a certain period of time in the instance, and which sessions are waiting for those events, which are represented in different colors.

Clicking the "duplicate sql" connection in the above figure will display the sql with a large number of repetitions in the instance. It is recommended that developers use parameter binding to modify these sql to improve cpu utilization.

9) availability

The availability section focuses on the setup and management of backup and recovery, which will be backed up using OEM below.

Click "backup Settings" in the above figure to go to the backup Settings page

Fill in the host × × × Ming, user name oracle, password: xxx, disk backup location is the default, parallelism is 1, and finally click "Test disk backup". If it is successful, the setting is complete, otherwise re-fill it according to the prompts.

Then click the backup set tab in the above figure, as shown in the following figure:

Fill in the size of the backup slice, compress the algorithm, and click the OK button to complete the setting. Click the Policy tab to set the backup policy, retention policy, and other policies, which are the default settings here.

Click OK after setting up

After the backup settings are completed, you need to schedule the backup settings (click "schedule backup" in the following figure)

Fill in the correct × × Ming, and click the "schedule Custom backup" button.

Set the scheduling frequency, select once (immediately), and click next.

Review the previous settings and confirm that they are correct, then click submit Job

After scheduling the backup successfully, you can click the "manage current backup" connection in the following figure to manage the backup

10) Server

The server part includes storage, database configuration, scheduling, statistics, resources, security, query optimization and change data management functions, as shown in the following figure:

Here is a common management function: user management

The first step to create a user is to create a tablespace for the user. As shown in the following figure, the interface presents some key metrics of the tablespace in the form of a list, such as allocated size, used space, whether to automatically expand, and free allocated space. Create a tablespace MDR below.

Click OK in the lower right corner, the tablespace has been created, now create the user, and first enter the user management interface, as shown in the following figure:

Click the create button in the image above and enter the relevant information, as shown in the following figure.

Then click roles, assign roles to the user, and click Edit list

Then click OK to create the user.

11) Plan

The solution part mainly includes the management of database objects, programs, materialized views, word change management, user-defined types, XML database, workspace manager and text manager, as shown in the following figure:

The most frequently used is the "table" management, here is a new table for MDR users.

Click create in the figure above.

12) data movement

The data movement part includes mobile row data, mobile data files, flow management and advanced replication functions, as shown in the following figure:

Next, use the export function of mobile row data to export the MDR scheme, and click "Export to Export File" in the figure above.

But the prompt cannot log in in the role of sysdba, so I will change it to the system user login operation here.

The image above is available by default.

After confirming the correctness, submit the homework.

The location of the exported file is the location of the data_pupm_dir directory, which can be queried through select * from dba_directories.

13) Software and support

The software and support section provides a wealth of software management content, including software configuration management, patch management, real application testing and deployment process manager.

Configuration management: host configuration, status information and resource utilization information.

Patch management: you can view the current patch recommendations, the prerequisites for installing the patch, and applying the patch.

Real application testing: includes database replay and sql performance analyzer.

Deployment process Manager: manages currently deployed processes, including editing, viewing, running, and monitoring deployed processes.

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.