adop patching

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

adop patching

Syed Tanweer Ali
Hi Erman,

Hope you are doing good.

Can we skip invalids compilation during adop apply phase.we have used adop phase=apply patches=26576846 options=nocompiledb but still from logs we could see the worker is running adutlrcmp.sql.please suggest

Thank you
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: adop patching

ErmanArslansOracleBlog
Administrator
interesting. Do you see something like "Calling: adpatch options=nocompiledb" in adop logs?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: adop patching

ErmanArslansOracleBlog
Administrator
Bytheway, please open your issues in the related category.
This should be in EBS 12.2 category.
I m moving this issue to EBS 12.2 category, follow it from there.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: adop patching

Syed Tanweer Ali
Dear Erman,

I could not find the "Calling: adpatch options=nocompiledb " in apply logs. Please find the log details below.

from u26576846.log

************* Start of AutoPatch session *************
AutoPatch version: 12.2.0
AutoPatch started at: Tue Aug 08 2017 15:24:06

APPL_TOP is set to /u02/PATCHAPPS/fs1/EBSapps/appl

Defaults Feature Enabled = YES.
Non-Interactive Mode = YES.
Num Workers = 8.
Options = "nocompiledb".
Patch Top = "/u02/PATCHAPPS/fs_ne/EBSapps/patch/26576846".
Patch Driver File = "u26576846.drv".



from adwork001.log


Start time for file is: Tue Aug 08 2017 15:30:35

sqlplus -s APPS/***** @/u02/PATCHAPPS/fs1/EBSapps/appl/ad/12.0.0/patch/115/sql/adsqlwrapper.sql '/u02/PATCHAPPS/fs1/EBSapps/appl/ad/12.0.0/sql/adutlrcmp.sql '
Connected.

PL/SQL procedure successfully completed.

Session Information:

INSTANCE_NAME    SCHEMA_NAME     EDITION_NAME    SYSDATE
---------------- --------------- --------------- ----------------
PATCHDB          APPS            V_20170808_1449 2017-08-08 15:30


Invalid Objects per Owner (before compile):

OWNER                              ACTUAL       STUB      TOTAL
------------------------------ ---------- ---------- ----------
APPS                                    7        107        114


Compiling Objects...

PL/SQL procedure successfully completed.

Elapsed: 00:36:35.48

Invalid Objects per Owner (after compile):

OWNER                              ACTUAL       STUB      TOTAL
------------------------------ ---------- ---------- ----------
APPS                                    0          1          1


Commit complete.

Can you suggest how to skip the invalid objects compilation in adop apply phase.

Thanks
Tanweer
sri
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: adop patching

sri
Dear erman,

Is this command correct to skip invalids?

adop phase=apply patches=26576846 options=nocompiledb
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: adop patching

ErmanArslansOracleBlog
Administrator
it is a little weird.
nocompiledb can be used to defer "Compile APPS schema"...
this compile thing may be patch specific.. I mean, it may be already embedded to your patch.. In to the drv file maybe or into a sql that your patch uses....
Anyways, which object is the cause of this long running compile?

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: adop patching

ErmanArslansOracleBlog
Administrator
Bytheway,

Did you run adop prepare command before this?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: adop patching

Syed Tanweer Ali
Dear Erman,

We have applied the patch using Patch cycle. We ran Adop Prepare phase.

Thanks
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: adop patching

ErmanArslansOracleBlog
Administrator
Then, this compile thing may be patch specific.. I mean, it may be already embedded to your patch.. In to the drv file maybe or into a sql that your patch uses....
Anyways, which object is the cause of this long running compile?
Loading...