Oracle 11gR2升级指南

需积分: 7 96 浏览量更新于2024-07-27 收藏 715KB PDF 举报

"Oracle Database 11gR2 Upgrade Companion 是一份针对 Oracle 数据库升级的指导文档，旨在帮助用户从 Oracle 9i Release 2 (9.2) 或 Oracle Database 10g 升级到 Oracle Database 11g Release 2。这份文档包含了预升级、升级以及升级后的指导，并随着新信息的出现不断更新。在进行任何升级操作前，建议查阅此文档。请注意，Upgrade Companion 是一份教学性质的辅助文档，不提供自动化工具，也不替代 Oracle Database 11g Upgrade Guide。它主要针对通用数据库的升级，对于客户或 Oracle 应用程序的特定升级需求，应按照产品文档的建议进行。对于数据库升级过程中的专业咨询或现场支持，可以参考 Oracle 的 Accelerate Technology Adoption 或 Oracle Consulting Upgrade Services。Oracle Advanced Customer Services 提供服务，帮助用户做出更好的 IT 决策，包括在升级过程中提供的选项和服务。" 在 Oracle Database 11gR2 Upgrade Companion 中，您会找到以下关键知识点： 1. **升级流程**：文档详细描述了从旧版本到 Oracle Database 11gR2 的整个升级流程，包括预升级检查、升级步骤以及升级后的验证和调整。 2. **预升级检查**：这部分内容涵盖了升级前需要进行的系统配置检查、兼容性评估、数据迁移准备、备份策略和环境清理等步骤，确保升级顺利进行。 3. **升级步骤**：文档详细列出升级数据库的具体步骤，包括安装新版本软件、执行升级脚本、转换数据文件和初始化参数文件等。 4. **后升级任务**：升级完成后，需要进行一系列的验证测试，如数据库功能测试、性能基准对比、应用兼容性检查以及安全性和审计设置的更新。 5. **错误处理与问题解决**：由于升级过程中可能出现各种问题，这份指南提供了常见问题的解决方案和错误代码的解释，帮助用户及时解决遇到的困难。 6. **最佳实践**：文档中包含了一系列最佳实践，比如如何最小化停机时间、如何规划和管理存储以及如何优化数据库性能。 7. **产品文档引用**：Upgrade Companion 强调了不能替代官方的 Upgrade Guide，因此用户还需要参照其他官方文档来获取更全面的信息，特别是针对特定应用程序或组件的升级指南。 8. **技术支持**：Oracle 提供了多种方式来获取升级过程中的专业支持，包括咨询服务和技术采纳加速计划，帮助用户在升级过程中得到及时的帮助。 9. **决策支持**：Oracle Advanced Customer Services 可以为用户提供高级支持，帮助制定升级策略，优化 IT 架构，并在升级过程中提供专业建议。 Oracle Database 11gR2 Upgrade Companion 是一个宝贵的资源，对于任何计划升级到 11gR2 版本的数据库管理员来说，都是不可或缺的工具。它不仅提供了详细的升级步骤，还强调了升级前后的注意事项和可能遇到的问题，有助于确保整个升级过程的顺利和成功。

6. Ensure there are no invalid objects in SYS and SYSTEM user

schema.

Check for invalid objects by performing the following commands:

spool invalid_pre.lst

select substr(owner,1,12) owner,

substr(object_name,1,30) object,

substr(object_type,1,30) type, status from

dba_objects where status <>'VALID';

spool off

If there are invalid objects you can recompile them by logging in as a

SYSDBA user and running the utlrp.sql located in the

$ORACLE_HOME/rdbms/admin directory. This script will attempt to

recompile the invalid objects and any dependencies. This script can be

run multiple times until all objects have been compiled.

If invalid objects still exist which do not have a name that begins with x_

$, check the owner of objects which can't be compiled successfully. In

most cases these objects belong to database options which have been

installed in earlier releases but do not exist in the current installation

anymore. In this case a support request (SR) with Oracle Support

should be opened to ask for the necessary scripts to drop these objects.

If valid or invalid objects exists that have a name that begins with x_$,

then refer to My Oracle Support

Document 361757.1: Invalid x_$ Objects

After Upgrade. These views were created by third party applications and

point to non-existent or modified x$ tables. Since these are not Oracle

created objects, they should be dropped before the upgrade. They

cannot be validated or dropped after the upgrade using normal methods.

NOTE: The Pre-Upgrade Information Tool checks for invalid objects.

Refer to My Oracle Support

Document 884522.1: How to Download and

Run Oracle's Database Pre-Upgrade Utility for details on downloading

an running the Pre-Upgrade Utility.

NOTE: To avoid effecting database performance, run the utlrp.sql script

during a time when the load on the database is low.

Oracle Database 11gR2 Upgrade Companion (Version 2.70) 08/10/2011

Page 16 of 94

7. Verify that all dba_registry components are valid.

If invalid components exist in dba_registry try the the steps below.

a. Recompile all of the invalid objects with utlrp.sql.

b. If there are still invalid components after running utlrp.sql, then

consult My Oracle Support for other solutions such as

Document

472937.1: Information On Installed Database Components and

Schemas and Document 753041.1: How to diagnose Components

with NON VALID status.

Use the following query to identify invalid compontents that may

still exist:

SQL> select substr(comp_id,1,15) comp_id,

substr(comp_name,1,30) comp_name,

substr(version,1,10) version,

status

from dba_registry

order by modified;

8. Disable all DBMS_JOBS, Batch, AT, and Cron Jobs before starting

the upgrade.

Please note that using STARTUP UPGRADE automatically disables

database jobs; however, any OS level or third-party tools that spawn

jobs at the OS level that then connect to the DB or do cleanup tasks

must be manually disabled.

9. Starting with Oracle Database 10g Release 2 the CONNECT role only

includes CREATE SESSION privilege.

If you have user or roles that require privileges other than CREATE

SESSION then document the user and roles and grant the specific

privileges after the upgrade. A WARNING is provided if you run the Pre-

Upgrade Information Tool. Refer to My Oracle Support

Document

884522.1: How to Download and Run Oracle's Database Pre-Upgrade

Utility for details on downloading an running the Pre-Upgrade Utility.

SELECT grantee

FROM dba_role_privs

WHERE granted_role = 'CONNECT' and

grantee NOT IN ('SYS', 'OUTLN', 'SYSTEM',

'CTXSYS', 'DBSNMP',

'LOGSTDBY_ADMINISTRATOR',

'ORDSYS', 'ORDPLUGINS',

'OEM_MONITOR', 'WKSYS',

'WKPROXY', 'WK_TEST',

'WKUSER', 'MDSYS',

'LBACSYS', 'DMSYS', 'WMSYS',

'EXFSYS', 'SYSMAN',

'MDDATA', 'XDB', 'ODM',

'SI_INFORMTN_SCHEMA');

Oracle Database 11gR2 Upgrade Companion (Version 2.70) 08/10/2011

Page 17 of 94

10. It is mandatory to run the pre-upgrade tool prior to the upgrade

process otherwise the upgrade will not continue. The pre-upgrade

tool validates whether the source database is ready to be

upgraded. Any area that does not meet the requirements must be

corrected. Refer to My Oracle Support

Document 884522.1: How to

Download and Run Oracle's Database Pre-Upgrade Utility for

details on downloading an running the Pre-Upgrade Utility.

11. Use Oracle Recovery Manager (RMAN) to take a complete online

backup of your database as well as make a backup copy of the

following files: init.ora or spfile, password file, and all SQL*Net

files (sqlnet.ora, listener.ora, tnsnames.ora, and so on...).

12. Consult the "Upgrading Your Applications" chapter of the upgrade

guide for specific instructions regarding applications.

13. Back up the oraInventory and ORACLE_HOME directories.

Preserve

It is important to preserve the current database before the upgrade begins so that a

known good state of the database can be restored in the event of a failure during the

upgrade process. Having a good fallback plan in place can prevent significant down

time and data loss in the event of a failure. Recording current performance data is

critical to diagnosing and the remediation of performance issues that arise once the

upgrade is completed. Without pre-upgrade data it will be more difficult to determine

why performance characteristics have changed.

Preserving Performance Baselines and Statistics for the

Source Database

Proper performance testing is the key to a successful upgrade. This section

discusses what needs to be done to properly capture performance data at all

stages of the upgrade process.

1. Capturing Performance Baselines Before Upgrading

It is very important to capture performance baselines before and after

the upgrade process (in current Oracle9i/Oracle Database 10g

PRODUCTION, TEST and upgraded PRODUCTION). These baselines

help to detect a performance regression on the TEST system and

perhaps later in production. These baselines will be captured in three

ways:

1. Unit tests: specific queries, transactions, and jobs that are

important to the business

2. Load tests: a load simulation that runs important business

activities at similar user levels and concurrency rates as are run

on the production system

3. Production workloads: Actual production workload performance

data captured prior to the upgrade from Oracle9i Release 2/

Oracle Database 10g Release 2 and after completing the upgrade

Documentation

● Backup and Recovery User's

Guide

● Oracle Database Real

Application Testing User's

Guide 11g

● Oracle Database

Performance Tuning Guide 11g

Release 2 > Chapter 17 >

Managing SQL Tuning Sets

Notes

● Document 560977.1: Real

Application Testing Now

Available for Earlier Releases

● Document 1268920.1: Real

Application Testing:Workload

Analyzer

● Document 1287620.1:

Database Replay Diagnostic

information

● Document 562899.1:

TESTING SQL

PERFORMANCE IMPACT OF

AN ORACLE 9i TO ORACLE

DATABASE 10g RELEASE 2

UPGRADE WITH SQL

PERFORMANCE ANALYZER

● Document 742644.1: SQL

PERFORMANCE ANALYZER

10.2.0.x to 10.2.0.y EXAMPLE

Oracle Database 11gR2 Upgrade Companion (Version 2.70) 08/10/2011

Page 18 of 94

to Oracle Database 11g

NOTE: SQL Plan Management (SPM) is a freely available new feature in

Oracle Database 11g that ensures plan stability and the same plan as in

the original (pre-upgrade) database release. With Oracle Database 11g

and SPM, the optimizer automatically manages plans and ensures that

only verified or known plans are used. SPM allows controlled plan

evolution by only using a new plan after it has been verified to perform

better than the current plan. Some small amount of preparation is

needed to ensure that execution plans are preserved for use after the

upgrade, but for best results, use SQL Plan Management as part of your

upgrade strategy.

For more details on SQL Plan Management:

●

Oracle Database Performance Tuning Guide - Using SQL Plan

Management

●

SQL Plan Management in Oracle Database 11g

●

Document 456518.1: SQL PLAN MANAGEMENT

●

Inside the Oracle Optimizer

In addition to using SPM,

Real Application Testing is a paid option that

includes

Database Replay and SQL Performance Analyzer (SPA). Use of

this option is highly recommended for mission critical databases, and

for instances where it is important to verify application functionality and

performance.

For critical databases and best results, use Database Replay to capture

actual production workload in Oracle9i/Oracle Database 10g for replay

in an Oracle Database 11g environment. Additionally, for testing SQL

execution plans, use SQL Performance Analyzer (SPA) on those same

databases. Starting with Oracle9i, an extended SQL trace can be

generated to capture SQL execution performance for key workloads for

input to SPA. For Oracle Database 10g Release 2, the more efficient

incremental cursor cache capture should be used to capture SQL into a

SQL Tuning Set for input to SPA. This may require licensing the Real

Application Testing option and Oracle Database Diagnostic and Tuning

Management Packs, but makes the task of testing upgrades significantly

easier and hence is the recommended best practice.

Baselines, Step-by-step

1. Choose important transactions, batch jobs, or queries (we'll call

these "activities") that must NOT be negatively impacted by the

upgrade.

2. Determine acceptable response times, throughput, and/or job

execution times that cannot be exceeded

3. Construct unit tests for the activities by either:

❍

Using Real Application Testing functionality (if licensed) to

capture actual production workloads directly. This will

provide the best results for upgrades

❍

Scripting the unit tests

SCRIPTS

● Document 742645.1:

Database Replay Command

Line Interface (CLI) usage

examples/scripts

● Document 787658.1:

SCALE_UP_MULTIPLIER:

DATABASE CAPTURE AND

REPLAY

How-To

● Document 465787.1:

Managing CBO Stats during an

upgrade to 10g or 11g

● Document 466350.1:

Recording Explain Plans before

an upgrade to 10g or 11g

● Document 376442.1:

Recommended Method for

Obtaining 10046 trace for

Tuning

Scripts and Tools

● Document 301137.1: OS

Watcher

● Document 461053.1: OSWg

● Document 352363.1: LTOM

White Papers

● Maximum Availability

Architecture (MAA)

● Document 466996.1:

Determining CPU Resource

Usage for Linux and Unix

● Document 467018.1:

Measuring Memory Resource

Usage for Linux and Unix

● SQL Performance Analyzer

● Database Replay

● Siebel on Exadata

● Upgrading from Oracle

Database 10g to 11g: What to

expect from the Optimizer

Oracle Database 11gR2 Upgrade Companion (Version 2.70) 08/10/2011

Page 19 of 94

剩余93页未读，继续阅读

lys_xy

粉丝: 0
资源: 90

Oracle 11gR2升级指南

11gR2 RAC 11.2.0.3升级到11.2.0.4详述：步骤与注意事项

从11gR2 RAC无缝升级至19c on RHEL7：实战教程与注意事项

Oracle 11gR2升级最佳实践：全面指南与文档资源

Veritas Access Appliance Upgrade Guide.pdf

11gr2 升级 11.2.0.1到11.2.0.3

SAP Value Upgrade.pdf

FT5x06_Upgrade.pdf

JasperReports-Server-Upgrade-Guide.pdf

Rockchip_Developer_Guide_Linux_Upgrade_CN.pdf

Upgrade9252.exe

最新资源