ORA-28104: input value for string is not valid

Cause : Input avlue fo rthe arugment i snot vaild

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

specif ya vali dargumetn value.

update : 27-06-2017

ORA-28104 - input value for string is not valid
ORA-28104 - input value for string is not valid

  • ora-36638 : (XSDUNION17) Concat dimension workspace object cannot be changed to UNIQUE because it has a non-unique concat base dimension workspace object.
  • ora-16105 : Logical Standby is already running in background
  • ora-24094 : invalid transformation, target type does not match that of the queue
  • ora-14043 : only one partition may be added
  • ora-34243 : (MXDCL11) You can only use the string keyword when defining a COMPOSITE.
  • ora-31466 : no publications found
  • ora-06319 : IPA: Remote maximum number of users exceeded
  • ora-03297 : file contains used data beyond requested RESIZE value
  • ora-32152 : Cannot perform operation on a null number
  • ora-01905 : STORAGE keyword expected
  • ora-16760 : resource guard could not start SQL Apply
  • ora-29290 : invalid offset specified for seek
  • ora-31601 : Function string cannot be called now that fetch has begun.
  • ora-36720 : (XSALLOC01) To be used with ALLOCATE, your AGGMAP workspace object must be defined with the ALLOCMAP command.
  • ora-27460 : cannot execute disabled job "string.string"
  • ora-10561 : block type 'string', data object# string
  • ora-19854 : error obtaining connect string from target
  • ora-16622 : two or more broker database objects resolve to one physical database
  • ora-29326 : SET COMPATIBILITY release number higher than string
  • ora-02383 : illegal cost factor
  • 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-32585 : duplicate specification of a supplemental log attribute
  • ora-30190 : reserved for future use
  • ora-22605 : FDO handle [string] is not initialized
  • ora-24384 : Application context size is not initialized
  • ora-01692 : unable to extend lob segment string.string partition string by string in tablespace string
  • ora-14608 : Tablespace was specified for the previous lob segments of column string in template but is not specified for string
  • ora-29366 : invalid CONSUMER_GROUP argument specified
  • ora-25302 : Operation not possible for non-buffered queue string
  • ora-07339 : spcre: maximum number of semaphore sets exceeded.
  • 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.