| |
Oracle9i
Patch Set Notes
Release 2 (9.2.0.7) Patch Set 6 for HP-UX Itanium
March 2006
These patch set notes accompany the Oracle9i release 2 (9.2.0.7) patch set.
This document contains the following sections:
- Patch Set Overview
- Oracle Universal Installer Version Requirements
- Patch Set Documentation
- System Requirements
- Review Changes in Oracle Text Filtering Technology
- Preinstallation Tasks
- Installation Tasks
- Postinstallation Tasks
- Removing the Patch Set Software
- Reinstalling the Patch Set Software
- Known Issues
- Fixed Platform-Specific Bugs
- Patch Set Components
- Documentation Accessibility
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 patch sets include only low impact fixes, you are not required to certify applications or tools against the server unless directed to by the operating system vendor.
Patch sets are cumulative. Patch set release 9.2.0.7 includes all fixes in patch sets 9.2.0.7 and earlier as well as new fixes for patch set 9.2.0.7. This means that unless the patch set documentation indicates otherwise, you can apply this patch set to any earlier release 9.2 installation. You do not have to install intermediate patch sets.
Patch sets contain generic fixes that apply to all platforms. Patch sets may also include additional platform-specific patches.
| Note: The 32-bit version of the patch set must be installed only on the 32-bit version of the database software, regardless of whether the operating system is 32-bit or 64-bit. The 64-bit version of the patch set must be installed only on the 64-bit version of the database software that runs on the 64-bit operating system. |
This patch set includes Oracle Universal Installer release 10.1.0.4. You must use this Oracle Universal Installer to install this patch set and not the Installer from the 9.2.0.x maintenance release media or Oracle home.
This is not a complete software distribution. You must install it in an existing Oracle9i release 2 (9.2.0.x.x) installation. Users applying this patch set must use Oracle Universal Installer release 10.1.0.4 (provided as part of this patch set) or later to ensure that their Oracle home can be patched in the future. Oracle Universal Installer release 10.1.0.4 is also installed when you install this patch set.
There are two documents related to this release of the Oracle9i release 2 patch set:
- Oracle9i Patch Set Notes, Release 2 (9.2.0.7) Patch Set 6 for HP-UX Itanium (this document)
This document provides:
- System requirements and information about how to install or reinstall the patch set
- A list of all bugs fixed to date that are specific to Oracle9i release 2 for HP-UX Itanium
- A list of known issues relating to Oracle9i release 2 for HP-UX Itanium
- Oracle9i List of Bugs Fixed, Release 2 (9.2.0.7) Patch Set 6
The List of Bugs Fixed is a list of all generic bugs related to Oracle9i release 2 that have been fixed in this release.
Both of these documents are included with the patch set. The Oracle9i List of Bugs Fixed is also available on OracleMetalink, from document 189908.1,
ALERT: Oracle9i Release 2 (9.2) Support Status and Alerts at:
ALERT: Oracle9i Release 2 (9.2) Support Status and Alerts at:
To locate document 189908.1:
- Click Advanced at the top of the OracleMetalink page.
- Enter 189908.1 in the Document ID field, then click Submit.
The following are the system requirements for this patch set:
- Operating System
HP-UX version B.11.22
- Oracle9i
Oracle9i release 2 (9.2.0.2.0) or later
Beginning with patch set release 9.2.0.7, INSO software is no longer shipped with Oracle Text. It is replaced with Verity KeyView Export from Verity, Inc. There are a number of differences between the old and the new filters. If you intend to use Oracle Text, review document 296405.1 on the OracleMetalink Web site:
To locate document 296405.1:
- Click Advanced at the top of the OracleMetalink page.
- Enter 296405.1 in the Document ID field, then click Submit.
Complete the following preinstallation tasks before installing the patch set:
- Review Known Preinstallation Issues
- Preinstallation Considerations for Oracle Real Application Clusters
- Identify the Oracle9i Installation
- Check Postrelease Updates
- Download and Extract the Installation Software
- Set the ORACLE_HOME and ORACLE_SID Environment Variables
- Shut Down Oracle Databases
- Stop All Processes
- Back Up the System
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.
- Database Upgrade for Oracle E-Business Suite
- Upgrade and SYS Schema
- Patch Set Application with Physical or Logical Standby Databases in Place
- Upgrading Preconfigured Standard Edition Databases
- Real Application Clusters Using Both UDP and HMP Protocols
- Oracle Streams
- Oracle Data Guard
- Oracle Advanced Queuing
- Event 10499: NUMBER Datatypes
- Oracle XDK
- XML DB
- PL/SQL Cursor Caching
- Oracle Directory Manager is Not Supported
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 at:
All other customers wanting to upgrade their databases directly to this patch set should read Upgrading Directly to a 9.2.0 Patch Set available on OracleMetalink from document 214887.1.
This is a generic issue applicable to the upgrade mode, for example, ALTER DATABASE OPEN MIGRATE. During an upgrade from release 9.2.0.1 or later, the catpatch.sql script can take a long time if there are statistics for the SYS schema. Delete the statistics on all of the objects in the SYS schema, and then recollect the statistics after normal database open, if necessary.
To drop and re-create the statistics, enter the following commands in SQL*Plus:
SQL> EXECUTE DBMS_STATS.DELETE_SCHEMA_STATS('SYS');
SQL> EXECUTE DBMS_STATS.GATHER_SCHEMA_STATS('SYS');
For information about applying a patch set to a current release of Oracle9i release 2 for a configuration that includes one or more physical standby databases, refer to notes available in OracleMetaLink document 187242.1.
If you are using an Oracle9i release 2 (9.2) preconfigured Standard Edition database, then the database contains the following components that are not supported by the Standard Edition:
- Oracle Data Mining
- Oracle OLAP Catalog
- Oracle OLAP Analytic Workspace
- Oracle OLAP API
- Spatial
The catpatch.sql script does not run the patch scripts for these components. It sets the component STATUS to OPTION OFF in the DBA_REGISTRY view. The original versions of the dictionary objects for the components remain in the database but the catpatch.sql script does not apply the patch to them.
The oracle executable installed by this patch uses UDP as the default interconnect protocol. To use HMP as the interconnect protocol for RAC installations, perform the following steps:
- Download and install HMP.
| See Also: Information about downloading and installing HyperFabric is available at the following URL: Information about configuring and using HMP over HyperFabric is available at the following URL: |
- Download the PHKL_28120 kernel patch from the following URL:
4.
- Install the PHKL_28120 kernel patch.
- Set the environment.
- Shutdown the database.
- Enter the following commands:
9. $ cd $ORACLE_HOME/rdbms/lib
10. $ make -f ins_rdbms.mk ipc_hms ioracle
All databases that use any features of Oracle Streams must be upgraded to release 9.2.0.2 or later. Operation between release 9.2.0.1 and release 9.2.0.2 is not supported for databases using Oracle Streams features.
Before you install the patch set software, review Oracle MetaLink note 283565.1.
Several known issues relate to the following components of Oracle Data Guard:
- Redo Apply (Physical Standby Databases)
- SQL Apply (Logical Standby Databases)
- Data Guard Broker
- Data Guard Broker Failover
Refer to OracleMetaLink document 259804.1 for a complete set of release notes applicable to Oracle Data Guard in Oracle9i release 2.
Before you install the patch set software, review Oracle MetaLink note 283565.1.
Customers running Oracle Applications release 11.5.7 or 11.5.8 with Advanced Queuing configured with multiconsumer queues may encounter corruption problems after upgrading their database to 9.2.0.x from any Oracle8i database.
| Note: Refer to Oracle MetaLink note 231074.1 for more information. |
Event 10499 was introduced in release 9.2.0.3 to allow customers to revert to the earlier behavior of NUMBER datatypes that have no explicit setting of their scale value. Any nonzero setting of the event level enables the old behavior.
Before the introduction of this event, server code could return zero for the scale if a NUMBER datatype was created without specifying the scale. Other code paths would return -127. With this event, all code paths return -127, as this is the correct behavior.
Client applications may rely on the previous (incorrect) behavior. Typically, client applications will test for a scale of -127 to distinguish between NUMBER and FLOAT datatypes. It is not sufficient to test the scale alone to distinguish between these two datatypes. You must test for a scale of -127 and a nonzero precision to identify a FLOAT.
Client applications that rely on the old behavior can still work as before if the event is set. However, these applications must be corrected before upgrading to the next major release of the Oracle database.
The Oracle9i release 2 (9.2.0.7) patch set contains XDK release 9.2.0.9.
XML DB users must use DB release 9.2.0.3 or later. Earlier releases are no longer supported.
In release 9.2.0.4 and earlier, the maximum number of cursors that could be cached for fast lookup by PL/SQL was bounded by the value of the OPEN_CURSORS initialization parameter. If you currently have this parameter set to a high value (for example, greater than 1000), it might be causing large numbers of PL/SQL cursors to be cached in the shared pool. This could lead to issues with memory management, frequent reloading of library cache objects, and ORA-04031 errors.
Starting with release 9.2.0.5, the SESSION_CACHED_CURSORS initialization parameter now determines the upper bound for PL/SQL cursor caching instead of the OPEN_CURSORS initialization parameter.
Most users do not need to modify the value of either of these parameters. If the SESSION_CACHED_CURSORS parameter value is greater than the OPEN_CURSORS parameter value, then this change has no performance affect on your system.
However, if the SESSION_CACHED_CURSORS parameter value is zero or a value significantly lower than the OPEN_CURSORS parameter value, and you want to cache PL/SQL cursors for optimal performance, then increase the SESSION_CACHED_CURSORS parameter value appropriately.
This issue is tracked with Oracle bug 3150705.
This release does not support Oracle Directory Manager due to a Java VM issue with JDK 1.4 on this platform.
Use one of the following methods to administer Oracle Internet Directory on this platform, till the patch is available:
- Use Oracle Directory Manager on any other 9.2.0.x platform
- Use command-line tools
| See Also: Oracle Internet Directory Administrator's Guide for more information about using command-line tools. |
This issue is tracked with Oracle bug number 2803056.
If you plan to install this patch in an Oracle Real Application Clusters environment, read the following section before proceeding:
This patch set enables you to install the included patches on multiple nodes in a cluster if release 9.2.0.1 or higher is already installed on those nodes. Oracle Universal Installer detects whether the system where you are installing the software is part of a cluster environment. If it is, then the Oracle Universal Installer displays the available nodes from the cluster.
| Note: It is important that you install the patch set on the same set of nodes, which had the base release installation. Choosing a different set of nodes during the patch set installation than were chosen during the base release installation will cause unwanted results in your Real Application Clusters environment, as some nodes will be upgraded to the new software versions, while others will not. |
This is not a complete software distribution. You must install it in an existing Oracle9i Oracle home. To identify Oracle home directories, view the /etc/oratab file.
If you are installing this patch set on an existing Real Application Clusters (RAC) installation, you must run the Installer from the same node from which you performed the initial installation.
Before installing this patch set in a production environment, review document 189908.1, ALERT: Oracle9i Release 2 (9.2) Support Status and Alerts, available on the OracleMetaLink Web site at:
To locate this document:
- Click Advanced at the top of the OracleMetalink page.
- Enter 189908.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.
To download and extract the patch set installation software:
- Download and extract the p4163445_9207_HPUX-IA64.zip patch set installation archive to a directory that is not the Oracle home directory or under the Oracle home directory. For example, Oracle_patch.
- Enter the following commands to unzip and extract the installation files:
3. $ unzip p4163445_9207_HPUX-IA64.zip
4.
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 Oracle9i installation that you want to upgrade is installed, and sid is the SID of the database that you want to upgrade.
Shut down any existing Oracle database instances with normal or immediate priority. On RAC systems, shut down all instances on each node.
Stop all listener and other processes running in the Oracle home directory where you want to install the patch set.
Oracle recommends that you create a backup of the Oracle9i installation before you install the patch set.
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 Patch Set Interactively" section.
- To install the patch set noninteractively, see the "Installing the Patch Set Noninteractively" section.
| Note: You must use Oracle Universal Installer release 10.1.0.4 or later to install this patch set. |
| Note: If you attempt to install this patch set in an Oracle home directory that does not contain an Oracle9i installation, the Installer displays a warning dialog with the following error: There are no patches that need to be applied from the patchset Oracle9i patch set 9.2.0.7.0 The Oracle Universal Installer does not allow the installation to proceed. Click OK, then click Cancel to end the installation. |
The following procedure describes how to install the patch set interactively:
- Log in as the Oracle software owner (typically oracle).
- If you are not installing the software on the local system, enter the following command to direct X applications to display on the local system:
· Bourne, Bash, or Korn shell:
· $ DISPLAY=local_host:0.0 ; export DISPLAY
·
· 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).
Enter following commands to start the Oracle UniversalInstaller where patchset_directory is the directory where you unzipped the patch set software:
$ patchset_directory/Disk1
$ ./runInstaller
On the Welcome screen, click Next.
On the Specify File Locations screen, click Browse next to the Path field in the Source section.
Select the products.xml file from the stage directory where you unpacked the patch set files, then click Next. For example:
patchset_directory/Disk1/stage/products.xml
In the Name field in the Destination section, select the name of the Oracle home that you want to update from the drop down list, then click Next.
If you are installing the patch set on an RAC cluster, click Next when the Selected Nodes screen appears.
| Note: The Selected Nodes screen lists the existing Oracle9i RAC release 2 (9.2) nodes. The first node in the list is the node from where Oracle9i RAC release 2 (9.2) was installed. You must install the patch set software from this node. If this is not the node where you are running the Installer, exit the Installer and install the patch set software from the first node in the list of nodes. |
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 RAC installation, then run the root.sh script on each node of the cluster.
On the End of Installation screen, click Exit, then click Yes to exit from the Installer.
The following procedure describes how to install the patch set noninteractively:
- Log in as the Oracle software owner (typically oracle).
- 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 <Value Required> as described by the comments and examples in the template.
- To run the Installer, enter a command similar to the following, where response_file is the full path to the response file that you edited:
5. $ cd patchset_directory/Disk1
6. $ ./runInstaller -silent -responseFile response_file
7.
- After the installation, run the $ORACLE_HOME/root.sh script as the root user. If you are applying the patch set to an RAC installation, then run the root.sh script on each node of the cluster.
- Log in as the Oracle software owner (typically oracle).
- Change directory to the $ORACLE_HOME/oui/bin directory.
- Enter the following command to start the Installer:
d. % cd $ORACLE_HOME/oui/bin
e. % ./runinstaller
f.
- Click Browse for the Source... entry field.
- Navigate to the stage directory where you unpacked the patch set tar file. For example, navigate to /Disk1/stage/.
- Select the products.xml file.
- Click Next.
The Available Products screen appears and displays the following products to install:
o Oracle Universal Installer
o Oracle9i release 2 R2 Patch Set
o Oracle Precompilers
Select Oracle Precompilers and click Install.
On the Summary screen, click Install.
On the End of Installation screen, click Exit, then click Yes to exit from the Installer.
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.
- Upgrading Databases from Previous Releases Directly to Oracle9i Release 2 (9.2.0.7)
- Required Postinstallation Tasks
- Pro*COBOL Postinstallation Tasks
- mod_plsql Postinstallation Steps
- Upgrade Ultrasearch Instances
To upgrade Oracle databases from a previous release directly to Oracle9i release 2 (9.2.0.7) follow the instructions in OracleMetalink note 214887.1 Upgrading Directly
to a 9.2.0 Patch Set.
to a 9.2.0 Patch Set.
| See Also: For more information about upgrading a database, see the Oracle9i Database Migration guide. |
Complete the following tasks after installing the patch set software:
- Check Tablespace Sizes and Set Parameter Values
- Upgrade the Database
- Download the Latest Version of OPatch
Review the following sections before upgrading a database.
If JServer is part of the installation ensure that there is at least 10 MB of free space allocated to the SYSTEM tablespace.
For RAC installations, ensure that there is at least 50 MB of free space allocated to the XDB tablespace.
Users who have JVM (Java enabled) or JVM and XDB installed on their 9.2.0.1 databases should make sure that the init.ora parameters SHARED_POOL_SIZE and JAVA_POOL_SIZE are each 150 MB or more before running the catpatch.sql upgrade script. Failure to do so could result in an unrecoverable memory failure while running of the script. Please note that JVM and XML DB was shipped as part of the default 9.2.0.1 seed database, and will be present unless the user explicitly installed a 9.2.0.1 instance without them.
Set the value of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters as follows:
- Start the database:
2. SQL> STARTUP
3.
- 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):
5. SQL> SHOW PARAMETER PFILE;
6.
This command displays the name and location of the server parameter file or the initialization parameter file.
- Determine the current values of these parameters:
8. SQL> SHOW PARAMETER SHARED_POOL_SIZE
9. SQL> SHOW PARAMETER JAVA_POOL_SIZE
10.
- 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:
b. SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;
c.
- If necessary, set the value of the JAVA_POOL_SIZE initialization parameter to at least 150 MB:
e. SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile;
f.
- 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).
- Shut down the database:
14.SQL> SHUTDOWN
15.
After you install the patch set, you must perform the following steps on every database associated with the upgraded Oracle home:
- Log in as the Oracle software owner (typically oracle).
- For RAC installations, start the Global Services Daemon (GSD) on each node of the cluster as follows:
3. $ gsdctl start
4.
- Start the Oracle Net listener as follows:
6. $ lsnrctl start
7.
| Note: For RAC installations, start the listener on each node of the cluster. If you are using the Oracle OLAP option, make sure that the listener is running. |
- For single-instance installations, use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
9. $ sqlplus /nolog
10.SQL> CONNECT / AS SYSDBA
11.
- For RAC installations:
- Start the database as follows, where db_name is the database name:
b. $ srvctl start database -d db_name
c.
- Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
e. $ sqlplus /nolog
f. SQL> CONNECT / AS SYSDBA
g.
- Set the CLUSTER_DATABASE initialization parameter to FALSE:
i. SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;
j.
| Note: If the system uses an initialization parameter file, change the value of the CLUSTER_DATABASE initialization parameter to FALSE in the initialization parameter file (initsid.ora). |
- Exit SQL*Plus and shut down the database:
l. SQL> EXIT
m. $ srvctl stop database -d db_name
n.
- Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
p. $ sqlplus /nolog
q. SQL> CONNECT / AS SYSDBA
r.
- Enter the following SQL*Plus commands:
14.SQL> STARTUP MIGRATE
15.SQL> SPOOL patch.log
16.SQL> @?/rdbms/admin/catpatch.sql
17.SQL> SPOOL OFF
18.
- Review the patch.log file for errors and inspect the list of components that is displayed at the end of catpatch.sql script.
This list provides the version and status of each SERVER component in the database.
- If necessary, rerun the catpatch.sql script after correcting any problems.
- Restart the database:
22.SQL> SHUTDOWN
23.SQL> STARTUP
24.
- Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.
26.SQL> @?/rdbms/admin/utlrp.sql
27.
- For RAC installations:
- Set the CLUSTER_DATABASE initialization parameter to TRUE:
b. SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;
| Note: If the system uses an initialization parameter file, change the value of the CLUSTER_DATABASE initialization parameters to TRUE in the initialization parameter file (initsid.ora). |
- Restart the database:
d. SQL> SHUTDOWN
e. SQL> STARTUP
f.
- If you are using the Oracle Recovery Manager catalog, enter the following command:
30.$ rman catalog username/password@alias
31.RMAN> UPGRADE CATALOG;
32.
- If Oracle Internet Directory release 9.2.0 is installed in the Oracle home, run the following shell script:
| Note: Make sure that the database and database listener are running, and all parameters for the oidpatchca.sh script are specified before running the script. |
$ORACLE_HOME/bin/oidpatchca.sh
-connect Connect_String
-lsnrport Listener_Port
-systempwd SYSTEM_Password
-odspwd ODS_Password
-sudn Super-User_DN
-supwd Super-User_Password
-dippwd Password_to_register_DIP_Server
In the preceding example, Password_to_register_DIP_Server must conform to the password policy in the Oracle Internet Directory server.
You must install OPatch version 1.0.0.0.53 in order to apply patches on top of 9.2.0.7. Download and unzip patch 2617419.
| See Also: OracleMetaLink Note 224346.1 and Note 189489.1 for more information. |
Perform the following steps before using the Pro*COBOL precompiler:
- Install the COBOL compiler in /opt/lib/cobol directory, if you have not installed it already
- Set the value of the COBDIR variable to /opt/lib/cobol.
- Include $COBDIR/lib:$LD_LIBRARY_PATH in the LD_LIBRARY_PATH environment variable setting.
- Include /opt/lib/cobol/bin/:$PATH in the PATH environment variable setting.
Complete the following steps only if mod_plsql is installed. The following steps should be repeated with all the database instances associated with this 9.2.0.7 Oracle home.
- Run owa_patch.sql to update owa packages from mod_plsql patch directory:
· Change to the $ORACLE_HOME/Apache/modplsql/patch directory. For example,
· $ cd $ORACLE_HOME/Apache/modplsql/patch
· Connect to the database instance as sysdba:
· $ sqlplus " / as sysdba"
· SQL> @@owa_patch.sql
Check owa_patch_sid.log file for any errors.
Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.
SQL> @?/rdbms/admin/utlrp.sql
Perform either of the following steps if you want ultrasearch to work with filter support:
- Add the following line to $ORACLE_HOME/ultrasearch/data/config/crawler.dat file, after the installation is over:
· FILTER_PATH=$ORACLE_HOME/ctx/bin/ctxhx
- Execute $ORACLE_HOME/ultrasearch/admin/wk0install.sql with the following 8 parameters:
| Parameters | Meaning of the parameter | Values in install area |
| SYS | sys user | SYS |
| SYSPW | sys password | welcome |
| WKSYSPW | wksys password | WKSYS |
| WK_TABLESPACE | wksys table space | DRSYS |
| WK_TEMPTABLESPACE | wksys temp tablespace | TEMP |
| CONN_STRING | DB connect string | @or123 |
| PORTAL_USER | portal user | PORTAL |
| LAUNCH_ANYWHERE | yes/no | yes |
Starting in 9.2.0.7.0, there is a new script called catbkout.sql. This script enables the user to restore the Oracle9i installation of the database back to the original 9.2 patch release (as long as it is 9.2.0.4 or greater) that the user backed up before applying the patch set. Perform the following steps for backing out from the 9207 patch release:
- Before restoring the Oracle home to the original release, perform the following steps:
2. $ sqlplus /nolog
3. SQL> connect / AS SYSDBA
4. SQL> SHUTDOWN
5. SQL> STARTUP MIGRATE
6. SQL> SPOOL catbkout.out
7. SQL> @?/rdbms/admin/catbkout.sql
8. SQL> SHUTDOWN IMMEDIATE
9.
- Restore the Oracle9i installation and Central Inventory (see /etc/oraInst.loc) that you backed up before applying the patch set
- After restoring the original Oracle home, perform the following steps:
12.$ sqlplus /nolog
13.SQL> connect / AS SYSDBA
14.SQL> STARTUP MIGRATE
15.SQL> SPOOL catpatch.out
16.SQL> @?/rdbms/admin/catpatch.sql
17.
- If Oracle Spatial is installed with the database, perform the following steps:
19.SQL> alter session set current_schema = mdsys;
20.SQL> @?/md/admin/prvtsidx.plb
21.SQL> @?/md/admin/prvt3glh.plb
22.SQL> @?/md/admin/prvt3gl.plb
23.SQL> alter session set current_schema = sys;
24.
- Shut down the database:
26.SQL> SHUTDOWN IMMEDIATE
27.
- Start the database and recompile the remaining invalid objects:
29.SQL> STARTUP
30.SQL> @?/rdbms/admin/utlrp.sql
31.
- Review catbkout.out and catpatch.out for errors
If necessary, you can reinstall a patch set that has been applied to an Oracle9i installation. You must reinstall the patch set interactively.
To reinstall the patch set:
- Log in as the Oracle software owner (typically oracle).
- If you are not installing the software on the local system, enter the following command to direct X applications to display on the local system:
· Bourne, Bash, or Korn shell:
· $ DISPLAY=local_host:0.0 ; export DISPLAY
·
· 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).
Enter the following commands to start Oracle Universal Installer, where patchset_directory is the directory where you unzipped the patch set software:
$ cd patchset_directory/Disk1
$ ./runInstaller
If you are installing the patch on an RAC cluster, click Next on the Selected Nodes screen.
On the Specify File Locations screen, click Browse next to the Path field in the Source section.
Select the products.xml file from the stage directory where you unpacked the patch set files. For example:
patchset_directory/Disk1/stage/products.xml
Select the Oracle home that you want to upgrade in the Name field in the Destination section, then click Next.
| Note: If you are not sure of the name of the Oracle home, click Installed Products to determine the name of the Oracle home that you want to upgrade. |
The Available Product Component screen appears. This screen contains a list of all components that have been patched by the original patch set installation. These components are grayed out, indicating they cannot be selected for installation.
Expand the nodes for each component listed in the tree to display the patch that corresponds to each component.
Select the patches that you want to install.
When you select a patch, the Install Status column changes to Reinstall.
Repeat the process for each patch bundled in the patch set, then click Next.
On the Summary screen, verify the list of patches to be reinstalled, then click Install.
On the End of Installation screen, click Exit, then click Yes to exit from the Installer.
Review the following known issues after you apply the patch set.The following known issues apply to this patch set release:
- Procedural Gateway for APPC or Transparent Gateway for IBM DRDA: Unspecified Error Message
- Oracle Procedural Gateway for APPC Configuration Parameters
- Bug 2602782
- Bug 3259636
- Bug 3785754
- Bug 4270038
During the installation of Procedural Gateway for APPC or Transparent Gateway for IBM DRDA, you may encounter an error message regarding an unspecified target of the makefile. The error message can be ignored. The following is an example of a message that can be ignored:
Error while invoking target <blank> of makefile
/oracle/9.2.0.7/gateway/lib/gateway.mk
The following is an example of a valid error message. Notice that the target of the makefile is identified. Messages similar to the following should not be ignored, and you should contact Oracle Support Services.
Error while invoking target install of makefile
/oracle/9.2.0.7/gateway/lib/gateway.mk
If you use Oracle Procedural Gateway for APPC, comment out the following parameters if they are present in the gateway shell script or initsid.ora files:
- FDS_CLASS
- FDS_CLASS_VERSION
- FDS_INSTANCE
Scrollable ResultSet returns 3 times NCHAR character byte size when database Ncharset is UTF8. This problem occurs only with the JDBC Thin driver.
If you use DBCA to create a new database using the seed database option, some of the components will be from an older version. This is because the seed database was created before the patch release.
To update all the components, ensure that you have followed the steps described in the "Upgrade the Database" section .
If you are using Oracle Streams, SQL Apply with a logical standby database, or the LogMiner query tool using the DICT_FROM_REDO_LOGS option, you might see a warning similar to the following when you run the catpatch.sql script:
***WARNING*** At 21-SEP-04 09:52:09 problems related to bug 3785754 were encountered. See Patch or Upgrade Notes.
Call Oracle support.
This warning indicates that problems were detected in the LogMiner dictionary. See Oracle MetaLink note 283565.1 for information about these problems.
Depending on the application that you are running, do the following:
- Oracle Streams
Destroy and re-create captures.
- Logical Standby
Reinstantiate the standby database.
If it is not practical to take these actions, contact Oracle Support for alternative instructions to repair the LogMiner dictionary.
| Note: If you receive this warning, you must fix the problems in the LogMiner dictionary before resuming normal operations. If you do not immediately fix the problems, you may not be able to fix the problems in the future. |
When using Database Configuration Assistant in standalone mode to create a database, the following error will occur:
ORA-29807: specified operator does not exist
Click Ignore.
The following table is a cumulative list of the platform-specific bugs fixed in all Oracle9i patch sets to date:
| Fixed in Release | Bug Number | Description |
| 9.2.0.4 | 2280360 | POLL() CAN NOT HANDLE SB4MAXVAL |
| 9.2.0.4 | 2821953 | SCHED_NOAGE FUNCTIONALITY ABSENT FROM 9202 IPF RELEASE |
| 9.2.0.4 | 3082649 | DBCA FAILED TO RUN DUE TO NOCLASSDEFFOUNDERROR |
| 9.2.0.5 | 3469726 | HP ITANIUM PROCOB MODULES INADEQUATE |
| 9.2.0.6 | 4274400 | COMPILER WARNINGS WHILE RELINKING ORACLE EXECUTABLE ON HP-UX ITANIUM |
| 9.2.0.6 | 4778209 | DIFFERENT SYSCALLS USED BY SETTING DB_FILE_MULTIBLOCK_ =16 OR 32 |
| 9.2.0.7 | 4367087 | FIX FOR GENERIC 2355062 NOT IN 9206 ON HP UX ITANIUM |
