Saturday, May 14, 2016

E-Business Suite R12.2: Online Patching


Oracle E-Business Suite Release 12.2 introduces Online Patching, a new feature that greatly reduces the downtime that was needed in previous releases for application of Release Update Packs (RUPs), Critical Patch Updates (CPUs), and other patches and bug fixes of various kinds.

How it Works?
  1. A copy is made of the running system.
  2. Patches are applied to the copy while users continue to access the running system.
  3. Transparently to users, the copy becomes the new running system.
  4. What was the original running system (now obsolete) is deleted. 
The Online Patching infrastructure is the Oracle E-Business Suite Release 12.2 mechanism that allows Oracle E-Business Suite patches to be applied online, while the system is running and users are working as normal. This infrastructure includes database objects and file system components.
To Incorporate the Online patching There few Architectural Changes in 12.2 to Support Online Patching.
Patching Occurs on a Copy Not on the Actual system.
  • Database
    • A separate copy is maintained of all database code objects that
      are changed by a patch
  • File system
    • All patches are applied to the secondary file system
    • Synchronization of the file systems is managed by the patching tools


DataBase 11G R2 Edition-Based Redefinition (EBR)
Enables the online upgrade of the database tier,Allows an application to efficiently store multiple copies of its application definition in the same database. Provides an isolation mechanism that allows pre-upgrade and post-upgrade schema to co-exist,Changes to database objects are made in the isolation of an “Edition” ,Changes to database objects do not effect the running Application.

Database Editions
  • Run Edition
    • The edition currently in use by the running application ,Used by Online Users
    • This is always the default database edition 
    • Never changed by a Patch
  • Patch Edition
    • The edition currently in use by the patching tool adop (AD Online Patching) utility.
    • This edition is only present when patching is in progress 
    • Changes do no affect the running Application
    • Always the direct child of the Run Edition.
  • Old Edition(s)
    • There maybe zero or more Old Editions
    • When the Patch Edition is promoted to production the previous Run Edition is now regarded as an Old Edition
    • Only retained until a full cleanup operation is run 

File System
EBS 12.2 is installed with 3 file systems,All 3 file system forms Single E-Business Suite Instance and connect to a single database.
  • FS-1 (Production file system),Used by the current users of the system
  • FS-2 (Copy of Production file system), Where Actual Patching is done
  • FS-NE (Non Editioned file system) ,Stores data that is stored on the file system

  • In Release 12.2, all patching operations are carried out while the applications are in use and users are online.
  • Patching is performed using the new adop (AD Online Patching) utility.
  • A short period of downtime is required, but this amounts to little more than a restart of the services: the time the applications are unavailable is measured in minutes rather than hours, and this can be specified to be at the most convenient time.
The two files systems are rotated between Run and Patch during every patch cycle


  • Run Edition
    • The edition currently in use by the running application ,Used by Online Users
    • Never changed by a Patch



  • Patch Edition
    • The edition currently in use by the patching tool adop (AD Online Patching) utility.
    • This edition is only present when patching is in progress 
    • Changes do no affect the running Application 
    • Currently being patched
      or
      Waiting for the next patch cycle
  The Online Patching cycle consists of the following phases:
  1. Prepare a virtual copy (patch edition) of the running application (run edition).
  2. Apply patches to the patch edition of the application.
  3. Finalize the system in readiness for the cutover phase.
  4. Cutover to the patch edition and make it the new run edition.
  5. Cleanup obsolete definitions or data to recover space.
This introduces the concept of a patching cycle that consists of several phases, in contrast to the model used in previous releases. These phases are denoted prepare, apply, finalize, cutover, and cleanup.


To support Online Patching Cycle phases, ADOP replaces ADPATCH utility to apply Application patches. In below diagram you can see how a patch is applied.
 

Prepare
  • Patch Edition & Run Edition of the file systems are synchronized
  • All files on the Patch Edition are an exact copy of the files on the Run Edition
  • Patch Edition is created in the database
  • All code objects in the Patch Edition begin as pointers to code objects in the Run Edition
  • Storage objects such as tables are not copied

Apply
  • Patches are applied to the copy (Patch Edition)
  • Users are connected to the Application and can perform their work unaffected by the patch
  • The running application is unaffected by these changes

Finalize
  • Patches are applied to the copy (Patch Edition)
  • Users are connected to the Application and can perform their work unaffected by the patch
  • The running application is unaffected by these changes

Cutover
  • During cutover a brief downtime is taken
  • Middle-tier processes stopped
  • File system roles swapped, where in Patched (FS-2) promoted to Run and FS-1 available for next patching cycle
  • In Database Patch Edition promoted to Run Edition
  • Middle-tier processes restarted

Cleanup
  • Cleanup occurs after users have been brought back online to the newly patched Application
  • In Database Code objects patched in the latest patching cycle are deleted from Old Editions.
  • In File System it does not perform any task, except marking Pre-Patch File System ready for the next Patching Cycle. 
Apart from the above Five phases we have hidden phase, Abort some thing slimier to adworker hidden option ,The Online Patching Cycle can be aborted at any time prior to Cutover.
 

Sunday, April 17, 2016

Concurrent Processing Analyzer


The Concurrent Processing Analyzer is a Self-Service Health-Check script which reviews the overall Concurrent Processing Footprint, analyzes the current configurations and settings for the environment providing feedback and recommendations on Best Practices.

NOTE: This is a non-invasive script - (Query only) it just reports on it. The Analyzer identifies known issues and provides solutions and recommended actions to be performed for the specific instance it was run on and can be run at any time. For production instances, always apply any changes to a recent clone to ensure an expected outcome.

Benefits
Immediate analysis and output of Concurrent Processing data from a particular environment
Identifies Concurrent Processing system setup and configurations
Provides recommended actions and best practices
Runs as a standalone or Concurrent Request

E-Business Applications Concurrent Request Analysis
  • Long Running Reports During Business Hours 
  • Elapsed Time History of Concurrent Requests 
  • Requests Currently Running on a System 
  • FND_CONCURRENT_REQUESTS Totals 
  • Running Requests 
  • Total Pending Requests by Status Code 
  • Count of Pending Regularly Scheduled Requests 
  • Count of Pending Non Regularly Scheduled Requests 
  • Count of Pending Requests on Hold 
  • Count of Pending Requests Not on Hold 
  • Listing of Scheduled Requests 
  • Listing of Pending Requests on Hold 
  • Listing of Scheduled Requests 
  • Volume of Daily Concurrent Requests for Last Month 
  • Identify/Resolve the "Pending/Standby" Issue, if Caused by Run Alone Flag 
  • Tablespace Statistics for the FND_CONCURRENT Tables 
  • Additional Tablespace Statistics for the FND_CONCURRENT Tables 
E-Business Applications Concurrent Manager Analysis
  • Concurrent Managers Active/Enabled and Workshifts 
  • Active Managers for Applications not Installed/Used 
  • Total Target Processes for Request Managers Excluding Off-Hours 
  • Request Managers with Incorrect Cache Size 
  • Concurrent Manager Request Summary by Manager 
  • Check Manager Queues for Pending Requests 
  • Check the Configuration of OPP 
This script can be used from 11.x.

Run the Analyzer via Sql*Plus

NOTE : The Concurrent Processing Analyzer Report (CP_Analyzer_<host>.<domain>_<SID>_<date>.html) location is specified at the completion of the analyzer execution, when running via Sql*Plus

Log into SQL*Plus as the APPS user, and run the script. Example:
$ sqlplus apps/ @cp_analyzer.sql


SQL*Plus: Release 11.2.0.3.0 - Production on Mon Apr 17 23:03:13 2016
Copyright (c) 1982, 2005, Oracle. All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

Output Files are located on Host : .
Output file : 
    /usr/tmp/CP_Analyzer_.__.html
Log file: 
    /usr/tmp/CP_Analyzer_.__.log


PL/SQL procedure successfully completed.


Complete Information can be obtained from Doc ID 1411723.1 EBS Concurrent Processing (CP) Analyzer



Friday, April 8, 2016

Orale Home Space Issues Because OPatch Backups


Often we all face issues with the Oracle Homes getting filled, and most likely we will go and remove the .patch storage, But we end up facing challeneges when ever next time we try applying new patches.
Oracle Recommends safe way how we can clean up the .patch storage in safe and Easy way.

oracle:ORCL>opatch util cleanup -help

Oracle Interim Patch Installer version 12.1.0.1.6

Copyright (c) 2016, Oracle Corporation.  All rights reserved.


DESCRIPTION

     This utility cleans up 'restore.sh,make.txt' files and 'scratch,backup'

     directories of the.patch_storage directory of Oracle Home.If -ps option is used,

     then, it cleans the above specified areas only for that patch, else for all

     patches under ORACLE_HOME/.patch_storage. You will be still able to

     rollback patches after this cleanup.

SYNTAX

opatch util cleanup  [-invPtrLoc <Path to oraInst.loc> ]

                     [-jre <LOC> ] [-oh <ORACLE_HOME> ]

                     [-silent] [-report]

                     [-ps <patch ID with time stamp>, this will

                       be located under ORACLE_HOME/.patch_storage/]



OPTIONS

       -invPtrLoc

              Used to locate the oraInst.loc file. Needed when the

              installation used the -invPtrLoc flag. This should be

              the path to the oraInst.loc file.



       -jre

              This option tells OPatch to use JRE (java) from the

              specified location instead of the default location

              under Oracle Home. Both -jdk and -jre options cannot

              be specified together. OPatch will display error in

              that case.



       -oh

              The oracle home to work on. This takes precedence over

              the environment variable ORACLE_HOME.



       -ps

              This option is used to specify the Patch ID with timestamp.

              This Patch ID with timestamp should be the same as in

              .patch_storage directory.



              A directory by this name will be present under

              ORACLE_HOME/.patch_storage. If this directory is specified

              and is valid, then the contents specified in the description

              will be cleaned up only for this patch. Otherwise, all patch

              related directories will be acted upon by this utility.



      -silent

              In silent mode, the cleanup always takes place.



      -report

              Prints the operations without actually executing them.

OPatch succeeded.

64bit test-db ~

oracle:ORCL>

Ref: How To Avoid Disk Full Issues Because OPatch Backups Take Big Amount Of Disk Space. (Doc ID 550522.1)

Locate and Download Recommanded Patches from MOS

To locate WebLogic patches for the versions you are interested in:

  1. Log onto My Oracle Support.
  2. Click on the "Patches & Updates" tab.
  3. Click on "Product or Family (Advanced Search)."
  4. For the "Product is" choose Oracle WebLogic Server
  5. For the "Release is" choose the WebLogic Server releases you want to search on.
  6. Choose "Platform" or (Select the default which is "Select up to 5" for any platforms).
  7. Hit Search.




Complete Information can be located in MOS NOTE:

How to Locate and Download Patches for WebLogic Server Using My Oracle Support (Doc ID 1302053.1)

To locate WebLogic Advised patches for the versions you are interested in:

  1. Log onto My Oracle Support.
  2. Click on the "Patches & Updates" tab.
  3. Click on "Recommended Patch Advisor."
  4. For the "Product is" choose Oracle WebLogic Server
  5. For the "Release is" choose the WebLogic Server releases you want to search on.
  6. Choose "Platform" or (Select the default which is "Select up to 5" for any platforms).
  7. Hit Search.