Skip to main content

Adop Prepare/Abort Phase Hung While Executing AD_ZD_SEED.PREPARE.FND_PROFILE_OPTION_VALUES

Adop Prepare/Abort Phase Hung While Executing AD_ZD_SEED.PREPARE.FND_PROFILE_OPTION_VALUES


Error:

adop prepare/abort phase is hanging and not completing even after 52 hours.

From the ADZDSHOWLOG.out file we can notice the below where it is stuck while executing synchronize task: FND_PROFILE_OPTION_VALUES_DELETE.

 489121669 12:58:59 00:00:00 ad.plsql.ad_zd_seed.run_in_parallel        PROCEDURE  begin: FND_PROFILE_OPTION_VALUES_DELETE
 489121669 12:58:59 00:00:00 ad.plsql.ad_zd_seed.run_in_parallel        STATEMENT  Create Task FND_PROFILE_OPTION_VALUES_DELETE
 489121669 12:59:00 00:00:01 ad.plsql.ad_zd_seed.run_in_parallel        STATEMENT  Executing synchronize task: FND_PROFILE_OPTION_VALUES_DELETE, chunks: 5
 489121649 12:59:51 00:00:50 ad.bin.adop                                EVENT      preparing the seed tables needed for autoconfig execution.
 489121649 12:59:51 00:00:00 ad.bin.adop                                PROCEDURE  [START] Preparing autoconfig related seed data tables
 489121649 12:59:52 00:00:00 ad.bin.adop                                STATEMENT  Sourcing Patch edition environment <APPL_TOP>/APPSSBOX_curtsriebsap3.env
 489121671 12:59:52 00:00:00 ad.plsql.ad_zd_seed.prepare                PROCEDURE  begin: FND_PROFILE_OPTION_VALUES
 489122494 10:23:19 21:23:26 ad.plsql.ad_zd.set_edition                 STATEMENT  Setting current edition to V_20230430_XXXX


Even when I checked for abort the session was stuck at

BEGIN
    ad_zd_seed.abort ('APPLSYS', 'FND_PROFILE_OPTION_VALUES');
END;





Solutions:

1. Verify the value of parameter SCHEDULER_DISABLED at both CDB and PDB level using the below query:

SQL> SELECT * FROM DBA_SCHEDULER_GLOBAL_ATTRIBUTE WHERE ATTRIBUTE_NAME = 'SCHEDULER_DISABLED';

2. Set SCHEDULER_DISABLED to FALSE at CDB level. Ensure that it is set to false at both CDB and PDB.

SQL> exec dbms_scheduler.set_scheduler_attribute('SCHEDULER_DISABLED','FALSE');

3. The prepare phase will progress after making the changes.
If the session has already been cancelled or if it does not progress, then bounce the database and retry prepare phase again.


OR


This was my case when the above solution was already place but the issues was the below.

the parameter "job_queue_processes" is not same for both CDB and PDB.

When checked for CDB the job_queue_processes was 0

And for PDB he job_queue_processes was 2


PDB

NAME TYPE VALUE
------------------------------------ ----------- --------------------
job_queue_processes integer 2

CDB

NAME TYPE VALUE
------------------------------------ ----------- --------------------
job_queue_processes integer 0


I changed the value as same for CDB and PDB level

Alter system set job_queue_processes=10;

Please restart your database once.


I did following afterwards

1. Run adop phase=abort

2. Run adop phase=cleanup

3. Run adop phase=fs_clone

4. Run adop phase=prepare.




If you like please follow and comment

Comments

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...