Oracle Apps R12.2 Online Patching

Oracle E-Business Suite Release 12.2 installation comes with a new feature called “Online Patching” with two editions (versions) of the application code and seed data. The file system contains two complete copies of the Oracle E-Business Suite and technology files. In the database, we use the Edition-based Redefinition feature to create a new database edition for each online patching cycle. The "Run Edition" is the code and data used by the running application. As a developer, you will connect to the Run Edition whenever you are engaged in normal development activity on the system. The "Patch Edition" is an alternate copy of Oracle E-Business Suite code and seed data that is updated by Online Patching. The Oracle E-Business Suite application-tier files are installed in a root directory of the customer's choosing. Within that root directory you will now find three important sub-directories: 1) How to see, the RUN, PATCH & NON-EDITIONED Filesystems? fs1 - file system 1 (either run or patch edition) fs2 - file system 2 (alternate of file system 1) fs_ne - non-editioned file system, for data files By just setting the ebs environment, shows the filesystems. [YesBolisetty1::ebsadmin]> . /u02/app/ebsadmin/120/YesBebs/EBSapps.env E-Business Suite Environment Information ---------------------------------------- RUN File System : /u02/app/ebsadmin/120/YesBebs/fs1/EBSapps/appl PATCH File System : /u02/app/ebsadmin/120/YesBebs/fs2/EBSapps/appl Non-Editioned File System : /u02/app/ebsadmin/120/YesBebs/fs_ne DB Host: YesBolisetty1.in Service/SID: YesBebs Sourcing the RUN File System ... [YesBolisetty1:YesBebs:ebsadmin]> 2) How to identify the PATCH & RUN edition of filesystem? [YesBolisetty1:YesBebs:ebsadmin]>pwd /u02/app/ebsadmin/120/YesBebs [YesBolisetty1:YesBebs:ebsadmin]> grep FILE_EDITION= */EBSapps/appl/*.env fs1/EBSapps/appl/ajithebs_ajithpathiyil1.env:FILE_EDITION="run" fs2/EBSapps/appl/ajithebs_ajithpathiyil1.env:FILE_EDITION="patch" [YesBolisetty1:YesBebs:ebsadmin]> 3) How to connect to the PATCH & RUN edition of filesystem? [YesBolisetty1:YesBebs:ebsadmin]> . /u02/app/ebsadmin/120/YesBebs/EBSapps.env run E-Business Suite Environment Information ---------------------------------------- RUN File System : /u02/app/ebsadmin/120/YesBebs/fs1/EBSapps/appl PATCH File System : /u02/app/ebsadmin/120/YesBebs/fs2/EBSapps/appl Non-Editioned File System : /u02/app/ebsadmin/120/YesBebs/fs_ne DB Host: YesBolisetty1.in Service/SID: YesBebs Sourcing the RUN File System ... [YesBolisetty1:YesBebs:ebsadmin]> echo $FILE_EDITION run [YesBolisetty1:YesBebs:ebsadmin]> . /u02/app/ebsadmin/120/YesBebs/EBSapps.env patch E-Business Suite Environment Information ---------------------------------------- RUN File System : /u02/app/ebsadmin/120/YesBebs/fs1/EBSapps/appl PATCH File System : /u02/app/ebsadmin/120/YesBebs/fs2/EBSapps/appl Non-Editioned File System : /u02/app/ebsadmin/120/YesBebs/fs_ne DB Host: YesBolisetty1.in Service/SID: YesBebs Sourcing the PATCH File System ... [YesBolisetty1:YesBebs:ebsadmin]> echo $FILE_EDITION patch [YesBolisetty1:YesBebs:ebsadmin]> 4) How to display edition status ? To help keep track of what environment and edition you are connected to, it can be helpful to set the TWO_TASK or FILE_EDITION environment variable as your shell prompt. [YesBolisetty1:YesBebs:ebsadmin]> . /u02/app/ebsadmin/120/YesBebs/EBSapps.env patch E-Business Suite Environment Information ---------------------------------------- RUN File System : /u02/app/ebsadmin/120/YesBebs/fs1/EBSapps/appl PATCH File System : /u02/app/ebsadmin/120/YesBebs/fs2/EBSapps/appl Non-Editioned File System : /u02/app/ebsadmin/120/YesBebs/fs_ne DB Host: YesBolisetty1.in Service/SID: YesBebs Sourcing the PATCH File System ... [YesBolisetty1:YesBebs:ebsadmin]> PS1='$TWO_TASK> ' ajithebs_patch> 5) How to find out whether a system is in an Online Patching cycle using the "adop -status" command. [YesBolisetty1:YesBebs:ebsadmin]> adop -status Enter the APPS username: apps Enter the APPS password: Current Patching Session ID: 7 Node Name Node Type Phase Status Started Finished Elapsed --------------- --------------- ----------- --------------- ------------------------------ ------------------------------ ------------ YesBolisetty1 master PREPARE COMPLETED 05-APR-14 03:57:39 +00:00 07-APR-14 04:55:57 +00:00 36:58:18 FINALIZE COMPLETED 07-APR-14 06:09:01 +00:00 07-APR-14 06:54:41 +00:00 0:45:40 CUTOVER COMPLETED 07-APR-14 06:59:47 +00:00 07-APR-14 07:26:32 +00:00 0:26:45 CLEANUP COMPLETED 07-APR-14 11:26:07 +00:00 07-APR-14 11:28:53 +00:00 0:02:46 APPLY COMPLETED File System Synchronization Used in this Patching Cycle: Full For more information, run ADOP Status Report by using -detail option Generating ADOP Status Report at location: /u02/app/ebsadmin/120/YesBebs/fs_ne/EBSapps/log/status_20140529_163313/adzdshowstatus.out Please wait... Done...! adop exiting with status = 0 (Success) [YesBolisetty1:YesBebs:ebsadmin]> 6) How to find names and status of past and present database editions using the ADZDSHOWED.sql script. The below lists the existing database editions and identifies the OLD, RUN, and PATCH editions. [YesBolisetty1:YesBebs:ebsadmin]> sqlplus apps/********* @ADZDSHOWED.sql SQL*Plus: Release 10.1.0.5.0 - Production on Thu May 29 16:37:18 2014 Copyright (c) 1982, 2005, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options ========================================================================= = Editions ========================================================================= Edition Name Type Status Current? --------------- -------- -------- -------- ORA$BASE RETIRED V_20140202_0749 OLD RETIRED V_20140405_2132 RUN ACTIVE CURRENT V_20140508_1528 PATCH ACTIVE Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options [YesBolisetty1:YesBebs:ebsadmin]> 7) How to change to the patch edition of database using SQL*Plus? [YesBolisetty1:YesBebs:ebsadmin]> sqlplus apps/********* @ADZDSHOWED.sql SQL*Plus: Release 10.1.0.5.0 - Production on Thu May 29 16:37:18 2014 Copyright (c) 1982, 2005, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> exec ad_zd.set_edition('PATCH'); 8) What are the Tools and Scripts for Edition-based Development? [YesBolisetty1:YesBebs:ebsadmin]> . /u02/app/ebsadmin/120/YesBebs/EBSapps.env run E-Business Suite Environment Information ---------------------------------------- RUN File System : /u02/app/ebsadmin/120/YesBebs/fs1/EBSapps/appl PATCH File System : /u02/app/ebsadmin/120/YesBebs/fs2/EBSapps/appl Non-Editioned File System : /u02/app/ebsadmin/120/YesBebs/fs_ne DB Host: YesBolisetty1.in Service/SID: YesBebs Sourcing the RUN File System ... [YesBolisetty1:YesBebs:ebsadmin]> which adop /u02/app/ebsadmin/120/YesBebs/fs_ne/EBSapps/appl/ad/bin/adop [YesBolisetty1:YesBebs:ebsadmin]> which xdfgen.pl /u02/app/ebsadmin/120/YesBebs/fs1/EBSapps/appl/fnd/12.0.0/bin/xdfgen.pl [YesBolisetty1:YesBebs:ebsadmin]> which xdfcmp.pl /u02/app/ebsadmin/120/YesBebs/fs1/EBSapps/appl/fnd/12.0.0/bin/xdfcmp.pl [YesBolisetty1:YesBebs:ebsadmin]> 9) Useful SQL*Plus scripts that provides information about the state of your editioned development environment. All ADZD* scripts are found under $AD_TOP/sql. Add this directory to the SQLPATH environment variable so that you can refer to the scripts by simple name. [YesBolisetty1:YesBebs:ebsadmin]> SQLPATH=$AD_TOP/sql; export SQLPATH [YesBolisetty1:YesBebs:ebsadmin]> echo $SQLPATH /u02/app/ebsadmin/120/YesBebs/fs1/EBSapps/appl/ad/12.0.0/sql [YesBolisetty1:YesBebs:ebsadmin]> ADZDDBCC - database compliance checker, shows violations of the database object development standards documented in the Oracle E-Business Suite Developer's Guide, Part No. E22961. Warning: this script takes a long time to run. ADZDSHOWED - Show database editions and current edition. ADZDSHOWLOG - Show full diagnostic log for online patching infrastructure ADZDSHOWLOGEVT - Show only event and error messages from online patching diagnostic log (a useful summary, without the detailed statement text). ADZDSHOWLOGERR - Show only error messages from online patching diagnostic log. ADZDSHOWEV TABLE_SYNONYM_NAME - Show editioning view column mapping for table. ADZDSHOWTAB TABLE_SYNONYM_NAME - Show table information and related objects. ADZDSHOWMV MVIEW_NAME - Show materialized view information and related objects. ADZDSHOWTS - Show important tablespace status. Ensure that you have enough SYSTEM tablespace. ADZDCMPED - Compare Patch Edition with Run Edition. Warning: this script may take a long time to run. ADZDSHOWDDLS - Show stored DDL summary by phase. ADZDALLDDLS - Show stored DDL statement text and status. ADZDDDLERROR - Show stored DDL execution errors and messages. adutlrcmp - Recompile all objects, with before/after status report. Warning: this script may take a long time to run. The following scripts are for experts: ADZDSHOWOBJS - Show Object Summary per edition. Counts of actual and stub (inherited) editioned object per edition. ADZDSHOWAOBJS - Show Actual Objects in the current edition. These are the editioned objects that have been changed by the patch. ADZDSHOWIOBJS - Show Inherited Objects in the current edition. These are the editioned objects that remain untouched in the Patch Edition. ADZDSHOWCOBJS - Show Covered Object Summary per edition. Count of objects in old editions that have a replacement in the run edition. ADZDSHOWCOBJX - Show Covered Object List. List of objects in old editions that have a replacement in the run edition. ADZDSHOWSM - Show Seed Manager status. ADZDSHOWTM - Show Table Manager status. ADZDSHOWAD - AD (online patching) database object status ADZDSHOWSES - Show sessions connected to the database (by edition). ADZDSHOWDEP OBJECT_NAME - Show objects that OBJECT_NAME depends on. ADZDSHOWDEPTREE OBJECT_NAME - Show full dependency tree of objects that OBJECT_NAME depends on. Conflict Resolution Manager Function of Conflict Resolution Manager:- Concurrent managers read request to start concurrent programs running. The Conflict Resolution Manager checks concurrent program definitions for incompatibility rules. If a program is identified as Run Alone, then the Conflict Resolution Manager prevents the concurrent managers from starting other programs in the same conflict domain. When a program lists other programs as being incompatible with it, the Conflict Resolution Manager prevents the program from starting until any incompatible programs in the same domain have completed running. If the Conflict Resolution Manager fails, the Internal Manager will restart the Conflict Resolution Manager, or will process incompatibilities if the profile option Concurrent: Use ICM is set to Yes.

Comments

Popular posts from this blog

AWR Reports

ORA-01565: error in identifying file '?/dbs/spfile@.ora'

My Fav Song in Telugu: Aa challani samudra garbham