Upgrade R12.2.0 to R12.2.10 fresh installation

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Upgrade R12.2.0 to R12.2.10 fresh installation

satish
Dear erman,

1)After installation of R12 2.0,we are applying patches in hot patch mode as per installation document but why are we shutting down the services except admin server in hot patch mode?

What will the consolidated seed upgrade patch will do?
Thanks,

Satish
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade R12.2.0 to R12.2.10 fresh installation

ErmanArslansOracleBlog
Administrator
That s because , we have that requirement even in the readme of those types of patches..

For instance ; in the Readme of  Patch 26787701: R12.2.0: CONSOLIDATED SEED TABLE UPGRADE PATCH
-->
This patch#26787701:12.2.0 must be applied in hotpatch mode with adop on the Run
File System, after ensuring that only AdminServer is up and running.

Seed data (not the tables even data!) is a little sensitive. The seed data is the data used by  the code itself, and unlike the application data stored in the application tables, the seed data is created and patched by Oracle..
The approach that Adop takes behind the scenes while patching the seed data using online patching is also a little different than other patches.

Anyways, there in consolidated seed table upgrade patches, we touch (maybe more than that... I didn't check the patch driver, but probably we do structural changes as well) the seed tables that are used by the code itself.. It is not a thing that we do everyday :) it is better to have apps services stopped.. Again -> Even the patch Readme say that!