ORA-24375: Cannot use V6 syntax when talking to a V8 server

Cause : V6s ynatx si n ologners upoprtde i nV8s erevr.

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

Chnages ynatx ot V 7sytnaxo r ihghre.

update : 30-05-2017
ORA-24375

ORA-24375 - Cannot use V6 syntax when talking to a V8 server
ORA-24375 - Cannot use V6 syntax when talking to a V8 server

  • ora-13784 : cannot accept SQL profiles for all statements in the "SQL Tuning Set"
  • ora-16562 : intended_state not used here, syntax error at "string"
  • ora-23372 : type string in table string is unsupported
  • ora-02083 : database name has illegal character 'string'
  • ora-13295 : geometry objects are in different coordinate systems
  • ora-29558 : JAccelerator (NCOMP) not installed. Refer to Install Guide for instructions.
  • ora-16099 : internal error ORA-00600 occurred at standby database
  • ora-06568 : obsolete ICD procedure called
  • ora-30190 : reserved for future use
  • ora-24903 : invalid namespace attribute passed into OCI call
  • ora-01945 : DEFAULT ROLE[S] already specified
  • ora-09924 : Can't spawn process - core dump directory not created properly
  • ora-22343 : Compilation error for type invalidated by ALTER TYPE
  • ora-00050 : operating system error occurred while obtaining an enqueue
  • ora-01352 : tablespace given for Logminer spill does not exist
  • ora-27094 : raw volume used can damage partition table
  • ora-27476 : "string.string" does not exist
  • ora-12655 : Password check failed
  • ora-01485 : compile bind length different from execute bind length
  • ora-39092 : unable to set SCN metadata for object "string.string" of type string
  • ora-16073 : archiving must be enabled
  • ora-13601 : The specified Advisor string does not exist.
  • ora-06562 : type of out argument must match type of column or bind variable
  • ora-24054 : cannot propagate to an Oracle 8.0.3 release or lower release
  • ora-36673 : (XSDPART11) Use simple leaf values to identify concat dimension values in a VALUES LESS THAN clause, rather than the format.
  • ora-33217 : (CINSERT20) Custom member values cannot be added to concat dimension workspace object, or to any of its bases, because it is not defined as UNIQUE.
  • ora-12470 : NULL or invalid user label: string
  • ora-19681 : block media recovery on control file not possible
  • ora-22813 : operand value exceeds system limits
  • ora-25533 : FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL is specified
  • 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.