Shulou(Shulou.com)05/31 Report--

How to understand the Oracle parameter COMPATIBLE, in view of this problem, this article introduces the corresponding analysis and solution in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible method.

There is a parameter that can be shared in the Oracle database. We sometimes call it the compiled version.

The official documentation explains the meaning of this parameter as follows:

COMPATIBLE allows you to use new versions of Oracle while ensuring backward compatibility with previous versions. This is useful if you need to revert to an earlier version.

Shareability allows you to use the new version of Oracle while ensuring backward compatibility with previous versions. This is helpful if it is necessary to revert to the previous version

This parameter specifies the version with which Oracle must maintain compatibility. It allows you to immediately take advantage of the new version of maintenance improvements in your production system without having to test new features in your environment. Some features of this version may be limited.

This parameter specifies the version of Oracle that must be compatible. It allows you to immediately take advantage of the new version of maintenance improvements in your production system without testing new features in the environment. Some features of this version may be limited

When using a standby database, this parameter must have the same value on the primary and standby databases.

When using a standby database, this parameter must have the same value on both the primary and standby databases

About compatible initialization parameters: about shared initialization parameters

The COMPATIBLE initialization parameter enables or disables features in the database that affect the file format on disk. For example, if you create an Oracle Database 11g Release 2 (11.2) database, but specify COMPATIBLE=10.0.0 in the initialization parameter file, features that require 11.2 compatibility generate errors when you try to use them. Such a database is called the 10.0.0 compatibility level.

Common initialization parameters enable or disable features in the database that affect the file format on disk. For example, if you create an Oracle database 11g 2. 0. Version (11.2) database, but specify compatibility = 10.0.0 in the initialization parameter file, then features that need to be compatible with 11.2 will generate an error if you try to use them. Such a database is said to be at the 10.0.0 compatibility level.

You can improve the compatibility level of the database by changing the COMPATIBLE initialization parameter. If you do so, you cannot start the database with a lower compatibility level setting unless the execution point is restored to some time before the compatibility improvement.

You can improve the compatibility level of the database by changing the common initialization parameters. If you do so, you cannot start the database with a lower compatibility level setting unless you do a point-in-time recovery before compatibility is advanced.

The default value of the COMPATIBLE parameter is the version number of the latest major version.

The default value for common parameters is the version number of the latest major version.

Parameter setting restrictions (for more information, please refer to the Oracle Database upgrade Guide 11g version 2 (11.2) E23633-09 for compatibility and interoperability between Oracle database versions)

It should be noted that this parameter can be lowered in Oracle 9i, but after 10g, it can only be adjusted higher, not lower.

Starting with Oracle Database 10g, compatible initialization parameters become irreversible; that is, they cannot be set to a value less than the previous value. Therefore, the compatibility of the database can only be forward, not backward.

For example, suppose you set COMPATIBLE to 10.0.0 and start the database, and then shut down the database to restart the COMPATIBLE setting to 9.2.0. During startup, an error occurs indicating that the compatibility settings cannot be reversed.

If you do improve the compatibility of the database by using the COMPATIBLE initialization parameter, you cannot start the database with a lower compatibility level setting unless the execution point is restored to some time before the compatibility improvement. Any subsequent changes will be lost.

As a result, the alterdatabasereset COMPATIBILITY command is now out of date.

As a result, the change database reset compatibility command is now out of date.

Sometimes, in the Oracle 10.2.0.4 database, we will see the compiled version 10.2.0.1. This may be because the database was created on version 10.2.0.1 of the database software, and then the database software was upgraded and inherited from the previous compiled version. If you create a new database on the 10.2.0.4 database version, the default compilation version is 10.2.0.3

The answer to the question on how to understand the Oracle parameter COMPATIBLE is shared here. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel for more related knowledge.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.