12.2.13

[Laurel]

Hi Erman! :)

1) question: 12.2.6->12.2.13
Going with Oracle E-Business Suite Release 12.2.13 Readme (Doc ID 2958077.)
and to Section 6
Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)
 Path B: Existing Release 12.2 customers (below AD-TXK Delta 16 codelevel)

So now I am in situation that on patch system all ETCC applied
With Active patch cycle applied AD+TXK16
Now according to the 1617461.1 I need to finish adop cycle and do fs_clone..

But to save time I was thinking that after AD+TXK I could continue with same cycle and apply  12.2.13 patchset in single adop cycle..

What do you think ?

2)Also in the same 1617461.1 is said that for critical patches

   " Patch 27911576:R12.OWF.C
Note that you do not need to apply this patch if you are planning an immediate upgrade to any of the following:
    Consolidated Bundle Patch on top of R12.ATG_PF.C.Delta.7 Patch 26924701:R12.ATG_PF.C.
    Oracle E-Business Suite 12.2.8 Release Update Pack Patch 26787767 or later.
    Oracle Applications Technology 12.2.9 Product Family Release Update Pack Patch R12.ATG_PF.C.delta.8 or later."

I dont have  this patch and plan in next adop cycle apply 12.2.13. Would it be enough or  how do you understand "immediate" ? the same patch cycle ?

Thx Alot!
Best wishes, Laurel

[Laurel]

Hi Erman!

Looks like found answers myself .. Even I dont like :) it as extra patching cycle needed
But maybe saves me time on troubleshooting if problem comes up and Oracle would say " Not recommended" :)

1.Can we apply AD/TXK Release Update patches and 12.2.x RUP in the same ADOP Patch cycle ? (Doc ID 2942144.1)
--> Separate cycles
2.About WF patch.. I guess  this will be immediate upgrade as well.
first AD/TXK , new adop cycles and R12.2.13

Take care! :) Have a nice weekend!
Laurel

[ErmanArslansOracleBlog]

Sorry for the late response Laurel. I was on a vacation.
Anyways, you already shared your answers. For that question about the interpretation of the word "immediate" :), my answer is, yes. Just apply one of those patches along the way, before finishing your upgrade work, before starting the services.. R12.2.13 is already in your short term plan of this patching project , so it is OK.

[Laurel]

Hi!
Great that  you had time off & vacation as well sometimes! :) Not only work and work  :)
Hope it was good one  too!

Thx for confirmation! :)
and now 12.2.14 is out, so we will take it !

br,Laurel

[Laurel]

Hi Again!
and one followup question :
the future PDB database/source db :
SQL> select * from nls_database_parameters where parameter like '%CHARACTERSET%';

PARAMETER
--------------------------------------------------------------------------------
VALUE
--------------------------------------------------------------------------------
NLS_NCHAR_CHARACTERSET
AL16UTF16

NLS_CHARACTERSET
UTF8

So, the CDB I will create   will have the same or do you see a problem here ?

Thx alot!
Br,Laurel

[ErmanArslansOracleBlog]

No problem.

Character Sets For CDB And PDB in 12.2 (Doc ID 2231602.1)

There are just 2 recommendations for that;

Oracle recommends the following when selecting character sets for CDBs:

1. For all new multitenant deployments, use AL32UTF8 as the database character set and AL16UTF16 as the national character set for a CDB.

2. Migrate your existing databases to AL32UTF8 database character set before consolidation and then consolidate the databases into one or more AL32UTF8 CDBs, depending on your needs. You can use the Oracle Database Migration Assistant for Unicode software to migrate a non-CDB to AL32UTF8 database character set.

There are some issues reported there.. Having the same characterset is safer it seems. -> EBS DB Upgrade to 19c : PDB Not In Unicode (AL32UTF8) Character Set. PDB Character Set US7ASCII. (Doc ID 2758403.1)