ADOP PHASES IN R12.2 / R12.2 PATCHING

ADOP PHASES IN R12.2  / R12.2 PATCHING :
===================================

 Prepare phase
==============
Gets patching filesystem ready to apply a patch.
Checks that ETCC has been run against the database Oracle Home and that all required 
patches are applied.
synchronize filesystems - If any configuration changes have been made, this will 
cause the prepare phase 
to initiate a fs_clone of the current run filesystem to the patch filesystem.
run autoconfig if necessary.
check tablespaces for sufficient free space before starting.
check APPS_FNDFS listener to make sure concurrent requests will launch.
launch concurrent request - "Online Patching In Progress" (ADZDPATCH).
synchronize snapshots between run and patch filesystems.

 Apply:($ adop phase=apply analytics=yes) 
====== 
merging patches - ADOP determines correct options automatically.
patch repository location.
ADOP log directories.
how to run ADOP unattended by passing the required passwords into the ADOP command.
how to use adctrl with ADOP.
viewing the ADOP patch log file while ADOP is running.
FINALIZE PHASE:(If finalize_mode=full, 
compute statistics for key data dictionary tables for improved performance.)
===============
compiles invalids objects in the patch edition.
determines DDL statements to execute at cutover.
validates that the system is ready for a cutover.
gathers statistics for performance.

 CUTOVER PHASE
================
once started, the abort phase can not be issued.
runs the finalize phase if it was missed.
cancels concurrent request - "Online Patching In Progress" (ADZDPATCH).
shuts down the internal concurrent manager.
stops any processes that may have been started on the patch filesystem.
stops the RUNNING applications tiers.
executes the DDL statements prepared during the finalize phase.
loads jar files into the database.
synchronizes snapshots between run and patch filesystems.
broadcasts a message to local users that a cutover is taking place and to re-source 
their working environment.
CLEANUP PHASE
==============
cleans up old editions
explains the three methods of cleanup.
QUICK cleanup performs removal of obsolete crossedition triggers and seed data.
STANDARD cleanup performs removal of obsolete crossedition triggers and seed data, 
drops (removes) 
obsolete editioned code objects (covered objects). (DEFAULT MODE)
FULL cleanup performs maximum cleanup, which drops all obsolete code and data from 
earlier editions
FS_CLONE PHASE
================
when to run fs_clone.
verifies cleanup was run and runs it if it has not.
performs the clone stage
performs the clone to patch filesystem
synchronizes snapshots between run and patch filesystems.
stops any patch filesystem processes that were started.

Comments

Post a Comment

Popular posts from this blog

Troubleshooting EBS login page issue in R12.2:

Troubleshooting EBS login page issue in R12.2: ------------------------------------------------------------------------------------------------------------------- 1. If the login page doesn't comes up then we have to focus on the varios logs present under $LOG_HOME directory. In case of EBS 12.2(as it is the latest release), 1) OHS (apache) failure If OHS is not running or not responding, one would see a message as below. If OHS is not running then there will not be any messages in any EBS log file for this request. Firefox: “The connection was reset” Steps to take Check OHS has started OK adapcctl.sh status adapcctl.sh stop adapcctl.sh start 2 OACore JVM process not available If the OACore JVM is not running or not reachable, then one will likely see the following message in the browser: Failure of server APACHE bridge: No backend server available for connection: timed out after 10 seconds or idempotent set to OFF or method not idempotent. There could be two reas...
Read more

Oracle Apps EBS R12.2 Login Flow

Image
EBS R12.2 Login Flow When a HTTP request is made for EBS, the request is received by the Oracle HTTP Server (OHS). When the configuration of OHS is for a resource that needs to be processed by Java, such as logging into EBS, the OHS configuration will redirect the request to the Web Logic Server (WLS) Java process (OACore in this case). WLS determines the J2EE application that should deal with the request, which is called "oacore". This J2EE application needs to be deployed and available for processing requests in order for the request to succeed.   The J2EE application needs to access a database and does this via a datasource which is configured within WLS. Login HTTP headers When the EBS login works OK, the browser will be redirected to various different URLs in order for the login page to be displayed.  The page flow below shows the URLs that will be called to display the login page: /OA_HTML/AppsLogin EBS Login URL /OA_HTML/AppsLocalLogin.jsp Redir...
Read more

Oracle apps dba Interview Q&A's

Oracle apps dba Interview Q&A's: =========================== What is the significance of utl_file_dir parameter in init.ora file? ===================================================================== Answer The value of this parameter is the group of directories to which u r database can write,  means u r database packages have permission to write to flat files in these directories. What is APPLPTMP environment variable? ======================================= Answer This is the temporary file location for the pl/sql temp files.  If this variable was not set then the concurrent programs may error-ed out. DIAG_PARAM ="Y" in adcmctl.sh. for CM issues oracle apps concurrent managers interview question and common information's Question:Error: ================ After submitting the concurrent program, i am getting the status as inactive and no manager and when i clicked on diagnostics button its showing a message like This request will not be pro...
Read more