10.2.0.4 to 10.2.0.5 Installation of Patch Set Release (Windows)

10.2.0.4 to 10.2.0.5 Installation of Patch Set Release (Windows)

Environment: 10.2.0.4 cluster database zlm10g (dual-node, zlm10g1, zlm10g2)

System: Windows 2003 Server 64Bit

Memory: 2 GB RAM

Storage: ASM

Objective: To upgrade the cluster database from 10.2.0.4 to 10.2.0.5, including cluster software and OEM Patch installation.

 

I. Preparations before Upgrade:

1. Check whether invalid objects exist.

SQL> select object_name, status from dba_objects where

Status = 'invalid ';

The purpose is to determine whether these invalid objects are generated during the upgrade or exist before the upgrade.

 

2. Check the Time Zone information in the database.

SQL> select version from v $ timezone_file;

2.1 return value is 4

If the database contains TZ information, no additional operations are required during the upgrade.

 

2.2 return value greater than 4

Please refer to the [ID 553812.1] Documentation

 

2.3 If the returned value is less than 4

Perform the following steps:

@? /Rdbms/admin/utltzpv4. SQL;

Select * from sys. sys_tzuv2_temptab;

If no row is returned, no additional operations are required during the upgrade process.

If the returned column information contains TZ, the upgrade operation will affect the TZ information.

 

If a SYS user has a SCHEDULER object, it can be ignored during the upgrade process. However, if there is user data or a job created by the user, you need to back up the data before the upgrade, after the upgrade, delete all jobs created by the user and recreate them.

 

Two upgrade methods:

Rolling upgrade (no downtime)

Non-rolling upgrade (with downtime)

 

Ii. Upgrade cluster database software

1. First, prepare the Patch medium for 10.2.0.5:

P8202632_10205_MSWIN-x86-64

 

2. Stop Oracle services and processes on all nodes

2.1 stop crs Resources

Emctlstop dbconsole

Isqlplusctlstop

Lsnrctlstop

Srvctlstop service-d zlm10g

Srvctlstop databse-d zlm10g

Srvctlstop asm-n rac1

Srvctlstop asm-n rac2

Srvctlstop listener-n rac1

Srvctlstop listener-n rac2

Srvctlstop nodeapps-n rac1

Srvctlstop nodeapps-n rac2

Crs_stat-t check if cluster resources are all closed

Srvctlstop crs

 

2.2 Stop Service

Run services. msc to check whether all Oracle services have been disabled.

The Distributed TransactionCoordinator service must also be stopped.

 

2.3 stop the process

Check whether any oracle-related processes are running in the task manager. Close all processes, such as one.exe.

 

3. Back up the following directory (copy to another path ):

% ORACLE_CRS_HOME %

% ORACLE_HOME %

% ORACLE_INVENTORY %

Note: We recommend that you back up the database using RMAN first.

 

4. Install the cluster Software Patch

During installation, the installation path overwrites the original path, that is, the crs_1 directory.

After the software is installed, run patch102.bat on node 1 and node 2 to complete the actual installation process. After the script is run, the system automatically runs the CRS-related services.

 

5. Check whether the cluster Patch is correctly installed.

Crsctlquery crs softwareversion

Crsctlquery crs activeversion

If the cluster Patch is properly installed, the output of the two commands is 10.2.0.5.0.

 

Iii. Database Software Patch installation

1. The installation media is the same as upgrading ClusterWare:

P8202632_10205_MSWIN-x86-64

 

2. Disable Oracle services and processes

2.1 stop crs Resources

Emctlstop dbconsole

Isqlplusctlstop

Lsnrctlstop

Srvctlstop service-d zlm10g

Srvctlstop databse-d zlm10g

Srvctlstop asm-n rac1

Srvctlstop asm-n rac2

Srvctlstop listener-n rac1

Srvctlstop listener-n rac2

 

2.2 Stop Service

Run services. msc to check whether all Oracle services have been disabled.

The Distributed TransactionCoordinator service must also be stopped.

 

2.3 stop the process

Check whether any oracle-related processes are running in the task manager. Close all processes, such as one.exe.

 

3. Install patches for Oracle database software

Select the same directory where the database software is installed, that is, the db_1 directory.

 

4. Modify cluster database Parameters

Log on to the system with sysdba after installation, and set cluster_database to False.

Sqlplus/nolog

SQL> alter system set cluster_database = falsescope = spfile;

SQL> shutdown immediate

 

5. Run the upgrade script on node 1 to upgrade the database.

 

5.1 enter the upgrade mode:

SQL> startup upgrade

 

5.2 pre-check whether the upgrade meets the following conditions:

SQL> spool patch_info.log

SQL> @? \ Rdbms \ admin \ utlu102i. SQL

SQL> spool off

For more supplementary scripts for each version of the pre-check script, the official website provides updated and more detailed pre-check content. For details, refer to [ID 884522.1].

5.3 Start executing the official upgrade script:

SQL> spool patch. log

SQL> @? \ Rdbms \ admin \ utlupgrd. SQL

10gR2 the process lasts for about 30 minutes, and 11gR2 takes about 50 minutes.

 

5.4 invalid objects generated after compilation and upgrade

SQL> spool rp. log

SQL> @? \ Rdbms \ admin \ utlrp. SQL

SQL> spool off

 

5.5 check whether the database components are valid after upgrade

SQL> select comp_id, comp_name, status from sys. dba_registry;

If the upgrade is completed normally, the values in the status column of all components should be VALID.

 

4. Use OPatch to install patches after 10.2.0.5

1. Media preparation and description

P8350262_10205_Generic (OEM patch)

P12429524_10205_MSWIN-x86-64

The purpose of this patch is to manage the database by using the OEM. As the OEM runs normally on 10.2.0.4 and 10.2.0.5, A bug exists. For details, see [ID1222603.1].

If this OEM patch is not applied, the system will prompt that the EM cannot be configured and the Database Control fails to be started when dbca, dbua, and emca are used to configure the OEM. The cause is that the root certificate CA is invalid at 31-DEC-2010, however, SSL Protocol cannot be used for communication, resulting in startup failure. This bug is limited to the one of the above two versions.

Here 2nd media, p12429524_10205_MSWIN-x86-64 contains more fixed bug, So if you directly install 12429524 this PSU, then you can also do not need to install 8350262, either choose one

 

2. Install OPatch

All Interim patches in Oracle, that is, the small patches we often call (PSU), can be installed using OPatch. This is an official Patch installation script provided by Oracle, the directory is placed in ORACLE_HOME \ OPatch.

The executable file for Windows is opatch. bat, decompress the patch to a directory, and then execute "opatch apply + extract directory path". You can also enter the directory of the number that is extracted, run opatch apply directly to install the patch. If you want to check which patches have been installed in the database, run opatch lsinventory [-detail]. For specific commands, add-help.

 

3. reconfigure OEM

After the patch is installed, if you start DBconsole directly, the system will still fail to start normally. Here, you need to reconfigure it, mainly in three steps:

 

3.1 Node 1 execution

Emctlsecure dbconsole-reset

 

3.2 Node 2 execution

Emctlsecure dbconsole

Note that the command does not contain the-reset parameter.

 

3.3 start dbconsole on node 1 (or node 2)

Emctlstart dbconsole

 

V. Final Stage

So far, all the upgrades are successfully completed. check whether any of the missing Oracle services and processes are not enabled. If yes, enable all of them.

Services. msc

Crs_stat-t

Emctlstart dbconsole

Isqlplusctlstart

Lsnrctlstart

Srvctlstart service-d zlm10g

Srvctlstart database-d zlm10g

Srvctlstart instance-d zlm10g-i zlm10g1

Srvctlstart instance-d zlm10g-i zlm10g2

Srvctlstart listener-n rac1

Srvctlstart listener-n rac2

Srvctlstart asm-n rac1

Srvctlstart asm-n rac2

Srvctlstart nodeapps-n rac1

Srvctlstart nodeapps-n rac2

The preceding commands are optional. Not all commands must be executed once. If the crs resources are ONLINE, you do not need to execute them.