DBChecks job shows incorrect version of oracle database after upgrade for compatible parameter

[mattsava]

After upgrading the database when running the DBCheck job it flags the compatible parameter as being incorrect. DBCheck seems to still be using the value of the old database not the current one. I know I can correct this in transaction DB17 but I would rather find the process that changed this during the database upgrade to ensure other checks are correct. Can anyone point me in the right direction?

[janos_mucsi-besze · Accepted solution]

Hi Matt,

Normally the compatible parameter is changed/adapted with our 'Custom Scripts' during the upgrade. If you did not include this script in the post_upgrade steps, this needs to be executed manually.

Our Upgrade notes contains these instruction. Just like here in section( Step: Check and Set Parameter 'COMPATIBLE') of below SAP note.

2660027 - Upgrading to Oracle Database 18c

The same is documented in the 12.2 and 19c upgrade notes as well.

[former_member207186]

Hi,

You can also check SAP Note ##1739274 - "Database Parameter COMPATIBLE" which contains default and supported values for Oracle database parameter 'COMPATIBLE' in SAP environments.

Regards,
Bíborka