ORA-26692: invalid value string, string should be in string format

Cause : The paarmeter psecifie dwas no tin thec orrectf ormat.

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

Specif ythe paarmeter avlue int he corerct foramt.

update : 25-04-2017

ORA-26692 - invalid value string, string should be in string format
ORA-26692 - invalid value string, string should be in string format

  • ora-33558 : (LOCKCHECK01) The status or contents of the workspace object dimension cannot be changed while the LOCK_LANGUAGE_DIMS option is set to value.
  • ora-02851 : Request list is empty when it should not be
  • ora-29345 : cannot plug a tablespace into a database using an incompatible character set
  • ora-00983 : cannot audit or noaudit SYS user actions
  • ora-19202 : Error occurred in XML processingstring
  • ora-14552 : cannot perform a DDL, commit or rollback inside a query or DML
  • ora-29268 : HTTP client error string
  • ora-16800 : redo transport service for a standby database incorrectly set to ALTERNATE
  • ora-22342 : dependent VARRAY column exceeds the maximum inline column size
  • ora-00096 : invalid value string for parameter string, must be from among string
  • ora-13614 : The template string is not compatible with the current advisor.
  • ora-38464 : expression set is not empty.
  • ora-06313 : IPA: Shared memory failed to initialise
  • ora-16522 : generic template not found
  • ora-27059 : could not reduce file size
  • ora-23318 : a ddl failure has occurred
  • ora-38412 : Expression set column string does not exist.
  • ora-01251 : Unknown File Header Version read for file number string
  • ora-02264 : name already used by an existing constraint
  • ora-23330 : column group string already exists
  • ora-29267 : illegal call
  • ora-32801 : invalid value string for string
  • ora-02314 : illegal use of type constructor
  • ora-25408 : can not safely replay call
  • ora-24184 : transformation string.string already exists
  • ora-24318 : call not allowed for scalar data types
  • ora-16622 : two or more broker database objects resolve to one physical database
  • ora-06603 : LU6.2 Driver: Error allocating memory
  • ora-15078 : ASM diskgroup was forcibly dismounted
  • ora-34841 : (OPCREATE02) The string option must be declared with the READONLY attribute.
  • 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.