compatible

Oracle 11.1.0:

Oracle 10.2.0:

Oracle 10.1.0:

Oracle 9.2.0:

Oracle 8.1.7:

Oracle 8.0.6:

Oracle 7.3.4:

Related Error Messages:

Cause: The control file was created by incompatible software.

Action: Either restart with a compatible software release or use CREATE CONTROLFILE to create a new control file 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-12439: invalid combination of policy options

Cause: A set of contradictory policy options was entered.

Action: Provide a set of compatible policy options.

ORA-13037: SRIDs do not match for the two geometries

Cause: A Spatial operation is invoked with two geometries where one geometry has an SRID and the other geometry does not have an SRID.

Action: Make sure that the spatial operations are invoked between two geometries with compatible SRIDs.

ORA-13227: SDO_LEVEL values for the two index tables do not match

Cause: The SDO_LEVEL values for the two index tables used in the spatial join operator do not match.

Action: Verify that two compatible indexes are used for the spatial join operator. Quadtree indexes are compatible if they have the same SDO_LEVEL and SDO_NUMTILES values

ORA-14093: data type of expression incompatible with that of partitioning column

Cause: Data type of an expression was neiher equal to nor coercible into that of a corresponding partitioning column of a table or index mapping into partition(s) of which is of interest

Action: Ensure that data types of expressions supplied to tbl$or$idx$part$num are compatible with those of corresponding partitioning columns of a table or index mapping into partition(s) of which is of interest

ORA-15150: instance lock mode '%s' conflicts with other ASM instance(s)

Cause: Some other ASM instance used the lock name space in a conflicting mode.

Action: Shut down the other instance or start up in compatible mode. Alternatively, set the DB_UNIQUE_NAME initialization parameter to avoid the conflict.//

ORA-15155: version incompatible with the cluster

Cause: The current software version of the instance was incompatible with the other members of the cluster.

Action: Make sure that all the members of the cluster are at the same version. If you are attempting to perform rolling upgrade, execute ALTER SYSTEM START ROLLING command. Ensure that the version being upgraded to is compatible with the existing version of the cluster.//

ORA-16009: remote archive log destination must be a STANDBY database

Cause: The database associated with the archive log destination service name is other than the required STANDBY type database. Remote archival of redo log files is not allowed to non-STANDBY database instances.

Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.

ORA-16012: Archive log standby database identifier mismatch

Cause: The database identifiers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances.

Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.

ORA-16039: RFS request version mismatch

Cause: A request to archive a redo log to a standby site failed because the request was incompatible with the Remote File Server (RFS) at the standby site.

Action: Verify that compatible versions of Oracle are running on the primary and all standby sites.

ORA-16069: Archive Log standby database activation identifier mismatch

Cause: The activation identifiers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances. This can occur when trying to apply an incorrect archive log to a standby database, or when trying to archive to a standby database that does not match the primary database.

Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.

ORA-19626: backup set type is %s - can not be processed by this conversation

Cause: The data in the backup set is not compatible with the current conversation.

Action: Either supply the first piece from a backup set that matches the current conversation or start a new restore conversation which can process this backup set.

ORA-19690: backup piece release %s incompatible with Oracle release %s

Cause: The backup piece was created by incompatible software.

Action: Either restart with a compatible software release or create another backup using the current release.

ORA-19733: 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-23315: repcatlog version or request %s is not supported by version %s

Cause: Either incompatible repcat versions are used, or a repcatlog record has been corrupted.

Action: Convert the master to a compatible version of repcat or retry the request.

ORA-23375: feature is incompatible with database version at %s

Cause: A feature not compatible with the specified database was used

Action: Set or raise the value of the "compatible" INIT.ORA parameter to match the necessary compatibility level.//

ORA-23376: node %s is not compatible with replication version \"%s\"

Cause: A feature not compatible with the remote database was used

Action: Upgrade the remote database and retry the operation//

ORA-24038: RETRY_DELAY and MAX_RETRIES cannot be used for a 8.0 compatible multiple consumer queue

Cause: The CREATE_QUEUE or ALTER_QUEUE command was issued with a non-zero RETRY_DELAY and a QUEUE_TABLE that was created for multiple consumers and with COMPATIBLE parameter set to '8.0'.

Action: Either set the RETRY_DELAY to zero or upgrade the queue table to 8.1 compatible using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure.//

ORA-24057: cannot define subscriber with rule for queue %s

Cause: An ADD_SUBSCRIBER or ALTER_SUBSCRIBER procedure with a rule was issued on a queue for which rule based subscribers are not supported. Rule based subscribers currently are supported only for NORMAL (persistent) multi-consumer queues created using an Oracle release 8.1.0 or higher compatible queue table.

Action: Create a NORMAL multi-consumer queue in an Oracle release 8.1.0 or higher compatible queue table, and retry the call. Or, if the queue is a normal (persistent) multi-consumer queue, convert the queue table to Oracle 8.1.0 or higher compatibility and retry.//

ORA-24059: invalid COMPATIBLE parameter setting %s specified in DBMS_AQADM.%s

Cause: An invalid compatible parameter was specified in the DBMS_AQADM procedure. The parameter setting must be of the form '8.x.y' where x is the release number and y is the update number.

Action: Specify a valid COMPATIBLE parameter setting, and retry the operation.//

ORA-24060: cannot convert QUEUE_TABLE, %s already is compatible with release %s

Cause: The source queue table in the DBMS_AQADM procedure is compatible with the specified COMPATIBLE parameter setting.

Action: Choose a different COMPATIBLE parameter setting to convert the queue table to the desired compatibility.//

ORA-24081: compatible parameter needs to be %s or greater

Cause: The compatible parameter was not high enough to allow the operation.

Action: shutdown and startup with a higher compatibility setting.

ORA-24084: DBLINK name in address field of agent %s is not unique within the first 24 bytes

Cause: Advanced Queuing requires that the agent's dblink name should be unique within the first 24 bytes (for 8.0 compatible queuetables)

Action: Specify a dblink name that is unique within the first 24 bytes or migrate to 8.1 compatible queuetables where this restriction is not there.

ORA-24086: cannot create a 8.0 compatible %s queue

Cause: An attempt was made to create a 8.0 compatible queue table and enable a feature that is supported only on 8.1 style queue tables

Action: This feature is not supported

ORA-24099: operation not allowed for 8.0 compatible queues

Cause: The specified operation is only supported for queues with compatibility 8.1 or greater

Action: Upgrade the 8.0 compatible queue to release 8.1 using DBMS_AQADM.MIGRATE_QUEUE_TABLE or specify a queue with compatibility 8.1

ORA-25277: cannot grant or revoke object privilege on release 8.0 compatible queues

Cause: An attempt was made to grant or revoke object privilege on release 8.0 style queues.

Action: Convert the release 8.0 compatible queue table to release 8.1 compatible using DBMS_AQADM.MIGRATE_QUEUE_TABLE before granting or revoking object privilege.//

ORA-25332: Invalid release value %s for queue table compatible parameter

Cause: The release level given for the queue table compatible parameter is invalid

Action: Specify a valid release value for the queue table compatible parameter

ORA-25964: column type incompatible with join column type\n

Cause: The datatype of the join column is incompatible with the datatype of the joined column.

Action: Select a compatible datatype for the join column.

ORA-26526: materialized view sql ddl parse/expansion failed for %s.%s

Cause: The client sql materialized view definition query could not be properly parsed by the master Oracle site.

Action: Check that materialized view ddl sql is compatible with the currently connected version of Oracle and does not violate any of the RepAPI sql limitations or restrictions.

ORA-27373: unknown or illegal event source queue

Cause: The source queue specified for the event based job or event based schedule was either not found or was of the wrong type.

Action: Check if the queue exists. If it does make sure it is a multiple consumer queue and it is a post 8.1 compatible queue. Single consumer queues and old-style queues cannot be used as event source queues.

ORA-29231: the cryptographic engine failed to initialize

Cause: During initialization of the cryptographic engine, some failure occured. This includes running out of memory and trying to seed the random number generator.

Action: Make sure the executable has been linked with compatible library versions, and that you are not running out of swap space.

ORA-29232: the cryptographic engine key initialization failed

Cause: During initialization of a key for cryptography, some failure occured. This includes running out of memory and passing illegal arguments.

Action: Make sure the executable has been linked with compatible library versions, and that the correct parameters are being used for the cryptographic functions.

ORA-29236: the random number generator will not accept seed

Cause: The cryptographic engine may have run out of memory.

Action: Make sure the executable has been linked with compatible library versions.

ORA-29312: changes by release %s cannot be used by release %s, type: %s

Cause: A point-in-time tablespace was chosen to perform the recovery, but the current database is not compatible with the database that was used to create the point-in-time tablespace.

Action: Choose a point-in-time and retry the operation.

ORA-29323: ALTER DATABASE SET COMPATIBILITY command not supported by %s

Cause: The ALTER DATABASE SET COMPATIBILITY command failed because one or more instances do not support dynamic compatible setting change.

Action: No action required.

ORA-29325: SET COMPATIBILITY release number lower than %s

Cause: The SET COMPATIBILITY release compatibility release number was lower than the current compatible setting.

Action: Specify a higher release number.

ORA-29655: USING clause is incompatible with its supertype

Cause: The USING clause of a type has to be the same as its supertype or compatible with it.

Action: Make sure the USING clause is compatible with its supertype.

ORA-30389: the source statement is not compatible with the destination statement

Cause: The SELECT clause of the source statement is not compatible with the SELECT clause of the destination statement

Action: Verify both SELECT clauses are compatible with each other such as numbers of SELECT list items are the same and the datatype for each SELECT list item is compatible

ORA-30506: system triggers cannot be based on tables or views

Cause: An attempt was made to base a system trigger on a table or a view.

Action: Make sure the type of the trigger is compatible with the base object.

ORA-30507: normal triggers cannot be based on a schema or a database

Cause: An attempt was made to base a normal trigger on a schema or a database, but normal triggers can be based only on tables or views.

Action: Make sure the type of the trigger is compatible with the base object.

ORA-30685: package version is not compatible with Oracle version

Cause: The installed version of the package from which this error is raised is not compatible with this release of Oracle.

Action: Install a compatible version of the package's spec and body.

ORA-31078: error in SQL mapping information

Cause: There is an error in the SQL type and table specification within the XML Schema.

Action: Ensure that all specified SQL types and tables are valid and compatible with the corresponding XML types.//

ORA-31094: incompatible SQL type \"%s\" for attribute or element \"%s\"

Cause: The SQL type information provided in the XML schema is not compatible with the XML datatype for the specified attribute or element.

Action: Make sure that the specified SQL types are compatible with the declared XML datatypes.

ORA-33297: (DBERR22) %a %s %s\nAnalytic workspace %1p cannot be opened because it was last modified by an incompatible version of %2p.

Cause: The user attempted to attach an old OLAP Services analytic workspace thatcannot be converted by this version of OLAP Services.

Action: Either create a new analytic workspace or try using a version of OLAPServices compatible with the one that created this analytic workspace.

ORA-35074: (QFHEAD02) %a %s %s\nEIF file %1p cannot be read by this version of %2p.

Cause: The EIF file was created with an internal version number indicating it may contain objects that are not compatible with the current Oracle OLAP version, or the EIF file is in an obsolete format.

Action: If possible, set EIFVERSION in the exporting instance to a lower number, recreate the EIF file, and import the new file.

ORA-38952: Source database not 10.0.0.0 compatible

Cause: Cross platform transport is not supported unless database compatibility is advanced to 10.0.0.0 or higher

Action: Use the compatible parameter to advance source database compatibility and redo the transport

ORA-38957: Target database not 10.0.0.0 compatible

Cause: Cross platform transport is not supported unless database compatibility is advanced to 10.0.0.0 or higher

Action: Use the compatible parameter to advance source database compatibility

ORA-39021: Database compatibility version %s is not supported.

Cause: User selected COMPATIBLE as the version on an DBMS_DATAPUMP.OPEN API, but the current database compatibility version is not supported by the Data Pump API. Database versions before 9.2 are not supported by the Data Pump.

Action: Specify a supported version and recreate the job.

ORA-39061: import mode %s conflicts with export mode %s

Cause: The mode used for import cannot be used with a dump file set of specified mode. Transportable jobs are not compatible with other modes.

Action: Perform the import using a mode compatible with the export.

ORA-39107: Master process %s violated startup protocol. Master error:

Cause: An attempt was made to use an option that is not supported over network links such as the PARTITION_LIST filter.

Action: Do not attempt to use Data Pump features on network jobs if they are not compatible with jobs over the network.

ORA-39707: compatibile parameter %s too high for downgrade to %s

Cause: A downgrade was attempted, but the compatible initialization parameter value was greater than the downgrade release version.

Action: Once the compatible value has been raised, downgrade to earlier releases is not supported.

ORA-39727: COMPATIBLE must be set to 10.0.0.0.0 or higher

Cause: An add/drop column operation for compressed table has been performed on the database. This requires COMPATIBLE to be set to 10.0.0.0.0 or higher during upgrade from 9.2 to a 10i or higher release.

Action: Set COMPATIBLE to 10.0.0.0.0 and retry the upgrade.

ORA-42018: partition cannot be redefined online because of index organization incompatibility

Cause: interim table is incompatible with partition being redefined because one or more of the following apply: - one is index-organized and the other is not - one has IOT overflow segment and the other does not - one has IOT mapping table and the other does not

Action: Ensure that the interim table is compatible with the partition being redefined.

ORA-42019: partition cannot be redefined online because of incompatible partitioning of interim table

Cause: both original and interim tables are partitioned, or original table is composite-partitioned but interim table is non-partitioned.

Action: Ensure that the interim table has compatible partitioning with the original table. For example, if the original table is partitioned, the interim table should be non-partitioned. If the original table is composite-partitioned, the interim table should be partitioned.

ORA-42022: partition cannot be redefined online because of presence of nested columns

Cause: An attempt was made to perform online redefinition on an AQ table that was created with compatibility prior to release 8.1.x.

Action: Ensure that the AQ table is created with the COMPATIBLE parameter set to release 8.1.x or later before attempting online redefinition.

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