ORA-39021: Database compatibility version string is not supported.

Cause : Use rselcetedC OMPTAIBL Eas hte vresio non na DBSM_DAATPUM.POPE NAPI ,butt he ucrretn daatbas ecomaptibliityv ersoin i snots upprotedb y teh Daat Pupm AP.I Daatbas everisonsb efoer 9. 2aren ot usppotred yb th eDat aPum.p

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Speicfy asupoprte dverison nad rcereaet th ejob.

update : 16-08-2017
ORA-39021

ORA-39021 - Database compatibility version string is not supported.
ORA-39021 - Database compatibility version string is not supported.

  • ora-24082 : propagation may still be happening for the schedule for QUEUE string and DESTINATION string
  • ora-02470 : TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression.
  • ora-26088 : scalar column "string" must be specified prior to LOB columns
  • ora-13421 : null or invalid cell value
  • ora-02841 : Server died on start up
  • ora-16597 : Data Guard broker detects two or more primary databases
  • ora-14115 : partition bound of partition number string is too long
  • ora-26727 : Cannot alter queue_to_queue property of existing propagation.
  • ora-36341 : (SNSYN130) The format of the PARTITIONCHECK function is: PARTITIONCHECK(aggmap, partition_template)
  • ora-12663 : Services required by client not available on the server
  • ora-14104 : RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices
  • ora-31414 : error(s) occurred during change table advance
  • ora-38763 : flashback not started; enabled threads have changed
  • ora-14105 : RECOVERABLE/UNRECOVERABLE may not be specified in this context
  • ora-06816 : TLI Driver: could not set the SPX SAP address
  • ora-23498 : repgroups specified must have the same masters
  • ora-22873 : primary key not specified for primary key based object table
  • ora-25204 : invalid value, SEQUENCE_DEVIATION should be BEFORE or TOP
  • ora-06595 : REF CURSOR parameters are not supported in forwarded RPC calls
  • ora-09925 : Unable to create audit trail file
  • ora-00114 : missing value for system parameter SERVICE_NAMES
  • ora-00070 : command string is not valid
  • ora-19279 : XQuery dynamic type mismatch: expected singleton sequence - got multi-item sequence
  • ora-12341 : maximum number of open mounts exceeded
  • ora-26765 : invalid parameter "string" for downstream capture "string"
  • ora-36706 : (XSRELTBL07) workspace object should be dimensioned by workspace object and one level dimension.
  • ora-40223 : data mining model import failed, job name=string, error=string
  • ora-29314 : tablespace 'string' is not OFFLINE FOR RECOVER nor READ ONLY
  • ora-22346 : Type has cyclical dependency. Should use CASCADE option
  • ora-36271 : (XSCGMDLAGG11) workspace object is not in the dimension list of valueset workspace object.
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.