Patching: ADOP finalize phase

By -

What is the ADOP Finalize Phase?

After applying the patches in the patch edition, it will create lots of invalid objects. The finalize phase will compile the invalid objects, and it will prepare the environment for the cutover phase.

The finalize phase is the optional phase in the patching cycle. After applying the patch, if we missed it, run Finalize and directorally run the cutover. The cutover phase will check if the if the finalize phase is completed or not. If not completed, the finalize phase cutover phase will start.


Key Actions during the Finalize Phase

  1. Mode Selection: ADOP offers two modes for finalization - "quick" and "full":

    • Quick Mode: This mode prioritizes speed by skipping non-essential tasks, making it ideal for scenarios where minimal downtime is critical.
    • Full Mode: In contrast, full mode executes additional actions such as gathering statistics to the DML statment and enhance system performance after the patch is applied. This mode is beneficial for maintaining optimal performance in the long run, especially after major Patches.

Step-by-Step Execution

1.Checking for Pending Sessions

To ensure a smooth transition, the system checks for any pending hotpatch or cleanup sessions. This is a vital step to avoid conflicts and ensure that all updates are applied correctly.

  • Pending Hotpatch Session: Verifying if there are any ongoing hotpatch sessions that need to be completed.
  • Pending Cleanup Session: Ensuring that any cleanup tasks from previous phases are finished.

2. Continuing with Existing Session

If an existing session is detected, the system continues with it, as indicated by the session ID.

  • Session ID: 22: The system identifies and continues with the ongoing session.

3. Verifying Data Dictionary

The system verifies the data dictionary to ensure that all database objects are correctly defined and consistent.

4. Running Finalize Phase Database Actions

This step involves executing specific database actions required to finalize the deployment.

  • Log: @ADZDSHOWLOG.sql: The system runs the log script to capture all actions taken during this phase.

5. Finalize System Actions

Executing the FINALIZE actions is critical to ensure that all components are correctly configured and ready for production.

  • Compiling Invalid Objects: The system compiles any invalid objects to ensure they are functional.
  • Generating Log Report: A comprehensive log report (adzdshowlog.out) is generated to document all actions taken during the finalize phase.

6. Successful Completion

The finalize phase concludes successfully.

Comments

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