Oracle upgrades from 10.2.0.1 to 10.2.0.5 operation experiment

Routine upgrades and patching are common tasks for system O & M personnel. In many cases, upgrading the database and patching are the ultimate policy to solve Oracle bugs.

Before Oracle 11gR2, Oracle generally adopted an incremental patch upgrade policy. The initial installation is a relatively low basic version, such as 10.2.0.1 or 11.2.0.1, which can be directly downloaded on the official website. If you need to upgrade the minor version or fix a specific bug, you need to download a dedicated patch package on the Oracle Support website. Our common 10.2.0.5 and 11.2.0.4 are upgraded using these policies.

In terms of upgrade, Oracle will officially launch two versions of patch packages, CPU and PSU. The CPU (Critical Patch Update) is a quarterly security Patch for its products. It is mainly used to fix product security risks. Patch Set Update is also a quarterly release, including Bug fixes and various approved low-risk patches.

After entering 11R2, the Oracle update policy has changed. We can directly download the higher version of PSU packages, which are actually brand new Oracle software packages. Currently, we can install PSU directly on both 11.2.0.3 and 11.2.0.4, without upgrading from the basic version.

This article mainly wants to record the history and introduce the process of upgrading from 10.2.0.1 to 10.2.0.5, waiting for a friend to be checked. Note: I would like to express my gratitude for the many network resources referenced in this experiment.

Detailed illustration of the entire process of VMware + Linux + Oracle 10G RAC

Install Oracle 11gR2 (x64) in CentOS 6.4)

Steps for installing Oracle 11gR2 in vmwarevm

Install Oracle 11g XE R2 In Debian

Steps for installing Oracle 11gR2 in vmwarevm

1. Environment Introduction

We have successfully installed Oracle 10gR2 on RedHat 6.5 and the version is 10.2.0.1.

[Oracle @ SimpleLinux ~] $ Uname-r

2.6.32-431. el6.i686

SQL> select * from v $ version;

BANNER

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

Oracle Database 10g Enterprise Edition Release 10.2.0.1.0-Prod

PL/SQL Release 10.2.0.1.0-Production

CORE 10.2.0.1.0 Production

TNS for Linux: Version 10.2.0.1.0-Production

NLSRTL Version 10.2.0.1.0-Production

The key oracle environment variables of the current operating system user are as follows:

[Oracle @ SimpleLinux ~] $ Env | grep ORA

ORACLE_SID = ora11g

ORACLE_BASE =/u01/app/oracle

ORACLE_HOME =/u01/app/oracle/product/10.2.0/db_1

The operating system has sufficient storage and memory resources.

[Oracle @ SimpleLinux ~] $ Df-h

Filesystem Size Used Avail Use % Mounted on

/Dev/mapper/vg_simplelinux-LogVol00 29G 8.7G 19G 32%/

Tmpfs 448 M 0 448 M 0%/dev/shm

/Dev/sda1 485 MB 33 M 427 M 8%/boot

[Oracle @ SimpleLinux ~] $ Free-m

Total used free shared buffers cached

Mem: 894 332 561 0 20 241

-/+ Buffers/cache: 70 824

Swap: 1999 0 1999

2. Backup environment and patch preparation

First, we need to close related objects such as databases and listeners. ASM and DB Control should also be disabled according to different situations.

[Oracle @ SimpleLinux ~] $ Lsnrctl stop

LSNRCTL for Linux: Version 10.2.0.1.0-Production on 13-MAY-2014 11:19:04

Copyright (c) 1991,200 5, Oracle. All rights reserved.

Connecting to (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (HOST = localhost) (PORT = 1521 )))

The command completed successfully

SQL> conn/as sysdba

Connected.

SQL> shutdown immediate;

Database closed.

Database dismounted.

ORACLE instance shut down.

The following describes how to back up the environment. Note: the upgrade process is risky, especially in the production environment. Two steps are important strategies to reduce upgrade risks: Multiple tests and data backup. Multiple tests (in the system test environment) can help us identify problems with the upgrade solution in advance, prepare policies, and verify the solution. Data backup can minimize the risk of data loss.

You can select RMAN, cold backup, and exp/expdp for different backup methods. Here I chose the complete method to directly copy the directory.

[Root @ SimpleLinux upload] # mkdir/u02

[Root @ SimpleLinux upload] # cd/u01

[Root @ SimpleLinux u01] # cp-r */u02

[Root @ SimpleLinux u01] #

Before proceeding, you must re-plan and confirm the upgrade steps. Two patch packages are required for this upgrade, one is 10.2.0.5 and the other is the patch package running on 10.2.0.5. Download the upgrade installation package for a specific version on MOS and upload it to the server.

[Root @ SimpleLinux ~] # Cd/upload/

[Root @ SimpleLinux upload] # ls-l

Total 1082304

-Rw-r -- 1 root 4278863 May 13 p11724962_10205_LINUX.zip

-Rw-r -- 1 root 1103992900 May 13 p8202632_10205_LINUX.zip-upgrade the 10.2.0.5 package

Note: There are two major steps to upgrade the database: Oracle software upgrade and Oracle Database Upgrade. We can recall that when installing the database, we first install the database software (including Grid and Clusterware) and then create the dbca database. The same is true for upgrades. We need to first update the database software to the latest version, and then clear existing database objects to upgrade them to the latest version.

3. Oracle software upgrade

First, we perform software upgrade and decompress the installation package.

[Root @ SimpleLinux upload] # ls-l

Total 1082472

Drwxr-xr-x 5 root 4096 Jul 23 2010 Disk1

-Rw-r -- 1 root 4278863 May 13 p11724962_10205_LINUX.zip

-Rw-r -- 1 root 1103992900 May 13 p8202632_10205_LINUX.zip

-Rwxrwxrwx 1 root 165290 Jul 20 2010 README.html

Grant permissions to oracle users in root.

[Root @ SimpleLinux upload] # cd/

[Root @ SimpleLinux/] # chown-p oracle: oinstall upload/

Chown: invalid option -- 'P'

Try 'chown -- help' for more information.

[Root @ SimpleLinux/] # chown-R oracle: oinstall upload/

[Root @ SimpleLinux/] #

The software upgrade is performed on the graphical interface. You need to configure XWindows or vnc interface tools. Run the. runInstall script in the directory to start the interface. If the environment variable is configured properly, the automatic Path will be included in the interface.

For most operations, click Next to confirm the process.

For more details, please continue to read the highlights on the next page:

1 2 3 Next Page