The DBA 2.0 era and Oracle revolution

Link: http://www.eygle.com/archives/2008/12/dba20_oem_grid_control.html

These days, kamus and Piner respectively wrote some OEM articles.
Kamus discusses the application of OEM in the tax industry, and Piner discusses database optimization in the 9i era.

AboutThe topic of DBA 2.0 is actually the constant revolution that Oracle has promoted in the post 9i era, and one of the main tools for change is the brand new OEM (GRID/Database Control ). So I try to make a final summary of this topic..

Since we started the discussion on DBA 2.0, how can we define where DBA 2.0 started?

It is widely believed that,DBAs 2.0 started in the era of Oracle Database 10 Gb. Due to the introduction of a large number of new features, DBAs have undergone qualitative changes..
For example, the introduction of ASM makes DBAs have to be more deeply involved in storage management and maintenance; the introduction of clusterware makes DBAs have to understand and maintain the cluster software.
If Oracle's OEL (Oracle Enterprise Linux) and the recently released exadata and HP Oracle
Database machine, now the host, operating system, and OS all need an Oracle DBA for in-depth intervention and management.
In traditional databases, automatic database management and self-maintenance are constantly improving. Grid Control/Database
Control can help us better monitor and manage databases, AWR (automatic workload information library) makes information collection automated, ADDM (automatic database diagnosis and monitoring program) makes the number
The database can perform automatic performance analysis and diagnosis based on AWR and other information. SQL advisor, SPM (SQL plan
Management) can help us make SQL adjustments and suggestions ....

To sum up,In the traditional database layer, Oracle is constantly strengthening automated management, improving database self-management, and reducing user intervention and workload. In addition to databases, Oracle is more backend, DBAs need to constantly expand to the system, storage, and even network fields. At the front-end, DBAs need to constantly expand to the application layer..

Therefore, the Mission of DBA 2.0 can be summarized as follows:In addition to constantly improving database management, it is extended to a broader system level, including applications
Such as application, system, storage, network, and architecture.
Provide more far-reaching architecture and decision-making support to promote enterprises' development towards a more comprehensive and reasonable sustainable IT architecture.

The "constantly improving database management" mentioned here is actually for DBA
An in-depth requirement of 2.0. If you want to extend to a broader field, you must be able to handle database management. The term proactive I mentioned earlier is the core requirement,
Only by proactively and proactively maintaining and managing databases can we eliminate many faults and improve database management.

Since DBA
2.0 means more extensive intervention and more in-depth knowledge, so Oracle is constantly strengthening its own products to reduce the complexity of DBA work and enhance database stability and reliability.
In fact, through continuous acquisition and long-term layout, Oracle has built a full range of DBA auxiliary tools and products with database as the core.

For example, I learned aboutReal user experience insight
Product, a software used to comprehensively monitor actual user activities, to ensure
The application performance can reach the expected level; analyze and notify when the expected level is not reached, and provide the software that the user should take relevant measures. Is its schematic, from page
When a request is sent to the request, the responses of all processes are recorded for warning and evaluation:

Sender oblog

This is the first time I have learned about Oracle's application monitoring software. In fact, it is moving forward at the front-end and application layer. This is one of Oracle's scaling strategies.

As I mentioned earlierOracle Enterprise Manager (the new version of Grid Control/Database Control) is a huge enhancement at the database level. Oracle continues to strengthen its product capabilities at the database level..
It is the top-down Application Management of Oracle in all stages from development to product (from the official Oracle demonstration document). The database-level diagnostic and
Tuning products, provisioning, configuration management and other products are all enhancements from OEM products.

Sender oblog

Oracle also has many new products in the application testing stage on the right, including real application testing (which is an oracle
The functions of database 11g are also integrated in Oracle 10.2.0.4 and later versions.
Masking is also the latest component included in the OEM.
Data Masking I just learned that this component can convert production data to protect the original sensitive information during data cloning, however, the data integrity can still be maintained for real application testing. This is indeed a good function and component.
At the 2008 Beijing Oracle Developer Conference held a few days ago, I also learned that TimesTen is now packaged into database products, oracle in-memory database cache can now be sold as a component of the database.

In the DBA 2.0 era, we hope that we will not face the previous situations:
The database suddenly slowed down, and customer complaints continued. DBAs continued to fight the rising flames like firefighters ....

In the DBA 2.0 era, we hope to anticipate system changes and eliminate and invisible problems.. This requires us to have a full grasp of the database running status.
As a DBA, I keep emphasizing the "full database information management" Mode in my team, that is, to fully understand the database operation status, for example, concurrency, load summary, logical read, and physical read changes
With comprehensive understanding of this information and timely monitoring, you can understand database changes and predict and solve possible performance problems as soon as possible.
In this regard, historical data collection and recording of AWR have helped me a lot. OEM diagnostics and SQL capture facilitate system tuning, oracle is also constantly solving problems for us in the 2.0 direction.

In the era of DBA 2.0, Oracle has been changing very fast as ever. It must be learned to keep up with the requirements of Oracle and the times!

In my initial article, I once mentioned the GRID/database control tool, which is a browser-based database management, maintenance, and monitoring tool introduced at the 10gb of Oracle Database, it is a new stage in the development of Oracle Enterprise Manager.
I don't know what kind of considerations oracle is based on and discussions began to abolish/discard the Oracle database
Client OEM tools developed in the 9i era based on Java (this story may be very interesting behind the scenes) may adapt to the trend of B/S, and may be the trend of the times. But in short, grid
/The emergence of Database Control makes people shine (it also makes many third-party database management tool manufacturers feel pressure ).
New OEM functions are becoming more and more powerful, and the scope of application is becoming wider and wider,Oracle intends to gradually evolve OEM into a comprehensive system management, maintenance and monitoring tool, covering not only databases, but also systems, networks, storage and other aspects..
In the recent 11g OEM process, we found that the host information and monitoring are increasingly improved, such as monitoring load, Io and other information:

Sender oblog

In grid control, more extensive information will be monitored and collected, such as application response and processing time. Through further drill-down and analysis, you can analyze and interpret performance issues at different levels:

Sender oblog

Although OEM cannot solve all our problems, it can be our good assistant in daily work.
I used a lot of space in my step-by-step Oracle to introduce the use of the new version of OEM.Through comprehensive monitoring and deployment, OEMs can automate the work that previously required a lot of manual processing. In the past, many script-writing and processing work was required. Now, OEMs can automatically complete the work with built-in functions, what I want to say is that this enhancement has common value for DBAs.
For example, in monitoring, we can define various metric conditions and trigger an alarm when a specific threshold is reached:

Sender oblog

Of course, we also need to configure Some SMTP and mail settings. If there is an alarm in the database, we can receive an alarm email in our mailbox. Below are some mail examples, when an error occurs in the warning log or the set space usage reaches, the automatic mail alarm is sent.

The enhancement of common functions is a very important part of OEM, because this enhancement can simplify the work that DBAs generally need to do and improve user efficiency..
Of course, OEM may be of limited help to many senior DBAs, but if 90% of Oracle database applications can use OEM as the management and monitoring of databases, the database management and maintenance efficiency will be greatly improved. As I mentioned here, 90% of enterprises may not have full-time DBAs at all, so OEM will be a very important boost.
Many OEM features can significantly reduce the workload of senior DBAs. I think among the many OEM pack packages, the most valuable to DBAs are the following:
1. Diagnostic pack
The diagnosis package uses the built-in self-diagnosis engine of the database to locate the performance bottleneck of the system and provides corresponding optimization suggestions.
2. tuning pack
The adjustment package automatically optimizes the specified SQL to meet the system performance requirements. Which SQL statements need to be optimized can be automatically captured from the current system by setting performance targets.

In OEMs, DBAs can easily capture and analyze performance issues through these two toolkit, and can refer to database suggestions for improvement! Capture problematic SQL using OEM (note:
Purpose: do not pay attention to the problem only when the problem occurs. daily attention and monitoring of the database is particularly important. Only by comprehensively tracking the database can DBAs be more predictable) and diagnosis becomes very fast and
Simple, these changes can even make people with only a preliminary understanding of the database very professional in solving database problems:

Sender oblog

However, the work that can be completed quickly in the OEM may lead to a lot of technical personnel who do not know much about the database in the past! We can say exactly that Oracle
The enhancement of OEM is also the enhancement of GRID/Database Control, which makes traditional database management easier and further promotes the change of database management!

Website related articles | related articles

DBAs 1.0 and DBAs 2.0

Dba2.0 era-Where will DBA go?

It168 & itpub University activity: I can also be a DBA

How to quickly become a qualified Oracle DBA?

DBA police record: accidental deletion of incorrect career operations

Today in history...

>

2006-12-21Article: Early-year-olds

>

2005-12-21Article: Internet make us closer to be loved -- by Jane

>

2004-12-21Article: Upgrade mt to version 3.1.4

Oracle's difficulty in integrating Renke