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 : 21-07-2017
ORA-39021

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

  • ora-26502 : error resignal
  • ora-16788 : unable to set one or more database configuration property values
  • ora-02072 : distributed database network protocol mismatch
  • ora-13144 : target table string not found
  • ora-30381 : REWRITE_TABLE is not compatible with Oracle version
  • ora-12037 : unknown export format
  • ora-15094 : attempted to write to file opened in read only mode
  • ora-07453 : requested resource manager plan schema does not contain OTHER_GROUPS
  • ora-00064 : object is too large to allocate on this O/S (string,string)
  • ora-01665 : control file is not a standby control file
  • ora-16746 : resource guard encountered errors during database mount
  • ora-31509 : publication does not exist
  • ora-06416 : NETCMN: error on test
  • ora-16032 : parameter string destination string cannot be translated
  • ora-06761 : TLI Driver: error sending orderly release
  • ora-01252 : cannot prevent writes - file string in recovery manager backup
  • ora-37082 : Invalid percent
  • ora-08177 : can't serialize access for this transaction
  • ora-13304 : failure to insert a transformed geometry object in a table
  • ora-28169 : unsupported certificate type
  • ora-01535 : rollback segment 'string' already exists
  • ora-38770 : FLASHBACK DATABASE failed during recovery.
  • ora-36702 : (XSRELTBL05) The format of the HIERHEIGHT function is: HIERHEIGHT(relation [,] level) level >= 1.
  • ora-38407 : The ADT associated with the attribute set already exists.
  • ora-09275 : CONNECT INTERNAL is not a valid DBA connection
  • ora-00294 : invalid archivelog format specifier 'string'
  • ora-25306 : Cannot connect to buffered queue's owner instance
  • ora-38485 : invalid object type for the user-defined function
  • ora-22061 : invalid format text [string]
  • ora-24061 : cannot specify non-zero SECONDARY_INSTANCE if PRIMARY_INSTANCE was zero
  • 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.