Applications

Expand all | Collapse all

upgrading 12.1.3 12c database to 19c

  • 1.  upgrading 12.1.3 12c database to 19c

    Posted 08-24-2020 12:04
    Hey everyone.  Just looking for a little feedback on this process as mutlitenant is still new to me.

    Following Oracle E-Business Suite Release 12.1 with Oracle Database 19c (Doc ID 2580629.1) and I've been able to upgrade a test environment but just wondering about a couple of things.

    1. Supported 19c level
    I haven't looked to see if Doc ID 2580629.1 has been updated since I started but I start with 19.3 and then at the end patch to 19.5.  Can I go with the latest as I noticed one person suggested in another post.

    2. CDB sizing
    Would I just size it the same as my current EBS instance with respect to SGA etc?

    3.  Database name when connecting from app tier
    When I connect from the app tier and do a select
    name from v$database it returns the CDB name.  Is that right?  If so it might throw the apps support staff so just wanted to confirm that is the expected result.

    4. Stopping and Starting

    addbctl.sh seems to operate a little differently in 19c than previous setup with 12c as in it just shuts down the PDB so I need to modify my stop and start scripts for this environment.  Correct?

    That's it for now I think just wanted to get this out there as hoping to get going here sooner than later.

    Also I see on James post a few people shared that there were some small issues, anything anybody wants to share as things to look out for?




    ------------------------------
    Mark Schlechte
    DBA
    City of Regina
    Regina SK
    ------------------------------


  • 2.  RE: upgrading 12.1.3 12c database to 19c

    Posted 08-24-2020 12:36
    1. We upgraded to 19.7 because we did our first database in May when 19.7 was available.
    2. We had to increase our shared pool and pga size
    3. you can do a select ora_database_name from dual and that will return the pdb name.





  • 3.  RE: upgrading 12.1.3 12c database to 19c

    Posted 08-25-2020 10:21
    Thanks for the reply Jeff,

    I'll try the query for pdb name you provided.
    Just a follow up question on the 19c version.  To get to 19.7 did you still start with 19.3 and then patch to 19.7 at the end versus 19.5?

    ------------------------------
    Mark Schlechte
    DBA
    City of Regina
    Regina SK
    ------------------------------



  • 4.  RE: upgrading 12.1.3 12c database to 19c

    Posted 08-26-2020 08:10
    1. Supported 19c level
    Yes, we did follow the same path of 19.3 as per the doc and patched to 19.7.
    2.CDB sizing
    The doc(s) specifies the sizing for initial install and one of the steps is to resize it from the upgraded non-cdb and applies it to the CDB before converting the non-CDB as PDB.
    3.I didn't see such a concern about the db name. You may try 'show con_name;' that tells you which container you are connected to.
    4. Starting and stopping
    Ours is a distributed appstier and dbtier hosted on different physical machines. So no such issues

    Hope this helps. Good luck

    ------------------------------
    Sridhar Kaza
    DBA
    Bob Evans Farms
    New Albany OH
    (614) 492-7604
    ------------------------------



  • 5.  RE: upgrading 12.1.3 12c database to 19c

    OATUG Star Partner
    Posted 08-27-2020 02:32
    Hi Mark

    You've already got replies to most of the questions
    Regarding 4. I had the same issue with my automated start/stop scripts as I wanted the whole DB isntance to be shut down, not just PDB.
    So I modified addbctl.sh to adcdbctl.sh
    Hope this helps

    Regards,
    Alex

    ------------------------------
    Aliaksandr Paulik
    Oracle DBA
    Enginatics
    (+41) 445 528765
    ------------------------------



  • 6.  RE: upgrading 12.1.3 12c database to 19c

    Posted 08-31-2020 11:36
    Edited by Mark Schlechte 08-31-2020 12:05
    Thanks for all the replies everyone.
    I did just complete another upgrade to confirm my steps and see what my results were.
    Alex - 4. yes my case also so thanks for replying as it is good to know I'm not alone there.
    Jeff - 3.  Select name from v$database; still returns CDB but select ora_database_name from dual; does return PDB so hopefully something we can live with.
    Sridhar - 1. Thanks for confirming the process and I guess my follow up task will be to patch to 19.8 now (as it appears to be supported) instead of 19.5.  I'll review CDB sizing also.

    ------------------------------
    Mark Schlechte
    DBA
    City of Regina
    Regina SK
    ------------------------------



  • 7.  RE: upgrading 12.1.3 12c database to 19c

    Posted 09-04-2020 18:30
    Before I let this thread die I was just wondering how the rapid cloning process is affected by this change?  I am on premise with a db tier and an app tier and I use rman to clone the database along with a few additional steps and then clone the app tier using rsync.  So how does the database cloning change?  Full disclosure I haven't researched it yet so my apologies for just throwing this out there and maybe there is a Doc ID on this.

    ------------------------------
    Mark Schlechte
    DBA
    City of Regina
    Regina SK
    ------------------------------



  • 8.  RE: upgrading 12.1.3 12c database to 19c

    Posted 09-11-2020 15:39

    You may want to consider this option:

     

    https://blogs.oracle.com/ebsandoraclecloud/oracle-e-business-suite-cloud-manager-overview

     

    --

     






  • 9.  RE: upgrading 12.1.3 12c database to 19c

    Posted 09-14-2020 10:51
    I think this is what I was looking for.
    Cloning Oracle E-Business Suite Release 12.1 with Multitenant Database using Rapid Clone (Doc ID 2560690.1)

    ------------------------------
    Mark Schlechte
    DBA
    City of Regina
    Regina SK
    ------------------------------



  • 10.  RE: upgrading 12.1.3 12c database to 19c

    Posted 09-14-2020 15:36
    Tired of me yet? lol.  Last question I promise.  Did anyone change their $ORACLE_HOME as part of this change?
    I mean EBS is always different than all our other oracle databases with the 'tech_st' reference and a different naming convention so the non EBS DBA's always complain about the different standard.  I just went with the same naming convention for my initial test but now I'm wondering if at a CDB level if I need to follow that same convention or if I would be creating myself a world of hurt if I try and change it?
    Is that clear without giving an example (which I don't like to do for security reasons).

    ------------------------------
    Mark Schlechte
    DBA
    City of Regina
    Regina SK
    ------------------------------



  • 11.  RE: upgrading 12.1.3 12c database to 19c

    Posted 09-15-2020 08:29

    Mark,

     

    You might also want to take a look at:

     

    Using Oracle 19c RAC Multitenant (Single PDB) with Oracle E-Business Suite Release 12.1 (Doc ID 2530680.1)

    Interoperability Notes: Oracle E-Business Suite Release 12.1 with Oracle Database 19c (Doc ID 2580629.1)

     

    I used both of these to migrate my EBS database from 11.2.0.4 to 19c.  However, I did not use rapid clone, I did a full export and full import between two Oracle cloud db systems.

     

     

    Thanks,

     

    Joe Thomas

    Director of Information Technology | Sinclair & Rush, Inc. | www.sinclair-rush.com

    T 636-282-6850 | 123 Manufacturers Dr, Arnold, MO 63010

    jthomas@sinclair-rush.com

     

    This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any review, retransmission, dissemination, or other uses of this information by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete the original message and all copies from your computer.

    WARNING: Although Sinclair & Rush has taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the use of this email or attachments.