R12.2 Jl8469071b.sql Running For 27 Hours During Upgrade (Doc ID 1956325.1)

Last updated on MAY 02, 2023

Applies to:

Symptoms

On : 12.2.4 version, Latin Am. Glob. (General)

Performance issue running the upgrade.

Expect to be able to finish the upgrade.

The issue can be reproduced at will with the following steps:

1.  jl8469071b.sql is running for 27 hours during R12.2 Upgrade.

You are in the process of upgrading 11.5.10.2 system to R12.2 and currently 12.2.0 driver is running.
In that, jl8469071b.sql is running for more than 27 hours and its simply stuck on below mentioned update.
You set the parameter, for the SLA pre-upgrade program, to pick only 6 months data; However, you see the 2000 year records are being processed.


Current SQL statement:
  UPDATE XLA_AE_HEADERS XLAH SET XLAH.CREATED_BY = 2, XLAH.LAST_UP
  DATED_BY = 2 WHERE (XLAH.APPLICATION_ID, XLAH.ENTITY_ID) IN (SELECT /*+ ROWID(xte) */ XTE.APPLICATION_ID, XTE.ENTITY_ID FROM XLA_TRANSACTION_ENTITIES XTE WHERE XTE.ENTITY_CODE = 'JL_BR_AR_COLL _DOC_OCCS' AND XTE.ROWID BETWEEN :B2 AND :B1 ) AND     XLAH.CREATED_BY = -2005 AND XLAH.LAST_UPDATED_BY = -2005


2.  Workaround:
Please skip the jobs for the problematic sql files from these 4 SQLs.
Once the UAT upgrade is finished, you can manually execute the latest file versions of the skipped files.

  jl8469071a.sql patch/115/sql 120.3.12020000.2
  jl8469071b.sql patch/115/sql 120.2.12020000.2
  jl8469071c.sql patch/115/sql 120.2.12020000.2
  jl8469071d.sql patch/115/sql 120.2

The latest files have been uploaded to SR.

Now another SQL armc120recpl.sql which is running for long time which is inserting records into XLA_AE_LINES.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.