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

OEM Profile

OEM is an intuitive and convenient graphical interface to control and manage the ORACLE database toolset, it contains a large number of tools useful to DBAs. In Oracle, database management and operations can be done using OEM, such as creating users and roles, assigning permissions, creating schema objects, and managing storage.

OEM Architecture

OEMs can manage database instances not only locally, but also in network and RAC environments. Whether managing a database locally or on the network, OEMs access the database via HTTP/HTTPS, and its architecture is as follows:

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

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

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

4)OC4J/J2EE: J2EE compliant application server.

5)Oracle web cache: for fast access to the web.

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

3. Two versions of OEM

OEM has two different versions: database control and grid control. Database control is typically used to monitor and manage a local single database or RAC database. Grid control is used to manage large-scale, complex system environments, which can manage the entire infrastructure including hosts, databases, web servers, listeners, services, etc.

For database control, usually nothing is configured, and database control is ready to use once the database has been created using DBCA or oracle universal installer. Of course, if you create a database manually, you need to configure the database control via EMCA (enterprise manager configuration assistant). Grid control needs to be installed separately from the database, and the installation process and configuration are more complicated.

OEM use

1. OEM installation and configuration

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

1) Configure OEM with DBCA

DBCA provides a graphical way to create OEMs, starting with DBCA.

In this way, the configuration of the database is completed using OEM database control, which is very simple and is all done visually through DBCA.

2) Manual configuration using EMCA

If you create the database manually with the create database statement, you need to configure the OEM through EMCA. EMCA can set OEM-related aspects such as repository repository rebuild and delete, profile creation and delete, etc. The following are common EMCA commands.

emca -config dbcontrol db: Configure OEM database control.

Emca -deconfig dbcontrol db: Delete the OEM database control configuration file.

Emca -pos drop: Delete the repository repository.

Emca -repos create: Create a new repository.

Emca -pos rebuild: rebuild the repository repository.

Use emca to reconfigure OEM below. Execute the emca-config dbcontrol db-pos rebuild command, which configures OEM database control and rebuilds the repository store.

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

2. Use EMCTL to control OEM

Before using OEM, you must ensure that the dbconsole process is started. Oracle provides EMCTL tools to start and stop dbconsole processes and view their status.

1) View OEM status

Execute emctl status dbconsole command to get whether OEM is running, OEM access address and log storage location. The results are as follows:

2) Close OEM

Execute the emctl stop dbconsole command.

3) Start OEM

Execute emctl start dbconsole

3. Use OEM monitoring and management database

OEMs provide very powerful monitoring and management capabilities, and here are a few common operations.

1) Start and close database using OEM

First make sure the monitor is running

2) View OEM status

3) Visit the OEM URL and click the Start button

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

5) Enter the main interface

6) OEM monitoring database operation

Once the OEM is up, you can use the OEM to manage, monitor, and maintain the database. Visit OEM first. and log in using SYS or SYSTEM accounts.

OEM users have two roles: administrator and non-administrator. Administrators have high privileges such as monitoring, modifying settings, auditing databases, upgrading, and backup recovery. Non-administrator privileges can only view information and cannot modify any settings. After logging in, you can see the OEM's main interface, which is divided into 7 functional tabs for users to choose from: Home Directory, Performance, Availability, Server, Solution, Data Movement, Software and Support. Their functions are described below.

7) Main directory

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

Click the monitor program in the above picture to pop up the following interface

8) Performance

The performance section provides host monitoring, user connection monitoring, and i/o performance, as well as other related connection options to assist in judgment.

Host monitoring: monitors cpu bottlenecks. It presents a graph of cpu usage, clearly showing how cpu usage varies over time. If CPU usage is found to be extremely high for a certain period of time and performance issues have occurred, such as end users reporting slow application systems, then it is necessary to analyze user sessions to see which SQL is consuming CPU resources.

Average Active Session Monitoring: This is a key part of analyzing performance issues, showing which events sessions are waiting for in an instance over a certain period of time and which sessions are waiting for those events, with events colored differently.

Click the "duplicate sql" connection in the above figure to display sql with a large number of duplicates in the instance. It is recommended that developers use parameter binding to modify these sqls 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 picture to enter the backup settings page

Fill in host ××× Ming, user name oracle, password xxx, disk backup location by default, parallelism is 1, and finally click "Test disk backup." If successful, the setting is completed, otherwise fill in again according to the prompt.

Then click the Backup Sets tab in the image above, as shown in the following:

Fill in the backup slice size, compression algorithm, click "OK" button to complete the settings. Click the Policies tab to set backup policies, retention policies, and other policies, which are the default settings.

Click OK after setting

Schedule backup settings are required after backup settings are completed (click Schedule Backup in the figure below)

Fill in the correct ××× and click the Schedule Custom Backup button

Set scheduling frequency, check "Once (immediately)" and click Next.

Review the previous settings and click Submit Job when you are sure they are correct

After the backup is scheduled successfully, click the Manage Current Backup connection in the figure below 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:

The following describes a common management function: user management

To create a user, first create a table space for the user, as shown in the figure below. This interface presents some key indicators of the table space in the form of a list, such as allocated size, used space, whether to automatically expand, and free allocated space. Next, create a table space MDR.

Click OK in the lower right corner to complete the creation of the table space. Now, create the user. First, enter the user management interface, as shown in the following figure:

Click on the "Create" button in the image above and enter the relevant information, as shown in the image below.

Then click Roles to assign roles to users, click Edit List

Then click OK to create the user.

11. Programmes

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:

Table management is most frequently used. Below is a new table for MDR users.

。

Click Create in the image above.

。

。

12) Data movement

Data movement includes moving row data, moving data files, stream management and advanced copy functions.

Next, export MDR scheme by using the export function of moving row data. Click Export to Export File in the above figure.

But the prompt cannot log in as sysdba, so I replace it here with system user login operation.

。

。

。

。

。

The above figure can be used by default

。

。

After confirmation, submit the assignment.

The export file location is where the data_puppy_dir directory is located, which can be queried by selecting * 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 current patch recommendations, prerequisites for installing patches, and application patches.

Real application testing: Includes database replay and sql performance analysis programs.

Deployment Process Manager: Manage 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.