EBS R12.2 Delta 6 Feature Review : Enhancement of adop console messages

ADOP console messages was always something that administrators needed changes. Delta 6 new features talks that there has been more enhancements done and running SQLs are displayed. Yes & True , it does but comparing to Delta 5 there are not much improvements. If you are from a older Delta version 2 or 3 , then Delta 6 upgrade might be interesting.

Instead of displaying the complete update statements , I can see messages like "[STATEMENT] Updating cutover_status=0 for session_id : 67" which are quite meaning full.

Still see a lot of technical names used like "[STATEMENT] Inside createPatchCtxFile()..."

EBS R12.2 Delta 6 Feature Review : EBS Technology Consistency Checker (ETCC)

With EBS R12.2 Delta 6 will not display a warning message when using the ADOP utility. An additional check is made every time ADOP tool is invoked which checks for the  recommended patches that are missing in the instance. This feature is ETCC and you will see something like this on the ADOP logs.

    [PROCEDURE] [START 2015/04/27 14:27:57] Performing database sanity checks
    [WARNING]   ETCC: The following database fixes are not applied in node vmohstest001
                  14046443
                  14255128
                  16299727
                  16359751
                  17250794
                  17401353
                  18260550
                  18282562
                  18331812
                  18331850
                  18440047
                  18689530
                  18730542
                  19472320
                  19487147
                  19896336
                Refer to My Oracle Support Knowledge Document 1594274.1 for instructions.
    [PROCEDURE] [END   2015/04/27 14:27:57] Finished performing database sanity checks

Recommendation is to review the below note and get all recommended patches applied.

Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (Doc ID 1594274.1)

Note : please refer to the recent product documentation to know the latest changes.

EBS R12.2 Delta 6 Feature Review : Single File System Instance

With one of the main feature in 12.2 dual file system, there was always a need about having a single file system in 12.2 like 12.1.x and get away with the ADOP patching cycle. With Delta 6 AD and TXK you can. It is important to understand the feature and know its limitations.

There are two advantages of this single file system feature in 12.2

• no more synchronization of run and patch file system
• save storage

Still it operates with same ADOP engine and it is NOT CERTIFIED for PRODUCTION.

This feature will be interesting for development team where they need an EBS 12.2 instance where they can test their custom code.

Here is how to setup 

• Install R12.2 Instance with dual file system or Clone an existing environment with dual file system. No option available in the Rapid Installer to select single file system instance.
• Remove the PATCH_BASE using operating system remove command rm -rf $PATCH_BASE
• Apply the patch using in ADOP downtime mode and run cleanup phase as required

So what is not possible ?

• You cannot clone the single file system to build another environment.
• You cannot enable the dual file system back and start a patching cycle

Note : please refer to the recent product documentation to know the latest changes.

EBS 12.2 do not ignore the database patches on top of AD Delta 5 and TXK Delta 5

Make sure all the recommended patches are in place as a part of the bundle patch. Your EBS 12.2 ADOP cycle could go unstable with out the database patches.