Oracle 11g数据库性能调优实战指南

需积分: 0 91 浏览量更新于2024-07-28 收藏 31.46MB PDF 举报

《Oracle Database 11g性能调优配方》是一本专门针对Oracle 11g数据库优化的实用指南，它涵盖了多个关键领域，帮助数据库管理员和开发者提升系统的性能和效率。本书旨在提供一系列针对性的“食谱”，解决在实际操作中遇到的各种性能瓶颈问题。第1章“优化表性能”着重于数据库设计前期对表性能的影响因素，包括物理存储特性。这包括选择合适的存储结构（如B树、哈希索引等）、行式和列式存储以及数据块大小，这些都是影响查询速度的关键要素。第2章“选择和优化索引”是提高查询速度的重要环节，作者讲解了如何根据数据访问模式和查询需求来创建和调整索引，以减少全表扫描，加快数据检索速度。第3章“优化实例内存”讨论了如何有效利用Oracle Database 11g的SGA（系统全局区）内存，包括共享池、大池、缓冲区缓存等组件的配置，以提高数据的读取和处理能力。第4章“监控系统性能”教导读者如何通过实时监控工具来识别性能瓶颈，了解CPU、I/O、内存使用情况，为后续调优提供数据支持。第5章“最小化系统竞争”关注并发环境下的资源争夺，作者会分享策略来避免锁定冲突，提升并发事务处理效率。第6章“分析操作系统性能”强调了操作系统与数据库交互的重要性，讲解如何通过操作系统级别的调优来优化数据库运行环境。第7章“数据库故障排查”介绍了在出现问题时的诊断和修复方法，确保数据库稳定运行。第8章至第10章分别深入探讨了编写高效SQL、手动调整SQL语句以及跟踪SQL执行路径的方法，这些都是优化查询性能的基础。第11章“自动化SQL调优”则引入了现代数据库管理工具，如SQL Tuning Advisor，以自动化地检测并优化查询性能。第12章和第13章关注执行计划优化和配置数据库优化器，这是决定查询执行效率的关键步骤，涉及到参数调整和配置设置。第14章“实施查询提示”介绍如何使用特定的SQL指令来影响优化器的行为，以适应特定场景的需求。第15章“并行执行SQL”讨论如何利用多核处理器和分布式环境的优势，实现更高效的并发查询处理。《Oracle Database 11g Performance Tuning Recipes》提供了全面且实用的性能调优策略，无论是初学者还是经验丰富的DBA，都能从中找到适合自己的优化技巧和最佳实践。通过阅读这本书，读者将能够有效地提升Oracle 11g数据库的整体性能，确保系统的高效运行。

CHAPTER 1 ■ OPTIMIZING TABLE PERFORMANCE

We realize that to take advantage of this feature the only “solution” is to upgrade to Oracle Database

11g R2, which is oftentimes not an option. However, we felt it was important to discuss this feature

because you’ll eventually encounter the aforementioned characteristics (when you start using the latest

release of Oracle).

You can disable the deferred segment creation feature by setting the database initialization

parameter DEFERRED_SEGMENT_CREATION to FALSE. The default for this parameter is TRUE.

You can also control the deferred segment creation behavior when you create the table. The CREATE

TABLE statement has two new clauses: SEGMENT CREATION IMMEDIATE and SEGMENT CREATION DEFERRED—for

example:

create table f_regs(

reg_id number

,reg_name varchar2(2000))

segment creation immediate;

■ Note The COMPATIBLE initialization parameter needs to be 11.2.0.0.0 or greater before using the SEGMENT

CREATION DEFERRED clause.

1-6. Maximizing Data Loading Speeds

Problem

You’re loading a large amount of data into a table and want to insert new records as quickly as possible.

Solution

Use a combination of the following two features to maximize the speed of insert statements:

• Set the table’s logging attribute to NOLOGGING; this minimizes the generation redo

for direct path operations (this feature has no effect on regular DML operations).

• Use a direct path loading feature, such as the following:

• INSERT /*+ APPEND */ on queries that use a subquery for determining which

records are inserted

• INSERT /*+ APPEND_VALUES */ on queries that use a VALUES clause

• CREATE TABLE…AS SELECT

Here’s an example to illustrate NOLOGGING and direct path loading. First, run the following query to

verify the logging status of a table. In this example, the table name is F_REGS:

CHAPTER 1 ■ OPTIMIZING TABLE PERFORMANCE

select

table_name

,logging

from user_tables

where table_name = 'F_REGS';

Here is some sample output:

TABLE_NAME LOG

------------------------------ ---

F_REGS YES

The prior output verifies that the table was created with LOGGING enabled (the default). To enable

NOLOGGING, use the ALTER TABLE statement as follows:

SQL> alter table f_regs nologging;

Now that NOLOGGING has been enabled, there should be a minimal amount of redo generated for

direct path operations. The following example uses a direct path INSERT statement to load data into the

table:

insert /*+APPEND */ into f_regs

select * from reg_master;

The prior statement is an efficient method for loading data because direct path operations such as

INSERT /*+APPEND */ combined with NOLOGGING generate a minimal amount of redo.

How It Works

Direct path inserts have two performance advantages over regular insert statements:

• If NOLOGGING is specified, then a minimal amount of redo is generated.

• The buffer cache is bypassed and data is loaded directly into the datafiles. This can

significantly improve the loading performance.

The NOLOGGING feature minimizes the generation of redo for direct path operations only. For direct

path inserts, the NOLOGGING option can significantly increase the loading speed. One perception is that

NOLOGGING eliminates redo generation for the table for all DML operations. That isn’t correct. The

NOLOGGING feature never affects redo generation for regular INSERT, UPDATE, MERGE, and DELETE statements.

One downside to reducing redo generation is that you can’t recover the data created via NOLOGGING

in the event a failure occurs after the data is loaded (and before you back up the table). If you can

tolerate some risk of data loss, then use NOLOGGING but back up the table soon after the data is loaded. If

your data is critical, then don’t use NOLOGGING. If your data can be easily re-created, then NOLOGGING is

desirable when you’re trying to improve performance of large data loads.

What happens if you have a media failure after you’ve populated a table in NOLOGGING mode (and

before you’ve made a backup of the table)? After a restore and recovery operation, it will appear that the

table has been restored:

CHAPTER 1 ■ OPTIMIZING TABLE PERFORMANCE

SQL> desc f_regs;

Name Null? Type

----------------------------------------- -------- ----------------------------

REG_ID NUMBER

REG_NAME VARCHAR2(2000)

However, when executing a query that scans every block in the table, an error is thrown.

SQL> select * from f_regs;

This indicates that there is logical corruption in the datafile:

ORA-01578: ORACLE data block corrupted (file # 10, block # 198)

ORA-01110: data file 10: '/ora01/dbfile/O11R2/users201.dbf'

ORA-26040: Data block was loaded using the NOLOGGING option

As the prior output indicates, the data in the table is unrecoverable. Use NOLOGGING only in situations

where the data isn’t critical or in scenarios where you can back up the data soon after it was created.

■ Tip If you’re using RMAN to back up your database, you can report on unrecoverable datafiles via the REPORT

UNRECOVERABLE command.

There are some quirks of NOLOGGING that need some explanation. You can specify logging

characteristics at the database, tablespace, and object levels. If your database has been enabled to force

logging, then this overrides any NOLOGGING specified for a table. If you specify a logging clause at the

tablespace level, it sets the default logging for any CREATE TABLE statements that don’t explicitly use a

logging clause.

You can verify the logging mode of the database as follows:

SQL> select name, log_mode, force_logging from v$database;

The next statement verifies the logging mode of a tablespace:

SQL> select tablespace_name, logging from dba_tablespaces;

And this example verifies the logging mode of a table:

SQL> select owner, table_name, logging from dba_tables where logging = 'NO';

How do you tell whether Oracle logged redo for an operation? One way is to measure the amount of

redo generated for an operation with logging enabled vs. operating in NOLOGGING mode. If you have a

development environment for testing, you can monitor how often the redo logs switch while the

transactions are taking place. Another simple test is to measure how long the operation takes with and

without logging. The operation performed in NOLOGGING mode should occur faster because a minimal

amount of redo is generated during the load.

CHAPTER 1 ■ OPTIMIZING TABLE PERFORMANCE

1-7. Efficiently Removing Table Data

Problem

You’re experiencing performance issues when deleting data from a table. You want to remove data as

efficiently as possible.

Solution

You can use either the TRUNCATE statement or the DELETE statement to remove records from a table.

TRUNCATE is usually more efficient but has some side effects that you must be aware of. For example,

TRUNCATE is a DDL statement. This means Oracle automatically commits the statement (and the current

transaction) after it runs, so there is no way to roll back a TRUNCATE statement. Because a TRUNCATE

statement is DDL, you can’t truncate two separate tables as one transaction.

This example uses a TRUNCATE statement to remove all data from the COMPUTER_SYSTEMS table:

SQL> truncate table computer_systems;

When truncating a table, by default all space is de-allocated for the table except the space defined by

the MINEXTENTS table-storage parameter. If you don’t want the TRUNCATE statement to de-allocate the

currently allocated extents, then use the REUSE STORAGE clause:

SQL> truncate table computer_systems reuse storage;

You can query the DBA/ALL/USER_EXTENTS views to verify if the extents have been de-allocated (or

not)—for example:

select count(*)

from user_extents where segment_name = 'COMPUTER_SYSTEMS';

How It Works

If you need the option of choosing to roll back (instead of committing) when removing data, then you

should use the DELETE statement. However, the DELETE statement has the disadvantage that it generates a

great deal of undo and redo information. Thus for large tables, a TRUNCATE statement is usually the most

efficient way to remove data.

Another characteristic of the TRUNCATE statement is that it sets the high-water mark of a table back to

zero. When you use a DELETE statement to remove data from a table, the high-water mark doesn’t

change. One advantage of using a TRUNCATE statement and resetting the high-water mark is that full table

scan queries search only for rows in blocks below the high-water mark. This can have significant

performance implications for queries that perform full table scans.

CHAPTER 1 ■ OPTIMIZING TABLE PERFORMANCE

Another side effect of the TRUNCATE statement is that you can’t truncate a parent table that has a

primary key defined that is referenced by an enabled foreign-key constraint in a child table—even if the

child table contains zero rows. In this scenario, Oracle will throw this error when attempting to truncate

the parent table:

ORA-02266: unique/primary keys in table referenced by enabled foreign keys

Oracle prevents you from truncating the parent table because in a multiuser system, there is a

possibility that another session can populate the child table with rows in between the time you truncate

the child table and the time you subsequently truncate the parent table. In this situation, you must

temporarily disable the child table–referenced foreign-key constraints, issue the TRUNCATE statement,

and then re-enable the constraints.

Compare the TRUNCATE behavior to that of the DELETE statement. Oracle does allow you to use the

DELETE statement to remove rows from a parent table while the constraints are enabled that reference a

child table (assuming there are zero rows in the child table). This is because DELETE generates undo, is

read-consistent, and can be rolled back. Table 1-4 summarizes the differences between DELETE and

TRUNCATE.

If you need to use a DELETE statement, you must issue either a COMMIT or a ROLLBACK to complete the

transaction. Committing a DELETE statement makes the data changes permanent:

SQL> delete from computer_systems;

SQL> commit;

■ Note Other (sometimes not so obvious) ways of committing a transaction include issuing a subsequent DDL

statement (which implicitly commits an active transaction for a session) or normally exiting out of the client tool

(such as SQL*Plus).

If you issue a ROLLBACK statement instead of COMMIT, the table contains data as it was before the

DELETE was issued.

When working with DML statements, you can confirm the details of a transaction by querying from

the V$TRANSACTION view. For example, say that you have just inserted data into a table; before you issue a

COMMIT or ROLLBACK, you can view active transaction information for the currently connected session as

follows:

SQL> insert into computer_systems(cs_id) values(1);

SQL> select xidusn, xidsqn from v$transaction;

XIDUSN XIDSQN

---------- ----------

3 12878

SQL> commit;

SQL> select xidusn, xidsqn from v$transaction;

no rows selected

剩余584页未读，继续阅读

haha875232

粉丝: 4
资源: 91

Oracle 11g数据库性能调优实战指南

Oracle Database 11g Performance Tuning Recipes 英文版

Oracle Database 11g Performance Tuning

Oracle Database 12c Performance Tuning Recipes

Apress.Oracle.Database.11g.Performance.Tuning.Recipes

Oracle 12c Peformance Tuning Recipes

Apress - Oracle SQL Recipes A Problem Solution Approach (November 2009) (ATTiCA).pdf

Oracle 11g性能调优实战指南：快速解决数据库问题

Oracle数据库12c性能调优实战

Oracle 12c数据库性能优化实战

Oracle 12c性能调优实战：问题-解决方案指南

最新资源