EBS 12.0.6 to 12.2.7 Upgrade confusions

Thanks Vishnu,

We have tried that but we encounter error. Four of failed workers which when search in metalink, there is no hits and even the object being referred to does not exist (even in 11i, 12.0, 12.1, 12.2)

I want to follow the same path as we upgaded last year which have done successfully.

Please help how to follow the old references.

I already raised SR to support but to no avail. They are pointing to another new patch sets, which make the upgrade docs moving target at complicated

Kind regards,

Hi Vishnu,

I got this worker01 error below always,

Please help how to resolve this error.

sqlplus -s APPS/***** @/mnt/applmgr/PPAPROD/fs1/EBSapps/appl/ad/12.0.0/patch/115/sql/adsqlwrapper.sql '/mnt/applmgr/PPAPROD/fs1/EBSapps/appl/ego/12.0.0/patch/115/sql/EGOSILDU.sql &un_ego'

Connected.

PL/SQL procedure successfully completed.

DECLARE

*

ERROR at line 1:

ORA-02149: Specified partition does not exist

ORA-06512: at line 408

========

sqlplus -s APPS/***** @/mnt/applmgr/PPAPROD/fs1/EBSapps/appl/ad/12.0.0/patch/115/sql/adsqlwrapper.sql '/mnt/applmgr/PPAPROD/fs1/EBSapps/appl/ad/12.0.0/patch/115/sql/adsstats.sql '

Connected.

PL/SQL procedure successfully completed.

declare

*

ERROR at line 1:

ORA-20000: ORA-20001: APPS.GL_DSC_ACRONYM is an invalid identifier Error while

executing

FND_STATS.GATHER_SCHEMA_STATISTICS package.

ORA-06512: at line 98

The breaking point is when the adworker failed with some error, and no solution is found in support notes.

So I need to rerun upgrade again using the old docs guide that is proven to run.

I am confused with lots of ADGRANTS.SQL . why do I need to run many version  adgrants? Can I not choose the latest?

Most of the time the latest has the one gets error.

Kind regards,

Thanks for all the help Vishnu, Michael, and all here,

I am now is the final stage >> Applying the patch 12.2.6

adop phase=apply apply_mode=downtime patches=21900901

I got error:

Applying patch 21900901.

    Log: /mnt/applmgr/PPAPROD/fs_ne/EBSapps/log/adop/2/20190418_002404/apply/oraapps/21900901/log/u21900901.log

AutoPatch error:

Error running SQL and EXEC commands in parallel

You should check the file

/mnt/applmgr/PPAPROD/fs_ne/EBSapps/log/adop/2/20190418_002404/apply/oraapps/21900901/log/u21900901.log

for errors.

    [UNEXPECTED]Error occurred executing "adpatch  workers=64   options=hotpatch     console=no interactive=no  defaultsfile=/mnt/applmgr/PPAPROD/fs1/EBSapps/appl/admin/PPAPROD/adalldefaults.txt patchtop=/mnt/UPGRADE_PATCH_APP/21900901 driver=u21900901.drv logfile=u21900901.log"

    [UNEXPECTED]Refer to the log files for more information.

    [UNEXPECTED]Apply phase has failed.

    [UNEXPECTED]Unable to find appltop_id for host oraapps in database

    [UNEXPECTED]Unable to find appltop_id for host oraapps in database

*******FATAL ERROR*******

PROGRAM : (/mnt/applmgr/PPAPROD/fs1/EBSapps/appl/ad/12.0.0/bin/adzdoptl.pl)

TIME    : Thu Apr 18 01:15:41 2019

FUNCTION: ADOP::CommonUtil::getAppltopId [ Level 1 ]

ERRORMSG: Unable to find appltop_id for host oraapps in database

I found this solution in google: O R A C L E Database & Applications : ADOP Failes with "Unable to find appltop_id for the host from database"

[ERROR]: Either the value of the context variables_shared_file_system in the run file system is not consistent between the file system and the database or the APPL_TOP name across nodes is not set correctly.

Solution:

This made me think about APPL_TOP Name again. I reviewed my context files on both the application tiers (Primary & Secondary) and found that the context variable s_atName is different on both the nodes.

For a shared Applicaiton Tier APPL_TOP name should be same across all the applicaiton tier nodes.
1) Modified context variable s_atName on Secondary node to Master Application Nodename .
2) Executed autoconfig and bounced services.

3) Then adop is went successfully.

But I do not know if we have the same issue or if it is applicable to our issue?

Please help....

Thanks!

Hi ALL,

I checked the context file of our appsTeir:

and it is:

<APPL_TOP_NAME oa_var="s_atName">AT_oraapps</APPL_TOP_NAME>

But in our working CRP instance which we upgraded last tyear, is it also similar:

<APPL_TOP_NAME oa_var="s_atName">AT_oraapps2</APPL_TOP_NAME>

Please help...

Hi ALL,

I run cleanup nodes and run autoconfig on the db and appstier.

But I got error on the db tier.

oracle.apps.ad.autoconfig.oam.InDbCtxFileException: Error executng BEGIN fnd_gsm_util.upload_context_file(:1,:2,:3,:4,:5); END;: 1; Oracle error -1400: ORA-01400: cannot insert NULL into ("APPLSYS"."FND_OAM_CONTEXT_FILES"."NODE_NAME") has been detected in FND_GSM_UTIL.upload_context_file.

I run node clean up and I restarted the patch, but I got another error

Kind regards,

Thanks Benny,

The content is below:

ATTENTION: All workers either have failed or are waiting:

           FAILED: file apssu.odf    on worker  2.

ATTENTION: Please fix the above failed worker(s) so the manager can continue.

Current time is: Thu Apr 18 2019 09:34:09

Telling workers to quit...

13 workers have quit.  Waiting for 51 more.

But worker2 has no ERROR contents?

AD Worker warning:

Product Data File

/mnt/applmgr/PPAPROD/fs1/EBSapps/appl/admin/cusprod.txt

does not exist for product "cus".

This product is registered in the database but the

above file does not exist in APPL_TOP.  The product

will be ignored without error.

Currently, the following language is installed:

Code   Language                                Status

----   --------------------------------------- ---------

US     American English                        Base

Your base language will be AMERICAN.

Ready to run jobs.

The job currently assigned to this worker has status FAILED.

Fix the problem then use adctrl to change the status to 'Fixed, Restart'.

Manager says to quit.

Time when worker quit: Thu Apr 18 2019 09:34:09

AD Worker is complete.

I got some info below:

Thanks.

I will try ko run the fix sql

SQL> @ADFIXUSER.sql

begin

*

ERROR at line 1:

ORA-00060: deadlock detected while waiting for resource

ORA-06512: at "SYS.AD_ZD_SYS", line 638

ORA-06512: at line 2

Please help...

Hi ALL,

I already run the fixuser, but the patch is always failing on worker 2 , but with no detail what is the error

Reading jobs from FND_INSTALL_PROCESSES table ...

Evaluating symbolic arguments for worker 2

    Fixed: file apssu.odf    on worker  2 for product ap  username AP.

Time is: Thu Apr 18 2019 11:27:44

Done reading jobs from FND_INSTALL_PROCESSES table ...

Telling workers to read 'todo' restart file.

Done.

Restarted: file apssu.odf    on worker  2 for product ap  username AP.

Time is: Thu Apr 18 2019 11:27:44

   FAILED: file apssu.odf    on worker  2 for product ap  username AP.

Time is: Thu Apr 18 2019 11:27:47

ATTENTION: All workers either have failed or are waiting:

           FAILED: file apssu.odf    on worker  2.

ATTENTION: Please fix the above failed worker(s) so the manager can continue.

Current time is: Thu Apr 18 2019 11:27:47

Telling workers to quit...

Please help...

Hi ALL,

Where can I get the detailed error message of adworkers please....

Thanks a lot.