RAC Grid Infrastructure安装11.2.0.3.5 14727347 PSU GI-RDBMS补丁

《【视频教学】Maclean教你用Vbox在Linux 6.3上安装Oracle 11gR2 RAC》 中我们介绍了在11.2.0.3 Grid Infrastructure GI环境下安装11.2.0.3.5 14727347 补丁的步骤; 由于该11.2.0.3.5的opatch auto安装会有问题,所以我们使用手动的opatch apply安装该补丁,以下是检验步骤:

14727347解压后包含了2个补丁目录14727310和15876003 ,已包含11.2.0.3.5 DB的PSU,下载了该GI PSU后无需再去下载DB 的PSU了。

 

PSU 14727347的下载地址
Patch 14727347 GRID INFRASTRUCTURE PATCH SET UPDATE 11.2.0.3.5 (INCLUDES DB PSU 11.2.0.3.5)
1) rootcrs.pl 停止本节点的服务,若有RDBMS DB在运行则首先关闭该实例

su – oracle

$ <ORACLE_HOME>/bin/srvctl stop database –d <db-unique-name>

su – root

$GRID_HOME/crs/install/rootcrs.pl -unlock

2) 给GI HOME打补丁

AIX上: su – root;  slibclean

 

su – grid

opatch napply -oh $GRID_HOME -local /tmp/patch/14727310
opatch napply -oh $GRID_HOME -local /tmp/patch/15876003/

 

3) 给RDBMS DB HOME打补丁

su – oracle

[oracle@vmac1 scripts]$ /tmp/patch/15876003/custom/server/15876003/custom/scripts/prepatch.sh -dbhome $ORACLE_HOME
/tmp/patch/15876003/custom/server/15876003/custom/scripts/prepatch.sh completed successfully.

opatch napply -oh $ORACLE_HOME -local /tmp/patch/15876003/custom/server/15876003
opatch napply -oh $ORACLE_HOME -local /tmp/patch/14727310
/tmp/patch/15876003/custom/server/15876003/custom/scripts/postpatch.sh -dbhome $ORACLE_HOME

 

4)执行rootcrs.pl -patch

su – root

[root@vmac1 ~]# /g01/11ggrid/app/11.2.0/grid/rdbms/install/rootadd_rdbms.sh
[root@vmac1 ~]# /g01/11ggrid/app/11.2.0/grid/crs/install/rootcrs.pl -patch

 

 

5) 在2节点上重复以上步骤

 

6)对于现有的DB 执行升级字典操作

 

cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @catbundle.sql psu apply
SQL> QUIT

 

7)执行utlrp 脚本 并重启DB

SQL> @?/rdbms/admin/utlrp
SQL> shutdown immediate;
SQL> startup;

 

8) 重启应用程序

Oracle数据库版本10.2实际进入扩展支持Extended Support周期

不了解Oracle软件Lifetime Support支持生命周期的朋友可以直接参阅Expect Lifetime Support http://www.oracle.com/us/support/lifetime-support/index.html页面。

 

我们知道Oracle软件的支持周期可以分为Premier Support 和 Extended Support, 在Premier Support 时期只要是购买了Oracle PS服务的用户都可以申请 创建或合并补丁(create or merge patch) , 当支持周期进入Extended Support后 只有购买了扩展服务包的用户才能申请 新的补丁。

 

具体各Release 版本的Database的Support 周期如下:

 

 

 

如上图所见 版本10.2的Premier Support 已在2010年过期,实际10.2已经过度到了Extended Support时期,且会在2013年进入Sustainging Support。

但是实际My Oracle Support并没有在2010年立即限制仅购买Premier Support的用户下载July 2010 后发布的一些PSU/CPU补丁,例如Patch 12419392: DATABASE PSU 10.2.0.5.4 (INCLUDES CPUJUL2011) 是在2011年7月发布的 , 仅购买了Premier Support的用户同样可以下载该Patch set Update。

因为Oracle没有立即限制扩展补丁的下载,所以我们有时候都已经忘记了 已经过度到Extended Support周期了。

但是最近发布的:

  • 10.2.0.5 上的
    • Patch 12827745: DATABASE PSU 10.2.0.5.5 (INCLUDES CPUOCT2011)
    • Patch 12828105: CPUOCT2011 DATABASE 10.2.0.5
  • 10.2.0.4 上
    • Patch 12827778: DATABASE PSU 10.2.0.4.10 (REQUIRES PRE-REQUISITE 10.2.0.4.4|INCLUDES CPUOCT2011)
    • Patch 12828112: CPUOCT2011 DATABASE 10.2.0.4

 

即 自2011 OCT以后发布的10.2上的 PSU和CPU补丁都要求 用户具有相关的Patch权限方能下载 , 见下图:

 

 

注意上图中的”You do not have privileges to download Extended Support patches. See How Patches and Updates Entitlements Works for more information.  learn more privileges “信息。

 

Mos 文档<How Patches and Updates Entitlement Works> 叙述了用户如何查询自身在MOS上的权限以及如何获得相关Patch的下载权限。

 

显然Oracle此举是一举三得的:

  1. 驱动坚持仅购买PS服务的用户尽快升级他们的数据库到仍在Premier Support 周期内的版本,如11.1和11.2
  2. 一方面在于向普通购买PS服务的用户表明购买Extended Support服务包的重要性
  3. 另一方面也是向已经购买ES服务的用户的一种示好姿态, 毕竟要给人家VIP的体验嘛!

 

关于更多Oracle database Lifetime policy 的信息见下文:

 

Oracle's Life Time Support Policy (LSP)
=======================================
Oracle Database Softwares are not desupported, they get in Sustaining Support with deliverable
restrictions as described below.
To help our customer to drive their business success, Oracle has put in place the Lifetime Support Policy (LSP).
Since Database version 8.1.7 there are 3 Stages of support:
1. Premier Support - provides maintenance and support of Oracle Database for five years from
their general availability date.
Premier Support include:
Major product and technology releases.
Technical support.
Updates, fixes, security alerts, data fixes, and critical patch updates.
Tax, legal, and regulatory updates.
Upgrade scripts.
Certification with most new third-party products/versions.
Certification with most new Oracle products
2. Extended Support - provides with an extra three years of support for specific Oracle releases
for an additional fee.
Extended Support include:
Major product and technology releases.
Technical support.
Updates, fixes, security alerts, data fixes, and critical patch updates.
Tax, legal, and regulatory updates.
Upgrade scripts.
Certification with most existing third-party products/versions.
Certification with most existing Oracle products
Extended Support may not include certification with some new third-party products/versions.
3. Sustaining Support - provide access to support tools, knowledgebase, pre-existing fixes,
and assistance from technical support experts.
Sustaining Support include:
Major product and technology releases.
Technical support.
Access to OracleMetaLink, POINT Support Portal, AVT Support Portal, Global Support Portal System.
Fixes, updates, and critical patch updates created during the Premier Support stage.
Upgrade scripts created during the Premier Support stage.
Assistance with service requests, on a commercially reasonable basis, 24 hours per day, 7 days a week
Sustaining Support does not include
New updates, fixes, security alerts, data fixes, and critical patch updates.
New upgrade scripts.
Certification with new third-party products/versions.
Certification with new Oracle products.
24 hour commitment and response guidelines for Severity 1 service requests as defined in the Severity
Level section of “Technical Support Policies“ document.
-> Premier and Extended Support dates for all current releases (e.g. 10.2 or 11.2) can be found in the
"http://www.oracle.com/us/support/library/lifetime-support-technology-069183.pdf#page=7"
-> 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 please see :
Oracle Technical Support Policy document
http://www.oracle.com/us/support/library/057419.pdf#page=7
section 6.
Note 1293180.1 Database Patch Set 10.2.0.4 patching extended to July 31, 2011
-> Patches created from August 2011 will be be Entitled under "Software Extended Support"
-> For downloading the Patches under Extended Support you would need Extended Support "EXS" CSI.
An Extended Support contract is required to receive patches once a release enters the Extended Support phase.
For more information, please see :
Note 757445.1 FAQ for Products in Extended Support
Lifetime Support Policy covering Technology Products for dates of Extended Support
"http://www.oracle.com/us/support/library/lifetime-support-technology-069183.pdf#page=7".
-> NOTE if you have a Valid CSI for Extended "EXS" Support, would request you to please create
a Non-Tech SR to verify the same as mentioned in
Note 757445.1 FAQ for Products in Extended Support
Usefull References :
====================
Note 742060.1 Release Schedule of Current Database Releases
Note 209768.1 Database, FMW, EM Grid Control, and OCS Software Error Correction Support Policy
Note 1293180.1 Database Patch Set 10.2.0.4 patching extended to July 31, 2011
Note 757445.1 FAQ for Products in Extended Support
Note 161818.1 Oracle Server (RDBMS) Releases Support Status Summary
Note 821748.1 What is the Lifetime Support Policy For Captovation Capture / Oracle Document Capture Products?
Lifetime Support Policy
http://www.oracle.com/us/support/library/lifetime-support-technology-069183.pdf
Oracle Software Technical Support Policies
http://www.oracle.com/us/support/library/057419.pdf

Patch Set Update and Critical Patch Update October 2011补丁更新发布了

2011年10月的CPU在18日发布了,Database相关的PSU/CPU包括:

最新发布的11.2.0.3 patchset补丁集这次没有出psu/cpu

11.2.0.2: CPU Patch 12828071, or DB PSU Patch 12827726, or GI PSU Patch 12827731, or Exadata BP12 Patch 12982245

注意Oracle Database 11.2.0.1 的Final Patch 是在July 2011,也就是说11.2.0.1 不会有新的psu/cpu了,包括Exadata的patch。

11.1.0.7 : CPU Patch 12828097, or PSU Patch 12827740

10.2.0.5 : CPU Patch 12828105, or PSU Patch 12827745

10.2.0.4 : CPU Patch 12828112, or PSU Patch 12827778

Oracle Database 11.2.0.3

Oracle Database 11.2.0.3 patch set includes all announced vulnerabilities; there are no Critical Patch Updates for October 2011.

Oracle Database 11.2.0.2

Patch Information for Oracle Database 11.2.0.2

Patch Information 11.2.0.2 Comments
Final patch July 2012
CPU On-Request platforms HP-UX PA RISCIBM: Linux on System Z
PSU On-Request platforms 32-bit client-only platforms except Linux x86

 

Patch Availability for Oracle Database 11.2.0.2

 

Oracle Database 11.2.0.2 UNIX Microsoft Windows (32-Bit) Microsoft Windows x64 (64-bit) Advisory Number Comments
Oracle Database home CPU Patch 12828071, or DB PSU Patch 12827726, or GI PSU Patch 12827731, or Exadata BP12 Patch 12982245 Bundle Patch 13038787 Bundle Patch 13038788 CVE-2011-3511, CVE-2011-3512

Oracle Database 11.1.0.7

Patch Information for Oracle Database 11.1.0.7

 

Patch Information 11.1.0.7 Comments
Final patch July 2015
CPU On-Request platforms
PSU On-Request platforms

 

Patch Availability for Oracle Database 11.1.0.7

 

Oracle Database 11.1.0.7 UNIX Microsoft Windows (32-Bit) Microsoft Windows x64 (64-Bit) Advisory Number Comments
Oracle Database home CPU Patch 12828097, or PSU Patch 12827740 Bundle Patch 12914915 Bundle Patch 12914916 CVE-2011-2301, CVE-2011-3511, CVE-2011-3512, CVE-2011-2322 (Windows only)
Oracle Database home Patch 9288120 Patch 9288120 Patch 9288120 Released April 2011 Database UIXFor Oracle Secure Enterprise Search 11.1.2.x installations, follow the instructions given in MOS note Note 1359600.1.
Oracle Database home Patch 10073948 Patch 10073948 Patch 10073948 Released April 2011 Enterprise Manager Database Control UIXNot applicable to Oracle Secure Enterprise Search 11.1.2.x
Oracle Database home Patch 11738232 Patch 11738232 Patch 11738232 Released April 2011 Warehouse BuilderNot applicable to Oracle Secure Enterprise Search 11.1.2.x

Oracle Database 10.2.0.5

Patch Information for Oracle Database 10.2.0.5

 

Patch Information 10.2.0.5 Comments
Final patch July 2013
CPU On-Request platforms HP-UX PA-RISCIBM: Linux on System ZLinux ItaniumLinux on POWER
PSU On-Request platforms

 

Patch Availability for Oracle Database 10.2.0.5

Oracle Database 10.2.0.5 UNIX Microsoft Windows (32-Bit) Microsoft Windows Itanium (64-Bit) Microsoft Windows x64 (64-Bit) Advisory Number Comments
Oracle Database home CPU Patch 12828105, or PSU Patch 12827745 Bundle Patch 12914911 NA Bundle Patch 12914913 CVE-2011-3511, CVE-2011-3512
Oracle Database home Patch 12536181 NA NA NA Released July 2011 Enterprise Manager Database ControlFor HP-UX PA-RISC and HP-UX Itanium platforms only
Oracle Database home Patch 11738172 Patch 11738172 Patch 11738172 Patch 11738172 Released April 2011 Warehouse Builder

Oracle Database 10.2.0.4

 

Patch Information for Oracle Database 10.2.0.4

 

Patch Information 10.2.0.4 Comments
Final patch July 2013 for Oracle Solaris x86 (32-bit) and Apple Mac OS XFinal patch date pending release of 10.2.0.5 patch set for HP Open VMS-Alpha and VMS-ItaniumJuly 2011 for all other platforms
CPU On-Request platforms Apple Mac OS XHP Open VMS-AlphaHP Open VMS-ItaniumOracle Solaris x86 (32-bit)
PSU On-Request platforms

Patch Availability for Oracle Database 10.2.0.4

 

Oracle Database 10.2.0.4 UNIX Advisory Number Comments
Oracle Database home CPU Patch 12828112, or PSU Patch 12827778 CVE-2011-2301, CVE-2011-3511, CVE-2011-3512
Oracle Database home Patch 12536167 Released July 2011 Enterprise Manager Database ControlFor HP-UX PA-RISC and HP-UX Itanium platforms only
Oracle Database home Patch 9249369 Released April 2011 Database UIX
Oracle Database home Patch 12758181 Released July 2011 Enterprise Manager Database Control UIX
Oracle Database home Patch 9273865 Released April 2011 iSqlPlus UIX

 Oracle Database 10.2.0.3

 

 Patch Information for Oracle Database 10.2.0.3
Patch Information 10.2.0.3 Comments
Final patch IBM zSeries (z/OS) only
CPU On-Request platforms

 

Patch Availability for Oracle Database 10.2.0.3

 

Component IBM zSeries (z/OS) Advisory Number Comments
Oracle Database home CPU Patch 12828128 CVE-2011-2301, CVE-2011-3511, CVE-2011-3512

Oracle Database 10.1.0.5

 

Patch Information for Oracle Database 10.1.0.5

 

Patch Information 10.1.0.5 Comments
Final patch January 2012
CPU On-Request platforms Apple Mac OS XHP Open VMS AlphaHP Tru64 UNIXIBM zSeries (z/OS)Linux ItaniumLinux on POWEROracle Solaris x86 (32-bit)

 

Patch Availability for Oracle Database 10.1.0.5

 

Oracle Database 10.1.0.5 UNIX Microsoft Windows (32-Bit) Microsoft Windows Itanium (64-Bit) Advisory Number Comments
Oracle Database home Patch 6640838 Patch 6640838 Patch 6640838 Released October 2010 Oracle Universal Installer
Oracle Database home Patch 11842285 NA NA Released July 2011 Oracle Universal Installer
Oracle Database home CPU Patch 12828135 Bundle Patch 12914905 Bundle Patch 12914906 CVE-2011-2301, CVE-2011-3512
Oracle Database home Patch 12535977 NA NA Released July 2011 Enterprise Manager Database ControlFor HP-UX PA-RISC and HP-UX Itanium platforms only
Oracle Workspace Manager home Patch 7341989 Patch 7341989 Patch 7341989 Released April 2009
Oracle Database home Patch 9249369 Patch 9249369 Patch 9249369 Released April 2011 Database UIX
Oracle Database home Patch 10036362 Patch 10036362 Patch 10036362 Released April 2011 Enterprise Manager Database Control UIX
Oracle Database home Patch 9273888 Patch 9273888 Patch 9273888 Released April 2011 iSqlPlus UIX

 

Patch Set Update Availability for Oracle Database

Oracle Database UNIX Advisory Number Comments
11.2.0.2.4 Database PSU Patch 12827726 See Section 3.1.3.3, “Oracle Database 11.2.0.2”
11.2.0.2.4 Grid Infrastructure PSU Patch 12827731 See Section 3.1.3.3, “Oracle Database 11.2.0.2” Includes CPUOct2011 and 11.2.0.2.4 Database PSUIBM: Linux on System Z and HP-UX PA-RISC are On-Request Platforms for GI PSU 11.2.0.2.4
11.2.0.2 BP12 for Exadata Patch 12982245 See Section 3.1.3.3, “Oracle Database 11.2.0.2” Includes CPUOct2011 and 11.2.0.2.4 Database and Grid Infrastructure PSU fixes for Exadata
11.1.0.7.9 Database PSU Patch 12827740 See Section 3.1.3.4, “Oracle Database 11.1.0.7”
11.1.0.7.7 CRS PSU Patch 11724953 Released April 2011
10.2.0.5.5 Database PSU Patch 12827745 See Section 3.1.3.5, “Oracle Database 10.2.0.5”
10.2.0.5.2 CRS PSU Patch 9952245 Released January 2011 IBM: Linux on System Z, Solaris x86-64 and HP-UX PA-RISC are On-Request Platforms for CRS PSU 10.2.0.5.2
10.2.0.4.10 Database PSU Patch 12827778 See Section 3.1.3.6, “Oracle Database 10.2.0.4” Overlay PSU
10.2.0.4.4 Database PSU Patch 9352164 Released April 2010 Base PSU for 10.2.0.4.10
10.2.0.4.4 CRS PSU Patch 9294403 Released April 2010

Applying 11G R2 GI PSU 11.2.0.2.3

GI PSU 11.2.0.2.3在最近的一次CPU July中被释出,该Patch Set Update包含了最新的CPU,且GI和Database PSU的都包含在其中,可以直接从<Patch 12419353: GI PSU 11.2.0.2.3 (INCLUDES DATABASE PSU 11.2.0.2.3)>页面下载到,该PSU所修复的Bug包括:

CPU molecules in GI PSU 11.2.0.2.3:
GI PSU 11.2.0.2.3 contains the following new CPU 11.2.0.2 molecules:
12586486 - DB-11.2.0.2-MOLECULE-004-CPUJUL2011
12586487 - DB-11.2.0.2-MOLECULE-005-CPUJUL2011
12586488 - DB-11.2.0.2-MOLECULE-006-CPUJUL2011
12586489 - DB-11.2.0.2-MOLECULE-007-CPUJUL2011
12586490 - DB-11.2.0.2-MOLECULE-008-CPUJUL2011
12586491 - DB-11.2.0.2-MOLECULE-009-CPUJUL2011
12586492 - DB-11.2.0.2-MOLECULE-010-CPUJUL2011
12586493 - DB-11.2.0.2-MOLECULE-011-CPUJUL2011
12586494 - DB-11.2.0.2-MOLECULE-012-CPUJUL2011
12586495 - DB-11.2.0.2-MOLECULE-013-CPUJUL2011
12586496 - DB-11.2.0.2-MOLECULE-014-CPUJUL2011
5.2 Bugs Fixed in GI PSU 11.2.0.2.3
GI PSU 11.2.0.2.3 contains all fixes previously released in GI PSU 11.2.0.2.2
(see Section 5.3 for a list of these bug fixes) and the following new fixes:
Note:
ACFS is not supported on HP and therefore the bug fixes for ACFS do not apply to the HP GI PSU 3. 
Automatic Storage Management
6892311 - PROVIDE REASON FOR MOUNT FORCE FAILURE WITHOUT REQUIRING PST DUMP
9078442 - ORA-19762 FROM ASMCMD CP COPYING FILE WITH DIFFERENT BYTE ORDER FROM FILESYSTEM
9572787 - LONG WAITS FOR ENQ: AM CONTENTION FOLLOWING CELL CRASH CAUSED CLUSTERWIDE OUTAGE
9953542 - TB_SOL_SP: HIT 7445 [KFKLCLOSE()+20] ERROR WHEN DG OFFLINE
10040921 - HUNG DATABASE WORKLOAD AND BACKGROUNDS AFTER INDUCING WRITE ERRORS ON AVD VOLUME
10155605 - 11201-OCE:DISABLE FC IN ONE NODE, ASM DISKGOUP FORCE DISMOUNTED IN OTHER NODES.
10278372 - TB:X:CONSISTENTLY PRINT "WARNING: ELAPSED TIME DID NOT ADVANCE" IN ASM ALERT LOG
10310299 - TB:X:LOST WRITES DUE TO RESYNC MISSING EXTENTS WHEN DISK GO OFFLINE DURING REBAL
10324294 - DBMV2: DBFS INSTANCE WAITS MUCH FOR "ASM METADATA FILE OPERATION"
10356782 - DBMV2+: ASM INSTANCE CRASH WITH ORA-600 : [KFCGET0_04], [25],
10367188 - TB:X:REBOOT 2 CELL NODES,ASM FOREGROUND PROCESS HIT ORA-600[KFNSMASTERWAIT01]
10621169 - FORCE DISMOUNT IN ASM RECOVERY MAY DROP REDO'S AND CAUSE METADATA CORRUPTIONS
11065646 - ASM MAY PICK INCORRECT PST WHEN MULTIPLE COPIES EXTANT
11664719 - 11203_ASM_X64:ARB0 STUCK IN DG REBALANCE
11695285 - ORA-15081 I/O WRITE ERROR OCCURED AFTER CELL NODE FAILURE TEST
11707302 - FOUND CORRUPTED ASM FILES AFTER CELL NODES FAILURE TESTING.
11707699 - DATABASE CANNOT MOUNT DUE TO ORA-00214: CONTROL FILE INCONSISTENCY
11800170 - ASM IN KSV WAIT AFTER APPLICATION OF 11.2.0.2 GRID PSU
11800854 - BUG TO TRACK LRG 5135625
12620422 - FAILED TO ONLINE DISKS BECAUSE OF A POSSIBLE RACING RESYNC
Buffer Cache Management
11674485 - LOST DISK WRITE INCORRECTLY SIGNALLED IN STANDBY DATABASE WHEN APPLYING REDO
Generic
9748749 - ORA-7445 [KOXSS2GPAGE]
10082277 - EXCESSIVE ALLOCATION IN PCUR OF "KKSCSADDCHILDNO" CAUSES ORA-4031 ERRORS
10126094 - ORA-600 [KGLLOCKOWNERSLISTDELETE] OR [KGLLOCKOWNERSLISTAPPEND-OVF]
10142788 - APPS 11I PL/SQL NCOMP:ORA-04030: OUT OF PROCESS MEMORY
10258337 - UNUSABLE INDEX SEGMENT NOT REMOVED FOR "ALTER TABLE MOVE"
10378005 - EXPDP RAISES ORA-00600[KOLRARFC: INVALID LOB TYPE], EXP IS SUCCESSFUL
10636231 - HIGH VERSION COUNT FOR INSERT STATEMENTS WITH REASON INST_DRTLD_MISMATCH
12431716 - UNEXPECTED CHANGE IN MUTEX WAIT BEHAVIOUR IN 11.2.0.2.2 PSU (HIGHER CPU POSSIBLE
High Availability
9869401 - REDO TRANSPORT COMPRESSION (RTC) MESSAGES APPEARING IN ALERT LOG
10157249 - CATALOG UPGRADE TO 11.2.0.2 FAILS WITH ORA-1
10193846 - RMAN DUPLICATE FAILS WITH ORA-19755 WHEN BCT FILE OF PRIMARY IS NOT ACCESSIBLE
10648873 - SR11.2.0.3TXN_REGRESS - TRC - KCRFW_REDO_WRITE
11664046 - STBH: WRONG SEQUENCE NUMBER GENERATED AFTER DB SWITCHOVER FROM STBY TO PRIMARY
Oracle Portable ClusterWare
8906163 - PE: NETWORK AND VIP RESOURCES FAIL TO START IN SOLARIS CONTAINERS
9593552 - GIPCCONNECT() IS NOT ASYNC 11.2.0.2GIBTWO
9897335 - TB-ASM: UNNECCESSARY OCR OPERATION LOG MESSAGES IN ASM ALERT LOG WITH ASM OCR
9902536 - LNX64-11202-MESSAGE: EXCESSIVE GNS LOGGING IN CRS ALERT FILE WHEN SELFCHECK FAIL
9916145 - LX64: INTERNAL ERROR IN CRSD.LOG, MISROUTED REQUEST, ASSERT IN CLSM2M.CPP
9916435 - ROOTCRS.PL FAILS TO CREATE NODEAPPS DURING ADD NODE OPERATION
9939306 - SERVICES NOT COMING UP AFTER SWITCHOVER USING SRVCTL START DATABASE
10012319 - ORA-600 [KFDVF_CSS], [19], [542] ON STARTUP OF ASM DURING ADDNODE
10019726 - MEMORY LEAK 1.2MB/HR IN CRSD.BIN ON NON-N NODE
10056713 - LNX64-11202-CSS: SPLIT BRAIN WHEN START CRS STACK IN PARALLEL WITH PRIV NIC DOWN
10103954 - INTERMITTENT "CANNOT COMMUNICATE WITH CRSD DAEMON" ERRORS
10104377 - GIPC ENSURE INITIAL MESSAGE IS NOT LOST DURING ESTABLISH PHASE
10115514 - SOL-X64-11202: CLIENT REGISTER IN GLOBAL GROUP MASTER#DISKMON#GROUP#MX NOT EXIT
10190153 - HPI-SG-11202 ORA.CTSSD AND ORA.CRSD GOES OFFLINE AFTER KILL GIPC ON CRS MASTER
10231906 - 11202-OCE-SYMANTEC:DOWN ONE OF PRIVAE LINKS ON NODE 3,OCSSD CRASHED ON NODE 3
10233811 - AFTER PATCHING GRID HOME, UNABLE TO START RESOURCES DBFS AND GOLDEN
10253630 - TB:X:HANG DETECTED,"WAITING FOR INSTANCE RECOVERY OF GROUP 2" FOR 45 MINUTES
10272615 - TB:X:SHUTDOWN SERVICE CELLD ON 2 CELL NODES,CSSD ABORT IN CLSSNMRCFGMGRTHREAD
10280665 - TB:X:STOP CELLD ON 2 CELL NODES,CSSD ABORT IN CLSSNMVVERIFYPENDINGCONFIGVFS
10299006 - AFTER 11.2.0.2 UPGRADE, ORAAGENT.BIN CONNECTS TO DATABASE WITH TOO MANY SESSIONS
10322157 - 11202_GIBONE: PERM OF FILES UNDER $CH/CRS/SBS CHANGED AFTER PATCHED
10324594 - STATIC ENDPOINT IN THE LEASE BLOCKS OVERWRITTEN DURING UPGRADE
10331452 - SOL-11202-UD: 10205->11202 NETWORK RES USR_ORA_IF VALUE MISSED AFTER UPGRADE
10357258 - SOL-11202-UD: 10205->11202 [IPMP] HUNDREDS OF DUP IP AFTER INTRA-NODE FAILOVER
10361177 - LNX64-11203-GNS: MANY GNS SELF CHECK FAILURE ALERT MESSAGES
10385838 - TB:X:CSS CORE DUMP AT GIPCHAINTERNALSEND
10397652 - AIX-11202-GIPC:DISABLE SWITCH PORT FOR ONE PRIVATE NIC,HAIP DID NOT FAILOVER
10398810 - DOUBLE FREE IN SETUPWORK DUE TO TIMING
10419987 - PEER LISTENER IS ACCESSING A GROCK THAT IS ALREADY DELETED
10621175 - TB_RAC_X64:X: CLSSSCEXIT: CSSD SIGNAL 11 IN THREAD GMDEATHCHECK
10622973 - LOSS OF LEGACY FEATURES IN 11.2
10631693 - TB:X:CLSSNMHANDLEVFDISCOVERACK: NO PENDINGCONFIGURATION TO COMPLETE. CSS ABORT
10637483 - TB:X:REBOOT ONE CELL NODE, CSS ABORT AT CLSSNMVDDISCTHREAD
10637741 - HARD STOP DEPENDENCY CAN CAUSE WRONG FAIL-OVER ORDER
10638381 - 11202-OCE-SYMANTEC: HAIP FAIL TO START WHEN PRIVATE IP IS PLUMBED ON VIRTUAL NIC
11069614 - RDBMS INSTANCE CRASH DUE TO SLOW REAP OF GIPC MESSAGES ON CMT SYSTEMS
11071429 - PORT 11GR2 CRS TO EL6
11654726 - SCAN LISTENER STARTUP FAILS IF /VAR/OPT/ORACLE/LISTENER.ORA EXISTS.
11663339 - DBMV2:SHARED PROCESS SPINNING CAUSES DELAY IN PRIMARY MEMBER CLEANUP
11682409 - RE-USING OCI MEMORY ACROSS CONNECTIONS CAUSES A MEMORY CORRUPTION
11698552 - SRVCTL REPORT WRONG STATUS FOR DATABASE INSTANCE.
11741224 - INCORRECT ACTIVE VERSION CHECK WHILE ENABLING THE BATCH FUNCTIONALITY
11744313 - LNX64-11203-RACG: UNEXPECTED CRSD RESTART DURING PARALLEL STACK START
11775080 - ORA-29701/29702 OCCURS WHEN WORKLOAD TEST RUNNING FOR A LONG TIME AND IS RESTART
11781515 - EVMD/CRSD FAIL TO START AFTER REBOOT, EVEN AFTER CRSCTL START CLUSTERWARE
11807012 - LNX64-11203-RACG: DB SERVICE RUNS INTO "UNKNOWN" STATE AFTER STACK START
11812615 - LNX64-11203-DIT: INCONSISTENT PERMISSION BEFORE/AFTER ROOTCRS.PL -UNLOCK/-PATCH
11828633 - DATABASE SERVICE DID NOT FAIL OVER AND COULD NOT BE STARTED AFTER NODE FAILURE
11840629 - KERNEL CRASH DUMP AND REBOOT FAIL INSIDE SOLARIS CONTAINER
11866171 - ENABLE CRASHDUMP WHEN REBOOTING THE MACHINE (LINUX)
11877079 - HUNDREDS OF ORAAGENT.BIN@HOSTNAME SESSSIONS IN 11.2.0.2 DATABASE
11899801 - 11202_GIBTWO_HPI:AFTER KILL ASM PMON, POLICY AND ADMIN DB RUNNING ON SAME SERVER
11904778 - LNX64-OEL6-11202: CRS STACK CAN'T BE START AFTER RESTART
11933693 - 11.1.0.7 DATABASE INSTANCE TERMINATED BY 11.2.0.2 CRS AGENT
11936945 - CVU NOT RECOGNIZING THE OEL6 ON LINUX
12332919 - ORAAGENT KEEPS EXITING
12340501 - SRVCTL SHOWS INSTANCE AS DOWN AFTER RELOCATION
12340700 - EVMD CONF FILES CAN HAVE WRONG PERMISSIONS AFTER INSTALL
12349848 - LNX64-11203: VIPS FELL OFFLINE WHEN BRING DOWN 3/4 PUBLIC NICS ONE BY ONE
12378938 - THE LISTENER STOPS WHEN THE ORA.NET1.NETWORK'S STATE IS CHANGED TO UNKNOWN
12380213 - 11203_110415:ERROR EXCEPTION WHILE INSTALLATION 11202 DB WITH DATAFILES ON 11203
12399977 - TYPO IN SUB PERFORM_START_SERVICE RETURNS ZERO (SUCCESS) EVEN WHEN FAILED
12677816 - SCAN LISTENER FAILD TO STARTUP IF /VAR/OPT/ORACLE/LISTENER.ORA EXIST
Oracle Space Management
8223165 - ORA-00600 [KTSXTFFS2] AFTER DATABASE STARTUP
9443361 - WRONG RESULTS (ROWDATA) FOR SELECT IN SERIAL FROM COMPRESSED TABLE
10061015 - LNX64-11202:HIT MANY ORA-600 ARGUMENTS: [KTFBHGET:CLSVIOL_KCBGCUR_9] DURING DBCA
10132870 - INDEX BLOCK CORRUPTION - ORA-600 [KCBZPBUF_2], [6401] ON RECOVER
10324526 - ORA-600 [KDDUMMY_BLKCHK] [6106] WHEN UPDATE SUBPARTITION OF TABLE IN TTS
Oracle Transaction Management
10053725 - TS11.2.0.3V3 - TRC - K2GUPDATEGLOBALPREPARECOUNT
10233732 - ORA-600 [K2GUGPC: PTCNT >= TCNT] OCCURS IN A DATABASE LINK TRANSACTION
Oracle Universal Storage Management
9867867 - SUSE10-LNX64-11202:NODE REBOOT HANG WHILE ORACLE_HOME LOCATED ON ACFS
9936659 - LNX64-11202-CRS: ORACLE HOME PUT ON ACFS, DB INST FAILS TO RESTART AFTER CRASH
9942881 - TIGHTEN UP KILL SEMANTICS FOR 'CLEAN' ACTION.
10113899 - AIX KSPRINTTOBUFFER TIMESTAMPS NEEDS TIME SINCE BOOT AND WALL_CLOCK TIMES
10266447 - ROOTUPGRADE.SH FAILS: 'FATAL: MODULE ORACLEOKS NOT FOUND' , ACFS-9121, ACFS-9310
11789566 - ACFS RECOVERY PHASE 2
11804097 - GBM LOCK TAKEN WHEN DETERMINING WHETHER THE FILE SYSTEM IS MOUNTED AND ONLINE
11846686 - ACFSROOT FAILS ON ORACLELINUX-RELEASE-5-6.0.1 RUNNUNG A 2.6.18 KERNEL
12318560 - ALLOW IOS TO RESTART WHEN WRITE ERROR MESG RETURNS SUCCESS
12326246 - ASM TO RETURN DIFF VALUES WHEN OFFLINE MESG UNSUCCESSFUL
12378675 - AIX-11203-HA-ACFS: HIT INVALID ASM BLOCK HEADER WHEN CONFIGURE DG USING AIX LVS
12398567 - ACFS FILE SYSTEM NOT ACCESSIBLE
12545060 - CHOWN OR RM CMD TO LOST+FOUND DIR IN ACFS FAILS ON LINUX
Oracle Utilities
9735282 - GETTING ORA-31693, ORA-2354, ORA-1426 WHEN IMPORTING PARTITIONED TABLE
Oracle Virtual Operating System Services
10317487 - RMAN CONTROLFILE BACKUP FAILS WITH ODM ERROR ORA-17500 AND ORA-245
11651810 - STBH: HIGH HARD PARSING DUE TO FILEOPENBLOCK EATING UP SHARED POOL MEMORY
XML Database
10368698 - PERF ISSUE WITH UPDATE RESOURCE_VIEW DURING AND AFTER UPGRADING TO 11.2.0.2
5.3 Bugs Fixed in GI PSU 11.2.0.2.2
This section describes bugs fixed in the GI PSU 11.2.0.2.2 release.
ACFS
10015603 - KERNEL PANIC IN OKS DRIVER WHEN SHUTDOWING CRS STACK
10178670 - ACFS VOLUMES ARE NOT MOUNTING ONCE RESTARTED THE SERVER
10019796 - FAIL TO GET ENCRYPTION STATUS OF FILES UNTIL DOING ENCR OP FIRST
10029794 - THE DIR CAN'T READ EVEN IF THE DIR IS NOT IN ANY REALM
10056808 - MOUNT ACFS FS FAILED WHEN FS IS FULL
10061534 - DB INSTANCE TERMINATED DUE TO ORA-445 WHEN START INSTANCE ON ALL NODES
10069698 - THE EXISTING FILE COULD CORRUPT IF INPUT INCORRECT PKCS PASSOWRD
10070563 - MULTIPLE WRITES TO THE SAME BLOCK WITH REPLICATION ON CAN GO OUT OF ORDER
10087118 - UNMOUNT PANICS IF ANOTHER USER IS SITTING IN A SNAPSHOT ROOT DIRECTORY
10216878 - REPLI-RELATED RESOURCE FAILED TO FAILOVER WHEN DG DISMOUNTED
10228079 - MOUTING DG ORA-15196 [KFC.C:25316] [ENDIAN_KFBH] AFTER NODE REBOOT
10241696 - FAILED TO MOUNT ACFS FS TO DIRECTORY CREATED ON ANOTHER ACFS FS
10252497 - ADVM/ACFS FAILS TO INSTALL ON SLES10
9861790 - LX64: ADVM DRIVERS HANGING OS DURING ACFS START ATTEMPTS
9906432 - KERNEL PANIC WHILE DISMOUNT ACFS DG FORCE
9975343 - FAIL TO PREPARE SECURITY IF SET ENCRYPTION FIRST ON THE OTHER NODE
10283549 - FIX AIX PANIC AND REMOVE -DAIX_PERF
10283596 - ACFS:KERNEL PANIC DURING USM LABEL PATCHING - ON AIX
10326548 - WRITE-PROTETED ACFS FILES SHOULD NOT BE DELETED BY NON-ROOT USER
ADVM
10045316 - RAC DB INSTALL ON SHARED ACFS HANGS AT LINKING PHASE
10283167 - ASM INSTANCE CANNOT STARTUP DUE TO EXISTENCE OF VMBX PROCESS
10268642 - NODE PANIC FOR BAD TRAP IN "ORACLEADVM" FOR NULL POINTER
10150020 - LINUX HANGS IN ADVM MIRROR RECOVERY, AFTER ASM EVICTIONS
Automatic Storage Management
9788588 - STALENESS REGISTRY MAY GET CLEARED PREMATURELY
10022980 - DISK NOT EXPELLED WHEN COMPACT DISABLED
10040531 - ORA-600 [KFRHTADD01] TRYING TO MOUNT RECO DISKGROUP
10209232 - STBH: DB STUCK WITH A STALE EXTENT MAP AND RESULTS IN DATA CORRUPTIONS
10073683 - ORA-600 [KFCBINITSLOT40] ON ASM ON DBMV2 WITH BP5
9715581 - DBMV2: EXADATA AUTO MANAGEMENT FAILED TO BRING UP DISKS ONLINE
10019218 - ASM DROPPED DISKS BEFORE DISK_REPAIR_TIME EXPIRED
10084145 - DBMV2: ORA-600 [1427] MOUNTING DISKGROUP AFTER ALL CELLS RESTARTED
11067567 - KEPT GENERATING "ELAPSED TIME DID NOT ADVANCE " IN ASM ALERT LOG
10356513 - DISK OFFLINED WITH NON ZERO TIMEOUT EXPELLED IMMEDIATELY
10332589 - TB:X:MOUNT NORMAL REDUNDANCY DG, FAILED WITH ORA-00600:[KFCINITRQ20]
10329146 - MARKING DIFFERENT SR BITS FROM MULTIPLE DBWS CAN CAUSE A LOST WRITE
10299224 - TB:X:PIVOTING AN EXTENT ON AN OFFLINE DISK CAN CAUSE STALE XMAPS IN RDBMS
10245086 - ORA-01210 DURING CREATE TABLESPACE
10230571 - TB:X:REBOOT ONE CELL NODE, RBAL HIT ORA-600[17183]
10228151 - ASM DISKGROUPS NOT GETTING MOUNTED
10227288 - DG FORCIBLY DISMOUNTED AFTER ONE FG LOST DUE TO "COULD NOT READ PST FOR GRP 4"
10222719 - ASM INSTANCE HANGS WITH RBAL PROCESS WAITS ON "NO FREE BUFFER"
10102506 - DISK RESYNC TAKES A LONG TIME EVEN WITH NO STALE EXTENTS
10094201 - DISK OFFLINE IS SLOW
10190642 - ORA-00600: [1433] FOLLOWED BY INSTANCE CRASH WITH ASM ON EXADATA
11067567 - 11202_gibtwo: kept generating "elapsed time did not advance " in asm alert log
Buffer Cache Management
9651350 - ora-00308 and ora-27037 when ora-8103 without event 10736 been set
10110863 - trace files is still generated after applying patch:9651350
10205230 - tb_x64: hit ora-00600: [kclwcrs_6]
10332111 - sql running long in active standby
CRS Group
CLEANUP
9949676 - GNSD.BIN CORE DUMP AFTER KILL ASM PMON ON ALL NODES AT SAME TIME
9975837 - GNS INCORRECTLY PROCESSES IPV6 LOOKUP REQUESTS
10007185 - GNS DUMPS CORE IN CLSKGOPANIC AT CLSKPDVA 717
10028343 - GNS CAN NOT BE RELOCATED AFTER PUBLIC RESTARTED
CRS
9876201 - OHASD AGENT CORE DUMP AT EONSHTTP.C:162
10011084 - 11202 STEP3 MODIFY BINARY AFTER INSTALLATION CANNOT EXCUTE SUCCESSFULLY
10028235 - 'CLSNVIPAGENT.CPP', LINE 1522: ERROR: FORMAL ARGUMENT TYPE OF ...
10045436 - 'ORA.LISTENER.LSNR' FAILED TO BE FENCED OFF DURING CRSD CLEANUP
10062301 - VALUE FOR FIELD 'CLUSTER_NAME' IS MISSING IN CRSCONFIG_PARAMS
10110969 - PORTABILITY ISSUES IN FUNCTION TOLOWER_HOST
10175855 - FAILED TO UGPRADE 11.2.0.1 + ARU 12900951 -> 11.2.0.2
9891341 - CRSD CORE DUMP IN PROATH_MASTER_EXIT_HELPER AT PROATH.C:1834
11655840 - RAC1 DB' STATE_DETAILS IS WRONG AFTER KILL GIPCD
10634513 - OHASD DUMPS CORE WHEN PLUG IN UNPLUGGED PRIVATE NETWORK NIC
10236074 - ASM INSTANCES CRASH SEVERAL TIMES DURING PARALLEL CRS STARTUP
10052529 - DB INST OFFLINE AFTER STOP/START CRS STACK ON ALL NODES IN PARALLEL
10065216 - VIRTUAL MEMORY USAGE OF ORAROOTAGENT IS BIG(1321MB) AND NOT DECREASING
10168006 - ORAAGENT PROCESS MEMORY GROWTH PERIODICALLY.
CSS
9907089 - CSS CORE DUMP DURING EXADATA ROLLING UPGRADE
9926027 - NODE REBOOTED AFTER CRS CLEAN-UP SUCCEEDED 11202 GI + 10205 RAC DB
10014392 - CRSCTL DELETE NODE FAILS WITH CRS-4662 & CRS-4000
10015460 - REMOVAL OF WRONG INCARNATION OF A NODE DUE TO MANUAL SHUTDOWN STATE
10040109 - PMON KILL LEAD TO OS REBOOT
10048027 - ASM UPGRADE FAILS
10052721 - 11201- 11202 NON-ROLLING,CRSCTL.BIN CORE AT CLSSNSQANUM, SIGNAL 11
10083789 - A NODE DOESNT INITIATE A RECONFIG DUE TO INCORRECT RECONFIG STATE
9944978 - FALSE CSS EVICTION AFTER PRIVATE NIC RESUME
9978195 - STOP DB ACTION TIMED OUT AND AGENT EXITS DUE TO FAILURE TO STOP EVENT BRIDGE
10248739 - AFTER APPLY THE PATCH, THE NODE EVICTED DURING START CRS STACK
CVU
9679401 - OUI PREREQ CHECKS FAILED FOR WRONG OWNSHIP OF RESOLV.CONF_`HOST`
9959110 - GNS INTEGRITY PREREQUISITE FAILED WITH PRVF-5213
9979706 - COMP OCR CHECK FAILS TO VERIFY SIZE OF OCR LOCATION
10029900 - CVU PRE NODEADD CHECK VD ERROR
10033106 - ADDNODE.SH SHOULD INDICATE WHAT HAPPENS WHEN ERROR OCCURRING
10075643 - UNABLE TO CONTINUE CONFIG.SH FOR CRS UPGRAD
10083009 - GIPCD FAILS TO RETRIEVE INFORMATION FROM PEERS DUE TO INVALID ENDPOINT
GIPC
9812956 - STATUS OF CRSD AND EVMD GOES INTERMEDIATE FOR EVER WHEN KILL GIPC
9915329 - ORA-600 [603] IN DB AND ORA-603 IN ASM AFTER DOWN INTER-CONNECT NIC
9944948 - START RESOUCE HAIP FAILED WHEN RUN ROOT.SH
9971646 - ORAROOTAGENT CORE DUMPED AT NETWORKHAMAINTHREAD::READROUTEDATA
9974223 - GRID INFRASTRUCTURE NEEDS MULTICAST COMMUNICATION ON 230.0.1.0 ADDRESSES WORKING
10053985 - ERROR IN NETWORK ADDRESS ON SOLARIS 11
10057680 - OHASD ORAROOTAGENT.BIN SPIN CPU AFTER SIMULATE ASM DISK ERROR
10078086 - ROOTUPGRADE.SH FAIL FOR 'CRSCTL STARTUPGRADE' FAIL,10205-> 11202
10260251 - GRID INSTALLATION FAILS TO START HAIP DUE TO CHANGE IN NETWORK INTERFACE NAME
10111010 - CRSD HANGS FOR THE HANAME OF PEER CRSD
11782423 - OHASD.BIN TAKES CPU ABOUT 95% ~ 100%
11077756 - STARTUP FAILURE OF HAIP CAUSES INSTALLATION FAILURE
10375649 - DISABLE HAIP ON PRIMECLUSTER
10284828 - INTERFACE UPDATES GET LOST DURING BOUNCE OF CRSD PROCESS
10284693 - AIX EPIPE FAILURE
10233159 - NEED 20 MINS TO STARTUP CRS WHEN 1/2 GIPC NICS DOWN
10128191 - LRGSRG9 AND LRGSRGE FAILURE
GNS
9864003 - NODE REBOOT DUE TO 'ORA.GNS' FAILED TO BE FENCED OFF DURING CRSD
GPNP
9336825 - GPNPD FLUSH PROFILE PUSH ERROR MESSAGES IN CRS ALERT LOG
10314123 - GPNPD MAY NOT UPDATE PROFILE TO LATEST ON START
10105195 - PROC-32 ACCESSING OCR; CRS DOES NOT COME UP ON NODE
10205290 - DBCA FAILED WITH ERROR ORA-00132
10376847 - [ORA.CRF] [START] ERROR = ERROR 9 ENCOUNTERED WHEN CONNECTING TO MOND
IPD-OS
9812970 - IPD DO NOT MARK TYPE OF DISKS USED FOR VOTING DISK CORRECTLY
10057296 - IPD SPLIT BRAIN AFTER CHANGE BDB LOCATION
10069541 - IPD SPLIT BRAIN AFTER STOPPING ORA.CRF ON MASTER NODE
10071992 - UNREASONABLE VALUES FOR DISK STATISTICS
10072474 - A NODE IS NOT MONITORED AFTER STOP AND START THE ORA.CRF ON IT
10073075 - INVALID DATA RECEIVED FROM THE CLUSTER LOGGER SERVI
10107380 - IPD NOT STARTED DUE TO SCRFOSM_GET_IDS FAILED
OCR
9978765 - ROOTUPGRADE.SH HANG AND CRSD CRASHED ON OTHER NODES,10205-> 11202
10016083 - 'OCRCONFIG -ADD' NEEDS HELPFUL MESSAGE FOR ERROR ORA-15221
OPSM
9918485 - EMCONFIG FAIL WITH NULLPOINTEREXCEPTION AT RACTRANSFERCORE.JAVA
10018215 - RACONE DOES NOT SHUTDOWN INSTANCE DURING RELOCATION
10042143 - ORECORE11 LWSFDSEV CAUSED SEGV IN SRVM NATIVE METHODS
OTHERS
9963327 - CHMOD.PL GETS CALLED INSTEAD OF CHMOD.EXE
10008467 - FAILS DUE TO WRONG VERSION OF PERL USED:
10015210 - OCTSSD LEAK MEMORY 1.7M HR ON PE MASTER DURING 23 HOURS RUNNI
10027079 - CRS_SHUTDOWN_SYNCH EVENT NOT SENT IN SIHA
10028637 - SCLS.C COMPILE ERRORS ON AIX UNDECLARED IDENTIFIERS
10029119 - 11201-11202 CRS UPGRADE OUI ASKS TO RUN ROOTUPGRADE.SH
10036834 - PATCHES NOT FOUND ERROR WHILE UPGRADING GRID FROM 11201 TO 11202
10038791 - HAS SRG SRV GETTING MANY DIFS FOR AIX ON LABEL 100810 AND LATER
10040647 - LNX64-112022-UD; AQ AND RLB DO NOT WORK AFTER UPGRADING FROM 11201
10044622 - EVMD FAILED TO START AFTER KILL OHASD.BIN
10048487 - DIAGCOLLECTION CANNOT RETRIEVE IPD REPORTS
10073372 - DEINSTALL FAILED TO DELETE CRS_HOME ON REMOTE NODE IF OCR VD ON NFS
10089120 - WRONG PROMPT MESSAGE BY DEINSTALL COMMAND WHILE DELETING CRS HOME
10124517 - CRS STACK DOES NOT START AUTOMATICALLY AFTER NODE REBOOT
10157622 - 11.2.0.2 GI BUNDLE 1 HAS-CRS TRACKING BUG
RACG
10036193 - STANDBY NIC DOESN'T WORK IF DOWN PUBLIC NIC
10146768 - NETWORK RESOURCE FAILS TO START WITH IPMP ON SOLARIS 11
USM Miscellaneous
10146744 - ORA.REGISTRY.ACFS BECOME UNKOWN AND ACFS FS DISMOUNT
10283058 - RESOURCES ACFS NEEDS AN OPTION TO DISALLOW THE MOUNTING OF FILE SYSTEMS ON RESOURCE START
10193581 - ROOT.SH CRS-2674: START OF 'ORA.REGISTRY.ACFS' FAIL
10244210 - FAIL TO INSTALL ADVM/ACFS ON SOLARIS CONTAINER
10311856 - APPLY ASSERTION FAILURE:PBOARDENTRY>USRGBOARDRECENTRY_RECORD
Generic
9591812 - incorrect wait events in 11.2 ("cursor: mutex s" instead of "cursor: mutex x")
9905049 - ebr: ora-00600: internal error code, arguments: [kqlhdlod-bad-base-objn]
10052141 - exadata database crash with ora-7445 [_wordcopy_bwd_dest_aligned] and ora-600 [2
10052956 - ora-7445 [kjtdq()+176]
10157402 - lob segment has null data after long to lob conversion in parallel mode
10187168 - obsolete parent cursors if version count exceeds a threshold
10217802 - alter user rename raises ora-4030
10229719 - qrmp:12.2:ora-07445 while performing complete database import on solaris sparc
10264680 - incorrect version_number reported after patch for 10187168 applied
10411618 - add different wait schemes for mutex waits
11069199 - ora-600 [kksobsoletecursor:invalid stub] quering pq when pq is disabled
11818335 - additional changes when wait schemes for mutex waits is disabled
High Availability
10018789 - dbmv2-bigbh:spin in kgllock caused db hung and high library cache lock
10129643 - appsst gsi11g m9000: ksim generic wait event
10170431 - ctwr consuming lots of cpu cycles
Oracle Space Management
6523037 - et11.1dl: ora-600 [kddummy_blkchk] [6110] on update
9724970 - pdml fails with ora-600 [4511]. ora-600 [kdblkcheckerror] by block check
10218814 - dbmv2: ora-00600:[3020] data block corruption on standby
10219576 - ora-600 [ktsl_allocate_disp-fragment]
Oracle Transaction Management
10358019 - invalid results from flashback_transaction_query after applying patch:10322043
Oracle Utilities
10373381 - ora-600 [kkpo_rcinfo_defstg:objnotfound] after rerunning catupgrd.sql
Oracle Virtual Operating System Services
10127360 - dg4msql size increasing to 1.5gb after procedure executed 250 times
Server Manageability
11699057 - ora-00001: unique constraint (sys.wri$_sqlset_plans_tocap_pk) violated

针对Grid Infrastructure的大致升级步骤如下,具体见该PSU的readme文档,见(6 Appendix A: Manual Steps for Apply/Rollback Patch)
部分:

1.升级Opatch,Patch 12419353 requires OPatch version 11.2.0.1.4.
可以从这里下载到11.2上最新的opatch工具,解压后直接覆盖原Opatch目录即可
2.关闭相关的RAC数据库  
<ORACLE_HOME>/bin/srvctl stop database –d <db-unique-name> 
3.Umount所有的ACFS文件系统
4. 切换到oracle用户,停止所有节点上的相关资源
su  - oracle
$<ORACLE_HOME>/bin/srvctl stop home -o <ORACLE_HOME> -s <status file location> -n <node name>
5.在所有节点上运行rootcrs.pl脚本停止GI相关资源
su - root
<GI_HOME>/crs/install/rootcrs.pl -unlock
Using configuration parameter file: /g01/11.2.0/grid/crs/install/crsconfig_params
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'vrh1'
CRS-2673: Attempting to stop 'ora.crsd' on 'vrh1'
CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on 'vrh1'
CRS-2673: Attempting to stop 'ora.asm' on 'vrh1'
CRS-2677: Stop of 'ora.asm' on 'vrh1' succeeded
CRS-2792: Shutdown of Cluster Ready Services-managed resources on 'vrh1' has completed
CRS-2677: Stop of 'ora.crsd' on 'vrh1' succeeded
CRS-2673: Attempting to stop 'ora.drivers.acfs' on 'vrh1'
CRS-2673: Attempting to stop 'ora.mdnsd' on 'vrh1'
CRS-2673: Attempting to stop 'ora.ctssd' on 'vrh1'
CRS-2673: Attempting to stop 'ora.evmd' on 'vrh1'
CRS-2673: Attempting to stop 'ora.asm' on 'vrh1'
CRS-2677: Stop of 'ora.asm' on 'vrh1' succeeded
CRS-2673: Attempting to stop 'ora.cluster_interconnect.haip' on 'vrh1'
CRS-2677: Stop of 'ora.evmd' on 'vrh1' succeeded
CRS-2677: Stop of 'ora.cluster_interconnect.haip' on 'vrh1' succeeded
CRS-2677: Stop of 'ora.mdnsd' on 'vrh1' succeeded
CRS-2677: Stop of 'ora.ctssd' on 'vrh1' succeeded
CRS-2673: Attempting to stop 'ora.cssd' on 'vrh1'
CRS-2677: Stop of 'ora.cssd' on 'vrh1' succeeded
CRS-2673: Attempting to stop 'ora.gipcd' on 'vrh1'
CRS-2673: Attempting to stop 'ora.diskmon' on 'vrh1'
CRS-2677: Stop of 'ora.diskmon' on 'vrh1' succeeded
CRS-2677: Stop of 'ora.gipcd' on 'vrh1' succeeded
CRS-2673: Attempting to stop 'ora.gpnpd' on 'vrh1'
CRS-2677: Stop of 'ora.drivers.acfs' on 'vrh1' succeeded
CRS-2677: Stop of 'ora.gpnpd' on 'vrh1' succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'vrh1' has completed
CRS-4133: Oracle High Availability Services has been stopped.
Successfully unlock /g01/11.2.0/grid
6.解压下载的PSU补丁包
unzip p12419353_112020_Linux-x86-64.zip 
7.
在所有节点上实施对GI的Patch
 <GI_HOME>/OPatch/opatch napply -oh <GI_HOME> -local /tmp/12419353
Invoking OPatch 11.2.0.1.6
Oracle Interim Patch Installer version 11.2.0.1.6
Copyright (c) 2011, Oracle Corporation.  All rights reserved.
UTIL session
Oracle Home       : /g01/11.2.0/grid
Central Inventory : /g01/oraInventory
   from           : /etc/oraInst.loc
OPatch version    : 11.2.0.1.6
OUI version       : 11.2.0.2.0
Log file location : /g01/11.2.0/grid/cfgtoollogs/opatch/opatch2011-08-12_00-07-39AM.log
Verifying environment and performing prerequisite checks...
OPatch continues with these patches:   12419353  
Do you want to proceed? [y|n]
Backing up files...
Applying interim patch '12419353' to OH '/g01/11.2.0/grid'
Patching component oracle.crs, 11.2.0.2.0...
Copying file to "/g01/11.2.0/grid/crs/install/crsconfig_lib.pm"
Copying file to "/g01/11.2.0/grid/crs/install/crspatch.pm"
Copying file to "/g01/11.2.0/grid/crs/install/s_crsconfig_lib.pm"
Patching component oracle.usm, 11.2.0.2.0...
Patches 12419353 successfully applied.
Log file location: /g01/11.2.0/grid/cfgtoollogs/opatch/opatch2011-08-12_00-07-39AM.log
OPatch succeeded.
<GI_HOME>/OPatch/opatch napply -oh <GI_HOME> -local /tmp/12419331
Invoking OPatch 11.2.0.1.6
Oracle Interim Patch Installer version 11.2.0.1.6
Copyright (c) 2011, Oracle Corporation.  All rights reserved.
UTIL session
Oracle Home       : /g01/11.2.0/grid
Central Inventory : /g01/oraInventory
   from           : /etc/oraInst.loc
OPatch version    : 11.2.0.1.6
OUI version       : 11.2.0.2.0
Log file location : /g01/11.2.0/grid/cfgtoollogs/opatch/opatch2011-08-12_00-10-46AM.log
Verifying environment and performing prerequisite checks...
OPatch continues with these patches:   12419331  
Backing up files...
Applying interim patch '12419331' to OH '/g01/11.2.0/grid'
ApplySession: Optional component(s) [ oracle.sysman.console.db, 11.2.0.2.0 ] ,
[ oracle.sysman.oms.core, 10.2.0.4.3 ] , [ oracle.rdbms.dv, 11.2.0.2.0 ] ,
[ oracle.sysman.plugin.db.main.repository, 11.2.0.2.0 ]  not present in the Oracle Home or a higher version is found.
Patching component oracle.rdbms.rsf, 11.2.0.2.0...
Patching component oracle.rdbms, 11.2.0.2.0...
Copying file to "/g01/11.2.0/grid/psu/11.2.0.2.3/catpsu.sql"
Copying file to "/g01/11.2.0/grid/psu/11.2.0.2.3/catpsu_rollback.sql"
Copying file to "/g01/11.2.0/grid/cpu/scripts/patch_8837510.sql"
Copying file to "/g01/11.2.0/grid/cpu/scripts/emdb_recomp_invalids.sql"
Patching component oracle.ldap.rsf, 11.2.0.2.0...
Patching component oracle.rdbms.dbscripts, 11.2.0.2.0...
Patching component oracle.rdbms.rman, 11.2.0.2.0...
Patches 12419331 successfully applied.
Log file location: /g01/11.2.0/grid/cfgtoollogs/opatch/opatch2011-08-12_00-10-46AM.log
OPatch succeeded.
后续对DB HOME升级的步骤可以参照以下文档摘录 
8.Run the pre script for DB component of the patch.
As the database home owner execute:
$<UNZIPPED_PATCH_LOCATION>/12419353/custom/server/12419353/custom/scripts/prepatch.sh -dbhome <ORACLE_HOME>
9.Apply the DB patch.
As the database home owner execute:
$<ORACLE_HOME>/OPatch/opatch napply -oh <ORACLE_HOME> -local <UNZIPPED_PATCH_LOCATION>/12419353/custom/server/12419353
$<ORACLE_HOME>/OPatch/opatch napply -oh <ORACLE_HOME> -local <UNZIPPED_PATCH_LOCATION>/12419331
10.Run the post script for DB component of the patch.
As the database home owner execute:
$<UNZIPPED_PATCH_LOCATION>/12419353/custom/server/12419353/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME>
11.Run the post script.
As the root user execute:
#<GI_HOME>/rdbms/install/rootadd_rdbms.sh
If this is a GI Home, as the root user execute:
#<GI_HOME>/crs/install/rootcrs.pl -patch
If this is an Oracle Restart Home, as the root user execute:
#<GI_HOME>/crs/install/roothas.pl -patch
12.Start the CRS managed resources that were earlier running from DB homes.
If this is a GI Home environment, as the database home owner execute:
$<ORACLE_HOME>/bin/srvctl start home -o <ORACLE_HOME> -s <status file location> -n <node name>
If this is an Oracle Restart Home environment, as the database home owner execute:
$<ORACLE_HOME>/bin/srvctl start home -o <ORACLE_HOME> -s <status file location> 

Waiting For KKSFBC CHILD COMPLETION?

客户有一套AIX 5.3上的10.2.0.4.5生产库系统,最近频繁出现”KKSFBC CHILD COMPLETION”等待,同时导致session不断spin消耗CPU并hang住,从表象看这似乎是由bug引起的。以KKSFBC CHILD COMPLETION为关键字到MOS查询可以找到<Bug 6795880 – Session spins / OERI after ‘kksfbc child completion’ wait – superceded [ID 6795880.8]>,该Bug的症状为进程不断spin且hang住、出现’KKSFBC CHILD COMPLETION’等待事件、还可能伴有’Waits for “cursor: pin S”‘等待事件,直接影响的版本有11.1.0.6、10.2.0.3和10.2.0.4。

对于该Bug的描述是在发生’kksfbc child completion’等待事件后会话陷入无休止的自旋(spins)中,这种自旋(spins)发生在由堆栈调用(stack call)kksSearchChildList->kkshgnc陷入对kksSearchChildList函数的无限循环中。

就当前用户提供的版本号及等待事件信息仍不足以定位到该Bug,我们需要更详细的stack call。所幸的是这个trouble是可以重现的(reproduceable),在之后的一次案发现场我们得到了必要的信息:

Name            PID  CPU%  PgSp Owner
oracle      3723390  10.0   7.0 oracle
SQL> oradebug setospid 3723390
Oracle pid: 155, Unix process pid: 3723390, image: oracle@lmsdb1
SQL> oradebug unlimit;
Statement processed.
SQL> oradebug short_stack;
ksdxfstk+002c<-ksdxcb+04e4<-sspuser+0074<-000044F0
<-kksfbc+0b9c<-kkspsc0+0ffc<-kksParseCursor+00d4
<-opiosq0+0ae0<-kpooprx+0168<-kpoal8+0400<-opiodr+0ae0<-ttcpip+1020<-opitsk+1124
<-opiino+0990<-opiodr+0ae0<-opidrv+0484<-sou2o+0090<-opimai_real+01bc<-main+0098<-__start+0098
SQL> oradebug dump processstate 10;
Statement processed.
SQL> oradebug dump systemstate 266;
Statement processed.
=========================process state dump=========================
SO: 7000003f72e3378, type: 4, owner: 7000003f225c798, flag: INIT/-/-/0x00
(session) sid: 270 trans: 0, creator: 7000003f225c798, flag: (41) USR/- BSY/-/-/-/-/-
DID: 0001-009B-0000017F, short-term DID: 0000-0000-00000000
txn branch: 0
oct: 0, prv: 0, sql: 700000243ef9540, psql: 7000002fe76d9c0, user: 28/OLSUSER
service name: SYS$USERS
O/S info: user: newprepay, term: unknown, ospid: 1234, machine: newprepayC
program: JDBC Thin Client
application name: JDBC Thin Client, hash value=2546894660
last wait for 'kksfbc child completion' blocking sess=0x0 seq=4397 wait_time=48840 seconds since wait started=144918
=0, =0, =0
Dumping Session Wait History
for 'kksfbc child completion' count=1 wait_time=48840
=0, =0, =0

可以从以上trace中看到会话确实曾长时间处于’kksfbc child completion’等待中,之后陷入无限自旋(spins)中消耗了大量CPU时间。但这里实际的表现又存有差异,引发无限循环的函数是kksfbc而不是kksSearchChildList(常规的调用序列是:kksParseCursor->kkspsc0->kksfbc ->kksSearchChildList->kkshgnc)。

kksfbc意为K[Kernel]K[Kompile]S[Shared]F[Find]B[Best]C[Child]该函数用以在软解析时找寻合适的子游标,在10.2.0.2以后引入了mutex互斥体来取代原有的Cursor Pin机制,Mutex较Latch更为轻量级。著名的Tanel Poder指出虽然mutex的引入改变了众多cursor pin的内部机制,但kksfbc仍需要持有library cache latches才能扫描library cache hash chains(However the traversing of library cache hash chains (the right child cursor lookup using kksfbc()) was still protected by library cache latches)。另一方面当kksfbc函数针对某个parent cursor找到合适child cursor后,可能使用KKSCHLPINx方法将该child cursor pin住,这个时候就需要exclusive地持有该child cursor相应的mutex,如:

SQL>  select mutex_addr,requesting_session rs,blocking_session bs,location from x$mutex_sleep_history;
MUTEX_ADDR               RS         BS LOCATION
---------------- ---------- ---------- ----------------------------------------
00000000A3CF8928        159        148 kksfbc [KKSCHLPIN1]
00000000A3CEA8A8        159          0 kksfbc [KKSCHLPIN1]
00000000A3CF5508        159          0 kksfbc [KKSCHLPIN1]
00000000A3CF10E8        148        159 kksLockDelete [KKSCHLPIN6]

当有一个进程执行kksfbc,而其他进程可能需要陷入’kksfbc child completion’等待中(更多的是cursor:pin S等待事件),但这种等待一般是十分轻微的,你很难从某个”仪表”上观察到这一事件。因为一系列kksfbc相关的bug仅发生在10.2.0.2以后,可以猜测是由于mutex的引入引起的。

打破’kksfbc child completion’异常等待的一种行之有效的workaround方法是设置隐藏参数_use_kks_mutex_pin为false,即使用传统的由latch保护的Cursor pin;设置该hidden parameter需要重启实例,具体的设置方法如下:

alter system set "_kks_use_mutex_pin"=false scope=spfile;
restart instance...........

但这种方法也仅仅是行之有效,而非万试万灵。从消极的角度来说,因为放弃了mutex保护cursor pin的机制,在解析频繁的系统中library cache latch的争用将白热化,有可能成为Top 5等待事件。

另一种值得推荐的workaround是减少硬编码的SQL语句,使用session_cached_cursor减少实际的软解析操作也有助于避免引发该Bug;当然这要求我们修改代码,但从长远来看这种改良是值得的。

最后Oracle在10.2.0.4上提供了该Bug的one-off Patch 8575528,其在10.2.0.4 psu4以后的等价补丁为(Equivalent patch)为merge patch 9696904:

8557428 9696904 7527908 Both fixes are needed. 6795880 superceded by 8575528 in 9696904 which includes extra files so may cause new conflicts

但merge patch 9696904目前仅有Linux x86/64平台上的版本,而问题数据库所在平台为IBM AIX on POWER Systems (64-bit)。如果要通过补丁来fix这个问题的话,AIX平台的用户可以要求Oracle development开发部门build一个Power版的9696904 patch,也可以升级到10.2.0.5上去

注意Patch 8575528: MISSING ENTRIES IN V$MUTEX_SLEEP.LOCATION目前有IBM AIX on POWER Systems (64-bit)平台上10.2.0.4.4的版本,经过验证该one-off patch可以在10.2.0.4 PSU4以后的版本上实施(包括10.2.0.4.5/10.2.0.4.6等),不需要如以上描述地去apply 9696904这个merge patch。当然升级到10.2.0.5/11.1.0.7或以上版本依然有效。

此外apply以上8575528:后需要修改隐藏参数”_cursor_features_enabled”并重启才能使fix生效,具体设置防范如下:

ALTER SYSTEM SET "_cursor_features_enabled"=10 scope=spfile;
restart instance.............

注意以上参数仅在使用one-off patch时需要设置,而当通过升级到10.2.0.5/11.1.0.7来修复问题时无需设置上述”_cursor_features_enabled”参数。

Pre-check while you are applying one-off patch

Oracle Database的补丁除去我们最常见的Patch set大补丁集(就是那种动辄1、2个G的补丁包)外,还包括Critical Patch Update(CPU)和Patch Set Update(PSU),one-off Patch(一次性补丁);在数据库使用过程中出现某些问题后(最常见的是出现ORA-00600、ORA-07445错误),通过DBA与MOS的协作将问题定位到某个大版本上的具体Bug,如果该Bug在该版本上现有one-off patch的话,我们可以通过one-off patch的实施来解决问题,one-off patch具有如下特点:

  1. one-off patch的patch包一般都很小,因为它是为了修正一个或多个bug所特制,它一般只包含必要的inventory xml信息,以及和bug相关的共享库文件(一般是.o或者.a文件)
  2. one-off patch绝大多数是随需随制,一般是Oracle内部人员发现Bug或者客户在生产过程中遇到Bug后,向Oracle development开发部门提出patch building的Request ,开发人员接到building或backport的要求后会为客户系统指定的数据库版本和操作系统平台特制一个补丁(如果还没有的话);举例来说可能一个bug在Linux平台的10.2.0.4版本中已有one-off patch,但客户在Solaris Sparc 平台上10.2.0.3上碰到同样的bug,那么这个时候就可以提交SR要求Oracle开发部门backport这个patch
  3. 绝大多数one-off patch只需要用Opatch工具apply即可,不需要升级/修正数据字典,这一点和Patch set/CPU/PSU是不同的
  4. one-off patch是针对某个特殊版本的,如10.2.0.4上的one-off patch只能针对10.2.0.4实施,而在10.2.0.4.8(10.2.0.4的PSU 8)上该one-off patch可能是一个conflicting Bug即有冲突的一次性bug补丁;针对这种情况Oracle一般会给出当前版本上的替代one-off patch,例如6996030″MERGE LABEL REQUEST ON TOP OF 10.2.0.4 FOR AUDIT TRAIL CLEAN-UP”是10.2.0.4上的一个one-off patch,但在10.2.0.4.4上6996030是一个conflicting bug存在冲突,这样我们就需要一个替代品、一个10.2.0.4.4上的Equivalent patch等价补丁,在我们的例子中这个patch是9650152 “MERGE REQUEST ON TOP OF 10.2.0.4.4 FOR BUGS 9589005 6805009 6991606”
  5. 实施one-off patch意味着你的数据库软件将与其他主流版本的数据库在行为方式上有所区别,另一方面你需要考虑到如果发现了新的Bug并考虑打上另一个one-off patch时可能存在Conflicting冲突。大多数情况下one-off patch可以迅速帮我们解决Bug,但反过来说实施任意一个one-off patch时我们可能冒着今后花费更多时间去维护数据库补丁的风险;就这一点来看,应用one-off patch有着它明显的缺点
  6. 在11g中提出了hot patch的概念,这里的patch就是指的one-off patch;就目前看来online-patching只是一个噱头,因为真正具备在线实施能力的patch少之又少,你很难从MOS上的patch专栏中找到一个可用的online-patch
  7. 一个我个人的观点:Oracle GCS会通过stack call、trace、dump等信息将问题定位到bug,最为常见的是ORA-00600、ORA-07445等内部错误,这些错误因为有着明确的error argument、stack call等信息可以让GCS精确地定位故障,而对于另一些问题例如process spin、异常等待事件等不产生明确argument、stack、dump的问题时,定位就要困难一些。我们经常可以看到一些bug note,在客户apply one-off patch并设置特定event后one-off patch并不起作用,导致这种情况的原因多种多样,一种可能是patch在开发过程中存在问题(补丁代码没有被正确触发),另一种则是bug没有被准确定位。

我们目前的问题在于虽然one-off patch存在这样那样的问题,但很多时候又不得不实施one-off patch(大多数原因是停机时间限制);以及在一个已经实施了诸多Patch set、PSU、CPU和one-off patch的环境中新增one-off patch,为了更好地完成这项工作,我们有必要在具体实施补丁前完成以下的预备工作:

1.在定位到具体Bug后我们可以获得一个Bug No#,使用该No#到My Oracle Support上的Patches & Updates专栏中搜索该Bug相关的patch信息,这里存在三种情况:

  • 最好的情况是指定的数据库版本和操作系统平台上存在相关的patch
  • 指定数据库版本上有patch,注意这里的指定数据库版本需要精确到具体的PSU,但没有指定操作系统平台上的,这个时候可以提交SR要求在指定平台上build一个
  • 指定数据库版本上没有patch,注意这里的指定数据库版本需要精确到具体的PSU,例如10.2.0.4上的patch是不能直接用在10.2.0.4.x上的;针对这种情况我们可以首先查询Metalink Note“Patch Set Updates – One-off Patch Conflict Resolution”,可以从这个Note中查到指定one-off patch是否被包含在某个psu中,或者在某个psu上有特定的等价补丁(Equivalent on top),一部分one-off patch在不同的psu之间还存在通用性,如10.2.0.4.4上的部分patch可以在10.2.0.4.5上实施,具体是否通用可以参考下文中冲突检查的方法来检验。如果都没有等价补丁也没有通用补丁那么需要提交SR让Oracle开发部门去merge一个

2.更复杂的情况是在现有版本上已经应用了某些特定的patch(psu、cpu、或者其他one-off patch),我们要保证需要新增的one-off patch之间不存在conflict关系,也不会和系统中已有的patch发生conflict,这时候我们可以使用opatch prereq命令来做冲突检查并得到相关建议,如:

[oracle@rh2 tmp]$ /s01/db_1/OPatch/opatch lsinventory
Invoking OPatch 11.2.0.1.3
Oracle Interim Patch Installer version 11.2.0.1.3
Copyright (c) 2010, Oracle Corporation.  All rights reserved.
Oracle Home       : /s01/db_1
Central Inventory : /s01/oraInventory
from           : /etc/oraInst.loc
OPatch version    : 11.2.0.1.3
OUI version       : 10.2.0.4.0
OUI location      : /s01/db_1/oui
Log file location : /s01/db_1/cfgtoollogs/opatch/opatch2011-05-06_21-41-39PM.log
Patch history file: /s01/db_1/cfgtoollogs/opatch/opatch_history.txt
Lsinventory Output file location : /s01/db_1/cfgtoollogs/opatch/lsinv/lsinventory2011-05-06_21-41-39PM.txt
--------------------------------------------------------------------------------
Installed Top-level Products (2): 
Oracle Database 10g                                                  10.2.0.1.0
Oracle Database 10g Release 2 Patch Set 3                            10.2.0.4.0
There are 2 products installed in this Oracle Home.
Interim patches (2) :
Patch  9654991      : applied on Fri May 06 21:33:38 CST 2011
Unique Patch ID:  12816418
Created on 30 Jun 2010, 18:30:40 hrs PST8PDT
Bugs fixed:
9714832, 9713537, 9678695, 9655017, 9173248, 8309642, 9678697, 9678690
9573054, 9654991
This patch overlays patches:
9352164
This patch needs patches:
9352164
as prerequisites
Patch  9352164      : applied on Fri May 06 21:29:20 CST 2011
Unique Patch ID:  12307477
Created on 1 Apr 2010, 11:33:14 hrs PST8PDT
Bugs fixed:
/* 以上示例环境中实施了10.2.0.4上的psu4(9352164)和psu5(9654991) */
/* 在示例环境中我们试图实施补丁7527908和9696904,这2个merge patch是针对psu4(10.2.0.4.4)版本的,
但在psu5(10.2.0.4.5)上没有相应的替代补丁,我们需要检测这2个patch是否和psu5发生冲突  */
[oracle@rh2 ~]$ mkdir $ORACLE_HOME/patches
/* 在Oracle HOME下创建存放patch的目录 */
[oracle@rh2 ~]$ cd $ORACLE_HOME/patches
[oracle@rh2 patches]$ unzip /home/oracle/patch/p7527908_102044_Linux-x86-64.zip 
Archive:  /home/oracle/patch/p7527908_102044_Linux-x86-64.zip
creating: 7527908/
creating: 7527908/files/
creating: 7527908/files/lib/
creating: 7527908/files/lib/libserver10.a/
inflating: 7527908/files/lib/libserver10.a/ktm.o
inflating: 7527908/files/lib/libserver10.a/ktu.o
inflating: 7527908/files/lib/libserver10.a/ktusm.o
creating: 7527908/etc/
creating: 7527908/etc/config/
inflating: 7527908/etc/config/inventory
inflating: 7527908/etc/config/actions
creating: 7527908/etc/xml/
inflating: 7527908/etc/xml/GenericActions.xml
inflating: 7527908/etc/xml/ShiphomeDirectoryStructure.xml
inflating: 7527908/README.txt      
[oracle@rh2 patches]$ unzip ~/patch/p9696904_102044_Linux-x86-64.zip
Archive:  /home/oracle/patch/p9696904_102044_Linux-x86-64.zip
creating: 9696904/
creating: 9696904/files/
creating: 9696904/files/lib/
creating: 9696904/files/lib/libserver10.a/
inflating: 9696904/files/lib/libserver10.a/kks1.o
inflating: 9696904/files/lib/libserver10.a/kksc.o
inflating: 9696904/files/lib/libserver10.a/kksh.o
inflating: 9696904/files/lib/libserver10.a/ksmp.o
inflating: 9696904/files/lib/libserver10.a/kspt.o
creating: 9696904/etc/
creating: 9696904/etc/config/
inflating: 9696904/etc/config/inventory
inflating: 9696904/etc/config/actions
creating: 9696904/etc/xml/
inflating: 9696904/etc/xml/GenericActions.xml
inflating: 9696904/etc/xml/ShiphomeDirectoryStructure.xml
inflating: 9696904/README.txt

接下来我们首先检查以上2个patch之间是否存在conflict冲突,这里我们会用到opatch prereq CheckConflictAmongPatchesWithDetail命令:

[oracle@rh2 db_1]$ /s01/db_1/OPatch/opatch prereq CheckConflictAmongPatchesWithDetail -phBaseDir $ORACLE_HOME/patches
Invoking OPatch 11.2.0.1.3
Oracle Interim Patch Installer version 11.2.0.1.3
Copyright (c) 2010, Oracle Corporation.  All rights reserved.
PREREQ session
Oracle Home       : /s01/db_1
Central Inventory : /s01/oraInventory
from           : /etc/oraInst.loc
OPatch version    : 11.2.0.1.3
OUI version       : 10.2.0.4.0
OUI location      : /s01/db_1/oui
Log file location : /s01/db_1/cfgtoollogs/opatch/opatch2011-05-06_22-07-18PM.log
Patch history file: /s01/db_1/cfgtoollogs/opatch/opatch_history.txt
Invoking prereq "checkconflictamongpatcheswithdetail"
Prereq "checkConflictAmongPatchesWithDetail" passed.
OPatch succeeded.
/* 可以看到以上补丁间冲突检查发现需要实施的补丁间不存在冲突 */

接着我们需要为将要实施的补丁与系统中现有的补丁检查是否存在冲突,这里我们要用到opatch prereq CheckConflictAgainstOHWithDetail命令,如:

[oracle@rh2 db_1]$ /s01/db_1/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /s01/db_1/patches/9696904
Invoking OPatch 11.2.0.1.3
Oracle Interim Patch Installer version 11.2.0.1.3
Copyright (c) 2010, Oracle Corporation.  All rights reserved.
PREREQ session
Oracle Home       : /s01/db_1
Central Inventory : /s01/oraInventory
from           : /etc/oraInst.loc
OPatch version    : 11.2.0.1.3
OUI version       : 10.2.0.4.0
OUI location      : /s01/db_1/oui
Log file location : /s01/db_1/cfgtoollogs/opatch/opatch2011-05-06_22-08-44PM.log
Patch history file: /s01/db_1/cfgtoollogs/opatch/opatch_history.txt
Invoking prereq "checkconflictagainstohwithdetail"
Prereq "checkConflictAgainstOHWithDetail" passed.
OPatch succeeded.
[oracle@rh2 db_1]$ /s01/db_1/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /s01/db_1/patches/7527908
Invoking OPatch 11.2.0.1.3
Oracle Interim Patch Installer version 11.2.0.1.3
Copyright (c) 2010, Oracle Corporation.  All rights reserved.
PREREQ session
Oracle Home       : /s01/db_1
Central Inventory : /s01/oraInventory
from           : /etc/oraInst.loc
OPatch version    : 11.2.0.1.3
OUI version       : 10.2.0.4.0
OUI location      : /s01/db_1/oui
Log file location : /s01/db_1/cfgtoollogs/opatch/opatch2011-05-06_22-08-57PM.log
Patch history file: /s01/db_1/cfgtoollogs/opatch/opatch_history.txt
Invoking prereq "checkconflictagainstohwithdetail"
Prereq "checkConflictAgainstOHWithDetail" passed.
OPatch succeeded.
/* 在这里另外举一个检查后发现冲突的例子 */

[oracle@rh2 tmp]$ /s01/db_1/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir 8557428
Invoking OPatch 11.2.0.1.3
Oracle Interim Patch Installer version 11.2.0.1.3
Copyright (c) 2010, Oracle Corporation.  All rights reserved.
PREREQ session
Oracle Home       : /s01/db_1
Central Inventory : /s01/oraInventory
from           : /etc/oraInst.loc
OPatch version    : 11.2.0.1.3
OUI version       : 10.2.0.4.0
OUI location      : /s01/db_1/oui
Log file location : /s01/db_1/cfgtoollogs/opatch/opatch2011-05-06_22-38-25PM.log
Patch history file: /s01/db_1/cfgtoollogs/opatch/opatch_history.txt
Invoking prereq "checkconflictagainstohwithdetail"
ZOP-47: The patch(es) has supersets with other patches installed in the Oracle Home (or) among themselves.
ZOP-40: The patch(es) has conflicts with other patches installed in the Oracle Home (or) among themselves.
Prereq "checkConflictAgainstOHWithDetail" failed.
Summary of Conflict Analysis:
There are no patches that can be applied now.
Following patches have conflicts. Please contact Oracle Support and get the merged patch of the patches :
9352164
Following patches are not required, as they are subset of the patches in Oracle Home or
subset of the patches in the given list : 
Following patches will be rolled back from Oracle Home on application of the patches in the given list :
9352164
Conflicts/Supersets for each patch are:
Patch : 8557428
Bug Conflict with 9352164
Conflicting bugs are:
8479537,  7462072,  8210889,  6404447

OPatch succeeded.
/* 可以看到以上发现了8557428 one-off patch与9352164(PSU4)之间存在冲突,
引发冲突的Bug是8479537,  7462072,  8210889,  6404447
opatch建议用户提交合并8557428和9352164补丁的服务要求  */

通过以上检查可以发现虽然是针对psu4(10.2.0.4.4)发布的one-off patch,但在对psu5(10.2.0.4.5)的ORACLE HOME做checkConflict时未发现冲突,接着我们opatch apply -report命令来预演补丁实施,使用-report选项让opatch仅报告其所会做的操作,而不真正去实施这些操作:

[oracle@rh2 db_1]$ cd patches/7527908/
[oracle@rh2 7527908]$ ls
etc  files  README.txt
[oracle@rh2 7527908]$ /s01/db_1/OPatch/opatch apply -report
Invoking OPatch 11.2.0.1.3
Oracle Interim Patch Installer version 11.2.0.1.3
Copyright (c) 2010, Oracle Corporation.  All rights reserved.
Oracle Home       : /s01/db_1
Central Inventory : /s01/oraInventory
from           : /etc/oraInst.loc
OPatch version    : 11.2.0.1.3
OUI version       : 10.2.0.4.0
OUI location      : /s01/db_1/oui
Log file location : /s01/db_1/cfgtoollogs/opatch/opatch2011-05-06_22-19-25PM.log
Patch history file: /s01/db_1/cfgtoollogs/opatch/opatch_history.txt
ApplySession applying interim patch '7527908' to OH '/s01/db_1'
Running prerequisite checks...
[Report: skip "rm -rf /s01/db_1/ccr"]
[Report: skip unzipping "/s01/db_1/OPatch/ocm/ocm.zip"]
Provide your email address to be informed of security issues, install and
initiate Oracle Configuration Manager. Easier for you if you use your My
Oracle Support Email address/User Name.
Visit http://www.oracle.com/support/policies.html for details.
Email address/User Name: 
You have not provided an email address for notification of security issues.
Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]:  Yes
[Report: Skip calling "/bin/sh /s01/db_1/ccr/bin/setupCCR -R
/s01/db_1/.patch_storage/ocmRespFile -S OPatch -V 11.2.0.1.3" under "/s01/db_1/ccr/bin"]
OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.
Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/s01/db_1')
Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files and inventory (not for auto-rollback) for the Oracle Home
Users request no RAC file generation.  Do not create MP files.
Skip patching component oracle.rdbms, 10.2.0.4.0 and its actions.
The actions are reported here, but are not performed.
Updating archive file "/s01/db_1/lib/libserver10.a"  with "lib/libserver10.a/ktm.o"
Updating archive file "/s01/db_1/lib/libserver10.a"  with "lib/libserver10.a/ktu.o"
Updating archive file "/s01/db_1/lib/libserver10.a"  with "lib/libserver10.a/ktusm.o"
Running make for target ioracle
ApplySession skipping inventory update.
Verifying the update...
Inventory and System verification is performed here.
The local system has been patched and can be restarted.
OPatch succeeded.
[oracle@rh2 patches]$ cd 9696904/
[oracle@rh2 9696904]$ /s01/db_1/OPatch/opatch apply -report
Invoking OPatch 11.2.0.1.3
Oracle Interim Patch Installer version 11.2.0.1.3
Copyright (c) 2010, Oracle Corporation.  All rights reserved.
Oracle Home       : /s01/db_1
Central Inventory : /s01/oraInventory
from           : /etc/oraInst.loc
OPatch version    : 11.2.0.1.3
OUI version       : 10.2.0.4.0
OUI location      : /s01/db_1/oui
Log file location : /s01/db_1/cfgtoollogs/opatch/opatch2011-05-06_22-22-11PM.log
Patch history file: /s01/db_1/cfgtoollogs/opatch/opatch_history.txt
ApplySession applying interim patch '9696904' to OH '/s01/db_1'
Running prerequisite checks...
[Report: skip "rm -rf /s01/db_1/ccr"]
[Report: skip unzipping "/s01/db_1/OPatch/ocm/ocm.zip"]
Provide your email address to be informed of security issues, install and
initiate Oracle Configuration Manager. Easier for you if you use your My
Oracle Support Email address/User Name.
Visit http://www.oracle.com/support/policies.html for details.
Email address/User Name: 
You have not provided an email address for notification of security issues.
Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]:  Yes
[Report: Skip calling "/bin/sh /s01/db_1/ccr/bin/setupCCR -R /s01/db_1/.patch_storage/ocmRespFile -S 
OPatch -V 11.2.0.1.3" under "/s01/db_1/ccr/bin"]
OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.
Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/s01/db_1')
Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files and inventory (not for auto-rollback) for the Oracle Home
Users request no RAC file generation.  Do not create MP files.
Skip patching component oracle.rdbms, 10.2.0.4.0 and its actions.
The actions are reported here, but are not performed.
Updating archive file "/s01/db_1/lib/libserver10.a"  with "lib/libserver10.a/kks1.o"
Updating archive file "/s01/db_1/lib/libserver10.a"  with "lib/libserver10.a/kksc.o"
Updating archive file "/s01/db_1/lib/libserver10.a"  with "lib/libserver10.a/kksh.o"
Updating archive file "/s01/db_1/lib/libserver10.a"  with "lib/libserver10.a/ksmp.o"
Updating archive file "/s01/db_1/lib/libserver10.a"  with "lib/libserver10.a/kspt.o"
Running make for target ioracle
ApplySession skipping inventory update.
Verifying the update...
Inventory and System verification is performed here.
The local system has been patched and can be restarted.
OPatch succeeded.

以上使用opatch apply -report进一步确认了实施以上补丁不会引起冲突或其他失败,我们可以放心地正式应用补丁了!

[oracle@rh2 patches]$ cd 7527908/
[oracle@rh2 7527908]$ /s01/db_1/OPatch/opatch apply
Invoking OPatch 11.2.0.1.3
Oracle Interim Patch Installer version 11.2.0.1.3
Copyright (c) 2010, Oracle Corporation.  All rights reserved.
Oracle Home       : /s01/db_1
Central Inventory : /s01/oraInventory
from           : /etc/oraInst.loc
OPatch version    : 11.2.0.1.3
OUI version       : 10.2.0.4.0
OUI location      : /s01/db_1/oui
Log file location : /s01/db_1/cfgtoollogs/opatch/opatch2011-05-06_22-24-46PM.log
Patch history file: /s01/db_1/cfgtoollogs/opatch/opatch_history.txt
ApplySession applying interim patch '7527908' to OH '/s01/db_1'
Running prerequisite checks...
Provide your email address to be informed of security issues, install and
initiate Oracle Configuration Manager. Easier for you if you use your My
Oracle Support Email address/User Name.
Visit http://www.oracle.com/support/policies.html for details.
Email address/User Name: 
You have not provided an email address for notification of security issues.
Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]:  Yes
OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.
Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/s01/db_1')
Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files and inventory (not for auto-rollback) for the Oracle Home
Backing up files affected by the patch '7527908' for restore. This might take a while...
Backing up files affected by the patch '7527908' for rollback. This might take a while...
Patching component oracle.rdbms, 10.2.0.4.0...
Updating archive file "/s01/db_1/lib/libserver10.a"  with "lib/libserver10.a/ktm.o"
Updating archive file "/s01/db_1/lib/libserver10.a"  with "lib/libserver10.a/ktu.o"
Updating archive file "/s01/db_1/lib/libserver10.a"  with "lib/libserver10.a/ktusm.o"
Running make for target ioracle
ApplySession adding interim patch '7527908' to inventory
Verifying the update...
Inventory check OK: Patch ID 7527908 is registered in Oracle Home inventory with proper meta-data.
Files check OK: Files from Patch ID 7527908 are present in Oracle Home.
The local system has been patched and can be restarted.
OPatch succeeded.
[oracle@rh2 7527908]$ cd ..
[oracle@rh2 patches]$ cd 9696904/
[oracle@rh2 9696904]$ /s01/db_1/OPatch/opatch apply
Invoking OPatch 11.2.0.1.3
Oracle Interim Patch Installer version 11.2.0.1.3
Copyright (c) 2010, Oracle Corporation.  All rights reserved.
Oracle Home       : /s01/db_1
Central Inventory : /s01/oraInventory
from           : /etc/oraInst.loc
OPatch version    : 11.2.0.1.3
OUI version       : 10.2.0.4.0
OUI location      : /s01/db_1/oui
Log file location : /s01/db_1/cfgtoollogs/opatch/opatch2011-05-06_22-25-58PM.log
Patch history file: /s01/db_1/cfgtoollogs/opatch/opatch_history.txt
ApplySession applying interim patch '9696904' to OH '/s01/db_1'
Running prerequisite checks...
Provide your email address to be informed of security issues, install and
initiate Oracle Configuration Manager. Easier for you if you use your My
Oracle Support Email address/User Name.
Visit http://www.oracle.com/support/policies.html for details.
Email address/User Name: 
You have not provided an email address for notification of security issues.
Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]:  Yes
OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.
Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/s01/db_1')
Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files and inventory (not for auto-rollback) for the Oracle Home
Backing up files affected by the patch '9696904' for restore. This might take a while...
Backing up files affected by the patch '9696904' for rollback. This might take a while...
Patching component oracle.rdbms, 10.2.0.4.0...
Updating archive file "/s01/db_1/lib/libserver10.a"  with "lib/libserver10.a/kks1.o"
Updating archive file "/s01/db_1/lib/libserver10.a"  with "lib/libserver10.a/kksc.o"
Updating archive file "/s01/db_1/lib/libserver10.a"  with "lib/libserver10.a/kksh.o"
Updating archive file "/s01/db_1/lib/libserver10.a"  with "lib/libserver10.a/ksmp.o"
Updating archive file "/s01/db_1/lib/libserver10.a"  with "lib/libserver10.a/kspt.o"
Running make for target ioracle
ApplySession adding interim patch '9696904' to inventory
Verifying the update...
Inventory check OK: Patch ID 9696904 is registered in Oracle Home inventory with proper meta-data.
Files check OK: Files from Patch ID 9696904 are present in Oracle Home.
The local system has been patched and can be restarted.
OPatch succeeded.
[oracle@rh2 9696904]$ /s01/db_1/OPatch/opatch lsinventory
Invoking OPatch 11.2.0.1.3
Oracle Interim Patch Installer version 11.2.0.1.3
Copyright (c) 2010, Oracle Corporation.  All rights reserved.
Oracle Home       : /s01/db_1
Central Inventory : /s01/oraInventory
from           : /etc/oraInst.loc
OPatch version    : 11.2.0.1.3
OUI version       : 10.2.0.4.0
OUI location      : /s01/db_1/oui
Log file location : /s01/db_1/cfgtoollogs/opatch/opatch2011-05-06_22-28-56PM.log
Patch history file: /s01/db_1/cfgtoollogs/opatch/opatch_history.txt
Lsinventory Output file location : /s01/db_1/cfgtoollogs/opatch/lsinv/lsinventory2011-05-06_22-28-56PM.txt
--------------------------------------------------------------------------------
Installed Top-level Products (2): 
Oracle Database 10g                                                  10.2.0.1.0
Oracle Database 10g Release 2 Patch Set 3                            10.2.0.4.0
There are 2 products installed in this Oracle Home.
Interim patches (4) :
Patch  9696904      : applied on Fri May 06 22:26:37 CST 2011
Unique Patch ID:  12575150
Created on 10 May 2010, 23:22:02 hrs PST8PDT
Bugs fixed:
7025450, 8575528, 6904068
This patch overlays patches:
9352164
This patch needs patches:
9352164
as prerequisites
Patch  7527908      : applied on Fri May 06 22:25:33 CST 2011
Unique Patch ID:  12546933
Created on 30 Apr 2010, 12:48:09 hrs PST8PDT
Bugs fixed:
7527908
This patch overlays patches:
9352164
This patch needs patches:
9352164
as prerequisites
Patch  9654991      : applied on Fri May 06 21:33:38 CST 2011
Unique Patch ID:  12816418
Created on 30 Jun 2010, 18:30:40 hrs PST8PDT
Bugs fixed:
9714832, 9713537, 9678695, 9655017, 9173248, 8309642, 9678697, 9678690
9573054, 9654991
This patch overlays patches:
9352164
This patch needs patches:
9352164
as prerequisites
Patch  9352164      : applied on Fri May 06 21:29:20 CST 2011
Unique Patch ID:  12307477
Created on 1 Apr 2010, 11:33:14 hrs PST8PDT
Bugs fixed:
.............................................................
/* Applied one-off patch successfully, That's great! */

解决Oracle错误ORA-15061一例

一套Linux上的11.2.0.1系统,告警日志中出现以下错误:

ORA-00202: control file: '+DATA/controlfile/current.256.7446483424'
ORA-17505: ksfdrsz:1 Failed to resize file to size 612 blocks
ORA-15061: ASM operation not supported [41]
WARNING: Oracle Managed File +FRA in the recovery area is orphaned by the control file.
The control file can not keep all recovery area files due to space limitation.
krse.c
Archived Log entry 200 added for thread 1 sequence 200 ID 0x3739c2f0 dest 1:
RMAN backup failed with
Rman backup error:
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 
ORA-19510: failed to set size of 6800 blocks for file "+FRA" (block size=8192)
ORA-17505: ksfdrsz:1 Failed to resize file to size 6800 blocks
ORA-15061: ASM operation not supported [41]
[oracle@rh2 ~]$ oerr ora 15061
15061, 00000, "ASM operation not supported [%s]"
// *Cause:  An ASM operation was attempted that is invalid or not supported
//          by this version of the ASM instance.
// *Action: This is an internal error code that is used for maintaining
//          compatibility between software versions and should never be
//          visible to the user; contact Oracle support Services.
//

提交SR后,根据Oracle GCS确认为BUG:9788316:

1.The following error indicates that it failed to resize the controlfile to 612 blocks. If the DB_BLOCK_SIZE is 8192, 
then 612 blocks is not more than 5MB. According to the results of the query on V$ASM_DISKGROUP in 'results01.txt' file, 
the ASM diskgroup +DATA has 108605 MB free space. So, the ASM diskgroup +DATA has enough space for the 612 blocks.
2. By the way, please confirm whether you have recently applied PSU #1. Anyway, 
please try to relink the Oracle executables, as shown here. Before you run the "relink" command, 
make sure to shutdown both the ASM instance and target database.
$ORACLE_HOME/bin/relink all
3 After relinking the Oracle executables, please confirm whether you are still 
experiencing the same ORA-15061 error.
ORA-15061: ASM Operation Not Supported [41] After Apply PSU #1 (Doc ID 1126113.1)
ORA-15061 reported while doing a file operation with 11.1 or 11.2 ASM after PSU applied in database home (Doc ID 1070880.1)

Hdr: 9788316 11.2.0.1.1 RDBMS 11.2.0.1.0 ASM PRODID-5 PORTID-267
Abstract: AFTER APPLY PSU 1 (11.2.0.1.1) ON RDBMS HOME UNABLE TO RESIZE ASM DATAFILE.

*** 06/07/10 02:09 pm ***
—-
3-1827355081

PROBLEM:
——–
1) After apply PSU 1 (11.1.0.2.1) on the 11.2.0.1.0 RDBMS Oracle Home
customer is unable to resize an ASM datafile:
============================================================
SQL> alter database datafile
‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’ resize 560M;
alter database datafile ‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’
resize 560M
*
ERROR at line 1:
ORA-1237: cannot extend datafile 4
ORA-1110: data file 4: ‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’
ORA-17505: ksfdrsz:1 Failed to resize file to size 71680 blocks
ORA-15061: ASM operation not supported [41]

============================================================

2) DB alertlog reports (alert_brg13ed1.log):
============================================================

Mon Jun 07 11:27:57 2010
Stopping background process CJQ0
Mon Jun 07 12:30:28 2010
alter database datafile ‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’
resize 536870915
ORA-1237 signalled during: alter database datafile
‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’ resize 536870915…
Mon Jun 07 13:07:40 2010
alter database datafile ‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’
resize 560m
ORA-1237 signalled during: alter database datafile
‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’ resize 560m…
Mon Jun 07 13:49:50 2010
alter database datafile ‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’
resize 800M
ORA-1237 signalled during: alter database datafile
‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’ resize 800M…
Mon Jun 07 13:58:51 2010
alter database datafile ‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’
resize 560M
ORA-1237 signalled during: alter database datafile
‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’ resize 560M…
Mon Jun 07 14:25:43 2010

============================================================

3) ASM alert.log does not report any problem.

DIAGNOSTIC ANALYSIS:
——————–
(see below)

WORKAROUND:
———–
None

RELATED BUGS:
————-

REPRODUCIBILITY:
—————-

TEST CASE:
———-

STACK TRACE:
————

SUPPORTING INFORMATION:
———————–

24 HOUR CONTACT INFORMATION FOR P1 BUGS:
—————————————-

DIAL-IN INFORMATION:
——————–

IMPACT DATE:
————

*** 06/07/10 02:09 pm ***
4) I can confirm that at (Jun 07 10:55:59 EDT 2010) customer installed the
Patch: 9355126 (on the Grid OH), which includes the fix for Bug: 8898852:
============================================================

Invoking OPatch 11.2.0.1.2

Oracle Interim Patch Installer version 11.2.0.1.2

Oracle Home : /u01/grid/oracle/product/grid
Central Inventory : /u01/app/oracle/oraInventory
from : /var/opt/oracle/oraInst.loc
OPatch version : 11.2.0.1.2
OUI version : 11.2.0.1.0
OUI location : /u01/grid/oracle/product/grid/oui
——————————————————————————

Installed Top-level Products (1):

Oracle Grid Infrastructure
11.2.0.1.0
There are 1 products installed in this Oracle Home.

Installed Products (87):

There are 87 products installed in this Oracle Home.

Interim patches (1) :

Patch 9355126 : applied on Mon Jun 07 10:55:59 EDT 2010
Unique Patch ID: 12175902
Created on 5 Feb 2010, 07:38:30 hrs PST8PDT
Bugs fixed:
8974548, 8898852
============================================================

5) Also, I can confirm that at (Mon May 03 00:01:14 EDT 2010) customer
installed the 11.2.0.1.1 Patch Set Update (PSU #1) which include as well the
patch for Bug: 8898852 (on the RDBMS OH):
============================================================
Invoking OPatch 11.2.0.1.2

Oracle Interim Patch Installer version 11.2.0.1.2

Oracle Home : /u01/app/oracle/product/11.2.0/db1
Central Inventory : /u01/app/oracle/oraInventory
from : /var/opt/oracle/oraInst.loc
OPatch version : 11.2.0.1.2
OUI version : 11.2.0.1.0
OUI location : /u01/app/oracle/product/11.2.0/db1//oui

——————————————————————————

Installed Top-level Products (1):

Oracle Database 11g
11.2.0.1.0
There are 1 products installed in this Oracle Home.

Installed Products (134):

. 11.2.0.1.0
There are 134 products installed in this Oracle Home.

Interim patches (1) :

Patch 9352237 : applied on Mon May 03 00:01:14 EDT 2010
Unique Patch ID: 12366369
Created on 6 Apr 2010, 05:03:41 hrs PST8PDT
Bugs fixed:
8661168, 8769239, 8898852, 8801119, 9054253, 8706590, 8725286, 8974548
8778277, 8780372, 8769569, 9027691, 9454036, 9454037, 9454038, 8761974
7705591, 8496830, 8702892, 8639114, 8723477, 8729793, 8919682, 8818983
9001453, 8475069, 9328668, 8891929, 8798317, 8820324, 8733749, 8702535
8565708, 9036013, 8735201, 8684517, 8870559, 8773383, 8933870, 8812705
8405205, 8822365, 8813366, 8761260, 8790767, 8795418, 8913269, 8897784
8760714, 8717461, 8671349, 8775569, 8898589, 8861700, 8607693, 8642202
8780281, 9369797, 8780711, 8784929, 8834636, 9015983, 8891037, 8828328
8570322, 8832205, 8665189, 8717031, 8685253, 8718952, 8799099, 8633358
9032717, 9321701, 8588519, 8783738, 8796511, 8782971, 8756598, 9454385
8856497, 8703064, 9066116, 9007102, 8721315, 8818175, 8674263, 9352237
8753903, 8720447, 9057443, 8790561, 8733225, 9197917, 8928276, 8991997,
8837736
============================================================

6) But the problem persists:
============================================================
SQL> alter database datafile
‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’ resize 560M;
alter database datafile ‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’
resize 560M
*
ERROR at line 1:
ORA-1237: cannot extend datafile 4
ORA-1110: data file 4: ‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’
ORA-17505: ksfdrsz:1 Failed to resize file to size 71680 blocks
ORA-15061: ASM operation not supported [41]

============================================================

7) 11.2.0.1.1 Patch Set Update (PSU #1) should include the fix for bug:
8898852 (ORA-15061: ASM operation not supported [41]).
This PSU contains a fix that adds an operation to the ASM protocol.
The problem is that the PSU has been applied correctly to the RDBMS
home, but the fix is not correctly applied to the ASM HOME.

So either install that patch to the ASM HOME, or if that has been done
check why it failed.

A common reason for failure is a permission problem. Check bug 9711074
and its duplicates for more background. And check documentation bug 8629483
for the solution.

How do I know the fix is not missing? This error message is the key:
ORA-15061: ASM operation not supported [41]
(especially with operation 41)

If the patch was applied to the grid home, then probably the relink failed
due to permission problems.

ORA-15061: ASM Operation Not Supported [41] After Apply PSU #1 [ID 1126113.1]

pplies to:
Oracle Server – Enterprise Edition – Version: 11.2.0.1 and later [Release: 11.2 and later ]
Information in this document applies to any platform.
Symptoms
1) After apply PSU 1 (11.2.0.1.1 ) on the Grid Infrastructure Oracle Home
customer is unable to resize an ASM datafile:

SQL> alter database datafile
‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’ resize 560M;
alter database datafile ‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’
resize 560M
*
ERROR at line 1:
ORA-1237: cannot extend datafile 4
ORA-1110: data file 4: ‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’
ORA-17505: ksfdrsz:1 Failed to resize file to size 71680 blocks
ORA-15061: ASM operation not supported [41]

2) DB alertlog reports (alert_brg13ed1.log):

Mon Jun 07 11:27:57 2010
Stopping background process CJQ0
Mon Jun 07 12:30:28 2010
alter database datafile ‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’
resize 536870915
ORA-1237 signalled during: alter database datafile
‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’ resize 536870915…
Mon Jun 07 13:07:40 2010
alter database datafile ‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’
resize 560m
ORA-1237 signalled during: alter database datafile
‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’ resize 560m…
Mon Jun 07 13:49:50 2010
alter database datafile ‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’
resize 800M
ORA-1237 signalled during: alter database datafile
‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’ resize 800M…
Mon Jun 07 13:58:51 2010
alter database datafile ‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’
resize 560M
ORA-1237 signalled during: alter database datafile
‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’ resize 560M…
Mon Jun 07 14:25:43 2010

3) ASM alert.log does not report any problem.

Changes
PSU 1 (11.2.0.1.1 ) patchset was installed on the Grid Infrastructure Oracle Home
Cause

The PSU #1 (11.2.0.1.1 ) patch on the Grid Infrastructure Oracle Home was not correctly linked by opatch.

The PSU #1 (11.2.0.1.1 ) patch on the Grid Infrastructure Oracle Home needs to be relinked.
Solution
Relink the PSU #1 patch on the Grid Infrastructure Oracle Home as follow:

1) Shutdown the database instances.

2) Shutdown the ASM instance.

3) Relink the Grid Infrastructure Oracle Home as follow:

script /tmp/relink_GI.txt

env | sort

$ORACLE_HOME/bin/relink all

exit

4) Startup the ASM instance.

5) Startup the databases.

6) Resize the datafile:

SQL> alter database datafile ‘+DATA/brg13ed/datafile/ts_brg_users.1279.711064345’ resize 560M;

该bug一般是由于对grid infrastructure实施了PSU 1 (11.2.0.1.1 )后,Oracle binary没有正确link导致的,可行的解决方案是relink all,但这需要重启instance!

沪ICP备14014813号

沪公网安备 31010802001379号