Wrong version after upgrading to R12.2.10

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

Wrong version after upgrading to R12.2.10

satish
This post was updated on .
Dear Erman,

We have upgraded oracle apps from R12.1.3 to R12.2.10. Applied RUP10 patch -->adop phase=apply apply_mode=downtime patches=30399999,33678475 merge=yes
Note:33678475 is Updated CETS for 12.2.10 (Patch)

We have ran empty patching cycle and it completed successfully-fsclone,prepare,finalize,cutover and cleanup

We have released the instance to users.

Here comes the problem-->Front end screen shows release version as R12.2.9 and backend also shows R12.2.9, But it should show R12.2.10.

We got the note id "EBS Application version is shown incorrectly as 12.2.9 after upgrading to 12.2.10 or higher (Doc ID 2857362.1)"

It says to reapply patch without merging...We need your guidance. Since we already applied the patch and released the instance to users.

At this stage,can we shut down the services and reapply the patch in downtime mode by running below command.

adop phase=apply apply_mode=downtime patches=30399999 options=forceapply

Do we need to apply the below patches once again after applying the above patch OR not required. We need your expertise.

like 33678475,1948857:R12.FND.C and online help patch


This is test instance. We need your suggestions.


Thanks,
Satish

 





Reply | Threaded
Open this post in threaded view
|

Re: Wrong version after upgrading to R12.2.10

ErmanArslansOracleBlog
Administrator
It should have been fixed in R12.AD.C.Delta.14  (Patch 33600809).

*So why didn't you go with that?

Oracle E-Business Suite Applications DBA and Technology Stack Release Notes for R12.AD.C.Delta.14 and R12.TXK.C.Delta.14 (Doc ID 2857317.1)

*You said your users are using this system. So is it a Production instance?

*If you are going to implement that workaround, just reapply the RUP patch as the MOS note suggests. Nothing more. You re doing this only for loading the correct version info once again, so if you will going to do that, just follow the MOS note, do only what it suggest and don't do anything else.
There you are just giving forceapply as an additional argument, so you will have the checkfile bydefault there in the backend.. (checkfile is the default) **Checkfile -> Purpose: Tells adop to either skip running EXEC, SQL, and EXECTIER commands if they are recorded as already run, or to record them as having run after running them.
Default: checkfile.. (so it is the default..)
So I don't think adop will do those patching activities once again.
Reply | Threaded
Open this post in threaded view
|

Re: Wrong version after upgrading to R12.2.10

satish
Hi Erman,

This is test instance. We will take downtime and run the below command:

adop phase=apply apply_mode=downtime patches=30399999 options=forceapply

Is that fine?



Thanks
Satish