ORA-12402: invalid format string: string

Cause : The format string is not supported by the policy.

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

Correct the syntax of the format string.

update : 22-06-2017

ORA-12402 - invalid format string: string
ORA-12402 - invalid format string: string

  • ora-07279 : spcre: semget error, unable to get first semaphore set.
  • ora-19210 : column 'string', specified to be a key or update column for DBMS_XMLSTORE, does not not exist in table 'string'
  • ora-07487 : scg_init_lm: cannot create lock manager instance.
  • ora-22607 : image handle already generated
  • ora-02445 : Exceptions table not found
  • ora-03002 : operator not implemented
  • ora-16132 : An error occurred during activation of the standby.
  • ora-02724 : osnpbr: cannot send break message to orapop
  • ora-24784 : Transaction exists
  • ora-12063 : unable to apply transaction from site string
  • ora-35917 : (XSHIDE05) You cannot HIDE model workspace object because the analytic workspace in which it is defined has not been upgraded to version string.
  • ora-06959 : Buffer I/O quota is too small
  • ora-02032 : clustered tables cannot be used before the cluster index is built
  • ora-16218 : This database is already preparing to switch over.
  • ora-30081 : invalid data type for datetime/interval arithmetic
  • ora-29295 : invalid mime header tag
  • ora-27091 : unable to queue I/O
  • ora-27461 : The value for attribute string is too large.
  • ora-30399 : a skip level must have at least one column that allows NULL values
  • ora-15126 : component within ASM file name 'string' exceeds maximum length
  • ora-33454 : (ESDREAD07) Discarding compiled code for workspace object because number is now string workspace object, whereas it was string workspace object when the code was compiled.
  • ora-00706 : error changing format of file 'string'
  • ora-38454 : attribute set not defined for the column being indexed
  • ora-02725 : osnpbr: cannot send break signal
  • ora-15109 : conflicting protection attributes specified
  • ora-19238 : XP0018 - focus not defined
  • ora-07584 : spdcr: invalid value for ORA_sid_(proc_)PQL$_item
  • ora-15175 : cannot create alias for diskgroup metadata file 'string'
  • ora-02423 : schema name does not match schema authorization identifier
  • ora-12219 : TNS:missing community name from address in ADDRESS_LIST
  • 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.