oracle8i 升级10g,数据库直接从8i升级到10g,

Oracle Database 10g: Changes in Default Behavior

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

This page describes some of the changes in the behavior of Oracle

Database 10g from that of previous releases. In some cases the

default values of some parameters have changed.  In other cases

new behaviors/requirements have been introduced that may affect

current scripts or applications. More detailed information is in

the documentation.

SQL OPTIMIZER

The Cost Based Optimizer (CBO) is now enabled by default.

* Rule-based optimization is not supported in 10g (setting

OPTIMIZER_MODE to RULE or CHOOSE is not supported).  See Chapter

12, "Introduction to the Optimizer," in Oracle Database

Performance Tuning Guide.

* Collection of optimizer statistics is now performed by default,

automatically for all schemas (including SYS), for pre-existing

databases upgraded to 10g, and for newly created 10g databases.

Gathering optimizer statistics on stale objects is scheduled by

default to occur daily during the maintenance window.  See

Chapter 15, "Managing Optimizer Statistics" in Oracle Performance

Tuning Guide.

* See the Oracle Database Upgrade Guide for changes in behavior

for the COMPUTE STATISTICS clause of CREATE INDEX, and for

behavior changes in SKIP_UNUSABLE_INDEXES.

UPGRADE/DOWNGRADE

* After upgrading to 10g, the minimum supported release to

downgrade to is Oracle 9i R2 release 9.2.0.3 (or later), and the

minimum value for COMPATIBLE is 9.2.0.  The only supported

downgrade path is for those users who have kept COMPATIBLE=9.2.0

and have an installed 9i R2 (release 9.2.0.3 or later)

executable.  Users upgrading to 10g from prior releases (such as

Oracle 8, Oracle 8i or 9iR1) cannot downgrade to 9i R2 unless

they first install 9i R2. When upgrading to10g, by default the

database will remain at 9i R2 file format compatibility, so the

on disk structures that 10g writes are compatible with 9i R2

structures; this makes it possible to downgrade to 9i R2. Once

file format compatibility has been explicitly advanced to 10g

(using COMPATIBLE=10.x.x), it is no longer possible to downgrade.

See the Oracle Database Upgrade Guide.

* A SYSAUX tablespace is created upon upgrade to 10g. The SYSAUX

tablespace serves as an auxiliary tablespace to the SYSTEM

tablespace. Because it is the default tablespace for many Oracle

features and products that previously required their own

tablespaces, it reduces the number of tablespaces required by

Oracle that you, as a DBA, must maintain.

MANAGEABILITY

* Database performance statistics are now collected by the

Automatic Workload Repository (AWR) database component,

automatically upon upgrade to 10g and also for newly created 10g

databases.  This data is stored in the SYSAUX tablespace, and is

used by the database for automatic generation of performance

recommendations. See Chapter 5, "Automatic Performance

Statistics" in the Oracle Database Performance Tuning Guide.

* If you currently use Statspack for performance data gathering,

see section 1. of the Statspack readme (spdoc.txt in the RDBMS

ADMIN directory) for directions on using Statspack in 10g to

avoid conflict with the AWR.

MEMORY

* Automatic PGA Memory Management is now enabled by default

(unless PGA_AGGREGATE_TARGET is explicitly set to 0 or

WORKAREA_SIZE_POLICY is explicitly set to MANUAL).

PGA_AGGREGATE_TARGET is defaulted to 20% of the SGA size, unless

explicitly set.  Oracle recommends tuning the value of

PGA_AGGREGATE_TARGET after upgrading.  See Chapter 14 of the

Oracle Database Performance Tuning Guide.

* Previously, the number of SQL cursors cached by PL/SQL was

determined by OPEN_CURSORS.  In 10g, the number of cursors cached

is determined by SESSION_CACHED_CURSORS.  See the Oracle Database

Reference manual.

* SHARED_POOL_SIZE must increase to include the space needed for

shared pool overhead.

* The default value of DB_BLOCK_SIZE is operating system

specific, but is typically 8KB (was typically 2KB in previous

releases).

TRANSACTION/SPACE

* Dropped objects are now moved to the recycle bin, where the

space is only reused when it is needed. This allows 'undropping'

a table using the FLASHBACK DROP feature.  See Chapter 14 of the

Oracle Database Administrator's Guide.

* Auto tuning undo retention is on by default. For more

information, see Chapter 10, "Managing the Undo Tablespace," in

the Oracle Database Administrator's Guide.

CREATE DATABASE

* In addition to the SYSTEM tablespace, a SYSAUX tablespace is

always created at database creation, and upon upgrade to 10g. The

SYSAUX tablespace serves as an auxiliary tablespace to the SYSTEM

tablespace. Because it is the default tablespace for many Oracle

features and products that previously required their own

tablespaces, it reduces the number of tablespaces required by

Oracle that you, as a DBA, must maintain. See Chapter 2,

"Creating a Database," in the Oracle Database Administrator's

Guide.

* In 10g, by default all new databases are created with 10g file

format compatibility. This means you can immediately use all the

10g features.  Once a database uses 10g compatible file formats,

it is not possible to downgrade this database to prior releases.

Minimum and default logfile sizes are larger. Minimum is now 4

MB, default is 50MB, unless you are using Oracle Managed Files

(OMF) when it is 100 MB.