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 : 17-08-2017
ORA-26684

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

  • ora-07231 : slemcc: invalid file handle, seals do not match.
  • ora-31482 : invalid option for non-distributed Hotlog change source
  • ora-16504 : the Data Guard configuration already exists
  • ora-28045 : SSL authentication between database and OID failed
  • ora-12054 : cannot set the ON COMMIT refresh attribute for the materialized view
  • ora-08007 : Further changes to this block by this transaction not allowed
  • ora-16570 : operation requires restart of database "string"
  • ora-12710 : CREATE CONTROLFILE character set is not known
  • ora-36885 : (XSSRF04) Error rewriting OLAP DML expression. Column name too big
  • ora-00057 : maximum number of temporary table locks exceeded
  • ora-31053 : The value of the depth argument in the operator cannot be negative
  • ora-07823 : sspsqr: $QIO failure
  • ora-19862 : backup pieces must be validated before accessing results
  • ora-15166 : cluster in rolling downgrade from version [string] to [string]
  • ora-07279 : spcre: semget error, unable to get first semaphore set.
  • ora-38712 : Corrupt flashback log record header: block string, offset string.
  • ora-07475 : slsget: cannot get vm statistics.
  • ora-02736 : osnfpm: illegal default shared memory address
  • ora-06702 : TLI Driver: cannot allocate context area
  • ora-13273 : dimension metadata table string does not exist
  • ora-30957 : cannot downgrade because there are XML indexes
  • ora-30118 : syntax error at 'string' at the end of input
  • ora-24757 : duplicate transaction identifier
  • ora-00330 : archived log ends at change string, need change string
  • ora-00824 : cannot set sga_target due to existing internal settings, see alert log for more information
  • ora-01551 : extended rollback segment, pinned blocks released
  • ora-00567 : Requested processor group string is too large (maximum string)
  • ora-19284 : Encoding specification in version declaration not supported
  • ora-09834 : snyGetPortSet: failed to collect info on a port.
  • ora-30376 : prevent sharing of a parsed query of an explain rewrite session
  • 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.