Souring run edition shows patch edition

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

Souring run edition shows patch edition

Daniesh
Dear Erman,

I recently upgraded from 12.1.3 to 12.2.5. Upgradation is done.
Whenever i want start the application i also i have to start the adop prepare phase.

I ran adop phase=fs_clone.

Still the problem is same.

When i source run edition. It goes to patch edition.

. ./EBSapps.env

  E-Business Suite Environment Information
  ----------------------------------------
  RUN File System           : /erppatches/ebs/12.2.5/fs1/EBSapps/appl
  PATCH File System         : /erppatches/ebs/12.2.5/fs2/EBSapps/appl
  Non-Editioned File System : /erppatches/ebs/12.2.5/fs_ne


  DB Host: crp.manafth.local  Service/SID: MANDEV


  E-Business Suite Environment Setting
  ------------------------------------
  - Enter [R/r] for sourcing Run File System Environment file, or
  - Enter [P/p] for sourcing Patch File System Environment file, or
  - Enter anything else to exit

  Please choose the environment file you wish to source [R/P]:R

  Sourcing the RUN File System ...

[appldev@crp 12.2.5]$
[appldev@crp 12.2.5]$
[appldev@crp 12.2.5]$
[appldev@crp 12.2.5]$ sqlplus apps

SQL*Plus: Release 10.1.0.5.0 - Production on Sun Aug 27 15:11:52 2017

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

Enter password:


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> select ad_zd.get_edition_type from dual;

GET_EDITION_TYPE
--------------------------------------------------------------------------------
PATCH

Please help me on this.

Thanks and Regards,
Reply | Threaded
Open this post in threaded view
|

Re: Souring run edition shows patch edition

ErmanArslansOracleBlog
Administrator
interesting.
This file should be created properly and automatically while upgrading to 12.2.5.
But it seems it is wrong in your case.

1)What is your current release?
2)Any errors or weirdness in the 12.2.5 upgrade patch log file?

Check the errors first and send me if you find anyting.

Also, we may find a way to walk around  this. Creating and completing a complete online patching cycle maybe..
3)Is your application services working properly?
4)Do they run from the run fs?
5)are the context values in your context files properly set for your run and patch edition?
6)What steps did you taken for this upgrade?
7)Send me the EBSapps.env file. (upload it to here.)