2.51 COMPATIBLE
COMPATIBLE
enables you to use a new release of Oracle while ensuring the ability to downgrade the database to an earlier release.
Property | Description |
---|---|
Parameter type |
String |
Syntax |
|
Default value |
|
Modifiable |
No |
Modifiable in a PDB |
No |
Range of values |
Values must be specified as at least three decimal numbers with each pair separated by a dot, such as |
Basic |
Yes |
Oracle RAC |
Multiple instances must have the same value. |
The COMPATIBLE
parameter specifies the Oracle version number that the database disk format must be compatible with. The database can be downgraded to the version specified in the COMPATIBLE
parameter or any later version.
Setting COMPATIBLE
ensures that new features do not write data formats or structures to disk that are not compatible with the earlier release, preventing a future downgrade. Features that require a higher value of COMPATIBLE
to work correctly may be restricted or disabled to ensure downgrades are possible.
Typically, users keep COMPATIBLE
unchanged when upgrading their Oracle software. After upgrade, users will run the new release of the Oracle software for a few weeks to ensure that the new release is working correctly. Afterwards, users can choose to update COMPATIBLE
to the latest version to take advantage of the new features.
Notes:
-
The value of the
COMPATIBLE
parameter can be increased to a higher version, but it can never be decreased to a lower version. - The value of the
COMPATIBLE
parameter should not be changed for a Release Update (RU) or Release Update Revision (RUR). For example, assume you are running Oracle Database 19c and the value ofCOMPATIBLE
is19.0.0
. You then apply Oracle Database Release Update 19.6.0.0.0. Do not set the value ofCOMPATIBLE
to19.6.0
; leave it set to19.0.0
. -
When using a standby database, this parameter must have the same value on both the primary and standby databases.
See Also:
Oracle Database Upgrade Guide for more information on setting this parameter