How to Apply Portal Patches to a Multi-midtier Environment?
Applies to:
Portal - Version: 10.1.4
Information in this document applies to any platform.
Goal
How should I be applying the Portal one-off patches such as Patch 4968540 to an environment that contains multiple Portal Midtiers.
Solution
Portal Patches
Portal patches come in two forms,
* Portal Repository patches - that will update the central Portal Database
* Portal Midtier patches - that will update files in the Midtier Oracle Home
In each case the command to apply the patch will need to be run from a Portal Midtier. To correctly apply the patch, it is important to understand if the patch is a Portal Repository patch or a Portal Midtier patch.
Applying Patches via OPatch
The accompanying ReadMe text file to every Portal patches, applied via OPatch, contains a generic APPENDIX describing the command structure to apply, show, check and rollback the patch from either the Portal Repository or the Portal Midtier.
For Portal Repository patches the command structure is:
./opatch apply -silent
-pre -s
-p
-c
For Portal Midtier patches the command structure is:
./opatch apply -silent
Applying to Multi-Midtier Environments
Portal Repository Patch
If the patch is a Portal Repository patch then this will be implied by the form of the command structure in the section "Applying this patch". When applying a Portal Repository patch to an environment containing more than one Portal midtier, the patch only needs to applied once and this can be done from any Portal Midtier, However, it is good practice to nominate one Midtier to be the patching Midtier.
Portal Midtier Patch
If the patch is a Portal Midtier patch then this will be implied by the form of the command structure in the section "Applying this patch". In this case the patch will need to be applied multiple times to each Portal Midtier.
Example - Applying Patch 4968540
At the top of the patch ReadMe is the section "Applying this patch", that should be followed to apply this specific patch. For Patch 4968540, this section clearly shows that applying this patch needs the Portal Repository form of command and so this by implication a Portal Repository patch. The ReadMe also states that this patch should be run from a Portal Midtier. So this patch needs to run once from any one of the available 10.1.4 Portal Midtiers. No action needs to be taken on any other 10.1.4 Portal Midtiers.
在多重midtier环境里如何申请补丁
应用:
Portal - Version: 10.1.4
该文档的信息可以运用到任何平台
目标
在一个包含多重的Midtiers的环境里如何去申请一个像补丁4968540 的临时补丁
解决方案
补丁有两种形式:
储存库补丁--会更新主要的数据库
Midtiers补丁--会更新Midtier Oracle Home里的文件
在每种情况下,申请补丁的指令都会避开Midtier。为了能够正确申请补丁,理解一个补丁是储存库补丁还是Midtier补丁很重要
通过OPatch来申请补丁
,
每个补丁附带的说明文件包含一般附录,描述结构指令的申请,显示、核对和从储存库补丁或者Midtier补丁回退补丁
储存库补丁的结构指令是:
./opatch apply -silent
-pre -s
-p
-c
Midtier 补丁的结构指令是:
./opatch apply -silent
储存库补丁
如果补丁是储存库补丁,在“申请补丁”部分会被结构指令的形式所隐含。将储存库补丁运用到一个包含不止一个midtier的环境里时,补丁只需要申请一次,并且能够被任何midtier完成。指定一个midtier为修补的midtier是个好的实践
midtier补丁
如果补丁是midtier补丁,在“申请补丁”部分会被结构指令的形式所隐含。在这种情况下,补丁会被多次运用到每一个midtier上
例子--申请补丁4968540
在补丁说明文件的顶端是“申请补丁”,它应该继承申请指定的补丁。对于补丁4968540,这部分能够清楚的显示:申请该补丁需要储存库指令的形式,并且被储存库补丁所暗示。说明文件同时也说明补丁应该从Midtier开始运行。因此,补丁需要从任何一个可用的Midtier运行一次。对于其他的Midtier不需要采取任何行动