[repaste]Oracle 11.2.0.2 Patch Set

作者: Maclean Liu , post on September 12th, 2010 , English Version
【本站文章除注明转载外,均为本站原创编译】
转载请注明:文章转载自: Oracle Clinic – Maclean Liu的个人技术博客 [http://www.oracledatabase12g.com/]
本文标题: [repaste]Oracle 11.2.0.2 Patch Set
本文永久地址: http://www.oracledatabase12g.com/archives/repasteoracle-11-2-0-2-patch-set.html

Oracle最新为Linux x86和x86-64平台发布了Oracle 11.2.0.2 patch set,这个庞大的patch set拥有5G的超大容量。所以几乎全世界的人都在问,这真的是一个补丁集吗?不仅仅是体积庞大,甚至还一改往日补丁集仅仅是作为Bug修复的角色,在 11.2.0.2中还包含了很多New Feature

Oracle专门为此补丁写了一篇文章-Important Changes to Oracle Database Patch Sets Starting With 11.2.0.2 ID 1189783.1,着重提到了几点。

1. Oracle 11.2.0.2 patch set是一个完整的安装包,以后Oracle也会如此发布后续的补丁包。所以在以后如果要安装新数据软件,不再需要安装一个Base版本然后再打补丁集到最新版本,而是直接使用最新补丁集安装包即可。
2. Oracle建议今后的补丁集安装都安装在一个与当前环境目录不同的全新目录下(Out-of-place upgrade),在安装完成以后再通过此份软件启动数据库实例。实际上以后安装补丁集的过程就等同于从一个版本升级到一个新版本的过程。
3. 为什么做这种改变,是因为Oracle认为Out-of-place upgrade是最佳实践,比较安全。当然这实际上符合Oracle的作风,他认为合理且最好的通常都会武断地改变并且说服客户去接受。
4. Oracle仅仅计划在11.2.0.2中提供一些新功能,今后的补丁集仍然会以修复bug为首要任务。

我个人承认确实Out-of-place upgrade是更加安全的,但是至少这种做法目前存在两点缺陷:
1. 补丁尺寸急剧增加,下载2G的补丁和下载5G的补丁还是有很大区别,但是这不是大问题。当然,由于需要安装在新Oracle Home中,在打补丁时需要额外的硬盘空间,但是不到10G的空间需求也不是大问题。
2. 由于在打完补丁以后,Oracle Home路径实际上发生了变化,那么在脚本中,服务定义中牵涉到的原ORACLE_HOME路径必须都要做相应改动。这是个大问题。

今后的补丁集发布计划可以参看Release Schedule of Current Database Releases ID 742060.1

From:http://lab.enmou.com/index.php?title=Oracle_11.2.0.2_Patch_Set

Important Changes to Oracle Database Patch Sets Starting With 11.2.0.2

Applies to:

Oracle Server – Enterprise Edition – Version: 11.2.0.2 and later   [Release: 11.2 and later ]
Oracle Server – Standard Edition – Version: 11.2.0.2 and later    [Release: 11.2 and later]
Oracle Server – Personal Edition – Version: 11.2.0.2 and later    [Release: 11.2 and later]
Information in this document applies to any platform.

What is being announced?

Important Changes to Oracle Database Patch Sets Starting With 11.2.0.2

What has changed?

Packaging: Starting with the first patch set for Oracle Database 11g Release 2 (11.2.0.2), Oracle Database patch sets are full installations of the Oracle Database software. In past releases, Oracle Database patch sets consisted of a set of files that replaced files in an existing Oracle home. Beginning with Oracle Database 11g release 2, patch sets are full installations that replace existing installations.

Because Oracle Database 11g Release 2 and later patch sets are a full installation, Oracle patch sets are now released as several installation bundles, just as are the base releases:

  • Oracle Database Server
  • Oracle Grid Infrastructure
  • Oracle Database Client
  • Companion/examples
  • Oracle Gateways


Simplified new installation: Because the release 11.2.0.2 patch set is a full installation package, if you are installing Oracle Database on a system without an existing Oracle Database installation, then you can simply install the release 11.2.0.2 patch set. You are no longer required to install the base release, and then apply the patch set.

Upgrade process:
Beginning with the release 11.2.0.2 patch set, you have two ways to apply a patch set:

  • Out-of-place upgrade – This is Oracle’s recommended way to apply a patch set. You install the patch set into a new, separate Oracle home location. After you install the patch upgrade, you then migrate the Oracle Database from the older Oracle home. The patch set upgrade is now the same process to upgrade from one version to another. Oracle recommends that you perform an out-of-place patch set upgrade, because this patch set application option requires much less downtime, and is safer because it does not require patching an ORACLE_HOME that is already being used in production. However, you must ensure that you have sufficient free disk space to accommodate two Oracle home directories at the same time.
  • In-place upgrade – You install the patch set into an existing Oracle home location. Oracle recommends that you select this option only if you do not have sufficient free disk space to perform an out-of-place upgrade, as the upgrade removes the existing Oracle installation. This patch option requires less disk space, but requires more time, and is riskier, because if you encounter an installation failure, then you must recover the entire existing Oracle home from a backup. If you choose this more risky option, then before you begin the patch installation, complete the following tasks:
    • Make a complete backup of your existing Oracle home
    • Read through the entire Upgrade Guide section dealing with in-place upgrades
Note: All Oracle Grid Infrastructure patch set upgrades must be out-of-place upgrades, in which you install the patch set into a new Grid home. In-place patch set upgrades are not supported.


Direct upgrade from previous releases:
You can upgrade from a previous Oracle Database release directly to the latest patch set update, without having to install the base release. For example, if you want to upgrade from Oracle Database 10g Release 2, or Oracle Database 11g Release 1, then you can upgrade directly to Oracle Database 11g Release 2, patch set 2 (11.2.0.2) using an out-of-place upgrade. Oracle now supports direct upgrades to the release 11.2.0.2 patch set from any release where direct upgrade to the base release (11.2.0.1) is supported, as well as direct upgrades from 11.2.0.1 to 11.2.0.2.
New Features Available in Patch Sets

In addition to the usual set of fixes, the release 11.2.0.2 patch set contains a small number of features that complete the Database 11g Release 2 feature set. The new features fall into the following five categories:

  • General improvements
  • Oracle Automatic Storage Management Cluster File System (ACFS) improvements
  • Quality of Service Management
  • Database Replay
  • Management

For information about all new features, refer to Oracle Database New Features Guide for Oracle Database 11g Release 2.

How to Obtain the Patch Set

As with all previous patch sets, the release 11.2.0.2 patch set is available for download from the Patches tab on My Oracle Support. In addition, the patch set is available for download from the following URL:

http://edelivery.oracle.com/

Important Changes to Note:

  1. Disk space requirement: Because the out-of-place upgrade requires the installation of a new Oracle home, you must have enough free disk space to accommodate the new Oracle home, as well as disk space needed for temporary files during installation.
  2. ORACLE_HOME location change: When using the out-of-place upgrade path, the location of your Oracle home is different after you complete the upgrade. You must change any direct references to the old location of your Oracle home (such as in /etc/oratab or in tnsnames.ora) to the new location, and update user environment variables for the Oracle home.
  3. In-place upgrade process differs from previous patch set installation processes: Even though it seems similar, the in-place upgrade process for the release 11.2.0.2 patch set differs from previous patch set installation procedures. It is very important to read the entire in-place upgrade process before you begin to install the release 11.2.0.2 patch set, because the preinstallation steps are different.

Frequently Asked Questions

Q. Is this really a patch set?

A. Yes – This patch release still consists primarily of incremental bug fixes to the base release (11.2.0.1). The patch release simply is packaged differently. While new features are included in 11.2.0.2, the number of new features is very small, and we currently have no plans to include new features in future11.2 patch sets.

Q. Why did Oracle make this change?

A. In response to customer feedback, Oracle is making this change for several reasons:

  • Out-of-place upgrade has been a best practice of many customers for patch set application for years. Out-of-place upgrades reduce downtime, because you can complete the initial installation and configuration of the upgrade before you take down the existing installation. Out-of-place patch upgrades are easier, safer, and provide faster fallback if needed: If you encounter issues with the new installation, then simply point clients back to the original Oracle Database installation Oracle home, and restart the database.
  • Out-of-place upgrades allow customers running multiple instances out of one Oracle home to upgrade each instance individually rather than having to upgrade all instances sharing an Oracle home at the same time (and incur downtime on them all simultaneously).
  • Full installations provide a better customer experience during the upgrade. By creating a full installation package that uses the same installation process as a base release (as opposed to a differential install of the changes objects), Oracle is able to use the same tools to build and test the patch set installation as Oracle uses with the base release. Improved testing enables a smoother, more trouble-free upgrade process that uses significantly less down time.
  • Full installations provide an easier upgrade for customers moving to release 11.2.0.2 from releases earlier than Oracle Database 11g release 2. Instead of having to install the most recent base release, and then applying a patch release, you can now upgrade to the latest release in one step.

Q. Is this new packaging unique to the 11.2.0.2 patch set, or will Oracle follow this model for future patch sets?

A. This will be the new model going forward. Oracle will release patch set release 11.2.0.3 and later patch sets as full installation packages. Direct out-of-place upgrade is the Oracle best practices recommendation for patch set upgrades.

Q. There are many new features in 11.2.0.2. Are patch sets not just for bug fixes?

A. Oracle intends to maintain the focus of patch sets as a fix delivery vehicle. Oracle has included a very small number of new features in past patch sets. In this case, after the release of Oracle Database 11g release 2 (11.2.0.1), Oracle completed development of a small number of features that are closely related to the 11.2 release, and Oracle is including these features so that you can use them now, rather than wait for their inclusion in next major release.

© 2010, www.oracledatabase12g.com. 版权所有.文章允许转载,但必须以链接方式注明源地址,否则追究法律责任.

相关文章 | Related posts:

  1. Patch set update 11.2.0.1.1 Readme quote
  2. 7月最新发布11.2.0.1.2 Patch set update
  3. Patch 9352164 – 10.2.0.4.4 Patch Set Update
  4. 7月最新发布10.2.0.4.5 Patch Set Update
  5. Patch 9352164 – 10.2.0.4.4 Patch Set Update Readme
  6. Upgrading to RAC 11g R2 What you should know
  7. CLOBs and NCLOBs character set storage in Oracle Release 8i, 9i, 10g and 11g
  8. Release 2 (9.2.0.8) Patch Set 7 for AIX 5L Based Systems (64-Bit)
  9. CRS PSU 10.2.0.4.4 Readme (BUNDLE Patch for Base Bug 9294403)
  10. AL32UTF8 / UTF8 (Unicode) Database Character Set Implications

5 comments to [repaste]Oracle 11.2.0.2 Patch Set

  • admin

    Release Schedule of Current Database Releases

    Applies to:

    Oracle Server – Enterprise Edition – Version: 10.1.0.5 to 11.2.0.1 – Release: 10.1 to 11.2
    Information in this document applies to any platform.

    What is being announced?

    Below is the schedule and pertinent support information for currently released Oracle Database base releases and patch sets. The table below represents the most accurate information Oracle can provide, and is updated frequently.

    Because Support cannot provide any dates other than these to customers, please do not log a Service Request asking for a schedule update.

    Disclaimer:

    The dates published in this document are for planning and discussion purposes only. It is intended solely to help you plan your I.T. projects. The dates are not a firm development plan. The release and timing of any platforms are subject to change at any time and at Oracle’s sole discretion.

    Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Software License and Service Agreement, which has been executed and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside of the licensed organization without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

    Current Oracle Database Release Schedule

     

    Platform 10.1.0.5 10.2.0.4 10.2.0.53 11.1.0.71 11.2.0.12 11.2.0.2
    Linux x86 30-JAN-2006 22-FEB-2008 30-APR-2010 18-SEP-2008 1-SEP-2009 OCT-2010
    Linux x86-64 24-FEB-2006 17-MAR-2008 30-APR-2010 18-SEP-2008 1-SEP-2009 OCT-2010
    Linux Itanium 30-APR-2006 24-SEP-2008 Q1CY2011 Platform desupported
    (see Doc ID 1130325.1)
    Platform desupported
    (see Doc ID 1130325.1)
     
    IBM Linux on POWER Not planned 9-JAN-2009
    Patching for previous
    release ended 9-Apr-09
    Q1CY2011 Not planned Sched TBA Sched TBA
    IBM Linux on System z 26-AUG-2006 16-DEC-2008
    Patching for previous
    release ended 16-Mar-09
    Q4CY2010 Not planned Not planned Q1CY2011
    HP-UX PA-RISC (64-bit) 05-FEB-2006 02-JUN-2008 Q4CY2010 11-Nov-2008 20-MAY-2010 Q1CY2011
    HP-UX Itanium 07-JUN-2006 30-APR-2008 3-JUN-2010 06-OCT-2008 22-DEC-2009 Q4CY2010
    Oracle Solaris SPARC (64-bit) 05-FEB-2006 30-APR-2008 19-MAY-2010 06-OCT-2008 6-Nov-2009 Q4CY2010
    Oracle Solaris x86-64 (64-bit) Not planned 13-NOV-2008 19-MAY-2010 Not planned 25-Nov-2009 Q4CY2010
    IBM AIX on POWER Systems 05-FEB-2006 15-MAY-2008 3-JUN-2010 06-OCT-2008 22-DEC-2009 Q4CY2010
    Microsoft Windows (32-bit) 13-FEB-2006 17-MAR-2008 19-JUL-2010 10-OCT-2008 5-APR-2010 Q4CY2010
    Microsoft Windows x64 (64-bit) Not planned 16-MAY-2008 27-JUL-2010 13-NOV-2008 2-APR-2010 Q4CY2010
    Microsoft Windows Itanium (64-bit) 30-JAN-2006 2-FEB-2009
    Patching for previous
    release ended 2-May-09
    Q4CY2010 Not planned Not planned Sched TBA
    Apple Mac OS X (PowerPC) 08-JAN-2007 Platform Obsolete Platform Obsolete Platform Obsolete Platform Obsolete Platform Obsolete
    Apple Mac OS X (Intel) Not planned 10-April-2009
    Single Instance only
    Sched TBA Not planned Sched TBA Sched TBA
    HP Tru64 UNIX 18-OCT-2006
    20-FEB-2009
    Patching for previous
    release ended 20-May-09

    Q1CY2011 Platform Obsolete Platform Obsolete Platform Obsolete
    Oracle Solaris x86 (32-bit) 18-JUN-2006 14-Nov-2008
    Last patch set for this
    platform
    Platform Obsolete Platform Obsolete Platform Obsolete Platform Obsolete
    HP OpenVMS Alpha 15-FEB-2008 15-Dec-2008
    Q3CY2011 Platform Obsolete Platform Obsolete Platform Obsolete
    HP OpenVMS Itanium Not planned 15-Dec-2008 Q3CY2011 Not planned Not planned Q1CY2011
    IBM z/OS on System z 06-MAR-2006 Not planned Q3CY2011 Unsupported
    Platform
    (see Doc ID 461234.1)
    Unsupported
    Platform
    (see Doc ID 461234.1)
    Unsupported
    Platform
    (see Doc ID 461234.1)
    Platform 10.1.0.5 10.2.0.4 10.2.0.5 11.1.0.7 11.2.0.1  

    Legend:

    Sched TBA = Schedule To Be Announced

    DD-MMM-YYYY: Available, date shown is when the patch set was made available on My Oracle Support/MetaLink

    1H or 2H CYyyyy: Date falls within the 1st half (six months) or 2nd half of Calendar Year. For example 1H CY2009 means “some time within the first six months of 2009″.

    Qn CYyyyy: Date falls within the nth Quarter (3 month period) of the Calendar Year specified. For example Q2 CY 2009 means “sometime within the second quarter of 2009, ie between April and June 2009″.

    Unsupported platform – means that no further Database releases will be ported to this platform

    Patching for previous release ends: explained in next section.

    Patching end date

    The date after which Oracle will no longer provide patches or CPUs for the previous release/patch level. This grace period is to allow customers adequate time to plan for the installation of the new patch set.  For example, 10.2.0.4 was first released on 22-Feb-08.  Oracle will continue to patch the previous patch set (10.2.0.3) for one year from that date on the assumption that customers are using this time to do whatever planning is necessary to be able to install 10.2.0.4.  For more information please see Database, FMW, EM Grid Control, and OCS Software Error Correction Support Policy (Doc ID 209768.1). In some cases the grace period for a particular platform release may end later than the standard grace period due to its being released more than 9 months after the base release – we always allow at least 3 months to install the new patch set. When that happens the specific end of patching for the previous release will be listed in the table entry for that release.

    The patching end dates for the different release/patch levels are as follows unless noted otherwise in the table:

    Release Patching Ends
    10.1.0.4 30-Jan-2007
    10.2.0.3 22-Feb-2009
    10.2.0.4 30-APR-2011
    11.1.0.6 18-Sep-2009

     Click here to view the dates.  Note that although 10.2 Extended Support begins in August 2010, Extended Support fees have been waived for the first year for all customers – for more information see the Oracle Technical Support Policy document section 6 (d).

    Notes:

    • 111.1.0.7 is the last patch set for Release 11.1.  Future integrated error correction will come in the form of Patch Set Updates.  Please see Patch Set Updates for Oracle Products (Doc ID 854428.1) for current details.
    • 211.2.0.1 is a base release.  
    • 310.2.0.5 is the last patch set for Release 10.2. Once patching ends for 10.2.0.4, future integrated error correction will come in the form of Patch Set Updates. Please see Patch Set Updates for Oracle Products (Doc ID 854428.1) for current details. 
      • The start of Extended Support no longer forces customers to run the last patch set in order to receive new fixes (such as PSU or CPU) – 10.2.0.4 will be patched up until the end date listed above.
    • Future Oracle Database releases are planned for the other platforms but due to Oracle’s revenue recognition policy we are unable to publish those schedules at this time. This schedule only includes releases which have already been released on at least one platform.
    • Last Patch Set: When Oracle knows which patch set will be the last for a particular release, it will be indicated but designation as such is at Oracle’s discretion and subject to change without notice.
    • Solaris x86-32: The last patch set for this platform is 10.2.0.4.
    • Solaris x86-64: Oracle has elevated the Solaris x86-64 to equal priority with SPARC Solaris for future Database releases.  Customers should expect more timely releases and patch sets for the Solaris x86-64 platform.
  • ztg

    “服务定义中牵涉到的原ORACLE_HOME路径必须都要做相应改动”,指的是自己写服务还是ORACLE自己的服务,如果是ORACLE自己的漏掉一个,可能引来很多麻烦

  • admin

    主要是自己写的脚本中定义的服务。

  • Is there a way to know upcoming Oracle 11G patches? how can we know when Oracle will publish the new patches, currently we are using 11G R2 V1 (11.0.2.0.1.0).
    also what is the difference between Oracle patch and Oracle patch-set.

    thank you.

  • [...] Set 11.2.0.2 for Win32 and Win64 now available Upgrading to the New ReleaseOracle 11.2.0.2 Patch Set(完) 此条目发表在 Database 分类目录,贴了 installation, patchset, upgrade, win [...]

Leave a Reply

  

  

  

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>