EBS 12.2 ADOP useful Queries

 

EBS 12.2 adop queries:  

adop session status:

set pagesize 200;

set linesize 160;

col PREPARE_STATUS format a15

col node_name format a30

col APPLY_STATUS format a15

col CUTOVER_STATUS format a15

col ABORT_STATUS format a15

col STATUS format a15

select NODE_NAME,ADOP_SESSION_ID, PREPARE_STATUS , APPLY_STATUS  ,CUTOVER_STATUS , CLEANUP_STATUS , ABORT_STATUS , STATUS from AD_ADOP_SESSIONS where ADOP_SESSION_ID=66;

Note: Y denotes that the phase is done

N denotes that the phase has not been completed

X denotes that the phase is not applicable

R denotes that the phase is running (in progress)

F denotes that the phase has failed

P (is applicable only to APPLY phase) denotes at least one patch is already applied for the session id

C denotes that the status of this ADOP session has completed

cutover statuses:

cutover_status='Y' 'COMPLETED'

cutover_status not in ('N','Y','X') and status='F' 'FAILED'

cutover_status='0' 'CUTOVER STARTED'

cutover_status='1' 'SERVICES SHUTDOWN COMPLETED'

cutover_status='3' 'DB CUTOVER COMPLETED'

cutover_status='D' 'FLIP SNAPSHOTS COMPLETED'

cutover_status='4' 'FS CUTOVER COMPLETED'

cutover_status='5' 'ADMIN STARTUP COMPLETED'

cutover_status='6' 'SERVICES STARTUP COMPLETED'

cutover_status='N' 'NOT STARTED'

cutover_status='X' 'NOT APPLICABLE'

fs_clone status:

set linesize 300

col node_name format a15

col clone_status format a20

col driver_file_name format a20

col clone_status format a20

select node_name,clone_status,driver_file_name,status,to_char(start_date,'DD-MON-YYYY HH:MI:SS PM'),to_char(end_date,'DD-MON-YYYY HH:MI:SS PM') from ad_adop_session_patches where adop_session_id=89;

To find the patches applied in the particular adop session:

select distinct BUG_NUMBER from AD_ADOP_SESSION_PATCHES  where adop_session_id='&session_id';

set linesize 300;

select distinct bug_number,node_name,to_char(start_date ,'DD-MON-YYYY HH24:MI:SS') START_DATE,to_char(end_date,'DD-MON-YYYY HH24:MI:SS')END_DATE from ad_adop_session_patches where adop_session_id=67 group by bug_number,node_name,start_date,end_date order by bug_number;

select distinct bug_number,node_name,to_char(start_date ,'DD-MON-YYYY HH24:MI:SS') START_DATE,to_char(end_date,'DD-MON-YYYY HH24:MI:SS')END_DATE from ad_adop_session_patches where adop_session_id=&session_id  and bug_number='&bug_number' group by bug_number,node_name,start_date,end_date order by bug_number;

AD,TXK VERSIONS:

SELECT abbreviation, codelevel FROM AD_TRACKABLE_ENTITIES WHERE abbreviation in ('txk','ad');

ETCC QUERIES:

set linesize 300;

col node_name format a10;

col database_name format a10;

col check_message format a50;

select database_name,node_name ,check_date ,component_name,component_version,check_message from apps.TXK_TCC_RESULTS where database_name='&DB_NAME';

adop failed with "Patch service is not exist or running"

While applying the patch  ,getting the error "Patch service  is not exist or running".


validating system setup.
    Node registry is valid.
    Log: /u01/JAYPRE/fs1/inst/apps/JAYPRE_JJ10003/logs/appl/rgf/TXK/verifyssh.log
    Output: /u01/JAYPRE/fs1/inst/apps/JAYPRE_JJ10003/logs/appl/rgf/TXK/out.xml
    Remote execution is operational.
    [ERROR]     Patch service  is not exist or running
 
Package AD_ZD_PREP is invalid.
                
SQL> alter package apps.AD_ZD_PREP compile;

Warning: Package altered with compilation errors.

SQL> show errors package body apps.AD_ZD_PREP;
Errors for PACKAGE BODY APPS.AD_ZD_PREP:

LINE/COL ERROR
-------- -----------------------------------------------------------------
463/3    PL/SQL: SQL Statement ignored
463/19   PL/SQL: ORA-00942: table or view does not exist
467/5    PL/SQL: SQL Statement ignored
467/21   PL/SQL: ORA-00942: table or view does not exist
501/5    PL/SQL: SQL Statement ignored
501/21   PL/SQL: ORA-00942: table or view does not exist


Run adgrants.sql script
SQL> @adgrants.sql APPS

SQL>  alter package apps.AD_ZD_PREP compile;

Package altered.

Now retry adop.It should work.

ADOP (Ad online patching utility) in R12.2

Adop(Ad online patching utility) is used in R12.2 to apply the patches online with out any downtimeit is the new utility which to apply patches in online patching mode .It is perl script and call adpatch internally to apply the patch. It is not recommended to apply the patches directly using adpatch in R12.2

For online patching to work Oracle Apps make use of 11g database feature called as “Edition Based Redefinition”, under this feature. On the Applications side, there will be two file systems, one called as patch and other called as run file system. Both are identical to each other and services will be running out of run file system. During patching process, patches are applied to patch file system, which does not require any downtime. For the patch changes to come to effect, patch file system is switched as run file system and vice versa, and services are restarted. In essence, Downtime will be only for the time duration during which services are restarted.

A complete patching cycle is following while applying the patches with adop. It consists of many phases

1.Prepare: This syncs the current patch file system with run file system, to make sure patch file system is up to date compared to run file system and ready for the patches to get applied. This also created a new patch edition in the database. This syncing process is incremental process to be efficient.

$ adop phase=prepare

2.Apply : Patches are applied to patch file system during this phase, we can apply as many patches we want during this phase. Changed code objects are from patch edition of database. Changes to tables are stored in new columns which are only visible from patch edition of the database.

$ adop phase=apply patches=

3.Finalize: This phase involves compiling of invalid objects etc.

$ adop phase=finalize

4.Cutover: This phase configures the patch file system as new run file system and patch edition of the database as new run edition. Restart application services from new run file system of Apps. This is where downtime is required.

$ adop phase=cutover

5.Cleanup: Deletes obsolete code objects and columns from earlier patch edition are removed at database.

$ adop phase=cleanup

Some more things about adop

1)Online Help
To obtain help about the basics of adop operation, enter the command:

adop -help

2) Enabling maintenance mode is not required in R12.2; it’s not applicable for online patching.

3) There are also three special phases, for use when needed.
Special phases:
abort – Abort the current patching cycle.
actualize_all – Create new copies of all code objects in the patch edition.
fs_clone – Copy the run file system to the patch file system.

4) The adop logfiles are located on the non-editioned file system (fs_ne), under:
s_ne_base/EBSapps/log/adop//__/ext_name>/log
For example, if s_ne_base was /u01/apps/R122_EBS/fs_ne, the session ID was 20, and the
was sunxx_test, the path to the adop log files from 1th July 2013 would resemble this:
/u01/apps/R122_EBS/fs_ne/EBSapps/log/adop/20/apply_20130701_112226/sunxx_te
stsys/log

5) You can obtain a brief report for the current patching session by running the command:
$adop -status
This will display information that includes phases completed and the time taken