db patches in upgrade from 12.1.3 to 12.2.5

[Linda]

Hi!
I am now preparing to upgrade  to 12.2.5
so there is a note 1594274.1 (12.2 Consolidated list of patches and tech. bug fixes)

There is a text that either follow this Note OR  if using/planning to use db PSU , need follow 1147107.1 ( DB patchset overlay patches required for use with PSUs)

So, my question is which path should I take ?  What is your opinion

Another question: Staged are are is confusing...
I dont think I need to download Vision db install zips, if I will not install it, right ?


Thanks for your time,Linda





Thanks,Linda

[ErmanArslansOracleBlog]

Hi Linda,

We can't say Database PSU is required or not required. Most of time, you don't apply DB PSUs, as  it s your choice.
But, if you like to apply Database PSU, then go ahead and follow that note too.
Currenty, EBS 12.2 certifies the Database as a whole. What I mean is, if EBS certifies 12.1.0.2, then it certifies with any PSU or without a PSU. EBS requires a list of DB patches to be applied but does not require a PSU to be applied.

Sometimes the hardware (such as Exadata and ODA) + combination of Hardware+EBS requires an Oracle Home to be on a certain PSU level. If that 's the case, you need to apply the PSU to be able to run your database on that hardware.
The section name already says that: "Database Patch Set Updates and Exadata/SuperClusters Patches"

Applying PSUs is a good thing, there are lots of bug fixes delivered with them.

So, if you have time, apply the latest PSU for your DB. (apply it carefully and then test your database afterwards)

But if you don't have time && if you don't have any requirements && if you don't give much importance to DB PSUs, then you can just follow the tables in the document 1594274.1 (For ex: Table 1.1 - Patches and bug numbers for Database 11.2.0.4.0 UNIX platforms) and apply the missing patches (not delivered with the startCD that you use)

So again, applying PSU is a good thing, but the choice is yours.

Lastly, you need to choose which table to follow using the following paragraph; (those "if" s are important)

*If you are following a Database Patch Set Update (PSU) patching strategy without the In-Memory option enabled, or using Exadata/SuperClusters regardless of In-Memory usage;
Then;
you follow->
The following documents provide a complete list of database patches that need to be applied for both PSU (without the In-Memory option enabled) and on Exadata/SuperClusters:
My Oracle Support Knowledge Document 1147107.1, Database Patch Set Update Overlay Patches Required for Use with PSUs.
My Oracle Support Knowledge Document 1392527.1, Database Patches Required by Oracle E-Business Suite on Oracle Engineered Systems: Exadata Database Machines and SuperClusters

*If you have upgraded to Oracle Database 11.2.0.4.0, you will need to apply all the patches listed in Table 1.1 or Table 1.2 for Microsoft Windows.

*If you have upgraded to Oracle Database 12.1.0.2.0 without the In-Memory option enabled apply all the patches listed in Table 1.3.

*If you have upgraded to Oracle Database 12.1.0.2.0 with the In-Memory option enabled apply all the patches listed in Table 1.4.1 which includes the latest recommended Database Bundle Patch. Existing installations configured using the previous Database Bundle Patch detailed in Table 1.4.0 should migrate to the list of patches listed in Table 1.4.1 at the next available opportunity.

*For Oracle Database 12.1.0.2.0 on Microsoft Windows with or without the In-Memory option enabled apply all the patches listed in Table 1.5.

[ErmanArslansOracleBlog]

bytheway, those Oracle Support documents are updated frequently. So when they are updated, you may see the same document in a different format and listing different patches..
That is , if you do your upgrade or installation project in a long of period of time; keep that in your mind as well.. (See document details; for ex: document 1594274.1 is updated in 2 August)
This is a just a reminder..

[Linda]

Hi Erman! Thank you for your time to answer!
I am after the "good" practise, be pro-active :)  We dont run exadata.  I just DONT  want to run in data corruption, wrong result or optimiz. issue. So, that why I think  PSU is a good thing to apply when I am doing upgrade and testing will be anyway ..

Risk is probably only the conflict of patches and in overlay note should be table what should i apply.
Its should not  also overwrite any IO patches with EBs, otherwise that note would mention it.


Br,Linda

[Linda]

Hi Erman!

What do you think ?
We dont use in memory db and not Exadat, no RAC.
I am in planning phase and users tests all is ahead of us...
SO, i would install rapidinstall start CD 12.2.0.v51 (latest) 1c home.

& I want to be proactive, so instead of PSU. I would take for 12.1.0.2   Combo patch (OJVM Jul + DB DB Bundle patch Jul 16) + consolidate patch for EBS and run ETCC.

Any negative  here ?
We will still be supported and if conflicts oracle should fix those...

Thanks again,L.

[ErmanArslansOracleBlog]

I think it is okay.
EBS does not prevent you applying any database patches and as it is documented, you can go ahead and put your plan in action. However, applying a big and very new patch may increase your deployment time. A conflict may aries, and it may take couple of days to solve (even with the Oracle Support). So keep that in mind as well.

Ref:

If the conflict resolution is not listed in either Document 1147107.1 or Document 1392527.1, or if a conflict is caused by additional patches that are not listed, contact Oracle Support and request a customer-specific merge patch. Do not roll back a PSU or Exadata/SuperClusters Bundle Patch unless Oracle documentation explicitly instructs you to do so.

Be aware that this consolidated patch does not include any database bundle patches or PSUs. Where applicable, you will need to download and apply these first, and then run ETCC detailed in Section 2 of this document. This will ensure that the bugfixes and patches for your release are identified before you download the appropriate consolidated zip file patch.