LOL. I checked a couple of days ago when I updated my Vagrant build and
13.3 was still only certified on 18c. Looks like I've got some changes to
make.
I'm a little cautious, but my advice would be.
1) Upgrade 13.2 to 13.3 as is. Let that bed in for a while and be happy it
is working. Our upgrade went fine, but recently when we pulled down the
latest plugins (13.3.2 I think), we had a few things go funky and had to
push out the agents again. I would say getting this settled first makes
sense.
2) Apply the latest quarterlies to your existing stuff (Database, WebLogic,
Clould Control etc.). Make sure it's all bang up to date. Once again, check
it's all good before you move on.
3) Once you know 13.3 is working fine, then do the database upgrade to
whatever version you like.
We use a simple installation on a VMware VM. We did the upgrade 13.2 to
13.3 a while ago. As I said, we've recently pulled down the latest plugins.
We try to do the quarterlies every quarter anyway. I am soon to embark on
the DB upgrade. This has been delayed a little because:
1) I was waiting for 19c to be certified.
2) I will need to move it all onto a new VM, as this is installed on OL6,
and 19c is not supported on OL6, so we need a new OL7 VM to do the 19c bit.
Like I said, I am overly cautious with this as all our backups are
scheduled from Cloud Control, so it's a real pain if it is down for too
long. If you are more adventurous, go for it as a big bang. :)
Cheers
Tim...
On Tue, Jun 18, 2019 at 8:58 PM Scott Canaan <srcdco@xxxxxxx> wrote:
That’s true! Thanks for the update.
*Scott Canaan ‘88*
*Sr Database Administrator *Information & Technology Services
Finance & Administration
*Rochester Institute of Technology *o: (585) 475-7886 | f: (585) 475-7520
*srcdco@xxxxxxx <srcdco@xxxxxxx>* | c: (585) 339-8659
*CONFIDENTIALITY NOTE*: The information transmitted, including
attachments, is intended only for the person(s) or entity to which it is
addressed and may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of any
action in reliance upon this information by persons or entities other than
the intended recipient is prohibited. If you received this in error, please
contact the sender and destroy any copies of this information.
*From:* Courtney Llamas <COURTNEY.LLAMAS@xxxxxxxxxx>
*Sent:* Tuesday, June 18, 2019 3:50 PM
*To:* Scott Canaan <srcdco@xxxxxxx>
*Cc:* gogala.mladen@xxxxxxxxx; oracle-l@xxxxxxxxxxxxx
*Subject:* Re: Cloud Control Question
Work and certified are 2 different things.
It has just been certified, MOS is being updated.
On Jun 18, 2019, at 2:43 PM, Scott Canaan <srcdco@xxxxxxx> wrote:
Thanks, that was what I was thinking. I’m reading through the upgrade
documentation now. Since we have a simple install (no RAC or Data Guard),
I think we should be ok.
*Scott Canaan ‘88*
*Sr Database Administrator *Information & Technology Services
Finance & Administration
*Rochester Institute of Technology *o: (585) 475-7886 | f: (585) 475-7520
*srcdco@xxxxxxx <srcdco@xxxxxxx>* | c: (585) 339-8659
*CONFIDENTIALITY NOTE*: The information transmitted, including
attachments, is intended only for the person(s) or entity to which it is
addressed and may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of any
action in reliance upon this information by persons or entities other than
the intended recipient is prohibited. If you received this in error, please
contact the sender and destroy any copies of this information.
*From:* oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> *On
Behalf Of *Mladen Gogala
*Sent:* Tuesday, June 18, 2019 3:29 PM
*To:* oracle-l@xxxxxxxxxxxxx
*Subject:* Re: Cloud Control Question
Yes, it will work. I have seen that working at a client of mine. Oracle
19.3 belongs to Oracle 12c family of products. Whatever 12.1.0.2 could do,
Oracle 19.3 can do. However, upgrading OEM on WL side can be tricky.
On 6/18/19 12:15 PM, Scott Canaan wrote:
I am looking at upgrading our Cloud Control install from 13.2 to 13.3. At
the same time, I’d like to upgrade the repository database from 12.1.0.2 to
19. Will that work? I don’t really see why it wouldn’t, but I can’t find
anything that tells me what database versions are supported (other than
comments in the upgrade doc about parameters for 12.2.0.1 and 18).
Thank you,
*Scott Canaan ‘88*
*Sr Database Administrator *Information & Technology Services
Finance & Administration
*Rochester Institute of Technology *o: (585) 475-7886 | f: (585) 475-7520
*srcdco@xxxxxxx <srcdco@xxxxxxx>* | c: (585) 339-8659
*CONFIDENTIALITY NOTE*: The information transmitted, including
attachments, is intended only for the person(s) or entity to which it is
addressed and may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of any
action in reliance upon this information by persons or entities other than
the intended recipient is prohibited. If you received this in error, please
contact the sender and destroy any copies of this information.
