upgrade Oracle 10.2.0.3 on HP-UX

最新推荐文章于 2024-07-12 14:26:59 发布

cuigu9713

最新推荐文章于 2024-07-12 14:26:59 发布

阅读量152

点赞数

文章标签：数据库 ux java

Oracle® Database Patch Set Notes
10g Release 2 (10.2.0.3) Patch Set 2 for HP-UX PA-RISC (64-Bit) [@more@]

Oracle® Database

Patch Set Notes

10g Release 2 (10.2.0.3) Patch Set 2 for HP-UX PA-RISC (64-Bit)

March 2007

These patch set notes accompany the Oracle Database release 10.2.0.3 patch set. This document contains the following sections:

This document may be updated after release. To check for updates to this document, see document 316900.1 on the OracleMetaLink Web site:

http://metalink.oracle.com

To locate document 316900.1:

Log on to OracleMetaLink.
Click Advanced at the top of the OracleMetaLink page.
Enter 316900.1 in the Document ID field, then click Submit.

1 Patch Set Overview

Patch sets are a mechanism for delivering fully tested and integrated product fixes. Patch sets provide bug fixes only; they do not include new functionality and they do not require certification on the target system.

Patch sets include all of the libraries that have been rebuilt to implement the bug fixes in the set. All of the fixes in the patch set have been tested and are certified to work with each other. Because the patch set includes only low impact patches, it does not require you to certify applications or tools against the server.

You can apply the Oracle Database release 10.2.0.3 patch set to the following Oracle Database 10g release 2 installations:

Oracle Database
Oracle Real Application Clusters
Oracle Database Client
Oracle Database Companion CD
Oracle Clusterware

For a list of products included in this patch set, see the "Patch Set Components" section.

2 Oracle Universal Installer Version Requirements

This patch set includes Oracle Universal Installer release 10.2.0.3, which is also installed when you install this patch set. This is to ensure that your Oracle home can be patched in the future. You should not use Oracle Universal Installer from the earlier maintenance release media or Oracle home.

This is not a complete software distribution. You must install it in an existing Oracle Database 10g (10.2.0.x) installation.

3 Patch Set Documentation

There are two documents related to this release of the Oracle Database patch set:

Oracle Database Patch Set Notes, 10g release 2 (10.2.0.3) Patch Set 2 for HP-UX PA-RISC (64-Bit) (this document)
Oracle Database List of Bugs Fixed, 10g release 2 (10.2.0.3) Patch Set 2

Both of these documents are included with the patch set. In addition, they are available from document 316900.1, ALERT: Oracle 10g release 2 (10.2) Support Status and Alerts on the OracleMetaLink Web site:

http://metalink.oracle.com

To locate document 316900.1:

Log on to OracleMetaLink.
Click Advanced at the top of the OracleMetaLink page.
Enter 316900.1 in the Document ID field, then click Submit.

The following sections describe the contents of the Oracle Database Patch Set Notes and the Oracle Database List of Bugs Fixed.

Oracle Database Patch Set Notes, 10g Release 2 (10.2.0.3) Patch Set 2 for HP-UX PA-RISC (64-Bit)

This document provides:

System requirements and information about how to install, reinstall or remove the patch set
A list of all bugs fixed to date that are specific to Oracle Database for HP-UX PA-RISC (64-Bit)
A list of known issues relating to Oracle Database on HP-UX PA-RISC (64-Bit)

Oracle Database List of Bugs Fixed, 10g Release 2 (10.2.0.3) Patch Set 2

The List of Bugs Fixed is a list of all generic bugs related to Oracle Database that have been fixed to date.

4 System Requirements

The following are the system requirements for this patch set:

Operating System: HP-UX 11.11 or HP-UX 11.23
Operating System Patches
For HP-UX 11.11
- PHCO_33711: s700_800 11.11 libc cumulative patch
- PHKL_33844: Patch to fix mmap hang issue
For HP-UX 11.23:
- PHSS_32740: ServiceGuard Extension for Oracle RAC Bundle A.11.16.00 (required for Oracle RAC only)

Oracle Database 10g (10.2.0.1) or later

5 Preinstallation Tasks

Complete the following preinstallation tasks before installing the patch set:

5.1 Review Known Preinstallation Issues

Review the information in the following sections. If any of the issues apply to your Oracle installation, follow the instructions before installing the patch set.

5.1.1 Upgrading Oracle E-Business Suite Databases

If you are an Oracle E-Business Suite customer and you want to upgrade your Oracle E-Business Suite release 11i database server to this patch set, then you must check the latest certification status and Interoperability Notes available on the OracleMetaLink Web site:

http://metalink.oracle.com

5.1.2 Upgrading Installations that use Physical or Logical Standby Databases

Before applying this patch set to an Oracle Database 10.2.0.x installation that uses one or more physical or logical standby databases, review the following OracleMetaLink documents:

For information about physical standby databases, review document 278641.1.
For information about logical standby databases, review document 278643.1.

These documents are available on the OracleMetaLink Web site:

http://metalink.oracle.com

5.1.3 Upgrading Installations that use Java Virtual Machine or Oracle interMedia

If any of the databases use Java Virtual Machine or Oracle interMedia, then install the Oracle Database 10g Products installation type from the Oracle Database 10g Companion CD before installing the 10.2.0.3 patch set. For information about installing the Oracle Database 10g Products installation type from the Companion CD, see the Oracle Database Companion CD Installation Guide for your platform. This installation type includes the Natively Compiled Java Library files to improve Java performance. If you do not install the Natively Compiled Java Library files, the ORA-29558:JAccelerator(NCOMP)not installed error occurs when a database that uses Java Virtual Machine is upgraded to the patch release.

5.1.4 Upgrading Oracle Clusterware

The Oracle Clusterware software must be at the same or newer level as the Oracle software in the Oracle RAC Oracle home. Therefore, you should always upgrade Oracle Clusterware before you upgrade Oracle RAC.

5.1.5 Notes to Oracle OLAP users

To apply this patch set, Oracle OLAP users should ensure that the base release is the Enterprise Edition of 10.2.0.x with the Oracle OLAP option installed. Oracle highly recommends the Data Warehouse configuration type to optimize the database for Oracle OLAP.

Oracle OLAP users upgrading the Oracle Database to 10.2.0.3.0 must upgrade the Analytic Workspace Manager client as well. This new 10.2.0.3.0 Analytic Workspace Manager can be found on Oracle Technology Network and on OracleMetaLink by referencing Oracle OLAP patch 5581559.

5.2 Identify the Oracle Database Installation

This is not a complete software distribution. You must install it in an existing Oracle Database 10g Oracle home. To identify Oracle home directories, view the /etc/oratab file.

If you are installing this patch set on an existing Oracle Real Application Cluster 10g release 10.2.0.x installation, you must run Oracle Universal Installer from the same node from which the Oracle Database software was installed.

5.3 Check Postrelease Updates

Before installing this patch set in a production environment, review document 316900.1, ALERT: Oracle 10g release 2 (10.2) Support Status and Alerts, available on the OracleMetaLink Web site:

http://metalink.oracle.com

To locate this document:

Log on to OracleMetaLink.
Click Advanced at the top of the OracleMetaLink page.
Enter 316900.1 in the Document ID field, then click Submit.

This document is created by Oracle Support Services and provides information about the status of issues discovered after this patch set was released. If you are unable to access this site, then contact Oracle Support Services before installing this patch set in a production environment.

5.4 Download and Extract the Installation Software

To download and extract the patch set installation software:

Download the p5337014_10203_HP64.zip patch set installation archive to a directory that is not the Oracle home directory or under the Oracle home directory.
Enter the following command to unzip and extract the installation files :
```
$ unzip p5337014_10203_HP64.zip
```

Download and extract the patch set installation archive to a directory that is not the Oracle home directory or under the Oracle home directory. For example, Oracle_patch.

5.5 Update Oracle Time Zone Definitions

The 10.2.0.3 patch set includes an update to the Oracle time zone definitions. The 10.2.0.3 patch set updates the standard version of the Oracle 10.2 time zone definitions version-2 to version-3. This version of the time zone definitions includes the changes to daylight saving time in the USA in 2007, and many other updates.

A list of updated time zones in version-3 of these definitions are available from document 412160.1 on the OracleMetaLink Web site:

http://metalink.oracle.com

To locate document 412160.1:

Log on to OracleMetaLink.
Click Advanced at the top of the OracleMetaLink page.
Enter 412160.1 in the Document ID field, then click Submit.

Perform the following actions to ensure that time zone data affected by the changes in these time zones are updated appropriately:

Download the patch 5601428 from OracleMetaLink.
Install the patch. The script utltzuv2.sql is installed into the $ORACLE_HOME/rdbms/admin directory.
Run utltzuv2.sql to check the data of datatype TIMESTAMP WITH TIME ZONE (TSTZ). The output of this script is a results table which highlights the affected columns.

Refer to the instructions in the utltzuv2.sql or OracleMetaLink note 396671.1: Usage of utltzuv2.sql before updating time zone files in Oracle 10, to evaluate results and if required save the existing TSTZ data. If no data was found, no further actions are needed.

Note:

If you saved the existing TSTZ data, you need to complete Updating Oracle Time Zone Definitions under the Postinstallation Tasks section to view the change.

To locate document 396671.1 on the OracleMetaLink Web site:

http://metalink.oracle.com

To locate document 396671.1:

Log on to OracleMetaLink.
Click Advanced at the top of the OracleMetaLink page.
Enter 396671.1 in the Document ID field, then click Submit.

Note:

If you have previously installed a patch for bug 4689959, the database is already using version 3 of the Oracle time zone definitions. In this case, the script in step 3 will display the following message: TIMEZONE data is consistent with the latest version 3 transition rules, No need to validate TIMEZONE data. In this case, no further action is needed and step 4 can be skipped.

If you have previously installed a patch for bug 5632264, the database is already using version 4 of the Oracle time zone definitions, which supersedes the version included in this patch set. The script in step 3 will display the following message: Your time zone upgrade needs a different script. Please contact Oracle support!. In this case, the actions from step 4 should be skipped and you should re-apply patch 5632264 on the 10.2.0.3 installation as soon as the patch set installation is completed.

5.6 Set the ORACLE_HOME and ORACLE_SID Environment Variables

Enter the following commands to set the ORACLE_HOME and ORACLE_SID environment variables:

Bourne, Bash, or Korn shell:

$ ORACLE_HOME=Oracle_home
$ ORACLE_SID=sid
$ export ORACLE_HOME ORACLE_SID

C shell:

% setenv ORACLE_HOME Oracle_home
% setenv ORACLE_SID sid

In these examples, Oracle_home is the Oracle home directory where the Oracle Database 10g installation that you want to upgrade is installed, and sid is the system identifier of the database that you want to upgrade. For Oracle RAC installations, sid is generally the sid prefix and the instance number. For example, ORCL1.

5.7 Stop All Processes

Go to the following sections based on your Oracle Database installation type:

5.7.1 Stopping All Processes for a Single Instance Installation

Shut down the following Oracle Database 10g processes in the order specified before installing the patch set:

Shut down all processes in the Oracle home that might be accessing a database, for example Oracle Enterprise Manager Database Control or iSQL*Plus:

$ emctl stop dbconsole
$ isqlplusctl stop

Note:

Before you shut down all processes that are monitored by Oracle Enterprise Manager Grid Control, set a blackout in Grid Control for the processes that you intend to shut down. This is necessary so that the availability records for these processes indicate that the shutdown was planned downtime rather than an unplanned system outage.

Shut down all database instances running in the Oracle home directory, where you need to install the patch set.
Shut down all listeners running in the Oracle home directory, where you need to install the patch set.
If there is an Automatic Storage Management instance present, then enter the following command to set the values for the environment variables $ORACLE_HOME and $ORACLE_SID:
- Bourne, Bash, or Korn shell:
```
$ export ORACLE_SID=+ASM
$ export ORACLE_HOME=ASM_HOME
```
- C shell:
```
% setenv ORACLE_SID +ASM
% setenv ORACLE_HOME ASM_HOME
```
Enter the following command to Shut down the Automatic Storage Management instance:
```
$ sqlplus /NOLOG
SQL> CONNECT SYS/SYS_password AS SYSDBA
SQL> SHUTDOWN IMMEDIATE
```
For Automatic Storage Management, to shut down the Oracle Cluster Synchronization Services daemon enter the following command as the root user:
```
# $ORACLE_HOME/bin/crsctl stop crs
```

5.7.2 Stopping All Processes for an Oracle Clusterware Installation

This section contains the following information:

5.7.2.1 Rolling Upgrade

By default, Oracle supports rolling upgrade for Oracle Clusterware. Complete the following steps only on one node:

Shut down all processes in the Oracle home on the node that might be accessing a database, for example Oracle Enterprise Manager Database Control or iSQL*Plus:

$ emctl stop dbconsole
$ isqlplusctl stop

Note:

Shut down all services in the Oracle home on the node that might be accessing a database:
```
$ srvctl stop service -d db_name [-s service_name_list [-i inst_name]]
```
Shut down all Oracle RAC instances on the node on which you intend to perform the rolling upgrade. To shut down Oracle RAC instances on individual nodes in the database, enter the following command where db_name is the name of the database:
```
$ srvctl stop instance -d db_name -i inst_name
```
If an Automatic Storage Management instance is present, then shut down the Automatic Storage Management instance on the node on which you intend to perform the rolling upgrade. To shut down an Automatic Storage Management instance, enter the following command where node is the name of the node where the Automatic Storage Management instance is running:
```
$ srvctl stop asm -n node
```
Stop all node applications on the node on which you intend to perform the rolling upgrade. To stop node applications running on a node, log in as the root user and enter the following command, where node is the name of the node where the applications are running:
```
# srvctl stop nodeapps -n node
```

Perform the steps mentioned in Section 6.

Note:

The following instructions are displayed on the Oracle Universal Installer screen:

To complete the installation of this patch set, perform the following tasks on each node:

Log in as the root user and enter the following command to shut down the Oracle Clusterware:
```
# CRS_home/bin/crsctl stop crs
```
Run the root102.sh script to automatically start the Oracle Clusterware on the patched node:
```
# CRS_home/install/root102.sh
```

To upgrade the rest of the nodes, go to the next node and perform Steps 1 to 5 and then log in as the root user and perform the following steps:
1. Enter the following command to shut down the Oracle Clusterware:
```
# CRS_home/bin/crsctl stop crs
```
2. Run the root102.sh script to automatically start the Oracle Clusterware on the patched node:
```
# CRS_home/install/root102.sh
```
Note:
Rolling upgrade is not supported on Shared Oracle home.

5.7.2.2 Non Rolling Upgrade

For non rolling upgrade, Oracle Clusterware needs to be shut down completely.

Complete the following steps:

Note:

You must perform these steps in the order listed.

Shut down all processes in the Oracle home on each node that might be accessing a database, for example Oracle Enterprise Manager Database Control or iSQL*Plus:

$ emctl stop dbconsole
$ isqlplusctl stop

Note:

Shut down all services in the Oracle home on each node that might be accessing a database:
```
$ srvctl stop service -d db_name [-s service_name_list [-i inst_name]]
```
Shut down all Oracle RAC instances on all cluster nodes by entering the following command where db_name is the name of the database:
```
$ srvctl stop database -d db_name
```
If Automatic Storage Management instance is present, then shut down Automatic Storage Management instances on all cluster nodes by entering the following command where node is the name of the node where the Automatic Storage Management instance is running:
```
$ srvctl stop asm -n node
```
Stop all node applications on all cluster nodes by entering the following command as the root user, where node is the name of the node where the applications are running:
```
# srvctl stop nodeapps -n node
```
Shut down the Oracle Clusterware processes by entering the following command on all nodes as the root user:
```
# CRS_home/bin/crsctl stop crs
```

Complete the steps mentioned in Section 6.

Note:

The following instructions are displayed on the Oracle Universal Installer screen:

To complete the installation of this patch set, perform the following tasks on each node:

Log in as the root user and enter the following command to shut down the Oracle Clusterware:
```
# CRS_home/bin/crsctl stop crs
```
Run the root102.sh script to automatically start the Oracle Clusterware on the patched node:
```
# CRS_home/install/root102.sh
```

5.7.3 Stopping All Processes for an Oracle RAC Installation

Shut down the following Oracle Database 10g processes before installing the patch set:

Shut down all processes in the Oracle home on each node that might be accessing a database, for example Oracle Enterprise Manager Database Control or iSQL*Plus:

$ emctl stop dbconsole
$ isqlplusctl stop

Note:

Shut down all services in the Oracle home on each node that might be accessing a database:
```
$ srvctl stop service -d db_name [-s service_name_list [-i inst_name]]
```
Shut down all Oracle RAC instances on the nodes, which run from the Oracle home on which you are going to apply the patch set. To shut down all Oracle RAC instances for a database, enter the following command where db_name is the name of the database:
```
$ srvctl stop database -d db_name
```
If Automatic Storage Management instance is present, then shut down all Automatic Storage Management instances on all nodes. To shut down an Automatic Storage Management instance, enter the following command where node is the name of the node where the Automatic Storage Management instance is running:
```
$ srvctl stop asm -n node
```

Stop any listeners that are running from the Oracle home that you are patching on all nodes. To stop the listener running on a node, enter the following command, where node is the name of the node where the listener is running:

$ srvctl stop listener -n node [-l listenername]

Note:

Using a logical standby database, you can upgrade Oracle Database software and patch sets with almost no downtime. Using Data Guard SQL Apply, you can perform a rolling upgrade of the Oracle Database software from release 10.2.0.1 to the current patch set release. During a rolling upgrade, you can run different releases of Oracle Database on the primary and logical standby databases, while you upgrade them, one at a time, incurring minimal downtime on the primary database.

5.8 Back Up the System

Oracle recommends that you create a backup of the Oracle Database 10g installation before you install the patch set.

6 Installation Tasks

You can install the patch set either interactively or noninteractively. See one of the following sections for information about how to complete the installation:

To install the patch set interactively, see the "Installing the Oracle Database 10g Patch Set Interactively" section.
To install the patch set noninteractively, see the "Installing the Oracle Database 10g Patch Set Noninteractively" section.

6.1 Installing the Oracle Database 10g Patch Set Interactively

To install the Oracle Database 10g patch set interactively:

Note:

If you attempt to install this patch set in an Oracle home directory that does not contain an Oracle Database 10g release 10.2.0.1 or 10.2.0.2 installation, Oracle Universal Installer displays a warning dialog with the following error:

OUI-10091: There are no patches that need to be applied from the patch set Oracle Database 10g Release 2 Patch Set 2
10.2.0.3

The Oracle Universal Installer does not allow the installation to proceed. Click OK, then click Cancel to end the installation.

Log in as the oracle user.
If you are not installing the software on the local system then, run the following command on remote machine:
- Bourne, Bash, or Korn shell:
```
$ export DISPLAY=localhost:0.0
```
- C shell:
```
% setenv DISPLAY local_host:0.0
```
In this example, local_host is the host name or IP address of the system that you want to use to display Oracle Universal Installer (your workstation or PC).
Now to enable X applications, run the following command on the machine that you want to use to display Oracle Universal Installer (your workstation or PC):
```
$ xhost + [fully_qualified_remote_host_name]
```
Enter the following commands to start Oracle Universal Installer, where patchset_directory is the directory where you unpacked the patch set software:
```
% cd patchset_directory/Disk1
% ./runInstaller
```
On the Welcome screen, click Next.
In the Specify Home Details screen, select the name of the Oracle home that you want to update, or select the Path that you want to update from the list, then click Next.
If you are installing the patch set on an Oracle RAC cluster, click Next when the Selected Nodes screen appears.
On the Summary screen, click Install.
This screen lists all of the patches available for installation.

When prompted, run the $ORACLE_HOME/root.sh script as the root user. If you are applying the patch set to an Oracle RAC installation, then run the root.sh script on each node of the cluster.

Note:

If you are applying this patch set to an Oracle Clusterware installation, then complete all of the steps displayed on the Oracle Universal Installer screen.

The Oracle Clusterware installation instructions displayed on the Oracle Universal Installer screen are also available in the CRS_home/install/readme.txt file.

When applying this patch set on an Oracle Clusterware home, Oracle Universal Installer prompts you to run the root102.sh script from $ORACLE_HOME/install. You must run this script as the root user on all nodes.
Before you add a new node, ensure that you run rootpre.sh script as the root user on the new node.

On the End of Installation screen, click Exit, then click Yes to exit from Oracle Universal Installer.

6.2 Installing the Oracle Database 10g Patch Set Noninteractively

To install the Oracle Database 10g patch set noninteractively:

Copy the response file template provided in the response directory where you unpacked the patch set archive file.
Edit the values for all fields labeled as as described by the comments and examples in the template.

Note:
For Oracle RAC installations, make sure the CLUSTER_NODES variable specifies all of the nodes used in the original Oracle RAC installation.
To run Oracle Universal Installer, enter a command similar to the following, where response_file is the full path to the response file that you edited:
```
$ ./runInstaller -silent -responseFile response_file
```

After the installation, run the $ORACLE_HOME/root.sh script as the root user. If you are applying the patch set to an Oracle RAC installation, then run the root.sh script on each node of the cluster.

Note:

If you are applying this patch set to an Oracle Clusterware installation, then complete all the steps in the CRS_home/install/readme.txt file. You must run this script as the root user on all nodes.

7 Postinstallation Tasks

Review the information in this section before using the upgraded software. This section lists required and optional postinstallation tasks, depending on the installation type and the products that you want to use.

7.1 Upgrading Earlier Oracle Database to Oracle Database 10g Release 2 (10.2.0.3)

Review the following sections before upgrading an earlier Database to Oracle Database 10g release 2 (10.2.0.3):

7.1.1 Upgrading Earlier Oracle Database Releases to Oracle Database 10g Release 2 (10.2.0.3)

For information about upgrading Oracle Databases from an earlier Oracle Database (Oracle8i, Oracle9i, or Oracle Database 10g), see Oracle Database Upgrade Guide.

If you are upgrading an Oracle RAC database, refer to the Oracle Real Application Clusters Administration Guide as well.

7.1.2 Upgrading a Release 9.2 Database Not Using Oracle Label Security

If you want to upgrade an Oracle9i release 9.2 preconfigured database, and you are not using Oracle Label Security, complete the following steps to avoid errors during the upgrade:

Use Oracle Universal Installer release 9.2 to install Oracle Label Security using the Custom installation type.
Run the $ORACLE_HOME/rdbms/admin/catnools.sql script with the SYSDBA privilege to remove Oracle Label Security components from the database.

7.2 Upgrading Oracle Database 10g Release 10.2.0.x to Oracle Database 10g Release 10.2.0.3

See one of the following sections for upgrading an Oracle Database 10g release 10.2.0.x to Oracle Database 10g release 10.2.0.3:

7.2.1 Upgrading a Release 10.2 Database using Oracle Database Upgrade Assistant

After you install the patch set, you must perform the following steps on every database associated with the upgraded Oracle home:

Note:

If you do not run the Oracle Database Upgrade Assistant as described in this section, then the following errors are displayed:

ORA-01092: ORACLE instance terminated.

ORA-39700: database must be opened with UPGRADE option.

Log in as the Oracle software owner user.
Set the values for the environment variables $ORACLE_HOME, $ORACLE_SID and $PATH.
For single-instance installations, if you are using Automatic Storage Management, start the Automatic Storage Management instance.
For Oracle single-instance installations, start the listener as follows:
```
$ lsnrctl start
```
Run Oracle Database Upgrade Assistant either in the interactive or noninteractive mode:
Interactive mode:
Enter the following command from the command prompt:
```
$ dbua
```
Complete the following steps displayed in the Oracle Database Upgrade Assistant screen:
1. On the Welcome screen, click Next.
2. On the Databases screen, select the name of the Oracle Database that you want to update, then click Next.
  
  Note:
  For Oracle RAC, enter the SYS password to do the upgrade.
3. On the Recompile invalid objects screen, select the Recompile the invalid objects at the end of upgrade option, then click Next.
4. If you have not taken the back up of the database earlier, on the Backup screen, select the I would like to take this tool to backup the database option, mention the Path, then click Next.
5. On the Summary screen, check the summary, then click Finish.
6. On the End of upgradation screen, click Exit, then click Yes to exit from Oracle Database Upgrade Assistant.
Noninteractive mode:
Enter the following command to upgrade Oracle Database using Oracle Database Upgrade Assistant in noninteractive mode:
```
$ dbua -silent -dbname $ORACLE_SID -oracleHome 
$ORACLE_HOME -sysDBAUserName UserName -sysDBAPassword SYS_password 
-recompile_invalid_objects true
```
If you are using the Oracle Recovery Manager catalog, enter the following command:
```
$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;
```
For Oracle RAC installations, start any database services that you want to use by entering the following command:
```
$ srvctl start service -d db_name -s service_name
```

7.2.2 Manually Upgrading a Release 10.2 Database

Complete the following sections to upgrade an Oracle Database 10g release 10.2.0.x to Oracle Database 10g release 10.2.0.3:

7.2.2.1 Required Preupgrade Checks

Check the SYSTEM tablespace size and set the initialization parameters.

Check the SYSTEM Tablespace Size
If JServer is part of the installation, ensure that there is at least 50 MB of free space allocated to the SYSTEM tablespace or autoextend space in your SYSTEM tablespace prior to upgrading.

Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE Initialization Parameters

Set the value of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters as follows:

Start the listener before attempting to connect to the database:
```
$ lsnrctl start 
```
Start the database with the NOMOUNT option:
```
SQL> STARTUP NOMOUNT
```
If necessary, enter the following command to determine whether the system uses an initialization parameter file (initsid.ora) or a server parameter file (spfiledbname.ora):
```
SQL> SHOW PARAMETER PFILE; 
```
This command displays the name and location of the server parameter file or the initialization parameter file.

Determine the current values of these parameters:

SQL> SHOW PARAMETER SHARED_POOL_SIZE
SQL> SHOW PARAMETER JAVA_POOL_SIZE

If the system is using a server parameter file:
If necessary, set the value of the SHARED_POOL_SIZE initialization parameter to at least 150 MB:
```
SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile; 
```
If necessary, set the value of the JAVA_POOL_SIZE initialization parameter to at least 150 MB:
```
SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile; 
```
If the system uses an initialization parameter file, if necessary change the values of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters to at least 150 MB in the initialization parameter file (initsid.ora).

If you use Automatic Shared Memory Management, ensure that the value of the SGA_TARGET initialization parameter size is at least 50 MB greater than the sum of the values of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters.

Note:

The value of the SGA_TARGET parameter depends on the environment. If you receive a system error when you restart the database, increase the value of the SGA_TARGET parameter to the value specified in the error.

Shut down the database:
```
SQL> SHUTDOWN
```

7.2.2.2 Upgrading a Release 10.2 Database

After you install the patch set, you must perform the following steps on every database associated with the upgraded Oracle home:

Note:

If you do not run the catupgrd.sql script as described in this section and you start up a database for normal operation, then ORA-01092: ORACLE instance terminated. Disconnection forced errors will occur and the error ORA-39700: database must be opened with UPGRADE option will be in the alert log.

Log in as the Oracle software owner user.
For Oracle RAC installations, start listener on each node of the cluster as follows:
```
$ srvctl start listener -n node
```
If you are using Automatic Storage Management, start the Automatic Storage Management instance.
For single-instance installations, start the listener as follows:
```
$ lsnrctl start
```
For single-instance installations, use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
```
$ sqlplus /nolog 
SQL> CONNECT SYS/SYS_password AS SYSDBA
```
For Oracle RAC installations:
1. Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
```
$ sqlplus /nolog 
SQL> CONNECT SYS/SYS_password AS SYSDBA
SQL> STARTUP NOMOUNT
```
2. Set the
  
  来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/7176288/viewspace-917709/，如需转载，请注明出处，否则将追究法律责任。