OverthinkerDave (Customer) asked a question.
I thought it was an "April fools", but it is not: Our database team is upgrading the Oracle database to 26ai on the 1:st of April.
So does anyone out there have any "early status" on how Aveksa 8.0 is behaving in early versions of 26ai?
Of my knowledge (so far):
Aveksa 8.0 (on Wildfly) is using the 19.3 thin client to connect to an Oracle database.
This 19.3-version is (what I have heard)
- not the most stable one
- where some important fixes came into 19.6 and above
- where 19.20 (allegedly by a colleague of mine) is the most stable one.
- where some important fixes came into 19.6 and above
Historically all new Oracle-versions have been somewhat "backwards-compatible" as long you do not try to use new functions that "change" in the newer versions. Also it has always been good to change to a jdbc thin driver FOR that specific newer version. Which in practice for Oracle 26 would mean that Aveksa 8.0 need to change the thin driver to something called 26.x, and then run in 19.x compatible mode on that driver.
I'm sure you are aware of this, but I will point out that getting support from RSA might be challenging if you are using a non supported and non qualified version of DB
RSA Governance & Lifecycle 8.0.0 Platform Datasheet and Support Matrix Guide | RSA Community
Correct. Oracle version 19 is needed to get support from RSA today.
However RSA will not get any support from Oracle after 2029, just saying 😉
Background for the question is that our database team have decided to test 26ai on all applications in our DEV environment.
And I have a feeling our database team is not the only one wanting to cross over to the next "Long Time Support" version from Oracle.
I will get back here on how 26ai goes with this 19.3 driver (from 2019).
Where the plan after that is to test P11 "as soon as it drops" (which rumors say has support for more modern cdb/pdb databases).
@DavidBryantRSA (RSA)​ ?