Upgrade EBS R12.1.3 to R12.2.10

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Upgrade EBS R12.1.3 to R12.2.10

satish

Dear Erman,

We are upgrading R12.1.3 to R12.2

DB 19.17
Application R12.1.3

Step 14: Apply the consolidated upgrade patch and run the 12.2.0 Upgrade (required) from https://docs.oracle.com/cd/E26401_01/doc.122/e73540/T660854T660862.htm#8333937



Merge the patch drivers in $APPL_TOP/admin/$TWO_TASK/preinstall directory with the 12.2.0 upgrade driver $AU_TOP/patch/115/driver/u10124646.drv

Done:

Change directory to <AU_TOP>/patch/115/driver

$ cd $AU_TOP/patch/115/driver
$ admrgpch -d . -preinstall -master u10124646.drv
Note: The default merged driver by name u_merged.drv is then created in the destination directory that is specified.

In progress:
========

We are applying the patch with command $ adpatch options=nocopyportion,nogenerateportion

ATTENTION: All workers either have failed or are waiting:

           FAILED: file aroir12ars.ldt on worker  1.
           FAILED: file asnresp.ldt  on worker  2.
           FAILED: file bimcursp.ldt on worker  3.
           FAILED: file bimrsphp.ldt on worker  4.
           FAILED: file wdfresp.ldt  on worker  5.
           FAILED: file flmresp.ldt  on worker  6.
           FAILED: file csresp.ldt   on worker  7.
           FAILED: file arg12ars.ldt on worker  8.

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


All workers have same error

Uploading from staging tables
  Error parsing the generated plsql wrapper statement ORA-06550: line 812, column 9:
PLS-00306: wrong number or types of arguments in call to 'LOAD_ROW'


Can you please guide

Thanks,
Satish
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade EBS R12.1.3 to R12.2.10

ErmanArslansOracleBlog
Administrator
It seems there is mismatch between There is a mismatch between FND_CONCURRENT_PROGRAMS_PKG.LOAD_ROW (AFCPMCPB.pls) and your lct(s)

Checking it with "R12.1 and 12.2 Oracle E-Business Suite Preinstall Patches Report (Doc ID 1448102.2)" may give you some clues on what is missing.. It is obvious that your target upgrade environment is missing something.
The following document which recommends you a patch might also help -> REL 12.2 - Patch fails with PLS-00306: wrong number or types of arguments in call to 'LOAD_ROW' (Doc ID 1933052.1) -- just check the file versions documented there and according to the situation you may consider applying it before the upgrade driver..


Reply | Threaded
Open this post in threaded view
|

Re: Upgrade EBS R12.1.3 to R12.2.10

satish
Hi Erman,
We have verified the note id, patches are not applied but the file versions are matching with with file versions from note ID.

R12.1.3:
--------

[applcrp@sssterpdev1 sql]$ adident Header AFCPMCPB.pls
AFCPMCPB.pls:
$Header AFCPMCPB.pls 120.3.12010000.3 2014/01/17 21:21:34 ckclark ship $



SQL> SELECT t1.name , t1.text
FROM dba_source t1
WHERE t1.NAME IN
(
'FND_CONCURRENT_PROGRAMS_PKG'
)
AND t1.line = 2
order by t1.name;  2    3    4    5    6    7    8

NAME
--------------------------------------------------------------------------------
TEXT
--------------------------------------------------------------------------------
FND_CONCURRENT_PROGRAMS_PKG
/* $Header: AFCPMCPS.pls 120.2.12010000.2 2014/01/17 21:41:21 ckclark ship $ */

FND_CONCURRENT_PROGRAMS_PKG
/* $Header: AFCPMCPB.pls 120.4 2009/07/22 15:24:29 tkamiya ship $ */


SQL> select bug_number from ad_bugs where bug_number=19003733;

no rows selected

SQL>  select bug_number from ad_bugs where bug_number=24849314;

no rows selected
____________________________________________________

R12.2:
------

SQL> SELECT t1.name , t1.text
  FROM dba_source t1
WHERE t1.NAME IN
  (
  'FND_CONCURRENT_PROGRAMS_PKG'
  )
  AND t1.line = 2
order by t1.name;  2    3    4    5    6    7    8

NAME
--------------------------------------------------------------------------------
TEXT
--------------------------------------------------------------------------------
FND_CONCURRENT_PROGRAMS_PKG
/* $Header: AFCPMCPS.pls 120.2.12010000.2 2014/01/17 21:41:21 ckclark ship $ */

FND_CONCURRENT_PROGRAMS_PKG
/* $Header: AFCPMCPB.pls 120.4 2009/07/22 15:24:29 tkamiya ship $ */




[applcrp@sssterpdev1 sql]$ adident Header AFCPMCPB.pls
AFCPMCPB.pls:
$Header AFCPMCPB.pls 120.4.12020000.2 2014/01/17 21:21:46 ckclark ship $



SQL> select bug_number from ad_bugs where bug_number=19003733;

no rows selected

SQL>  select bug_number from ad_bugs where bug_number=24849314;

no rows selected




Thanks,
Satish.

Reply | Threaded
Open this post in threaded view
|

Re: Upgrade EBS R12.1.3 to R12.2.10

satish
Any idea,can you pls advic
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade EBS R12.1.3 to R12.2.10

satish
Dear erman,

From above outputs,do we need to apply the patch to R12.2..After laying down the file system and after applying the CUP 13(latest) for ad.

and before running the upgrade driver. Pls advice

Thanks,
Satish
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade EBS R12.1.3 to R12.2.10

satish
Dear erman,

Can u pls guide.

Thanks,
Satish
Reply | Threaded
Open this post in threaded view
|

Re: Upgrade EBS R12.1.3 to R12.2.10

ErmanArslansOracleBlog
Administrator
I was on a vacation. I couldn't answer you.
So what is current situation?

And about your question: "From above outputs, do we need to apply the patch to R12.2..After laying down the file system and after applying the CUP 13(latest) for ad and before running the upgrade driver", my answer is yes. But! this is not an expected problem, so probably you are doing something wrong during the way.

You know what.. Just after applying the CUP 13, check "FND_CONCURRENT_PROGRAMS_PKG.LOAD_ROW", if it is again in the mismatch state, then we'll decide what to do. But applying the patch after CUP seems like a good idea at the first glance and even at the second glance :)