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 : 25-04-2017
ORA-26684

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

  • ora-16806 : supplemental logging is not turned on
  • ora-07417 : sfareq: One or more database writers not active.
  • ora-36666 : (XSDPART04) workspace object is not a concat dimension.
  • ora-26733 : timed-out waiting for file group lock
  • ora-16015 : log string sequence# string not archived, media recovery disabled
  • ora-30047 : Internal event for kti tracing
  • ora-19038 : Invalid opertions on query context
  • ora-28661 : Object already has COMPRESS clause specified
  • ora-22818 : subquery expressions not allowed here
  • ora-13765 : Value "string" is illegal for a result limit.
  • ora-00960 : ambiguous column naming in select list
  • ora-30340 : illegal dimension name
  • ora-02339 : invalid column specification
  • ora-06979 : X.25 Driver: server cannot start oracle
  • ora-10565 : Another test recovery session is active
  • ora-13217 : invalid parameters supplied in ALTER INDEX statement
  • ora-13118 : invalid node_id [string]
  • ora-09747 : pw_detachPorts: server call pws_detach failed.
  • ora-24082 : propagation may still be happening for the schedule for QUEUE string and DESTINATION string
  • ora-12900 : must specify a default temporary tablespace for a locally managed database
  • ora-24345 : A Truncation or null fetch error occurred
  • ora-24029 : operation not allowed on a single-consumer queue
  • ora-25214 : cannot specify delay or expiration for enqueue to exception queue
  • ora-01866 : the datetime class is invalid
  • ora-36848 : (XSLMGEN18) Dimension string.string!string is missing a COLUMNNAME property value
  • ora-30360 : REF not supported with query rewrite
  • ora-01273 : STANDBY_FILE_MANAGEMENT = AUTO needs COMPATIBLE = string or higher
  • ora-16730 : error executing dbms_logstdby.skip_txn procedure
  • ora-33219 : (CINSERT05) %K cannot be added to workspace object because it is already a value of the dependent UNIQUE concat dimension workspace object, from leaf dimension workspace object.
  • ora-13331 : invalid LRS segment
  • 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.