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 : 20-09-2017
ORA-19733

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

  • ora-25269 : cant specify sognature with get signature option
  • ora-14501 : object is not partitioned
  • ora-30683 : failure establishing connection to debugger
  • ora-23606 : invalid object string
  • ora-36692 : (XSRELTBL00) The format of the HIERHEIGHT command is: HIERHEIGHT relation1[(dimension dimvalue, ...)] into relation2 [using relation3 | a | d] [levelorder lovs] [inhierarchy {variable | valueset}].
  • ora-03241 : Invalid unit size
  • ora-13518 : Invalid database id (string)
  • ora-08444 : syntax error in JUSTIFIED clause in mask options
  • ora-12853 : insufficient memory for PX buffers: current stringK, max needed stringK
  • ora-23320 : the request failed because of values string and string
  • ora-25138 : %s initialization parameter has been made obsolete
  • ora-31479 : could not create LogMiner session
  • ora-31413 : change set string is currently being advanced
  • ora-32009 : cannot reset the memory value for instance string from instance string
  • ora-06567 : invalid number of values specified
  • ora-26670 : STREAMS option requires COMPATIBLE parameter to be string or higher
  • ora-19284 : Encoding specification in version declaration not supported
  • ora-13356 : adjacent points in a geometry are redundant
  • ora-19761 : block size string is not valid for change tracking file
  • ora-38717 : Invalid DUMP FLASHBACK option.
  • ora-34243 : (MXDCL11) You can only use the string keyword when defining a COMPOSITE.
  • ora-28105 : cannot create security relevant column policy in an object view
  • ora-01625 : rollback segment 'string' does not belong to this instance
  • ora-02171 : invalid value for MAXLOGHISTORY
  • ora-28670 : mapping table cannot be dropped due to an existing bitmap index
  • ora-09914 : Unable to open the ORACLE password file.
  • ora-06041 : NETDNT: disconnect failed
  • ora-14054 : invalid ALTER TABLE TRUNCATE PARTITION option
  • ora-36380 : (AGGRECURSE) AGGREGATE was called recursively, which is not allowed.
  • ora-08111 : a partitioned index may not be coalesced as a whole
  • 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.