Oracle9i Patch Set Notes Release 2 (9.2.0.8) Patch Set 7 for Microsoft Windows (64-Bit) on Intel Itanium |
|
Oracle9i
Patch Set Notes
Release 2 (9.2.0.8) Patch Set 7 for Microsoft Windows (64-Bit) on Intel Itanium
August 2006
These patch set notes accompany the Oracle9i release 2 (9.2.0.8) patch set.
This document contains the following sections:
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 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.8 includes all fixes in patch sets 9.2.0.8 and earlier as well as new fixes for patch set 9.2.0.8. 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: Oracle provides both 32-bit and 64-bit versions of Oracle9i for Windows. Currently, the 32-bit version of the patch set must only be installed on the 32-bit version of the database. The 64-bit version of the patch set must only be installed on the 64-bit version of the database. |
For a list of products included in this patch set, see the "Patch Set Components" section.
See Also: Oracle9i Database and Client Release Notes for Windows (part number B10694-02) for a list of components that are not supported on 64-bit Windows |
2 Oracle Universal Installer Version Requirements
This patch set includes Oracle Universal Installer release 10.1.0.5. You must use this Oracle Universal Installer to install this patch set and not Oracle Universal 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.5 (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.5 is also installed when you install this patch set.
3 Patch Set Documentation
There are two documents related to this release of the Oracle9i release 2 patch set:
-
Oracle9i Patch Set Notes, Release 2 (9.2.0.8) Patch Set 7 for Microsoft Windows (64-Bit) (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 Microsoft Windows (64-Bit)
-
A list of known issues relating to Oracle9i release 2 for Microsoft Windows (64-Bit)
-
-
Oracle9i List of Bugs Fixed, Release 2 (9.2.0.8) Patch Set 7
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:
http://metalink.oracle.com
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.
4 System Requirements
The following are the system requirements for this patch set:
-
System Architecture:
Itanium 2 or higher
-
Operating System
-
Windows XP 64-bit Edition Version 2003
-
Windows Server 2003 Datacenter Edition for 64-bit Itanium 2 Systems
-
Windows Server 2003 Enterprise Edition for 64-bit Itanium 2 Systems
-
-
Oracle9i
Oracle9i release 2 (9.2.0.2.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 Patch Set Application with Physical or Logical Standby Databases in Place
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.
5.1.2 Notes to OLAP users
Anyone desiring to use the OLAP option must have the Enterprise Edition of 9.2.0.1.0 with the OLAP option installed as their original base release, prior to installing any of the 9i patch sets, up to and including 9.2.0.8.0. Oracle highly recommends the Data Warehouse configuration type to optimize the database for OLAP.
5.1.3 Upgrading Preconfigured Standard Edition Databases
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
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.
5.1.4 Oracle Streams
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 OracleMetaLink note 283565.1.
5.1.5 Oracle Data Guard
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 OracleMetaLink note 283565.1.
5.1.6 Oracle Advanced Queuing
There are two known issues while upgrading from Oracle8i to Oracle9i release 2:
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 from any Oracle8i database to 9.2.
Note: Refer to OracleMetalink note 231074.1 for more information. |
Oracle Streams Advanced Queuing (AQ) propagations that were previously scheduled must be unscheduled before upgrading an Oracle8i database. To unschedule AQ propagations, run the DBMS_AQADM.UNSCHEDULE_PROPAGATION PL/SQL
procedure.
See Also: PL/SQL Packages and Types Reference for more information about this procedure |
5.1.7 Oracle Data Mining
Oracle Data Mining customers must ensure that the Oracle Data Mining account (ODM) is unlocked before applying the patch set. If the ODM account is locked, the patch installation generates an error and one of the Oracle Data Mining tables will be empty.
5.1.8 Event 10499: NUMBER Datatypes
Event 10499 was introduced in release 9.2.0.4.1 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.
5.2 Review Changes in Oracle Text Filtering Technology
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:
http://metalink.oracle.com
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.
5.3 Creating a Database with Database Configuration Assistant
During database creation using Database Configuration Assistant, you may encounter an ORA-01430 error message. This error message can be ignored. The following is an example error message:
(SDO_ROOT_MBR mdsys.sdo_geometry) * ERROR at line 2: ORA-01430: column being added already exists in table
This issue is tracked with Oracle bug 3955522.
5.4 Preinstallation Considerations for Oracle Real Application Clusters
If you plan to install this patch in an Oracle Real Application Clusters environment, read the following section before proceeding:
5.4.1 Preinstallation Considerations for Oracle Real Application Clusters
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.
Oracle provides clusterware and a cluster file system for Real Application Clusters running on Windows platforms. Patches to these components are provided in a separate patch (Patch 4374611). You must install this patch separately from the 9.2.0.8 patch set.
To locate this patch on OracleMetaLink:
-
Click Patches from the left-hand column.
-
Enter the patch number 4374611 in the search field.
-
Click Search.
OracleMetaLink is available at the following URL:
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. |
5.5 Identify the Oracle9i Installation
This is not a complete software distribution. You must install it in an existing Oracle9i Oracle home. To identify Oracle home directories, use Oracle Universal Installer. From the Welcome screen, click Installed Products, then click Environment tab.
If you are installing this patch set on an existing Oracle RAC installation, you must run Oracle Universal Installer from the same node from which you performed the initial installation.
5.6 Check Postrelease Updates
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:
http://metalink.oracle.com
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.
5.7 Download and Extract the Installation Software
Download and extract the p4547809_9208_WINNT64.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.
5.8 Shut Down Oracle Databases
Shut down any existing Oracle database instances with normal or immediate priority. On Oracle RAC systems, shut down all instances on each node.
5.9 Stop All Processes
Stop all listener and other processes running in the Oracle home directory where you want to install the patch set.
When performing an Oracle RAC installation, shut down all Oracle services except the following services, if present:
-
Oracle Object Service
-
OracleClusterVolumeService
-
OracleCMService9i
6 Migration Tasks
The procedures to migrate a pre-Oracle9i release 2 database are described in Section 5, "Migration" of Oracle9i Database and Client Release Notes for 64-Bit Windows (part number B10694-02).
The following procedures describe how to migrate an Oracle database version 7 for 32-bit Windows to an Oracle9i release 2 release 2 (9.2.0.2.1) database for 64-bit Windows.
On the 32-bit windows computer:
-
Shut down the database and perform a full offline backup.
-
Install 9.2.0.2.1 32-bit software on the 32-bit computer which has the 7.3.4 database. Selecting the Software Only option is sufficient.
-
Run the migration utility (
mig.exe
) from the 9.2.0.2.1 installation against the 7.3.4 instance. These steps are documented in Appendix D, "Upgrading an Oracle7 Database Using the MIG Utility" of Oracle9i Database Migration (part number A96530-02).
Note:
The migration utility creates a convert file that contains the information of the Oracle database version 7 control file. Later in the upgrade process, the convert file is used byALTER
DATABASE
CONVERT
to create a new control file in Oracle9i release 2.The name and location of the convert file are operating system-specific. For example, on a UNIX operating system, the default location isORACLE_HOME
/dbs
in the Oracle database version 7 environment, and the default file name in this directory isconv
sid
.dbf
, wheresid
is your Oracle database version 7 instance ID. On Windows platforms, the default location isORACLE_HOME
\rdbms
in the Oracle9i release 2 environment, and the default file name in this directory isconvert.ora
.
To migrate into the 64-bit Oracle9i release 2 home, complete the following steps on the 64-bit Windows computer:
-
Install Oracle9i release 2 Database release 2 (9.2.0.2.1) for 64-bit Windows.
See Also:
Oracle9i Database Installation Guide for 64-Bit Windows (part number B10546-01) for more information
-
Create the new Oracle9i release 2 database service at the command prompt:
C:\> ORADIM -NEW -SID SID [-INTPWD PASSWORD] -MAXUSERS USERS -STARTMODE AUTO -PFILE
ORACLE_HOME
\DATABASE\INITSID.ORAwhere:
Variable Description SID
The SID of the database you are upgrading. PASSWORD
The password for the new Oracle9i release 2 Database for 64-bit Windows. This is the password for the user connected with SYSDBA
privileges. The-INTPWD
option is not required. If you do not specify it, then operating system authentication is used, and a password is not required.USERS
The maximum number of users who can be granted SYSDBA
andSYSOPER
privileges.ORACLE_HOME
The release 9.2 Oracle home directory. Ensure that you specify the full path name with the -PFILE
option, including drive letter of the Oracle home directory.
-
Copy the 32-bit data files to the new 64-bit Oracle home.
-
Copy the
convert.ora
file generated by the migration utility toORACLE_BASE
\
ORACLE_HOME
\rdbms
directory on the 64-bit computer. -
Copy the 32-bit configuration files to the 64-bit Oracle home.
If your 32-bit initialization parameter file has an
IFILE
(include file) entry, then copy the file specified by theIFILE
entry to the 64-bit Oracle home and edit theIFILE
entry in the initialization parameter file to point to its new location.If you have a password file in the 32-bit Oracle home, then copy the password file to the 64-bit Oracle home. The default 32-bit password file is located in
ORACLE_BASE
\
ORACLE_HOME
\database\pwd
sid
.ora
. Thesid
is your Oracle instance ID. -
In the 64-bit Oracle home, add the
_SYSTEM_TRIG_ENABLED = false
parameter to the initialization parameter file before changing the word size. -
Follow the migration steps documented in the "Upgrade the Database" section in Chapter 3 of Oracle9i Database Migration (part number A96530-02).
-
Run
utlirp.sql
at the end to complete the word size change. -
Remove the
_SYSTEM_TRIG_ENABLED = false
parameter from the initialization parameter file.
7 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 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.5 or later to install this patch set.
7.1 Installing the Patch Set Interactively
Note: If you attempt to install this patch set in an Oracle home directory that does not contain an Oracle9i installation, Oracle Universal 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.8.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 on as a member of the Administrators group to the computer on which to install Oracle components. If you are installing on a Primary Domain Controller (PDC) or a Backup Domain Controller (BDC), log on as a member of the Domain Administrators group.
-
Start Oracle Universal Installer release 10.1.0.5 located in the unzipped area of the patch set. For example,
Oracle_patch\setup.exe
. -
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 unzipped the patch set files, then click Next. For example:Oracle_patch\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 Oracle 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 Oracle Universal Installer, then exit Oracle Universal 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.
-
On the End of Installation screen, click Exit, then click Yes to exit Oracle Universal Installer.
7.2 Installing the Patch Set Noninteractively
The following procedure describes how to install the patch set noninteractively:
-
Log on as a member of the Administrators group to the computer on which to install Oracle components.
-
Copy the response file template provided in the
response
directory where you unzippedthe patch set archive file. -
Edit the values for all fields labeled as
<Value Required>
as described by the comments and examples in the template.
Note:
For Oracle RAC installations, make sure theCLUSTER_NODES
variable specifies all of the nodes used in the original Oracle RAC installation.
-
Enter a command similar to the following to start Oracle Universal Installer in noninteractive mode. If Oracle Universal Installer is located in
Oracle_patch\setup.exe
, then pass the full path of the response file template you have edited locally as the last argument:C:\Oracle_patch> setup.exe -silent -responseFile response_file_path
where
Oracle_patch
is the location of the patch set you downloaded andresponse_file_path
is the full path of the locally edited response file.
8 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.
8.1 Configure OracleGSDService
By default, the OracleGSDService
is configured to run under the LocalSystem
account. Manually configure OracleGSDService
to run under a user account that is a member of the ORA_DBA
group.
8.2 Required Postinstallation Tasks
Complete the following tasks after installing the patch set software:
8.2.1 Check Tablespace Sizes and Set Parameter Values
Review the following sections before upgrading a database.
8.2.1.1 Check SYSTEM Tablespace Size
If JServer is part of the installation ensure that there is at least 20 MB of free space allocated to the SYSTEM tablespace.
8.2.1.2 Check XDB Tablespace Size
For Oracle RAC installations, ensure that there is at least 50 MB of free space allocated to the XDB tablespace.
8.2.1.3 Set the SHARED_POOL_SIZE
and JAVA_POOL_SIZE
Initialization Parameters
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:
-
Use SQL*Plus to login to the database as the
SYS
user withSYSDBA
privileges:C:\> sqlplus /NOLOG SQL> CONNECT SYS/SYS_password AS SYSDBA
-
Start the database:
SQL> STARTUP
-
If necessary, enter the following command to determine whether the system uses an initialization parameter file (
init
sid
.ora
) or a server parameter file (spfile
dbname
.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 theJAVA_POOL_SIZE
initialization parameters to at least 150 MB in the initialization parameter file (init
sid
.ora
). -
Shut down the database:
SQL> SHUTDOWN
8.2.2 Upgrade the Database
After you install the patch set, you must perform the following steps on every database associated with the upgraded Oracle home:
-
Log on as a member of the Administrators group to the computer where the Oracle components are installed.
-
For Oracle RAC installations, start the Global Services Daemon (GSD) on each node of the cluster as follows:
C:\> gsdctl start
-
Start the Oracle Net listener as follows:
C:\> lsnrctl start
Note:
For Oracle RAC installations, start the listener on each node of the cluster.
-
For single-instance installations, use SQL*Plus to login to the database as the
SYS
user withSYSDBA
privileges:C:\> sqlplus /NOLOG SQL> CONNECT SYS/password AS SYSDBA
-
For Oracle RAC installations:
-
Start the database as follows, where
db_name
is the database name:C:\> srvctl start database -d
db_name
-
Use SQL*Plus to login to the database as the
SYS
user withSYSDBA
privileges:C:\> sqlplus /NOLOG SQL> CONNECT SYS/password AS SYSDBA
-
Set the
CLUSTER_DATABASE
initialization parameter toFALSE
:SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;
Note:
If the system uses an initialization parameter file, change the value of theCLUSTER_DATABASE
initialization parameter toFALSE
in the initialization parameter file (init
sid
.ora
).
-
Exit SQL*Plus and shut down the database:
SQL> EXIT C:\> srvctl stop database -d
db_name
-
Use SQL*Plus to login to the database as the
SYS
user withSYSDBA
privileges:C:\> sqlplus /NOLOG SQL> CONNECT SYS/password AS SYSDBA
-
-
Enter the following SQL*Plus commands:
SQL> STARTUP MIGRATE SQL> SPOOL patch.log SQL> @
ORACLE_BASE
\ORACLE_HOME
\rdbms\admin\catpatch.sql SQL> SPOOL OFF -
Review the
patch.log
file for errors and inspect the list of components that is displayed at the end ofcatpatch.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:
SQL> SHUTDOWN SQL> STARTUP
-
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> @
ORACLE_BASE
\ORACLE_HOME
\rdbms\admin\utlrp.sql -
For Oracle RAC installations:
-
Set the
CLUSTER_DATABASE
initialization parameter toTRUE
:SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;
Note:
If the system uses an initialization parameter file, change the value of theCLUSTER_DATABASE
initialization parameters toTRUE
in the initialization parameter file (init
sid
.ora
).
-
Restart the database:
SQL> SHUTDOWN SQL> STARTUP C:\> srvctl start database -d db_name
-
-
If you are using the Oracle Recovery Manager catalog, enter the following command:
C:\> rman catalog username/password@alias RMAN> UPGRADE CATALOG;
-
If Oracle Internet Directory release 9.2.0 is installed, then complete the steps in the "Upgrading Oracle Internet Directory 9.2.0.x.x" section
Note: If you are using the Oracle OLAP option, then you must runcatpatch.sql and utlrp.sql on any additional instance created from your main 9.2.0.8 database. Your catpatch log should show the status of the three OLAP components as follows: OLAP Analytic Workspace UPGRADED 9.2.0.8.0 Oracle OLAP API UPGRADED 9.2.0.8.0 OLAP Catalog VALID 9.2.0.8.0 |
8.2.3 Upgrade Ultrasearch Instances
Perform the following steps to update the database with correct filter paths for all the ultrasearch instances running:
-
Change the directory to
ORACLE_HOME\ultrasearch\admin
. For example,c:\>cd c:\oracle\ora92\ultrasearch\admin
where,
c:\oracle\ora92
is the location ofORACLE_HOME
. -
Log in to SQL*Plus as the
WKSYS
user. For example,c:\oracle\ora92\ultrasearch\admin> sqlplus WKSYS/WKSYS
where, the
WKSYS
user has used the password asWKSYS
. -
Run wk0updatefilter.sql with
ORACLE_HOME
as a parameter. For example,SQL> @wk0updatefilter.sql c:/oracle/ora92
where,
c:\oracle\ora92
is the location ofORACLE_HOME
.
8.3 Upgrading Oracle Internet Directory 9.2.0.x.x
Complete the following steps only if Oracle Internet Directory version 9.2.0.x.x was installed in the Oracle home.
Note: Make sure that the database and database listener are running, and all parameters for theoidpatchca.bat script are specified before to running the script. |
-
Temporarily set the
ORACLE_HOME
andORACLE_SID
environment variables. For example:C:\> set
ORACLE_HOME
=D:\oracle\ora92 C:\> setORACLE_SID
=sales -
Verify that the
WINDIR
system variable is set. For example:C:\winnt
-
Verify that the
PATH
system variable contains the Oracle homebin
directory. For example:D:\oracle\ora92\bin
-
Ensure that the database and database listener are running, and all
oidpatchca.bat
parameters are specified correctly before you run the script:ORACLE_BASE
\ORACLE_HOME
\bin\oidpatchca.bat -connect Connect_String\ -lsnrportListener_Port
\ -systempwdSYSTEM_Password
\ -odspwdODS_Password
\ -sudnSuper-User_DN
\ -supwdSuper-User_Password
\ -dippwdPassword_to_register_DIP_Server
\ -windir %windir%In the preceding command,
Password_to_register_DIP_Server
must conform to the password policy in the Oracle Internet Directory server.
9 Removing the Patch Set Software
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 9.2.0.8 patch release:
-
Before restoring the Oracle home to the original release, perform the following steps:
For Oracle RAC installations:
-
Use SQL*Plus to log in to the database as the
SYS
user withSYSDBA
privileges:C:\> sqlplus /nolog SQL> CONNECT SYS/SYS_password AS SYSDBA
-
Set the
CLUSTER_DATABASE
initialization parameter toFALSE
:SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;
-
Exit SQL*Plus and shut down the database:
SQL> EXIT C:\> srvctl stop database -d db_name
C:\> sqlplus /nolog SQL> CONNECT SYS/SYS_password AS SYSDBA SQL> STARTUP MIGRATE SQL> SPOOL catbkout.out SQL> @
ORACLE_BASE
\ORACLE_HOME
\rdbms\admin\catbkout.sql SQL> SPOOL OFF SQL> SHUTDOWN IMMEDIATEFor Single Instance:
C:\> sqlplus /nolog SQL> CONNECT SYS/SYS_password AS SYSDBA SQL> SHUTDOWN SQL> STARTUP MIGRATE SQL> SPOOL catbkout.out SQL> @
ORACLE_BASE
\ORACLE_HOME
\rdbms\admin\catbkout.sql SQL> SPOOL OFF SQL> SHUTDOWN IMMEDIATE -
-
Restore the Oracle9i installation that you backed up before applying the patch set.
-
After restoring the original Oracle home, perform the following steps:
C:\> sqlplus /nolog SQL> CONNECT SYS/SYS_password AS SYSDBA SQL> STARTUP MIGRATE SQL> SPOOL catpatch.out SQL> @
ORACLE_BASE
\ORACLE_HOME
\rdbms\admin\catpatch.sql -
If Oracle Spatial is installed with the database, perform the following steps:
SQL> alter session set current_schema = mdsys; SQL> @
ORACLE_BASE
\ORACLE_HOME
\md\admin\prvtmd.plb SQL> @ORACLE_BASE
\ORACLE_HOME
\md\admin\prvtmd2.plb SQL> @ORACLE_BASE
\ORACLE_HOME
\md\admin\sdopidx.sql SQL> @ORACLE_BASE
\ORACLE_HOME
\md\admin\prvtpidx.plb SQL> @ORACLE_BASE
\ORACLE_HOME
\md\admin\prvtsidx.plb SQL> @ORACLE_BASE
\ORACLE_HOME
\md\admin\sdogeom.sql SQL> @ORACLE_BASE
\ORACLE_HOME
\md\admin\prvt3glh.plb SQL> @ORACLE_BASE
\ORACLE_HOME
\md\admin\prvtgeom.plb SQL> @ORACLE_BASE
\ORACLE_HOME
\md\admin\prvt3gl.plb SQL> alter session set current_schema = sys; -
Shut down the database:
SQL> SHUTDOWN IMMEDIATE
-
Start the database and recompile the remaining invalid objects:
SQL> STARTUP SQL> @
ORACLE_BASE
\ORACLE_HOME
\rdbms\admin\utlrp.sql -
Review
catbkout.out
andcatpatch.out
for errors. -
Restart the database:
For Oracle RAC installations:
Set the
CLUSTER_DATABASE
initialization parameter toTRUE
:SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile; SQL> SHUTDOWN SQL> EXIT C:\> srvctl start database -d db_name
Note:
If the system uses an initialization parameter file, change the value of theCLUSTER_DATABASE
initialization parameters toTRUE
in the initialization parameter file (init
sid
.ora
).
For Single Instance:
SQL> SHUTDOWN SQL> STARTUP
10 Reinstalling the Patch Set Software
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:
-
Make sure you complete the same set of preinstallation tasks that you performed when you installed the patch set initially:
-
Log on as a member of the Administrators group to the computer on which to install Oracle components. Log on as a member of the Domain Administrators group if you are installing on a Primary Domain Controller (PDC) or a Backup Domain Controller (BDC).
-
Unzip the downloaded patch set file in a new directory.
-
Shut down the existing Oracle server instance with normal or immediate priority.
-
Stop all listener, agent, and other processes running in or against the Oracle home in which you are installing.
-
-
Start Oracle Universal Installer release 10.1.0.5 located in the unzipped area of the patch set. For example,
Oracle_patch\setup.exe
. -
On the Welcome screen, click Next. The File Locations screen appears.
-
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 unzipped the patch set files. For example:Oracle_patch\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.
If you are installing the patch on an Oracle RAC cluster, click Next on the Selected Nodes screen.
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 node for each component listed in the tree. You will see a patch that corresponds to each component.
-
Select the patch for installation by selecting the check box to the left of the patch name. As you do this, the Install Status column should say Reinstall.
-
Repeat the process for each patch bundled in the patch set.
-
Click Next. The patches to be reinstalled will appear.
-
Verify the list of patches to be reinstalled.
-
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 Oracle Universal Installer.
11 Known Issues
Review the following known issues after you apply the patch set.The following known issues apply to this patch set release:
11.1 Upgrade and SYS Schema
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');
11.2 PL/SQL Cursor Caching
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.
11.3 OID Registration Fails
Oracle Internet Directory (OID) registration fails if you try to register a database after creating it using Database Configuration Assistant (DBCA).
Workaround:
Apply patch 5396877.
This issue is tracked with Oracle Bug 5396877
11.4 Bug 2602782
Scrollable ResultSet returns 3 times NCHAR character byte size when database Ncharset is UTF8. This problem occurs only with the JDBC Thin driver.
11.5 Bug 3259636
If you use Database Configuration Assistant (DBCA) to create a new database, using the seed database option, some of the components are 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.
11.6 Bug 2908196
If you use USER_FILTER
for custom filtering or INSO_FILTER
for filtering formatted documents, then ensure that the environment variable for the temporary file directory location does not contain spaces.
Workaround:
Modify the temporary file directory environment variable to a directory name that does not contain any spaces, and then bounce the database in a manner, such that, it picks up this new value of the environment variable.
Examples of correct environment variables are as follows:
TEMP=C:\TEMP TMP=C:\TMP
11.7 Bug 4270038
When using Database Configuration Assistant in standalone mode to create a database, the following error will occur:
ORA-29807: specified operator does not exist
Workaround:
Click Ignore.
11.8 Running catpatch.sql during postinstallation steps
When running catpatch.sql
as part of the postnstallation process, the following error may occur:
create type XMLTypePI OID '0000000000000000000000000002014F' as * ERROR at line 1: ORA-04021: timeout occurred while waiting to lock object SYS.XMLTYPEPI
Workaround:
Ignore this error message.
12 Fixed Platform-Specific Bugs for Windows (32-Bit)
The following table is a cumulative list of the platform-specific bugs fixed in all Oracle9i for Windows 32-bit patch sets to date:
Fixed in Release | Bug Number | Description |
---|---|---|
9.2.0.4 | 2866965 | CAN'T ATTACH ANY AW'S UPDATED IN 9.2.0.2 |
9.2.0.4 | 2838610 | CAN NOT CREATE MORE THAN 10 POLICIES IN LABEL SECURITY |
9.2.0.4 | 2691996 | NUMBERFORMATEXCEPTION IN PERFORMANCE MANAGER WHEN MONITORING OS CHARTS |
9.2.0.4 | 2368369 | WHEN OCISETATTRIBUTE IS CALLED TO SET NON-BLOCKING ON WINDOWS NT GETS ERROR |
9.2.0.4 | 2593071 | IMPLEMENT CHANGES DONE TO SL.H FOR BUG 2285641 ON NT |
9.2.0.4 | 2635260 | ORA_OEMAGENT_DIR PREVENTS AGENT FROM STARTING |
9.2.0.4 | 2613603 | USER DEFINED EVENT SUDDENLY FAILS WITH FAILURE -- NO RESULT RETURNED IN OUTPUT |
9.2.0.4 | 2453901 | CMANAGER DISCOVERY SCRIPT IS USING A WRONG LOG FILENAME |
9.2.0.4 | 2225320 | GETTING NEGATIVE DISKSPACE VALUES RETURNED FROM PCT DISKSPACE BASED EVENTS |
9.2.0.4 | 1867995 | DEFAULT AGENT DISCOVERS FAI L SAFE DATABASES |
9.2.0.8 | 4185747 | ORA-01459 ERROR ON KEYSET-DRIVEN RECORDSET WITH LONG/LONG RAW |
9.2.0.8 | 3781883 | ODBC CAUSES ACCESS VIOLATION WHEN STRING LITERAL CONTAINS CR LF CODE |
9.2.0.8 | 4608183 | PERFORMANCE ISSUES WITH THE 10.1.0.4.0 ORACLE ODBC DRIVER |
9.2.0.8 | 4719436 | 10.1.0.4.0 ODP.NET PUBLISHER POLICY DOES NOT ADDRESS THE 9.2.0.2.102 VERSION |
9.2.0.8 | 4537790 | CLUSTER NODES HANG AND THEN BUGCHECK ON REBOOTS |
9.2.0.8 | 4312390 | ORADIM COMMAND CAN'T SHUTDOWN DATABASE : ORA-1031 |
9.2.0.8 | 4632494 | DBMS_LOB.FILEOPEN GETS ORA-22288 WHEN FILE NAME INCLUDES 0X5C |
9.2.0.8 | 4947132 | ENCOUNTER ORA-911 AGAINST JAPANESE TABLE/COL NAME |
9.2.0.8 | 3734843 | CLIENT CONNECTION HANGS AFTER VIP FAILOVER |
9.2.0.8 | 4407799 | OCIBREAK() THROWS DR.WATSON ORAN9!ZTVULL (ACCESS VIOLATION) |
9.2.0.8 | 4308824 | NTS FAILS IF AUTH PACKET IS GREATER THAN SDU |
9.2.0.8 | 4278371 | STARTING ASM INSTANCE FAILS IF WORKGROUP NAME AND NETBIOS NAME ARE SAME |
9.2.0.8 | 3991216 | NMS-1078 ON TABLESPACE FULL EVENT |
9.2.0.8 | 4108430 | NMS-1005 EVENT SUBMISSION FAILS IN FIALSAFE ENVIRONMENT |
9.2.0.8 | 3760624 | OEM SRVCTL SYNTAX IS INCORRECT STARTING / SHUTTING DOWN ORACLE RAC DB |
13 Fixed Platform-Specific Bugs for Windows (64-Bit Itanium)
The following is a cumulative list of the platform-specific bugs fixed in all Oracle9i for Windows 64-bit patch sets to date:
Fixed in Release | Bug Number | Description |
---|---|---|
9.2.0.7 | 3610617 | ORA_WORKINGSETMIN AND MAX DO NOT WORK CORRECTLY |
9.2.0.8 | 3825041 | WIN64:CALL STACK IS MISSING THE FUNCTION CALLS PRODUCED ONLY THE HEADER INFO |
9.2.0.8 | 4865122 | PERFORMANCE ISSUES ON WIN64 WITH LARGE SGA WHEN DEP IS ON |
9.2.0.8 | 4727131 | DATABASE HANG SPORADIC WITH WINDOWS2003 64-BIT SP1 AT ITANIUM |
14 Patch Set Components
The following table lists the components included in this patch set:
Component | Version |
---|---|
Advanced Queuing (AQ) API | 9.2.0.8.0 |
Agent required support files | 9.2.0.8.0 |
Assistant common files | 9.2.0.8.0 |
Data Management Services common files | 9.2.0.8.0 |
Authentication and encryption | 9.2.0.8.0 |
Database SQL scripts | 9.2.0.8.0 |
Database Verify utility | 9.2.0.8.0 |
Export/import | 9.2.0.8.0 |
JDBC common files | 9.2.0.8.0 |
JDBC/OCI common files | 9.2.0.8.0 |
LDAP required support files | 9.2.0.8.0 |
Migration utility | 9.2.0.8.0 |
Object Type Translator | 9.2.0.8.0 |
Oracle C++ Call Interface | 9.2.0.8.0 |
Oracle Call Interface (OCI) | 9.2.0.8.0 |
Oracle Client required support files | 9.2.0.8.0 |
Oracle Connection Manager | 9.2.0.8.0 |
Oracle Core required support files | 9.2.0.8.0 |
Oracle database demos | 9.2.0.8.0 |
Oracle database utilities | 9.2.0.8.0 |
Oracle Data Mining | 9.2.0.8.0 |
Oracle interMedia Client compatibility files | 9.2.0.8.0 |
Oracle interMedia Java Advanced Imaging | 9.2.0.8.0 |
Oracle Internet Directory Client | 9.2.0.8.0 |
Oracle Internet Directory Server | 9.2.0.8.0 |
Oracle Intelligent Agent | 9.2.0.8.0 |
Oracle interMedia Locator | 9.2.0.8.0 |
Oracle JDBC Development Drivers | 9.2.0.8.0 |
Oracle JDBC Thin Driver for JDK 1.2 | 9.2.0.8.0 |
Oracle JDBC Thin Driver for JDK 1.4 | 9.2.0.8.0 |
Oracle JVM | 9.2.0.8.0 |
Oracle Java Tools | 9.2.0.8.0 |
Oracle Label Security | 9.2.0.8.0 |
Oracle Net Configuration Assistant | 9.2.0.8.0 |
Oracle Net Listener | 9.2.0.8.0 |
Oracle Net Manager | 9.2.0.8.0 |
Oracle Net | 9.2.0.8.0 |
Oracle Net Protocol Support | 9.2.0.8.0 |
Oracle Net required support files | 9.2.0.8.0 |
Oracle OLAP | 9.2.0.8.0 |
Oracle Partitioning | 9.2.0.8.0 |
Oracle Text | 9.2.0.8.0 |
Oracle Ultra Search common files | 9.2.0.8.0 |
Oracle Ultra Search middle-tier | 9.2.0.8.0 |
Oracle UltraSearch server | 9.2.0.8.0 |
Oracle Wallet Manager | 9.2.0.8.0 |
Oracle XML Developer's Kit | 9.2.0.10.0 |
Oracle XML SQL utility | 9.2.0.8.0 |
Oracle9i release 2 Globalization | 9.2.0.8.0 |
Oracle9i release 2 Real Application Clusters | 9.2.0.8.0 |
Oracle9i release 2 | 9.2.0.8.0 |
Oracle PL/SQL | 9.2.0.8.0 |
Oracle PL/SQL required support files | 9.2.0.8.0 |
Precompiler common files | 9.2.0.8.0 |
Precompiler required support files | 9.2.0.8.0 |
Pro*C/C++ | 9.2.0.8.0 |
Oracle database required support files | 9.2.0.8.0 |
Oracle Recovery Manager | 9.2.0.8.0 |
Secure Socket Layer (SSL) | 9.2.0.8.0 |
SQL*Loader | 9.2.0.8.0 |
SQL*Plus | 9.2.0.8.0 |
SQLJ Runtime | 9.2.0.8.0 |
SSL required support files | 9.2.0.8.0 |
Utilities common files | 9.2.0.8.0 |
XML Parser for C | 9.2.0.8.0 |
XML Parser for C++ | 9.2.0.8.0 |
XML Parser for Java | 9.2.0.8.0 |
XML Parser for PL/SQL | 9.2.0.8.0 |
XML Parser for Oracle JVM | 9.2.0.8.0 |
XSQL Servlet | 9.2.0.8.0 |
15 Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
TTY Access to Oracle Support Services
Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.
Oracle9i Patch Set Notes, Release 2 (9.2.0.8) Patch Set 7 for Microsoft Windows (64-Bit) on Intel Itanium
Copyright © 2006, Oracle. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.