|
微信公众号:云库管 www.yunDBA.com 北京云库管科技有限公司 （内部培训资料） 返回上级
|
|
||||
|
|
Critical Patch Update January
2010 Patch Availability Document for Oracle Products (Doc ID 967472.1) |
|
|
|
APPLIES TO:
Information
in this document applies to any platform. This Critical Patch Update
(CPUJan2010) supersedes earlier Critical Patch Updates that have been
released for the same product releases. This document is subject to continual
update after initial release. Critical Patch Update January 2010 Patch Availability Document
for Oracle Products
My Oracle Support
Note 967472.1 Released January 12, 2010 This document contains the following
sections: ·
Section 1, "How to Use this Document" ·
Section 2, "What's New in this Critical Patch
Update" ·
Section 3, "About Critical Patch Updates" ·
Section 4, "Critical Patch Update Availability for
Oracle Products" ·
Section 5, "Planned Patches for the Next Critical
Patch Update Release" ·
Section 6, "Terminal Critical Patch Update
History" ·
Section 7, "Determining Oracle Environment
Settings" ·
Section 8, "Sources of Additional Information" ·
Section 9, "Modification History" ·
Section 10, "Documentation Accessibility" 1 How to Use this Document
Oracle provides Critical Patch Updates
to its customers to fix security vulnerabilities. These updates occur every
quarter. For the list of products covered by this document, see Section 4, "Critical Patch Update Availability for
Oracle Products." For information about Oracle
E-Business Suite, review My Oracle Support Note 985520.1, Oracle
E-Business Suite Critical Patch Update Note January 2010, which
contains information related to Oracle E-Business Suite products. In order to download and apply the
correct Critical Patch Updates for your environment, you should make a list
of all your Oracle products, the release numbers and components. Section 7, "Determining Oracle Environment
Settings," may be
helpful in gathering this information. You may also want to refer to the
Advisory for January 2010, http://www.oracle.com/technology/deploy/security/critical-patch-updates/cpujan2010.html, which documents the security vulnerabilities addressed
in CPUJan2010. Review Section 2, "What's New in this Critical Patch
Update," as it lists
documentation and packaging changes along with announcements such as upcoming
terminal Critical Patch Updates. Section 4, "Critical Patch Update Availability for
Oracle Products," includes
the details of which patches are needed for particular products and product
suites. The products are listed in alphabetical order. If there is only a
table of minimum product requirements that is shown, the installed components
must be at this release level. The Critical Patch Update
Availability tables list the patch numbers for specific product releases. For
product suites, there is one availability table for each product suite
release. It lists all Critical Patch Update to apply to the various Oracle
homes that are associated with the product suite. These patches are listed in
the order to apply. Apply only the patches applicable to the component
releases that are installed in your environment. For example, the Oracle
Fusion Middleware 10.1.2.3 table lists an Oracle Portal Repository patch for
Oracle Portal 10.1.4.2 Repository and a different patch for Oracle Portal
10.1.2.3 Repository. Apply the corresponding patch based on which release of
Oracle Portal is installed in your system.
2 What's New in this Critical Patch Update
This section highlights changes in
this document and important new changes in CPUJan2010. This section contains the following: ·
Section 2.1, "CPUJan2010 and Oracle Database
11.2.0.1" ·
Section 2.2, "Patch Set Updates for Oracle Database
11.1.0.7 and 10.2.0.4" ·
Section 2.3, "CPUJan2010 and Oracle Fusion
Middleware 10.1.3.5.1" ·
Section 2.5, "Changes to the Critical Patch Update
Patch Conflict Resolution Schedule" ·
Section 2.6, "Platforms Added to the On-Request
Program" ·
Section 2.7, "Terminal Critical Patch Updates" ·
Section 2.8, "New Minimum Requirements for
CPUJan2010" ·
Section 2.9, "OPatch Requirements for
CPUJan2010" 2.1 CPUJan2010 and Oracle
Database 11.2.0.1
There is no CPUJan2010 patch for
Oracle Database 11.2.0.1. The security vulnerabilities
announced in the Advisory for January 2010 are fixed in Oracle Database
11.2.0.1. 2.2 Patch Set Updates for Oracle
Database 11.1.0.7 and 10.2.0.4
Concurrent with the release of
CPUJan2010, the Database Patch Set Update 11.1.0.7.2 and the Database Patch
Set Update 10.2.0.4.3 are released. A Patch Set Update (PSU) is a proactive,
cumulative patch that contains the recommended bug fixes and the Critical
Patch Update security content, and therefore is an option to apply instead of
the Critical Patch Update. For more information, see My Oracle Support Note 854428.1, Patch Set
Updates for Oracle Products, and Section 3.4, "Critical Patch Updates and Patch Set
Updates." 2.3 CPUJan2010 and Oracle Fusion
Middleware 10.1.3.5.1
With CPUJan2010 there is a Critical
Patch Update released for Oracle Fusion Middleware 10.1.3.5.1. For more
information, see Section 4.13.7, "Critical Patch Update Availability
for Oracle Fusion Middleware 10.1.3.5.x." 2.4 Changes To
Critical Patch Update And Patch Set Update Platform Release Plans for Oracle
Database 10.2.0.4
Because of the popularity of Patch
Set Updates on the "on request" platforms, beginning with
CPUOct2009, Oracle now delivers Patch Set Updates for all 10.2.0.4 platforms
on the release date, but for selected platforms, releases the Critical Patch
Update only on-request. For information on what patches are released for each
platform, refer to Note 882604.1 Change to Critical Patch Update and
Patch Set Updates Platform Release Plans. 2.5 Changes to the Critical Patch
Update Patch Conflict Resolution Schedule
For Fusion Middleware releases
(excluding BEA) and for Oracle Database releases 10.1.0.5 and earlier, Oracle
has changed the schedule for Critical Patch Update conflict resolution
requests and the delivery of the merge patches. These schedule changes allow
Oracle to provide patches to customers sooner. The request period is changed
to two weeks from the release date; the merge patch availability is changed
to four weeks from the release date. Previously, the merge patches were
available seven weeks after the release. For more information, see Section 3.2, "Critical Patch Update Patch Conflict
Resolution." 2.6 Platforms Added to the
On-Request Program
For CPUJan2010, there are no new
platforms that have been added to the On-Request Program. 2.7 Terminal Critical Patch
Updates
For information on the error
correction support policy for Critical Patch Updates, refer to My Oracle Support Note 209768.1, Database, FMW,
EM Grid Control, and OCS Software Error Correction Support Policy. In Table 49 and Table 50, the
terminal Critical Patch Update for each release version is indicated.
Terminal Critical Patch Updates for CPUJan2010, the next Critical Patch
Update, and newly scheduled terminal Critical Patch Updates are listed below. For terminal Critical Patch Update
history information, see Table 51. ·
CPUJan2010
is the terminal Critical Patch Update for Oracle Enterprise Manager Grid
Control 10.2.0.4. 2.8 New Minimum Requirements for
CPUJan2010
The following is a new minimum
version: ·
The
minimum version for Oracle Application Express is 3.2.1.00.11. For more
information, see Section 4.1, "Oracle Application Express." 2.9 OPatch Requirements for
CPUJan2010
There are no new minimum OPatch
requirements for CPUJan2010. However, as part of general best
practices, Oracle recommends that you use the latest released OPatch when
using OPatch to install CPUJan2010 patches. 2.10 CPUJan2010 README Patch Apply
Changes for Database and Fusion Middleware Critical Patch Updates
There are no changes to the patch
apply steps in the READMEs for the CPUJan2010 Database and Fusion Middleware
Critical Patch Updates since CPUOct2009. 3 About Critical Patch Updates
This section contains the following: ·
Section 3.1, "Terminology in the Tables" ·
Section 3.2, "Critical Patch Update Patch Conflict
Resolution" ·
Section 3.3, "On-Request Patches for Oracle Database
and Oracle Fusion Middleware Products" ·
Section 3.4, "Critical Patch Updates and Patch Set
Updates" 3.1 Terminology in the Tables
The tables in the following sections
show the Critical Patch Updates based on product and platform. The following
terminology is used with patch availability: ·
Bundle The Critical Patch Update and Patch Set Update
fixes are included in cumulative Microsoft Windows Bundles. ·
Patch Number The Critical
Patch Update is available on the platform for the release version. ·
<DD-MMM-YY> The Critical Patch Update is not currently
available. The date is the release date. ·
Planned The Critical Patch Update is planned. ·
Not Applicable (NA) The Critical Patch Update is not planned for
this platform and release version combination. This may be due to several reasons including: 1.
The
release version is not available on this platform. 2.
The
release version does not fall under Critical Patch Update release policies.
Refer to My Oracle Support Note 209768.1, Database, FMW,
EM Grid Control, and OCS Software Error Correction Support Policy. These
tables reflect the available release versions and platforms as of the
Critical Patch Update release date. The patch availability is updated for any
platform releases that occur after the Critical Patch Update release date for
which a Critical Patch Update is provided. Note that depending on when a
platform is released only, the next Critical Patch Update will be provided.
For more information, see Section 5, "Planned Patches for the Next Critical
Patch Update Release." ·
On-Request (OR) Oracle no longer issues proactive patches for
platform-version combinations that have fewer than 10 downloads
in the prior Critical Patch Update period. Oracle will deliver patches for
these historically inactive platform-version combinations when requested. 3.2 Critical Patch Update Patch
Conflict Resolution
If you encounter a patch conflict
while installing the Critical Patch Update patch for Database, Enterprise
Manager, Fusion Middleware and BEA, you need to file a service request (SR)
with Oracle Global Support to request a merge patch. For 10.2.0.4 and later Database
versions see My Oracle Support Note 438314.1 Critical Patch Update - Introduction to Database n-Apply
CPU Patches for a description of how merge patches are provided. For Fusion Middleware patches
(excluding BEA) and Database versions 10.1.0.5 and earlier, approved merge
conflicts are incorporated into a Critical Patch Update merge patch that is
released four weeks after the Critical Patch Update release date. Critical
Patch Update merge patches are only provided for the platforms for which an
SR request has been filed. All merge requests are subject to approval based
on technical feasibility. To be considered for the next Critical Patch Update
merge patch, requests must be submitted before the conflict request deadline
date, which is two weeks after the Critical Patch Update release date. See Table 1 for the
specific dates for CPUOct2009. Any merge request that is submitted
after the conflict request deadline for any given Critical Patch Update will
be considered for inclusion in the Critical Patch Update merge patch for the
following Critical Patch Update. For example, the conflict request deadline
for CPUOct2009 is November 3rd. If a request is filed on November 15th, then
the conflict merge will be considered for the CPUJan2010 merge patch. Table 1 lists the
conflict request deadline for CPUJan2010 and the planned release date for the
Critical Patch Update merge patches. Table 1 Critical
Patch Update Merge Patch Schedule
3.3 On-Request Patches for Oracle
Database and Oracle Fusion Middleware Products
Oracle no longer issues proactive
patches for platform-version combinations that have fewer than 10 downloads in the prior Critical Patch Update period.
Oracle will deliver patches for these historically inactive platform-version
combinations when requested. To obtain a Critical Patch Update that has been indicated as on-request (OR), file a service
request (SR) with Oracle Global Support. You may file an on-request Critical
Patch Update as long as the version is supported for Critical Patch Updates.
For desupported codelines, an OR can be requested for 2 weeks after the
terminal Critical Patch Update is released. For example, Oracle Database
10.1.0.5 is supported through the release of CPUJan2012 on January 17, 2012.
This means you can file a request for 10.1.0.5 through January 31, 2012. A request may be made at any time. A
specific Critical Patch Update (e.g. CPUJan2010) cannot be requested. Either
the current Critical Patch Update or the next Critical Patch Update will be
provided depending on when the request is received and processed. A planned
availability date for the Critical Patch Update will be provided to you. Once
the Critical Patch Update becomes available, Table 16 or Table 37 will
indicate the Critical Patch Update as Available instead
of OR. For a patch set or product release
that is made available on a platform after a Critical Patch Update release
date, Oracle will provide the following Critical Patch Update for that
platform/release combination. A customer may request the current Critical
Patch Update, by following the on-request process indicated above. Depending
on when the request is received, the current or next Critical Patch Update
will be provided. For example, if a 10.2.0.4 database
patch set is released for a platform on August 1, 2008, Oracle will provide
the 10.2.0.4 CPUOct2008 on that platform. A customer may request a 10.2.0.4
CPUJul2008 on the platform, and Oracle will review the request and determine
whether to provide CPUJul2008 or CPUOct2008. 3.4 Critical Patch Updates and
Patch Set Updates
The Patch Set Updates and Critical
Patch Updates that are released each quarter contain the same security fixes.
However, they use different patching mechanisms and Patch Set Updates include
both security and recommended bug fixes. Please be aware of the following
when considering to apply Patch Set Updates instead
of Critical Patch Updates. ·
Critical
Patch Updates are applied only on the base release version, for example
10.2.0.4.0. ·
Patch Set
Updates can be applied on the base release version or on any earlier Patch
Set Update. For example, 10.2.0.4.2 can be applied on 10.2.0.4.1 and
10.2.0.4.0 ·
Once a
Patch Set Update has been applied, the recommended way to get future security
content is to apply subsequent Patch Set Updates. Reverting from an applied
Patch Set Update back to the Critical Patch Update, while technically
possible, requires significant time and effort, and is not advised. For more information on Patch Set
Updates, see Note 854428.1, Patch Set
Updates for Oracle Products. 4 Critical Patch Update Availability for Oracle Products
This section contains the following: ·
Section 4.1, "Oracle Application Express" ·
Section 4.2, "Oracle Audit Vault" ·
Section 4.3, "Oracle BEA Releases" ·
Section 4.4, "Oracle Beehive" ·
Section 4.5, "Oracle Business Intelligence
Enterprise Edition 10.1.3.4.x" ·
Section 4.6, "Oracle Business Intelligence
Publisher" ·
Section 4.7, "Oracle Collaboration Suite" ·
Section 4.8, "Oracle COREid" ·
Section 4.9, "Oracle Database" ·
Section 4.10, "Oracle Database Patch Set Update
(PSU)" ·
Section 4.11, "Oracle Database 10g Companion CD" ·
Section 4.12, "Oracle Enterprise Manager Grid
Control" ·
Section 4.13, "Oracle Fusion Middleware" ·
Section 4.14, "Oracle Hyperion BI+" ·
Section 4.15, "Oracle Outside In Technology" ·
Section 4.16, "Oracle Secure Backup" ·
Section 4.17, "Oracle Secure Enterprise Search" ·
Section 4.18, "Oracle TimesTen" ·
Section 4.19, "Oracle Workflow Server" ·
Section 4.20, "Oracle Workspace Manager" 4.1 Oracle Application Express
Table 2 describes
the minimum requirements for Oracle Application Express. The Oracle
Application Express downloads and installation instructions can be found at http://www.oracle.com/technology/products/database/application_express/download.html. Table 2 Minimum Product Requirements for
Oracle Application Express
4.2 Oracle Audit Vault
Table 3 describes
the minimum requirements for Oracle Audit Vault. Table 3 Minimum Product Requirements for
Oracle Audit Vault
Table 4 describes
the patches available for Oracle Audit Vault 10.2.3.2, based on release and
platform. For each home you are about to
administer, find the appropriate patches based on the components installed in
that home. Then, apply those patches in the order listed. Table 4 Critical Patch Update Availability for
Oracle Audit Vault 10.2.3.2
Table 5 describes
the patches available for Oracle Audit Vault 10.2.3.1, based on release and
platform. For each home you are about to
administer, find the appropriate patches based on the components installed in
that home. Then, apply those patches in the order listed. Table 5 Critical Patch Update Availability for
Oracle Audit Vault 10.2.3.1
4.3 Oracle BEA Releases
Table 6 describes
the available patches for Oracle BEA Releases based on release and platform.
The patches for the BEA components are documented in My Oracle Support Note 967464.1, Critical Patch
Update January 2010 Patch Availability Document for Oracle BEA Releases. For each home you are about to
administer, find the appropriate patches based on the components installed in
that home. Then, apply those patches in the order listed. Table 6 Critical Patch Update Availability for
Oracle BEA Releases
4.4 Oracle Beehive
Oracle Beehive environments contain
Oracle Database and Oracle Fusion Middleware homes. For information on Oracle
Database and Oracle Fusion Middleware Critical Patch Updates that apply to
Beehive homes, see My Oracle Support Note 758816.1, Applying
Critical Patch Updates to Beehive 1.5. 4.4.1 Minimum Product Requirements for Oracle
Beehive
Table 7 describes
the minimum requirements for Oracle Beehive. Table 7 Minimum Product Requirements for
Oracle Beehive
4.4.2 Critical Patch Update Availability for
Oracle Beehive 1.5.1
Table 8 describes
the patches that are available for Oracle Beehive 1.5.1. For each home you are about to
administer, find the appropriate patches based on the components installed in
that home. Then, apply those patches in the order listed. Table 8 Critical Patch Update Availability for
Oracle Beehive 1.5.1
4.5 Oracle Business Intelligence
Enterprise Edition 10.1.3.4.x
Table 9 describes
the patches that are available for Oracle Business Intelligence Enterprise Edition. Table 9 Critical Patch Update Availability for
Oracle Business Intelligence Enterprise Edition 10.1.3.4.x
4.6 Oracle Business Intelligence
Publisher
Table 10 describes
the patches that are available for Oracle Business Intelligence Publisher. Customers on earlier versions of
Oracle Business Intelligence Publisher will need to apply 10.1.3.3.2 or
10.1.3.4.0 and then apply the Critical Patch Update. Table 10 Critical Patch Update Availability
for Oracle Business Intelligence Publisher
4.7 Oracle Collaboration Suite
Oracle Collaboration Suite homes
contain database and application server homes. For more information on Oracle
Database and Oracle Fusion Middleware Critical Patch Updates that apply to
Oracle Collaboration Suite homes, see My Oracle Support Note 559534.1 Applying Critical Patch Updates to
Collaboration Suite 10g. 4.7.1 Minimum Product Requirements for Oracle
Collaboration Suite
Table 11 describes
the minimum requirements for Oracle Collaboration Suite. For CPUJan2010 patch
information, see Section 4.7, "Oracle Collaboration Suite." Table 11 Minimum Product Requirements for Oracle
Collaboration Suite
4.7.2 Critical Patch Update Availability for
Oracle Collaboration Suite
Table 12 describes
the patches that are available for Oracle Collaboration Suite. For minimum
requirements information. For each home you are about to
administer, find the appropriate patches based on the components installed in
that home. Then, apply those patches in the order listed. Table 12 Critical Patch Update Availability
for Oracle Collaboration Suite
4.8 Oracle COREid
Table 13 describes
the patches that are available for Oracle COREid. Customers on earlier
versions of Oracle COREid will need to apply the patches listed below. Table 13 Critical Patch Update Availability
for Oracle COREid
4.9 Oracle Database
This section contains the following: ·
Section 4.9.1, "Critical Patch Update Availability
for Oracle Database" ·
Section 4.9.2, "Oracle Database 11.1.0.7" ·
Section 4.9.3, "Oracle Database 10.2.0.4" ·
Section 4.9.4, "Oracle Database 10.2.0.3" ·
Section 4.9.5, "Oracle Database 10.1.0.5" ·
Section 4.9.6, "Oracle Database 9.2.0.8 DV" ·
Section 4.9.7, "Oracle Database 9.2.0.8" 4.9.1 Critical Patch Update Availability for
Oracle Database
Table 14 describes
the available patches for Oracle Database on UNIX. For information about
conflicts when installing patches, see Section 3.2, "Critical Patch Update Patch Conflict
Resolution." For Oracle Database 11.1.0.7 and
10.2.0.4, the Patch Set Update (PSU) is an alternate patch that includes the
CPUJan2010 security bug fixes. For more information, see Table 22,
and My Oracle Support Note 854428.1 Patch Set Updates for Oracle
Products. Table 14 Available Critical Patch Updates and
Patch Set Updates for Oracle Database on UNIX
Table 15 describes
the available patches for Oracle Database on Microsoft Windows. As Microsoft
Windows Bundles are cumulative, you may install the indicated patch or any
later bundle in the Windows bundle series to get the CPUJan2010 security bug
fixes. Table 15 Available Bundles for Oracle Database
on Microsoft Windows
4.9.2 Oracle Database 11.1.0.7
Table 16 describes
the patches that are available for Oracle Database 11.1.0.7. Table 16 Patch Availability for Oracle
Database 11.1.0.7
4.9.3 Oracle Database 10.2.0.4
Table 17 describes
the patches that are available for Oracle Database 10.2.0.4. Table 17 Patch Availability for Oracle
Database 10.2.0.4
4.9.4 Oracle Database 10.2.0.3
Table 18 describes
the patches that are available for Oracle Database 10.2.0.3. Table 18 Patch Availability for Oracle
Database 10.2.0.3
4.9.5 Oracle Database 10.1.0.5
Table 19 describes
the patches that are available for Oracle Database 10.1.0.5. Table 19 Patch Availability for Oracle
Database 10.1.0.5
4.9.6 Oracle Database 9.2.0.8 DV
Table 20 describes
the patches that are available for Oracle Database 9.2.0.8 DV. Table 20 Patch Availability for Oracle
Database 9.2.0.8 DV
4.9.7 Oracle Database 9.2.0.8
Table 21 describes
the patches that are available for Oracle Database 9.2.0.8. Table 21 Patch Availability for Oracle
Database 9.2.0.8
4.10 Oracle Database Patch Set
Update (PSU)
Table 22 lists the
patches for Oracle Database patch set updates. As Windows Bundles are cumulative,
you may apply the patch indicated in Table 16 or any
later bundle in the Windows bundle series to obtain the Patch Set Update bug
fixes. Table 22 Patch Set Update Availability for
Oracle Database
4.11 Oracle Database 10g Companion
CD
Table 23 lists
the patches for Oracle Fusion Middleware components, such as Oracle HTTP
Server, which are installed using the Oracle Database companion CD. Table 23 Critical Patch Update Availability for
Oracle Database 10g Companion CD
4.12 Oracle Enterprise Manager
Grid Control
Table 24 describes
the minimum requirements for Oracle Enterprise Manager Grid Control. For
CPUJan2010 patch information, see Section 4.12, "Oracle Enterprise Manager Grid
Control." For
information on identifying the components that are installed in your
environment, see My Oracle Support Note 605398.1, How To Find
The Version Of The Main EM Components. Table 24 Minimum Product Requirements for
Oracle Enterprise Manager Grid Control
The following tables describe
Critical Patch Update availability for Oracle Enterprise Manager Grid
Control: ·
Table 25, "Critical Patch Update Availability for
Oracle Enterprise Manager Grid Control 10.2.0.5" ·
Table 26, "Critical Patch Update Availability for
Oracle Enterprise Manager Grid Control 10.2.0.4" ·
Table 27, "Critical Patch Update Availability for
Oracle Enterprise Manager Grid Control 10.1.0.6" ·
Table 28, "Critical Patch Update Availability for
Oracle9i Enterprise Manager" The Critical Patch Updates for
Enterprise Manager Grid Control are not inclusive of the Oracle Database and
Oracle Fusion Middleware middle tier patches. Since these products are
bundled with Enterprise Manager Grid Control, the Repository (Oracle Database)
and Oracle Management Server (Oracle Fusion Middleware middle tier) should be
patched separately, depending on which versions are installed. For more
information, see My Oracle Support Note 412431.1, Grid Control
Certification Matrix. 4.12.1 Critical Patch Update Availability for
Oracle Enterprise Manager Grid Control 10.2.0.5
Table 25 describes
the patches that are available for Oracle Enterprise Manager Grid Control
10.2.0.5. For minimum requirements information, see Table 24, "Minimum Product Requirements for Oracle
Enterprise Manager Grid Control". For each home you are about to
administer, find the appropriate patches based on the components installed in
that home. Then, apply those patches in the order listed. For information on
identifying the components that are installed in your environment, see My
Oracle Support Note 605398.1, How To Find
The Version Of The Main EM Components. Table 25 Critical Patch Update Availability
for Oracle Enterprise Manager Grid Control 10.2.0.5
4.12.2 Critical Patch Update Availability for
Oracle Enterprise Manager Grid Control 10.2.0.4
Table 26 describes
the patches that are available for Oracle Enterprise Manager Grid Control 10.2.0.4.
For minimum requirements information, see Table 24, "Minimum Product Requirements for Oracle Enterprise
Manager Grid Control". For each home you are about to
administer, find the appropriate patches based on the components installed in
that home. Then, apply those patches in the order listed. For information on
identifying the components that are installed in your environment, see My
Oracle Support Note 605398.1, How To Find
The Version Of The Main EM Components. Table 26 Critical Patch Update Availability
for Oracle Enterprise Manager Grid Control 10.2.0.4
4.12.3 Critical Patch Update Availability for
Oracle Enterprise Manager Grid Control 10.1.0.6
Table 27 describes
the patches that are available for Oracle Enterprise Manager Grid Control 10.1.0.6.
For minimum requirements information, see Section 4.12, "Minimum Product Requirements for Oracle
Enterprise Manager Grid Control." For each home you are about to
administer, find the appropriate patches based on the components installed in
that home. Then, apply those patches in the order listed. Table 27 Critical Patch Update Availability
for Oracle Enterprise Manager Grid Control 10.1.0.6
4.12.4 Critical Patch Update Availability for
Oracle9i Enterprise
Manager
Table 28 describes
the patches that are available for Oracle9i Enterprise Manager. For minimum
requirements information, see Table 24, "Minimum Product Requirements for Oracle
Enterprise Manager Grid Control".4 For each home you are about to
administer, find the appropriate patches based on the components installed in
that home. Then, apply those patches in the order listed. Table 28 Critical Patch Update Availability
for Oracle9i Enterprise Manager
4.13 Oracle Fusion Middleware
Oracle Fusion Middleware 10.1.x
consists of the Oracle Fusion Middleware middle tier and the Oracle Fusion
Middleware Infrastructure. Oracle Fusion Middleware 11.1.1.1 consists of the
Oracle Fusion Middleware home. If you have questions on how to
identify the Critical Patch Update patches for your particular Oracle Fusion
Middleware deployment, refer to My Oracle Support Note 405972.1, Oracle
Application Server 10g Examples for Critical Patch Updates. The
note includes detailed scenarios specific to Critical Patch Update releases,
including CPUJan2010. This section contains the following: ·
Section 4.13.1, "Minimum Requirements for Oracle
Identity Management" ·
Section 4.13.2, "Critical Patch Update Availability
for Oracle Identity Management 10.1.4.3" ·
Section 4.13.3, "Critical Patch Update Availability
for Oracle Identity Management 10.1.4.0.1" ·
Section 4.13.4, "Oracle Fusion Middleware Minimum
Requirements" ·
Section 4.13.5, "Critical Patch Update Availability
for Oracle Fusion Middleware" ·
Section 4.13.6, "Critical Patch Update Availability
for Oracle Fusion Middleware 11.1.1.x" ·
Section 4.13.7, "Critical Patch Update Availability
for Oracle Fusion Middleware 10.1.3.5.x" ·
Section 4.13.8, "Critical Patch Update Availability
for Oracle Fusion Middleware 10.1.3.4" ·
Section 4.13.9, "Critical Patch Update Availability
for Oracle Fusion Middleware 10.1.2.3" 4.13.1 Minimum Requirements for Oracle Identity
Management
Table 29 describes
the minimum requirements for Oracle Identity Management 10.1.4.x. Table 29 Minimum Product Requirements for
Oracle Identity Management
4.13.2 Critical Patch Update Availability for
Oracle Identity Management 10.1.4.3
Table 30 describes
patch information for Oracle Identity Management 10.1.4.3. For each home you are about to
administer, find the appropriate patches based on the components installed in
that home. Then, apply those patches in the order listed. For information
about the different types of installations, see Section 4.13, "Oracle Fusion Middleware." See Table 33 prior to
downloading the infrastructure and middle tier patches to verify the patches
are available on your target platforms. Table 30 Critical Patch Update Availability
for Oracle Identity Management 10.1.4.3
4.13.3 Critical Patch Update Availability for
Oracle Identity Management 10.1.4.0.1
Table 31 describes
patch information for Oracle Identity Management 10.1.4.0.1. For each home you are about to
administer, find the appropriate patches based on the components installed in
that home. Then, apply those patches in the order listed. For information
about the different types of installations, see Section 4.13, "Oracle Fusion Middleware." See Table 33 prior to
downloading the infrastructure and middle tier patches to verify the patches
are available on your target platforms. Table 31 Critical Patch Update Availability
for Oracle Identity Management 10.1.4.0.1
4.13.4 Oracle Fusion Middleware Minimum
Requirements
Table 32 describes
the minimum requirements for all Oracle Fusion Middleware products, including
infrastructure, middle tier and standalone homes. For CPUJan2010 patch
information, see Section 4.13, "Oracle Fusion Middleware." Table 32 Minimum Product Requirements for
Oracle Fusion Middleware Critical Patch Updates
Footnote 1 JInitiator is a Java Virtual Machine plug-in
which has its own installation process. It is not part of any Oracle home. It
is installed by default only in homes where Oracle Forms is installed. 4.13.5 Critical Patch Update Availability for
Oracle Fusion Middleware
Table 33 describes
the patches that are available for Oracle Fusion Middleware, based on release
and platform. Table 33 Critical Patch Update Availability
for Oracle Fusion Middleware
4.13.6 Critical Patch Update Availability for
Oracle Fusion Middleware 11.1.1.x
Table 34 describes
patch information for Oracle Fusion Middleware 11.1.1.x. Table 34 Critical Patch Update Availability
for Oracle Fusion Middleware 11.1.1.x
4.13.7 Critical Patch Update Availability for
Oracle Fusion Middleware 10.1.3.5.x
Table 35 describes
patch information for Oracle Fusion Middleware 10.1.3.5.x. For each home you are about to
administer, find the appropriate patches based on the components installed in
that home. Then, apply those patches in the order listed. For information
about the different types of installations, see Section 4.13, "Oracle Fusion Middleware." See Table 33 prior to
downloading the infrastructure and middle tier patches to verify the patches
are available on your target platforms. Table 35 Critical Patch Update Availability
for Oracle Fusion Middleware 10.1.3.5.x
4.13.8 Critical Patch Update Availability for
Oracle Fusion Middleware 10.1.3.4
Table 36 describes
patch information for Oracle Fusion Middleware 10.1.3.4. For each home you are about to
administer, find the appropriate patches based on the components installed in
that home. Then, apply those patches in the order listed. For information
about the different types of installations, see Section 4.13, "Oracle Fusion Middleware." See Table 33 prior to
downloading the infrastructure and middle tier patches to verify the patches
are available on your target platforms. Table 36 Critical Patch Update Availability
for Oracle Fusion Middleware 10.1.3.4
4.13.9 Critical Patch Update Availability for
Oracle Fusion Middleware 10.1.2.3
Table 37 describes
patch information for Oracle Fusion Middleware 10.1.2.3. For each home you are about to
administer, find the appropriate patches based on the components installed in
that home. Then, apply those patches in the order listed. For information
about the different types of installations, see Section 4.13, "Oracle Fusion Middleware." Table 37 Critical Patch Update Availability
for Oracle Fusion Middleware 10.1.2.3
4.14 Oracle Hyperion BI+
Table 38 describes
the patches available for Oracle Hyperion BI+, based on release. Table 38 Minimum Product Requirements for
Oracle Hyperion BI+
4.15 Oracle Outside In Technology
Table 39 describes
the minimum requirements for Oracle Outside In Technology. Table 39 Minimum Product Requirements for
Oracle Outside In Technology
Table 40 describes
the available patches for Oracle Outside in Technology. Table 40 Critical Patch Update Availability
for Oracle Outside In Technology
4.16 Oracle Secure Backup
Table 41 describes
the minimum requirements for Oracle Secure Backup. Table 41 Minimum Product Requirements for
Oracle Secure Backup
Table 42 describes
the available patches for Oracle Secure Backup. Table 42 Critical Patch Update Availability
for Oracle Secure Backup
4.17 Oracle Secure Enterprise
Search
Table 43 describes
the minimum requirements for Oracle Secure Enterprise Search. Table 43 Minimum Product Requirements for
Oracle Secure Enterprise Search
Table 44 describes
the patches that are available for Oracle Secure Enterprise Search. Table 44 Critical Patch Update Availability
for Oracle Secure Enterprise Search
4.18 Oracle TimesTen
Table 45 describes
the minimum requirements for Oracle TimesTen. Table 45 Minimum Product Requirements for
Oracle TimesTen
4.19 Oracle Workflow Server
Table 46 describes
the minimum requirements for Oracle Workflow Server. For CPUJan2010 patch
information, see Section 4.9, "Oracle Database" and Section 4.13, "Oracle Fusion Middleware." Table 46 Minimum Product Requirements for
Oracle Workflow Server
Table 47 describes
the patches that are available for Oracle Workflow Server. Table 47 Critical Patch Update Availability
for Oracle Workflow Server
4.20 Oracle Workspace Manager
Table 48 describes
the patches that are available for Oracle Workspace Manager, based on
release. Table 48 Oracle Workspace Manager Patch
Availability
5 Planned Patches for the Next Critical Patch Update Release
This section lists the planned
patches for the next Critical Patch Update release. It is intended for your
planning purposes only. ·
Bundle The Critical Patch Update and Patch Set Update
fixes are included in cumulative Microsoft Windows Bundles. ·
Planned The Critical Patch Update is planned. ·
Not Applicable (NA) The Critical Patch Update is not planned for
this platform and release version combination. This may be due to several reasons including: 1.
The
release version is not available on this platform. 2.
The release
version does not fall under Critical Patch Update release policies. Refer to
the My Oracle Support Note 209768.1, Database, FMW,
EM Grid Control, and OCS Software Error Correction Support Policy. ·
On-Request (OR) In order to provide enhanced support to our
customers, Oracle no longer issues proactive patches for platform-version
combinations that have had fewer than 10 downloads in the prior Critical
Patch Update period. Oracle delivers patches for these historically inactive
platform-version combinations to customers on an on-request basis. Requests
are considered only for platform-version combinations indicated with OR in
the following tables: o Table 49, "Planned Critical Patch Updates for Oracle
Database" Table 49 describes
the planned patches for Oracle Database, based on release: Table 49 Planned Critical Patch Updates for
Oracle Database
Table 50 describes
the planned patches for Oracle Fusion Middleware Infrastructure and middle tiers. Table 50 Planned Critical Patch Updates for
Oracle Fusion MIddleware Infrastructure and Middle Tier
6 Terminal Critical Patch Update History
Table 51 describes
the release for terminal Critical Patch Updates. Table 51 Terminal Critical Patch Update
History
7 Determining Oracle Environment Settings
The following sections describe how
to determine your environment settings: ·
Section 7.1, "Oracle Application Express Release
Information," ·
Section 7.2, "Oracle Database Release
Information" ·
Section 7.3, "Oracle Fusion Middleware Release
Information" ·
Section 7.4, "Oracle Workflow Server Release
Information" 7.1 Oracle Application Express
Release Information
To find out which version of
Application Express is installed, execute the following query from any
schema: select * from apex_release;
7.2 Oracle Database Release
Information
To determine the Oracle Database
release information, you can issue the following commands. ·
Start
SQL*Plus from the Oracle home directory: · sqlplus /nolog · SQL> CONNECT / AS SYSDBA · SQL> select * from v$version; The
command returns the release information, such as the following: Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production PL/SQL Release 9.2.0.8.0 - Production CORE 9.2.0.8.0 Production TNA for 32-bit Windows: Version 9.2.0.8.0 - Production NLSRTL Version 9.2.0.8.0 - Production
7.3 Oracle Fusion Middleware
Release Information
To determine the Oracle Fusion
Middleware release information, check the installed product information using
the Oracle Universal Installer. 7.4 Oracle Workflow Server
Release Information
Oracle Workflow Server is installed
as follows: ·
Non-default
option for Oracle Database ·
CMSDK
component for Oracle Fusion Middleware ·
Non-default
option for Oracle Collaboration Suite 10g To determine the Oracle Workflow release information: ·
Log in to
the database as the · select wf_core.translate('WF_VERSION') from dual; 8 Sources of Additional Information
The following documents provide
additional information about Critical Patch Updates: ·
My Oracle
Support Note 967493.1, Critical Patch
Update January 2010 Database Patch Security Vulnerability Molecule Mapping ·
My Oracle
Support Note 967492.1, Critical Patch
Update January 2010 Known Issues for Oracle Enterprise Manager Grid Control. ·
My Oracle
Support Note 967475.1, Critical Patch
Update January 2010 Oracle Fusion Middleware Known Issues. ·
My Oracle
Support Note 967430.1, Critical Patch
Update January 2010 Database Known Issues. ·
My Oracle
Support Note 605795.1, Introduction
to catbundle.sql. ·
My Oracle
Support Note 605398.1, How To Find
The Version Of The Main EM Components. ·
My Oracle
Support Note 559534.1, Applying
Critical Patch Updates to Collaboration Suite 10g. ·
My Oracle
Support Note 438314.1, Critical Patch
Update - Introduction to Database n-Apply CPU Patches. ·
My Oracle
Support Note 412431.1, Grid Control
Certification Matrix. ·
My Oracle
Support Note 405972.1, Oracle
Application Server 10g Examples for Critical Patch Updates. ·
My Oracle
Support Note 209768.1, Database, FMW,
EM Grid Control, and OCS Software Error Correction Support Policy. ·
My Oracle
Support Note 161549.1, Oracle
Database Server and Networking Patches for Microsoft Platforms. 9 Modification History
Table 52 lists the
modification history for this document.
10 Documentation Accessibility
Our goal is to make Oracle products,
services, and supporting documentation accessible to all users, including
users that are disabled. 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. Deaf/Hard of Hearing Access to Oracle Support Services To reach Oracle Support Services, use
a telecommunications relay service (TRS) to call Oracle Support at
1.800.223.1711. An Oracle Support Services engineer will handle technical
issues and provide customer support according to the Oracle service request
process. Information about TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of phone numbers is available at http://www.fcc.gov/cgb/dro/trsphonebk.html. |