Upgrade from 12.1.3 to 12.2.9, AD_ZD_TABLE_APPLY.sql Script Stuck on GMF Tables
(Doc ID 2634643.1)
Last updated on SEPTEMBER 10, 2024
Applies to:
Oracle Applications DBA - Version 12.2.9 and laterOracle Process Manufacturing Financials - Version 12.2.9 and later
Information in this document applies to any platform.
Symptoms
During upgrade from EBS R12.1.3 to R12.2.9, the patch installation is stuck on AD_ZD_TABLE_APPLY.sql script.
Many DBMS_SCHEDULER sessions are being spawned and each one is performing the same update:
UPDATE /*+ rowid (tbl) */
GMF.CM_ACST_LED tbl
SET WHSE_CODE = WHSE_CODE
WHERE ROWID BETWEEN :start_id AND :end_id
There are tables being updated in this task, specifically those from the GMF schema, that have large amount of data.
Updating these tables using this query and the DBMS_SCHEDULER jobs takes an extremely long amount of time.
UPDATE /*+ rowid (tbl) */
GMF.CM_ACST_LED tbl
SET WHSE_CODE = WHSE_CODE
WHERE ROWID BETWEEN :start_id AND :end_id
AWR report shows that most of the top sql's by elapsed time are updates to GMF tables in which a column value is being set to itself, such as the above example of cm_acst_led, next one is:
update /*+ rowid (tbl) */ GMF.GMF_TRANSACTION_VALUATION tbl set PROGRAM_UPDATE_DATE=PROGRAM_UPDATE_DATE where rowid between :start_id and :end_id
etc.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |