Init parameterCompatibility

COMPATIBLE

What it controls

The release whose on-disk format and features the database uses.

Know this before you change it

Once raised it can't be lowered; going back means restoring from backup. Raise it only after an upgrade has settled, and raise the standby's before the primary's.

Check and change it

1-- Current value on every instance2SELECT inst_id, name, value, isdefault, ismodified3FROM gv$parameter4WHERE name = 'compatible';5 6-- Value stored in the spfile7SELECT sid, value FROM v$spparameter WHERE name = 'compatible' AND isspecified = 'TRUE';8 9-- Static: saved in the spfile, takes effect after a restart10ALTER SYSTEM SET compatible = '19.0.0' SCOPE = SPFILE SID = '*';

Related scripts

• Installed components and their statusEverything in DBA_REGISTRY. Anything not VALID after a patch or upgrade needs attention before you hand the database back.

Open in the parameter referenceOracle's reference

More in Compatibility

• ENABLE_PLUGGABLE_DATABASEWhether the database is a multitenant container database.
• NLS_LENGTH_SEMANTICSWhether VARCHAR2 lengths in new columns default to bytes or characters.