During an R12.2 Upgrade Script Asobomci.sql is Missed By The Upgrade Driver
(Doc ID 2147469.1)
Last updated on JUNE 15, 2017
Applies to:Oracle Applications DBA - Version 12.2.2 to 12.2.5 [Release 12.2Cloud to 12.2]
Information in this document applies to any platform.
During an R12 upgrade, the script asobomci.sql is not executed by the upgrade driver because the version of the file is the same as the version of the release you upgraded from.
This can be determined by looking at the header of the file in question for its checkfile information. This information is also available in the patch / upgrade driver file.
<code>REM $Header: asobomci.sql 120.2 2006/08/04 21:33:29 skulkarn noship $
REM dbdrv: sql ~PROD ~PATH ~FILE none none none sqlplus_parallel \\ REM dbdrv: &phase=last+1 checkfile(115.0=120.2):~PROD:~PATH:~FILE</code>
So if you are upgrading and currently have version 115.0 of the script installed in the database, adpatch will skip / checkfile the script because it is already at the proper level.
The information of what scripts in the upgrade driver were skipped, due to the files being equivalent or at a higher version, can be reviewed in the adpatch logfile with the extension .lgi
When running the driver for the first time the script does not run because it is same version, but once the concurrent managers started the mandatory concurrent requests were not submitted (due to a custom trigger).
After running the driver a second time using options=nocheckfile,forceapply to get the concurrent requests submitted, the script asobomci.sql gets run which was not executed in the first run.
The document will cover why the script ran and whether it is the intended functionality.
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