| Oracle9i Patch Set Notes
Release 2 (9.2.0.6) Patch Set 5 for Solaris Operating System (SPARC 64-bit) |
|
Patch Set Notes
Release 2 (9.2.0.6) Patch Set 5 for Solaris Operating System (SPARC 64-bit)
September 2005
These patch set notes accompany the Oracle9i release 2 (9.2.0.6) patch set.
This document contains the following sections:
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.6 includes all fixes in patch sets 9.2.0.6 and earlier as well as new fixes for patch set 9.2.0.6. 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.3. 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.
For a list of products included in this patch set, see the "Patch Set Components" section.
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.3 (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.3 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.6) Patch Set 5 for Solaris Operating System (SPARC 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 Solaris Operating System (SPARC 64-bit)
A list of known issues relating to Oracle9i release 2 for Solaris Operating System (SPARC 64-bit)
Oracle9i List of Bugs Fixed, Release 2 (9.2.0.6) Patch Set 5
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.
The following are the system requirements for this patch set:
Operating System
Solaris 2.6, Solaris 7, Solaris 8, or Solaris 9
Oracle9i
Oracle9i release 2 (9.2.0.1.0) or later
Complete the following preinstallation tasks before installing the patch set:
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.
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:
http://metalink.oracle.com/
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.
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
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.
Oracle Text uses the INSO filter during the indexing of binary documents. This filtering technology is based on the Stellent Chicago Corporation HTML Export technology and is licensed from Stellent Chicago Corporation.
INSO 7.5 is included with this patch set and supports additional platforms and document types. A full list of supported platforms and document types is documented in OracleMetaLink note 212584.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.
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 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: You must install this patch set on the same set of nodes that the base release was installed on. |
If you plan to install this patch in an Oracle Real Application Clusters environment, read the following sections before proceeding:
Preinstallation Considerations for Oracle Real Application Clusters
Preinstallation Considerations for Oracle Real Application Clusters with Sun Clusterware
If the directory /usr/ucb is in the search path on a UNIX
system, then ensure that it is listed after /usr/bin and
/usr/ccs/bin in the $PATH setting.
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: You must install this patch set on the same set of nodes that the base release was installed on. |
The UDLM 3.3.4.5 patch must be installed before applying this patch set for
Oracle Real Application Clusters environments. The UDLM patch is included in
this patch set. The installation instructions are located in the
/Disk1/racpatch/README.udlm file.
This is not a complete software distribution. You must install it in an
existing Oracle9i Oracle home. To identify Oracle home directories,
view the /var/opt/oracle/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:
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.
To download and extract the patch set installation software:
Download and extract the p3948480_9206_solaris64.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:
$ unzip p3948480_9206_solaris64.zip
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. After the patch set is installed, there is no way to remove it.
Install Oracle Universal Installer release 10.1.0.3:
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 the Installer (your
workstation or PC).
Enter the following commands to start the Installer, where
patchset_directory is the directory where you unzipped
the patch set software:
$ cd patchset_directory/Disk1 $ ./runInstaller
On the Welcome screen, click Next.
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.
The Products to Install screen appears.
Select Universal Installer 10.1.0.3, then click Next.
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 from the Installer.
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.3 or later to install this patch set. |
Installing the Patch Set Interactively
To install the Oracle9i patch set interactively:
|
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.6.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:
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 the Installer (your
workstation or PC).
For RAC installations, enter the following commands where
oracle_home is the Oracle home where you installed
Oracle Universal Installer 10.1.0.3:
$ cd oracle_home/oui/bin $ ./runInstaller -updateNodeList -noClusterEnabled -local ORACLE_HOME=$ORACLE_HOME CLUSTER_NODES=node1,node2,node3
Enter following commands to start the Installer 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.
Select Oracle 9iR2 Patchset 9.2.0.6.0 from the available options.
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.
Installing the Patch Set Noninteractively
To install the Oracle9i 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:
$ cd patchset_directory/Disk1
$ ./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 RAC installation, then
run the root.sh script on each node of the cluster.
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.
To upgrade Oracle databases from a previous release directly to Oracle9i release 2 (9.2.0.6) follow the instructions in OracleMetalink note 214887.1 Upgrading Directly to a 9.2.0 Patch Set.
|
See Also: For more information about upgrading a database, see the Oracle9i Database Migration guide. |
Review the "Check Tablespace Sizes and Set Parameter Values" section and complete the steps in the "Upgrade the Database" section after you have installed the patch set software.
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 DB tablespace.
Set the value of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters as follows:
Start the database:
SQL> STARTUP
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).
Shut down the database:
SQL> SHUTDOWN
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:
$ gsdctl start
Start the Oracle Net listener as follows:
$ lsnrctl start <db_listener_name>
|
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:
$ sqlplus /nolog SQL> CONNECT / AS SYSDBA
For RAC installations:
Start the database as follows, where db_name is the
database name:
$ srvctl start database -d db_name
Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
$ sqlplus /nolog SQL> CONNECT / AS SYSDBA
Set the CLUSTER_DATABASE initialization parameter to FALSE:
SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;
|
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:
SQL> EXIT $ srvctl stop database -d db_name
Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
$ sqlplus /nolog SQL> CONNECT / AS SYSDBA
Enter the following SQL*Plus commands:
SQL> STARTUP MIGRATE SQL> SPOOL patch.log SQL> @?/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 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:
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> @?/rdbms/admin/utlrp.sql
If you will use Oracle OLAP, enter the following commands:
SQL> ALTER USER OLAPSYS IDENTIFIED BYpasswordACCOUNT UNLOCK; SQL> CONNECT OLAPSYS/passwordSQL> @cwmlite/admin/postamd.sql
For RAC installations:
Set the CLUSTER_DATABASE initialization parameter to TRUE:
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:
SQL> SHUTDOWN SQL> STARTUP
If you are using the Oracle Recovery Manager catalog, enter the following command:
$ rman catalog username/password@alias RMAN> UPGRADE CATALOG;
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 theoidpatchca.sh script
are specified before running the script. |
$ORACLE_HOME/bin/oidpatchca.sh -connect Connect_String -lsnrportListener_Port-systempwdSYSTEM_Password-odspwdODS_Password-sudnSuper-User_DN-supwdSuper-User_Password-dippwdPassword_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 cannot remove the patch set software after you have installed it. Oracle recommends that you back up the Oracle9i installation before applying the patch set. If you do not want to use a patch set applied to an Oracle9i installation, do one of the following:
Restore the Oracle9i installation that you backed up before applying the patch set.
Reinstall Oracle9i.
If you choose not to use a patch set because you are encountering a problem, contact Oracle Support Services to verify that the problem you are encountering is being addressed.
If you completed the steps in the "Upgrade the Database" section, you must do one of the following for each database that you upgraded to the patch set:
Use a point-in-time or full database backup and recovery to restore the database to its condition before you upgraded the database.
Export, rebuild, and import the database. If the database is too large, use Transportable Tablespaces for the export/import process.
|
See Also: For more information about using Transportable Tablespaces for the export/import process, see notes 100693.1 and 77523.1 available on the OracleMetaLink Web site. |
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 the Installer (your
workstation or PC).
Enter the following commands to start the 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:
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.6/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.6/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 correct this problem, run the catpatch.sql script as
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. |
The following table is a cumulative list of the platform-specific bugs fixed in all Oracle9i patch sets to date:
|
Note: You may or may not receive platform-specific bugs. |
| Fixed in Release | Bug Number | Description |
|---|---|---|
| 9.2.0.3 | 2453925 | AVMPING dumps core (APRAC64 bit 9.2 release) |
| 9.2.0.3 | 2490128 | Process class missing from Operating System cart |
| 9.2.0.3 | 2746047 | Siemens bug - DLMD's DD_TS enqueue not cleaned during RCFG |
| 9.2.0.3 | 2749790 | SIGBUS in XSCBIXLINBYTE2SEG during dynamic aggregate |
| 9.2.0.4 | 2805249 | SGA shrink may not release memory back to the O/S on Solaris. |
| 9.2.0.5 | 2854962 | Sun: Oracle Real Application Clusters on Solaris can only support up to 4 nodes. |
| 9.2.0.5 | 2872469 | ORA-03113 for select on ALL_CONSTRAINTS over informix gateways link |
| 9.2.0.4 | 2882059 | OLAP API library built incorrectly |
| 9.2.0.4 | 2917199 | FTP operation with SB XMLTYPE stored as CLOB results in corrupt data |
| 9.2.0.5 | 2986722 | the problem of external procedure calling C shell script |
| 9.2.0.5 | 3081593 | network data class always zero in 64-bit version |
| 9.2.0.5 | 3211137 | Not able to move SGABEG on a 64-bit Operating System |
| 9.2.0.5 | 3234112 | bug 2954997 not fixed in 9204 on solaris 64-bit |
| 9.2.0.5 | 3391626 | LCK process terminates getting an error at SSKGXPRDTRCV using RSM/RDT |
| 9.2.0.5 | 3566420 | BACKGROUND PROCESS GOT OERI:KSLAWE:!PWQ AND INSTANCE CRASHES |
| 9.2.0.5 | 3623983 | BASE BUG FOR CORE PORTION OF VOS FIX IN 3616577 |
The following table lists the components included in this patch set:
| Component | Version |
|---|---|
| Advanced Queuing (AQ) API | 9.2.0.6 |
| Agent required support files | 9.2.0.6 |
| Assistant common files | 9.2.0.6 |
| Data Management Services common files | 9.2.0.6 |
| Authentication and encryption | 9.2.0.6 |
| Database SQL scripts | 9.2.0.6 |
| Database Verify utility | 9.2.0.6 |
| DCE integration | 9.2.0.6 |
| Export/import | 9.2.0.6 |
| External naming: NIS | 9.2.0.6 |
| Generic connectivity common files | 9.2.0.6 |
| Generic connectivity using ODBC | 9.2.0.6 |
| JDBC common files | 9.2.0.6 |
| JDBC/OCI common files | 9.2.0.6 |
| LDAP required support files | 9.2.0.6 |
| Migration utility | 9.2.0.6 |
| Object Type Translator | 9.2.0.6 |
| Oracle C++ Call Interface | 9.2.0.6 |
| Oracle Call Interface (OCI) | 9.2.0.6 |
| Oracle Client required support files | 9.2.0.6 |
| Oracle Connection Manager | 9.2.0.6 |
| Oracle Core required support files | 9.2.0.6 |
| Oracle database demos | 9.2.0.6 |
| Oracle database utilities | 9.2.0.6 |
| Oracle Data Mining | 9.2.0.6 |
| Oracle interMedia Client compatibility files | 9.2.0.6 |
| Oracle interMedia Java Advanced Imaging | 9.2.0.6 |
| Oracle Internet Directory Client | 9.2.0.6 |
| Oracle Internet Directory Server | 9.2.0.6 |
| Oracle Intelligent Agent | 9.2.0.6 |
| Oracle interMedia Locator | 9.2.0.6 |
| Oracle JDBC Development Drivers | 9.2.0.6 |
| Oracle JDBC Thin Driver for JDK 1.2 | 9.2.0.6 |
| Oracle JDBC Thin Driver for JDK 1.4 | 9.2.0.6 |
| Oracle JVM | 9.2.0.6 |
| Oracle Java Tools | 9.2.0.6 |
| Oracle Label Security | 9.2.0.6 |
| Oracle Names | 9.2.0.6 |
| Oracle Net Configuration Assistant | 9.2.0.6 |
| Oracle Net Listener | 9.2.0.6 |
| Oracle Net Manager | 9.2.0.6 |
| Oracle Net | 9.2.0.6 |
| Oracle Net Protocol Support | 9.2.0.6 |
| Oracle Net required support files | 9.2.0.6 |
| Oracle OLAP | 9.2.0.6 |
| Oracle Partitioning | 9.2.0.6 |
| Oracle Procedural Gateway for IBM MQSeries | 9.2.0.6 |
| Oracle Procedural Gateway for APPC | 9.2.0.6 |
| Oracle9i Real Application Clusters Guard | 9.2.0.6 |
| Oracle Text | 9.2.0.6 |
| Oracle Transparent Gateway for Informix | 9.2.0.6 |
| Oracle Transparent Gateway for DRDA | 9.2.0.6 |
| Oracle Transparent Gateway for INGRES II | 9.2.0.6 |
| Oracle Transparent Gateway for Sybase | 9.2.0.6 |
| Oracle Transparent Gateway for Teradata | 9.2.0.6 |
| Oracle Ultra Search common files | 9.2.0.6 |
| Oracle Ultra Search middle-tier | 9.2.0.6 |
| Oracle UltraSearch server | 9.2.0.6 |
| Oracle Wallet Manager | 9.2.0.6 |
| Oracle XML Developer's Kit | 9.2.0.8.0 |
| Oracle XML SQL utility | 9.2.0.6 |
| Oracle9i release 2 Globalization | 9.2.0.6 |
| Oracle9i release 2 Real Application Clusters | 9.2.0.6 |
| Oracle9i release 2
|
9.2.0.6 |
| Oracle PL/SQL | 9.2.0.6 |
| Oracle PL/SQL required support files | 9.2.0.6 |
| Precompiler common files | 9.2.0.6 |
| Precompiler required support files | 9.2.0.6 |
| Pro*C/C++ | 9.2.0.6 |
| Pro*COBOL | 1.8.77.6.0 |
| Pro*COBOL | 9.2.0.6 |
| Pro*FORTRAN | 1.8.77.6.0 |
| Oracle database required support files | 9.2.0.6 |
| Oracle Recovery Manager | 9.2.0.6 |
| Secure Socket Layer (SSL) | 9.2.0.6 |
| SQL*Loader | 9.2.0.6 |
| SQL*Module Ada | 9.2.0.6 |
| SQL*Module Ada common files | 9.2.0.6 |
| SQL*Plus | 9.2.0.8.0 |
| SQLJ Runtime | 9.2.0.6 |
| SSL required support files | 9.2.0.6 |
| Utilities common files | 9.2.0.6 |
| XML Parser for C | 9.2.0.6 |
| XML Parser for C++ | 9.2.0.6 |
| XML Parser for Java | 9.2.0.6 |
| XML Parser for PL/SQL | 9.2.0.6 |
| XML Parser for Oracle JVM | 9.2.0.6 |
| XSQL Servlet | 9.2.0.6
|
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
Orac
le 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.
Oracle Database Patch Set Release Notes, Release 2 (9.2.0.6) Patch Set 5 for Solaris Operating System (SPARC 64-bit)
Copyright © 2005, 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 Retek 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.