ORA-19733: COMPATIBLE parameter needs to be string or greater

Cause : Th eCOPMATBILEi niitalziatoin apraemte risn oth ig henuoght o lalo wth eopreatoin.A llwoin gth ecomman dwolud amket hed atbaas einocmptaibel wtih hte erlesae psecfiie dbyt hec urerntC OMAPTILBE apraemte.r

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

Shtudonw adn satrtpu wtih ahihgerc omaptiibliyt stetign.

update : 24-07-2017
ORA-19733

ORA-19733 - COMPATIBLE parameter needs to be string or greater
ORA-19733 - COMPATIBLE parameter needs to be string or greater

  • ora-02769 : Setting of handler for SIGTERM failed
  • ora-37038 : (XSMLTDCL04) You cannot change definitions of objects in analytic workspace string because it is attached in MULTI mode.
  • ora-23441 : object does not exist for refresh group template
  • ora-16075 : standby database destination mismatch
  • ora-38957 : Target database not 10.0.0.0 compatible
  • ora-14109 : partition-extended object names may only be used with tables
  • ora-02277 : invalid sequence name
  • ora-00360 : not a logfile member: string
  • ora-14110 : partitioning column may not be of type ROWID
  • ora-09300 : osncon: unable to connect, DPMI not available
  • ora-30023 : Duplicate undo tablespace specification
  • ora-13861 : Statistics aggregation for client identifier string is already enabled
  • ora-24015 : cannot create QUEUE_TABLE, QUEUE_PAYLOAD_TYPE string.string does not exist
  • ora-08323 : scnmin: close of bias lock failed
  • ora-32583 : query passed to table function has wrong number of elements in select list
  • ora-01574 : maximum number of concurrent transactions exceeded
  • ora-24505 : cannot change character set id on the handle
  • ora-07482 : snlmini: cannot create lock manager instance.
  • ora-01314 : Name of the column to be mined should be a string literal
  • ora-02092 : out of transaction table slots for distributed transaction
  • ora-39130 : Object type string not imported. Base object name conflicts with the master table
  • ora-14196 : Specified index cannot be used to enforce the constraint.
  • ora-19262 : XQ0042 - namespace constructor not inside an element constructor
  • ora-25206 : enqueue failed, enqueue to exception queue string.string not permitted
  • ora-31616 : unable to write to dump file "string"
  • ora-01155 : the database is being opened, closed, mounted or dismounted
  • ora-13430 : the GeoRaster object has null attribute(s)
  • ora-12198 : TNS:could not find path to destination
  • ora-14111 : creation of a GLOBAL partitioned index on clustered tables is not supported
  • ora-28042 : Server authentication failed
  • 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.