ADOP Patch Overview

By Anonymous -

ADOP patch (application DBA online patch) It is relisted to R12.2

It is utility to apply online patch

There are five phases are available

adop phase=Prepare

adop phase=apply patches=<patch _number>

adop phase=finalize

adop phase=cutover

adop phase=cleanup

 

ADOP Applying process:-

 Step 1: Source the file system

Step 2: Check the patch already applied are not?

 (EX)

Connect Sqlplus apps/apps

select bug_number from ad_bugs where bug_number = 'Patch_number';


SQL> select bug_number from ad_bugs where bug_number = '24962217';

BUG_NUMBER

------------------------------

 24962217

SQL> select bug_number from ad_bugs where bug_number='20518445';

no rows selected

Download the patch and move the patch in $PATCH_TOP

cd $PATCH_TOP

  Or

cd /apps/applmgr/fs_ne/EBSapps/patch


Step 3: adop phase=prepare

adop prepare phase will be create a new patching cycle

Synchronizing filesystem of Run to Patch


Step 4: adop phase=apply patches=234567 

adop apply phase is applies the PATCHES to the patch edition


Step 5: adop phase=finalize

adop finalize phase is performed to system ready to cut over phase

It is perform the operations are compile the invalid objects


Step 6: adop phase=cutover

adop cutover phase is restart application services and run edition will promote patch edition patch edition will promote run edition for in this phase.

Disconnect all users

Perform Maintenance task


Step 7: adop phase=cleanup

 

cleanup_mode=(full|standard|quick) [default: standard]

Quick mode provides the shortest execution time, by skipping non-essential actions.

Standard mode performs additional processing to drop obsolete code objects from old editions.

Full mode performs additional processing to drop emptydatabase editions and unused table columns.

Example - Run quick cleanup for minimum delay to next prepare:

adop phase=cleanup cleanup_mode=quick

Example - Run full cleanup for maximum space recovery:

adop phase=cleanup cleanup_mode=full


adop phase=abort

 If patching cycle encounters problems that can’t fix immediately we can abort the patching cycle and return to the normal operations

The abort command drops the database patch edition and returns the system to normal runtime state. Immediately

following abort, you must also run a full cleanup and fs_clone


adop phase=prepare
adop phase=apply patches=123456
unfixable error reported
adop phase=abort
adop phase=cleanup cleanup_mode=full
adop phase=fs_clone

 

So, this will remove all columns that were added by the patches but are no longer needed because of the abort.

And If that columns are not removed, then that may create problems in a later patching cycle.

 

Adop Monitoring & Reporting commands

adopmon:

Adopmon utility 12.2.5 new feature. Its provide the continuously refreshed view of the adop phase actions

$ adopmon
Running script. Press Ctrl-C to quit.

Enter the APPS password:

Adopreports:

Adopreport utlity executed in application and and database patch related reports in without sql command

$ adopreports <APPS username> <APPS password>

Log file location and commands:

 cd $ADOP_LOG_HOME

adop log directory

adopscanlog

adopscallog utlity show the latest adop session errors and this utlity provide the various options

adopscalog –help

adopscalog –latest=yes

adopscalog –latest=yes –phase=<phase_name>

adopscalog  -session_id=<Number>

adopscalog –scan_dir=<Directory_Path>


Commonly using patch related SQL Queries:

 

How to check patch already applied are not?

SQL> select bug_number from ad_bugs where bug_number = '24962217';


How to check AD version in application

SQL> select product_version from fnd_product_installations where patch_level like %AD%;

 

ADOP (Online Patch)  Frequently Asked Questions(FAQ)

 

What is Online Patching?

Online patching is a new patching mechanism that allows the application of patches while the system is up and running, and the users are working as normal.

What types of patch are applied online?

All Oracle E-Business Suite Release 12.2 patches are applied online. This includes one-off patches, patch rollups, consolidated updates and security patches.

Is there any downtime in Online Patching?

There is a short period of downtime when the application tier services are shut down and restarted. The database remains open all the time. For more details of these topics, see the Online Patching Concepts section below.

What are the phases that make up the Online Patching cycle?

The Online Patching cycle consists of the following phases:

• Prepare a virtual copy (patch edition) of the running application (run edition).

• Apply patches to the patch edition of the application.

• Finalize the system in readiness for the cutover phase.

• Cutover to the patch edition and make it the new run edition.

• Cleanup obsolete definitions or data to recover space.

What downtime is required during an Online Patching cycle?

The cutover phase requires a short period of downtime (typically a few minutes) for transition tasks such as a restart of the application tier services.

Is any downtime required for the database tier?

No. In fact, the database needs to be up and running during each phase of the Online Patching cycle. However, non-Oracle E-Business Suite delivered database clients need to re-establish their database connection after the Online Patching cutover phase is performed. This includes connections from ODI Agent and Discoverer Server, as well as connection pools from Oracle SOA Suite and any other third party software connected to the Oracle E-Business Suite database

Can I apply multiple patches in an Online Patching cycle?

Yes. We recommend that if you have multiple patches to apply, you apply them in a single Online Patching cycle. This will minimize the overall time needed.

Is it possible to abort an Online Patching session?

Yes. Up to cutover, you can run the abort phase to undo the changes made so far in the patching cycle. It is not possible to back out patches once cutover is complete.

What is duplicated on the second file system used by Online Patching?

The second file system contains a copy of all the components that make up an application tier file system, including:

• APPL_TOP - Oracle E-Business Suite code

• INST_TOP- Instance Configuration Home

• FMW_HOME - Oracle Weblogic Server Home and Oracle E-Business Suite Domain

• ORACLE_HOME - Oracle Application Server Home, Forms, Reports

• IAS_ORACLE_HOME - Oracle OHS Home

• COMMON_TOP - Oracle E-Business Suite Java code, third-party libraries

What is downtime mode and when can it be used?

To optimize the process of upgrading to E-Business Suite Release 12.2, the AD Delta 5 Release Update Pack introduced downtime mode, which is used as follows:

$ adop phase=apply patches=<patch_number> apply_mode=downtime

Downtime mode does not use an online patching cycle. The process of applying a patch in downtime mode completes more quickly than in online mode, but at the cost of increased system downtime. When applying Oracle E-Business Suite patches in this mode, adop will first confirm that the application tier services are down, and will then proceed to apply the patch to the run edition of the Oracle E-Business Suite database and file system.

Downtime mode is supported for:

• All patching (including post-upgrade patching) that forms part of the Release 12.2 upgrade process and is completed before the system is scaled up, the application tier services are started, and users log in to the upgraded system.

• Single-node development or test environments, where production support and high availability are not required.

Downtime mode allows the 12.2 upgrade process to be completed as quickly as possible. Once the upgrade is complete and users are online, all subsequent patching on a production system should use online mode, not downtime mode, unless the patch readme states otherwise. 

Several restrictions apply to the use of downtime mode:

 

• You cannot validate successful patch application before cutover to the updated code takes place.

 

• There is no capability to abort a failed patch and return to the existing run edition.

 

• Release 12.2 patches are not normally tested in downtime mode.

 

• Use of downtime mode in a multi-node application tier environment is not tested or supported.

 

What can I do to reduce the time required for cutover?

It is important to distinguish between the time needed for the whole cutover phase, and the downtime period within the phase. The actual downtime (during which users cannot log in) is significantly shorter than the whole phase. To help reduce the overall time taken by cutover, you can do three things:

• Run the finalize phase explicitly, to obviate the need for cutover to do so.

• Shut down the concurrent managers before running cutover, to avoid having to wait for concurrent requests to complete. Alternatively, ensure no long-running concurrent jobs are submitted while a patching cycle is in progress.

• Ensure you are using the maximum number of parallel workers your system will support.

What is fs_clone and how is it used? 

The command adop phase=fs_clone is a special command that is used to copy the run file system to the patch file system. Also see previous question.

Refer:

E-Business Suite - ADOP Basic Usage Training Videos [Video] (Doc ID 2103131.1)

Comments

Post a Comment

Popular posts from this blog

How to troubleshoot long running concurrent request in R12.2

By -
Normally we are getting concurrent program running longer and concurrent request not picking jobs, etc. those are very frequent issue we expected from development team. Collect below basis level of information to development team 1 Oracle seeded program/Custom program? 2 How much time it used earlier? 3 Is there any recent code change done in concurrent program? 4 Is this program fetching higher data compare to last run? 5 Does this job running any specific time/ It can be run any time? 6 Does this job fetching data using DB link? 7 Does the problem happen on both the test and production instance? Once asked above questions to development team in meanwhile we need to start basic sanity check in our environment. 1 Verify the status of the concurrent program Copy select REQUEST_ID,phase_code,status_code,ORACLE_SESSION_ID from apps.fnd_concurrent_requests where request_id=’1234567’;
Read more

How to run Gather Schema Statistics in R12.2

By -
Image
What is Gather Schema Statistics? Gather Schema Statistics program generates statistics that quantify the data distribution and storage characteristics of tables, columns, indexes, and partitions. The cost-based optimization (CBO)  uses these statistics to calculate the selectivity of prediction and to estimate the cost of each execution plan. Why Run the Gather Schema Statistics? When Data is update, insert, delete in table of user end Like (Technical User ,Finance User ,Ect) It become necessary to run the Gather Schema Statistics It’s recommended to Run GSS in Weekly Once or twice. How to run Gather Schema Statistics? Login application with sysadmin user Submit Request Window Navigate to: Concurrent > Requests Enter the parameters This can be run for specific schemas by specifying the schema name or enter ‘ALL’ to gather statistics for every schema in the database Submit the Gather Schema Statistics program Parameters: Schem
Read more

How to compile forms in R12.2

By -
STEP 1--> Login to app server STEP 2--> Go to  directory $AU_TOP/forms?US STEP 3--> Move to ".fmb" file STEP 4--> Execute the below command to generate ".fmx" frmcmp_batch userid=apps/<apps_pwd> module=<form_name>.fmb output_file=<form_name>.fmx module_type=form batch=no compile_all=special (EX):-   frmcmp_batch userid=apps/apps module=JAINTAXT.fmb output_file=$JA_TOP/forms/US/JAINTAXT.fmx module_type=form batch=no compile_all= special (O/p):   Created form file /oracle/CLONE/apps/fs2/EBSapps/appl/ja/12.0.0/forms/US/ JAINTAXT.fmx Refer: R12: How to Compile a Form in Release 12 (Doc ID 1085928.1)
Read more