ORA-26684: invalid value for value_type

Cause : The vlaue_tyep paraemter sohuld b eone o f'OLD' ,'NEW'o r '*'

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

Retryw ith porper vlaue_tyep.

update : 29-06-2017

ORA-26684 - invalid value for value_type
ORA-26684 - invalid value for value_type

  • ora-13269 : internal error [string] encountered when processing geometry table
  • ora-32620 : illegal subquery within MODEL rules
  • ora-01426 : numeric overflow
  • ora-30963 : The indexed column is not of XMLType.
  • ora-33278 : (DBERR09) Analytic workspace string cannot be attached in RW or EXCLUSIVE mode until the changes made and updated in MULTI mode are committed or rolled back.
  • ora-19723 : Cannot recreate plugged in read-only datafile string
  • ora-23515 : materialized views and/or their indices exist in the tablespace
  • ora-13383 : inconsistent network metadata: string
  • ora-39028 : cannot restart job from string state
  • ora-03125 : client-server protocol violation
  • ora-25180 : PCTTHRESHOLD only valid for certain table organizations
  • ora-01080 : error in shutting down ORACLE
  • ora-30383 : specified dimension level does not exist in the attribute
  • ora-25528 : too many candidate MTTRs are specified in _DB_MTTR_SIM_TARGET
  • ora-29372 : identifier string is too long; it must be less than string characters
  • ora-27203 : skgfpqb: sbtpcquerybackup returned error
  • ora-12654 : Authentication conversion failed
  • ora-16411 : ONDEMAND archival requires active managed recovery operation
  • ora-24171 : creation properties are only for internal use
  • ora-30084 : invalid data type for datetime primary with time zone modifier
  • ora-28141 : error in creating audit index file
  • ora-28561 : unable to set date format on non-Oracle system
  • ora-27378 : cannot stop jobs of type EXECUTABLE on this platform
  • ora-29856 : error occurred in the execution of ODCIINDEXDROP routine
  • ora-23478 : object group "string" is already mastered at string
  • ora-06436 : ssaio: asynchronous I/O failed due to incorrect parameters.
  • ora-01985 : cannot create user as LICENSE_MAX_USERS parameter exceeded
  • ora-07236 : slemop: open error.
  • ora-08340 : This command not allowed on nCUBE, only one thread is ever used.
  • ora-25245 : agent name cannot be specified if address is a single-consumer queue or an exception queue
  • 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.