city_85

0 积分	1 好友	2 主题

发消息

[ORA-600/ORA-7445] 请教下exadata上打PSU 16869210

1^#

发表于 2013-9-2 20:52:54 | 查看: 4469| 回复: 8

exadata机器两台：别名为exadata1和exadata2吧
OS RHEL5.8 DB version：11.2.0.3
目前客户需要在两台exadata上打PSU 16869210的补丁（FOR exadata）。
环境为：两台exadata上面都只使用oracle用户（没有grid用户）装了几套RAC系统，
exadata1上面有2套RAC数据库，实例名为A1、A2及B1和B2
exadata2上面有3套RAC数据库，实例名为A1、A2(为上面A1、A2的双活adg)及C1和C2、D1和D2
由于打PSU因为涉及到adg，所以不太好操作，
请教下maclean，我打的过程是不是要把exadata1上的A1、A2切换为备库，让exadata2上A1、A2切换为主库后先打exadata2啊
然后再切回来打exadata1，这样可以的不？

或者是我把exadata1上面的A1、A2实例的参数LOG_ARCHIVE_DEST_STATE_1先给defer掉，打完exadata1主库再打exadata2备库，最后再把该参数enable进行同步，可以吗？

先谢谢maclean了！！

分享0

收藏0 回复只看该作者道具举报

city_85

2^#

发表于 2013-9-2 20:56:20

本帖最后由 city_85 于 2013-9-2 20:57 编辑

刚才没有说清楚，补充一下：所谓的2套rac或3套rac都是指在exadata上面使用oracle用户安装了crs及数据库软件后，再用DBCA新建了不同的实例A1、A2及B1、B2，即共享CRS软件及数据库软件，多个不同的实例而已。

回复只看该作者道具举报

Maclean Liu(刘相兵

3^#

发表于 2013-9-4 21:52:37

Exadata 上一般推荐打BP bundle Patch，为什么要打PSU

回复只看该作者道具举报

city_85

4^#

发表于 2013-9-4 22:22:42

是安全检查以及为了减少bug打补丁，oralce的推荐打PSU 16869210: QUARTERLY PATCH FOR EXADATA (JUL 2013 - 11.2.0.3.20)这个补丁，安装的方式为：
方案为先打exadata1，当然要把实例A上的同步参数先defer掉，打完后对每套rac进行跑catbundle.sql，然后观察exadata1是否有问题，没问题就继续打exadata2，打完后对每套rac进行跑catbundle.sql（adg的不跑），数据字典变化到时由主库直接同步过去。

回复只看该作者道具举报

city_85

5^#

发表于 2013-9-4 22:24:24

Maclean Liu(刘相兵发表于 2013-9-4 21:52
Exadata 上一般推荐打BP bundle Patch，为什么要打PSU

这种补丁跟PSU有很大差别的吗

回复只看该作者道具举报

Maclean Liu(刘相兵

6^#

发表于 2013-9-4 22:28:23

Exadata 上一般推荐都打BP bundle Patch

(1) Recommended bundle patches, named Quarterly Database Patch for Exadata (QDPE), will be released quarterly,
aligned with and including the database Critical Patch Update (CPU) and Patch Set Update (PSU) releases. QDPE
releases are targeted for planned grid infrastructure and database patching activities and are the only patch
bundles that will be applied by most customers.
Oracle will also continue to make important fixes available in monthly or bimonthly interim bundle patches. Most
customers will only install these if they are recommended by Oracle Support to address a specific issue that is fixed
in an interim bundle patch and the customer cannot wait for the next QDPE containing the fix. Interim bundle
patches provide faster response for specific issues and are expected to contain fewer fixes than QDPEs.
All bundle patches are cumulative, as in previous releases.
(2) Error correction support for 11.2.0.2, originally scheduled to end 23-Sep-2012 (one year after the release of
11.2.0.3) per the Software Error Correction Support Policy in Document 209768.1, has been extended to 28-Feb-
2013. Exadata customers running 11.2.0.2 or earlier should plan to upgrade to 11.2.0.3 or later by 28-Feb-2013 to
continue to receive error correction support.
(3) In accordance with the Software Error Correction Support Policy in Document 209768.1, new 11.2.0.1 Database
Bundle Patches for Exadata ceased as of 13-Sep-2011 (one year after the release of 11.2.0.2). There will be no
further 11.2.0.1 bundle patches. However, as a special exception for Exadata customers, Oracle will continue to
provide interim patches on 11.2.0.1 for the Exadata Database Machine until 30-April-2012. Exadata customers
running 11.2.0.1 should plan to upgrade to 11.2.0.2 or 11.2.0.3 by 30-April-2012 to continue to receive error
correction support.

回复只看该作者道具举报