Let's be honest, the highest confirmed version is 18. But 220.127.116.11 is 19.
Normally it should fit, but BMC does not give an unqualified confirmation. As long as BMC doesn't think your problem is related to the higher DB version, you have support. Otherwise you are on your own and have to prove to BMC that it has nothing to do with the higher version.
Before my hint is called unfair again: I know that BMC is trying to ignore the dB version. However, in the worst case it can happen and I don't want to be responsible for the affected productive system
Ultimately it is you who decides whether or not you can bear this minimal risk.
Yes, we support 18, but also recommends any higher version of DB is supported as long as Oracle takes care of backward compatible. This is fair expectation with any product to support existing functionality.in higher version.
Absolutely, but why doesn't BMC manage to regularly and officially support the current versions.
That's how I understood you, to give your customers a real security.
I will raise it with respective stake holders within BMC.
I am sure BMC will always keep upgrading to latest versions depends on priority. Recently we BMC started supporting new OS, like RHEL 8 and Suse15 enterprises in previous release 2008.
As per our discussion within BMC, Oracle 19 is in our list of database to certify.
Correction - Recently BMC started supporting new OS, like RHEL 8 and Suse15 enterprises in previous release 2008 2002.