Patching: ADOP Prepare Phase

By -

adop phase=prepare

Understanding ADOP Prepare Parameters

Before diving into the prepare phase, let's go over the key parameters:

  1. skipsyncerror: This parameter specifies whether to ignore errors that may occur during incremental file system synchronization.

    • Options: yes or no (default: no)
    • Usage: Set to yes if you encountered errors in a previous patching cycle but decided to continue with the cutover. This will ignore apply errors during the next synchronization.

  2. sync_mode: This parameter determines the method used to synchronize the patch file system with the run file system.

    • Options: delta or patch (default: patch)
    • Usage:
      • delta: Uses the file system synchronization command specified in $AD_TOP/patch/115/etc/delta_sync_drv.txt.
      • patch: Reapplies patches applied on the run file system.

Example Command

adop phase=prepare skipsyncerror=yes sync_mode=delta


Step-by-Step Execution
1. Validating Passwords
The process begins by validating the credentials for apps, system, and WebLogic.
2. Creating the Session ID
A unique session ID is generated for this patching cycle.
  • Example: session id: 22
3. Generating the Log File
A log file is created to record the patching activities.
  • Example: /apps/oracle/fs_ne/EBSapps/log/adop/22/20200127_122704/adop.log
4. Configuration Validation
The system configuration is validated to ensure everything is ready for the prepare phase.
5. Verifying Data Dictionary
It will verify the data disctionary objects.
6. Checking System Readiness
The system undergoes various checks to confirm it is ready to proceed with the prepare phase.
7. Checking AD-TXK Code Level
The current AD-TXK code level is verified.
8. Checking for Pending Cleanup Actions
Any pending cleanup actions from previous patching cycles are identified and resolved.
9. Validating Database Readiness
The database is validated to ensure it is ready for the prepare phase.
10. Generating Tablespace Report
A report on key tablespaces is generated to provide insights into the current state of the database.
11. Submitting ADZDPATCH Concurrent Program
The ADZDPATCH concurrent program is submitted.
12. Waiting for Conflicting Requests
Any conflicting requests are waited on to complete before proceeding.
13. Preparing System
The system is prepared for the patching process.
14. Synchronizing Patch Filesystem with Run Filesystem
The synchronization of the patch filesystem with the run filesystem is executed. This can be done in two modes:
  • Incremental Synchronization Mode: Only the modifications from the patches are synchronized.
  • Full Synchronization Mode: If the previous patching cycle was aborted, the system performs a 
  • full synchronization by deleting the patch file system rm -rf command and
  • restoring the entire content from the run file system.
15. Preparing Seed Data Tables
The seed data tables are prepared.
16. Running AutoConfig
AutoConfig is run on the patch edition file system.
17. Synchronizing Snapshots
Snapshots are synchronized to ensure consistency.
18. Generating Editions Report
An editions report is generated.
19. Generating Log Report
A log report is generated for review.
20. Stopping Services
Services on the patch file system are stopped, including:
  • Admin server
  • Node manager
Completion
The prepare phase completes successfully, setting the stage for the next steps in the patching cycle.

Comments

  1. Unknown28 February 2020 at 13:02

    Easy "water hack" burns 2 lbs OVERNIGHT

    At least 160 000 women and men are utilizing a easy and secret "water hack" to drop 2lbs every night in their sleep.

    It is easy and works on everybody.

    Just follow these easy step:

    1) Go get a clear glass and fill it half full

    2) Now do this awesome hack

    you'll become 2lbs skinnier when you wake up!

    ReplyDelete

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