Copy of Oracle FAQ ORACLE RECOVERY without DUL
ORAFAQ HOME | ORAFAQ ASK QUESTION | ORAFAQ ADD INFO | ORAFAQ SEARCH | ORAFAQ E-MAIL
 

Index > ORACLE Server Parameters > compatible

compatible

Oracle 10.0.1:

Paramter Name:compatible
Description:Database will be completely compatible with this software version
Type:CHAR Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:FALSE

Oracle 9.2.0:

Paramter Name:compatible
Description:Database will be completely compatible with this software versio
Type:CHAR Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:FALSE

Oracle 8.1.7:

Paramter Name:compatible
Description:Database will be completely compatible with this software versio
Type:CHAR Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:FALSE

Oracle 8.0.6:

Paramter Name:compatible
Description:Database will be completely compatible with this software versio
Type:CHAR Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:FALSE

Oracle 7.3.4:

Paramter Name:compatible
Description:Database will be completely compatible with this software versio
Type:CHAR Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:FALSE

Related Error Messages:

ORA-00201: controlfile version %s incompatible with ORACLE version %s
    Cause: The controlfile was created by incompatible software.

    Action: Either restart with a compatible software release or use CREATE CONTROLFILE to create a new controlfile that is compatible with this release.

ORA-00331: log version %s incompatible with ORACLE version %s

    Cause: The log was written by incompatible version of Oracle.

    Action: Recover the database with the compatible software, shut it down cleanly, then restart with current software.

ORA-00373: online log version %s incompatible with ORACLE version %s

    Cause: The online log was written by incompatible version of Oracle. Can occur when the log file was created by either a new or older version of Oracle.

    Action: Recover the database with the compatible software, shut it down cleanly, then restart with current software.

ORA-00403: %s (%s) is not the same as other instances (%s)

    Cause: Another instance has set the compatible or compatible no recovery parameters differently than this instance.

    Action: Change the parameters of the current instance to match other instances already running.

ORA-00406: COMPATIBLE parameter needs to be %s or greater

    Cause: The COMPATIBLE initialization parameter is not high enough to allow the operation. Allowing the command would make the database incompatible with the release specified by the current COMPATIBLE parameter.

    Action: Shutdown and startup with a higher compatibility setting.

ORA-00409: COMPATIBLE needs to be %s or higher to use AUTO SEGMENT SPACE MANAGEMENT

    Cause: This is due to migrating from an older release of Oracle with tablespaces created using AUTO SEGMENT SPACE MANAGEMENT. To open the database, the COMPATIBLE parameter needs to be set to the specified value.

    Action: Shutdown and startup with the specified compatibility setting.

ORA-00702: bootstrap verison '%s' inconsistent with version '%s'

    Cause: The reading version of the boostrap is incompatible with the current bootstrap version.

    Action: Restore a version of the software that is compatible with this bootstrap version.

ORA-00723: Initialization parameter COMPATIBLE must be explicitly set

    Cause: Oracle detected that the initialization parameter COMPATIBLE was not explicitly specified, and the compatibility of the database is lower than the default value of the COMPATIBLE parameter. In order to use the new compatible setting, the intialization parameter must be explicitly set by the user.

    Action: Explicitly set the value of COMPATIBLE parameter either in PFILE or SPFILE, whichever is used.

ORA-01038: cannot write database file version %s with ORACLE version %s

    Cause: Attempting to write datafile headers in an old format. The new format can not be used until after the database has been verified as being compatible with this software version.

    Action: Open the database to advance to the new file formats, then repeat the operation. If the operation is required before the database can be opened, then use the previous software release to do the operation.

ORA-01102: cannot mount database in EXCLUSIVE mode

    Cause: Some other instance has the database mounted exclusive or shared.

    Action: Shutdown other instance or mount in a compatible mode.

ORA-01174: DB_FILES is %s buts needs to be %s to be compatible

    Cause: The maximum number of database files supported by this instance is not the same as for the other instances. All instances must be able to open all the files any instance can open.

    Action: Change the value of the DB_FILES parameter to be compatible

ORA-01273: STANDBY_FILE_MANAGEMENT = AUTO needs COMPATIBLE = %s or higher

    Cause: The COMPATIBLE initialization parameter was not set to the correct value for setting STANDBY_FILE_MANAGEMENT to AUTO.

    Action: Restart the instance with COMPATIBLE set to the correct release. *Cause: Automated standby file management was disabled, so an added file

ORA-01295: DB_ID mismatch between dictionary %s and logfiles

    Cause: The dictionary file is produced by a database that is different from that produced the logfiles.

    Action: Specify a compatible dictionary file.

ORA-01571: redo version %s incompatible with ORACLE version %s

    Cause: This software version can not read the current redo logs, and either crash recovery is required or there are offline database files that need media recovery. If a file name is listed then it needs media recovery.

    Action: Shutdown and startup using the compatible software. Do any required media recovery, and open the database. Shutdown and then startup using current software. If the file is going to be dropped then take it offline with the DROP option to skip this check.

ORA-01638: parameter %s does not allow ORACLE version %s to mount cluster database

    Cause: This software version can not read the current redo logs, and either crash recovery is required or there are offline database files that need media recovery. If a file name is listed then it needs media recovery.

    Action: Shutdown and startup using the compatible software. Do any required media recovery, and open the database. Shutdown and then startup using current software. If the file is going to be dropped then take it offline with the DROP option to skip this check.

ORA-02267: column type incompatible with referenced column type

    Cause: The datatype of the referencing column is incompatible with the

    Action: Select a compatible datatype for the referencing column.

ORA-3008: parameter COMPATIBLE >= %s needed for %s

    Cause: An attempt was made to use a feature for a later Oracle version, than the setting of the initialization parameter, COMPATIBLE.

    Action: Set COMPATIBLE to the value in the message (or higher), and retry the command, but be aware that this will limit your downgrade options.

ORA-10335: extra check in kck_rls_check

    Cause: An attempt was made to use a feature for a later Oracle version, than the setting of the initialization parameter, COMPATIBLE.

    Action: Set COMPATIBLE to the value in the message (or higher), and retry the command, but be aware that this will limit your downgrade options.

ORA-12439: invalid combination of policy options

    Cause: A set of contradictory policy options was entered.

    Action: Provide a set of compatible policy options.

This parameter is documented in the Oracle Server Reference Guide. Search for more info about [ compatible ] on the Oracle FAQ.

ORAFAQ HOME | ORAFAQ ASK QUESTION | ORAFAQ ADD FAQ | ORAFAQ SEARCH | ORAFAQ E-MAIL
All content of this page is copy from www.orafaq.com