Sanity Check regarding database migration OJVM target server newer version 19c
From: Chris Taylor <christopherdtaylor1994_at_gmail.com>
Date: Tue, 11 Jul 2023 14:40:49 -0400
Message-ID: <CAP79kiSMeUyRsR2Z-Z0S8S-=_jXhr5cr+BrxN1bz2-cBaMz4xw_at_mail.gmail.com>
For some reason, our 19.17 home on SOURCE server still has the 19.14 OJVM software binaries/version.
Date: Tue, 11 Jul 2023 14:40:49 -0400
Message-ID: <CAP79kiSMeUyRsR2Z-Z0S8S-=_jXhr5cr+BrxN1bz2-cBaMz4xw_at_mail.gmail.com>
For some reason, our 19.17 home on SOURCE server still has the 19.14 OJVM software binaries/version.
Our TARGET server (ExaCS) has 19.17 with 19.17 OJVM.
If I migrate a database to this new server & 19.17 OJVM libraries, will it affect my database if my database doesn't use the JVM normally?
I'm "thinking" 19.14 OJVM database internals should be ok with 19.17 OJVM binaries *but* I seem to remember running into a problem with that in the past if there were java classes used inside the database.
I guess worse case scenario (which I'm going to test) is to patch the OJVM on the TARGET once I migrate it (active duplicate) and open it over there.
Does anyone know off the top of their head if OJVM difference are going to cause me any heartburn in this scenario?
Thanks,
Chris
--http://www.freelists.org/webpage/oracle-l Received on Tue Jul 11 2023 - 20:40:49 CEST