DB Patches different for same DB home version dependent upon ODA/OAK version
We recently hit a bug, which brought to light... dependent upon the version of OAK/ODA that is being run, the patches that are included for the DB version are different, for the same DB Version. For example:
- OAK 12.1.2.11 DB Version 12.1.0.2.170418. DB created using oakcli create database...
-- this includes four interim patches: 25942196, 21794615, 25886529, 25171037
- OAK 12.2.1.4 DB Version 12.1.0.2.170418. DB created using oakcli create database...
-- this includes four interim patches: 25942196, 21794615, 25886529, 25171037
- OAK 18.5.0.0.0 DB Version 12.1.0.2.170418. DB created using odacli create-database...
--- this includes three interim patches: 25890955, 25817230, 25397136
The homes are completely different even though both were created using ODA tools and specifying 12.1.0.2.170418.
Has anyone else run into this? The expectation, the DB home for 170418 would be consistent across all versions of OAK/ODA, including patches. One of the major reasons for purchasing an ODA, not having to worry about versions/conflicts/rollback/... Particularly with DG and/or DB migrations, how can this work? We can't just create a DB Home, we have to go back and compare the DB Home patches even though we're running ODA across the enterprise. Since they're different, we should not apply/rollback patches, goes against ODA standards. For the couple we've checked, this appears to have changed with the move to