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 : 23-06-2017

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

  • ora-16095 : Dependent destination removal for inactivation
  • ora-09703 : sem_release: cannot release latch semaphore
  • ora-13005 : recursive HHCODE function error
  • ora-04062 : %s of string has been changed
  • ora-28593 : agent control utility: command terminated with error
  • ora-29807 : specified operator does not exist
  • ora-12808 : cannot set string_INSTANCES greater than number of instances string
  • ora-00064 : object is too large to allocate on this O/S (string,string)
  • ora-01429 : Index-Organized Table: no data segment to store overflow row-pieces
  • ora-39068 : invalid master table data in row with PROCESS_ORDER=string
  • ora-12724 : regular expression corrupt
  • ora-31610 : cannot call this function from a non-master process
  • ora-00447 : fatal error in background process
  • ora-39954 : DEFERRED is required for this system parameter
  • ora-02780 : Name given for the core dump directory is invalid
  • ora-13239 : sdo_dimensionality not specified during n-d R-tree creation
  • ora-09834 : snyGetPortSet: failed to collect info on a port.
  • ora-30000 : missing either trim specification or char expression in TRIM
  • ora-38784 : Cannot create restore point 'string'.
  • ora-00069 : cannot acquire lock -- table locks disabled for string
  • ora-02430 : cannot enable constraint (string) - no such constraint
  • ora-06519 : active autonomous transaction detected and rolled back
  • ora-02728 : osnfop: access error on oracle executable
  • ora-24303 : call not supported in non-deferred linkage
  • ora-21500 : internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
  • ora-19722 : datafile string is an incorrect version
  • ora-39107 : Master process string violated startup protocol. Master error:
  • ora-19802 : cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE
  • ora-01693 : max # extents (string) reached in lob segment string.string
  • ora-36691 : (NTEXTCNV02) Invalid escape sequence in argument to UNISTR function: string.
  • 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.