ORA-23449: missing user name

Cause : hT esures epicifdeb yht esuren ma eaparemet rodsen toe ixtsi nht eadatabes.

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

oCrrce tnai vnladiu es ranemo rrcaeett ehu es rnit ehm saet radatabes .sU eht eBD_ASURE Sivwet oeseltct ehv ladid tabasa esure.s

update : 26-09-2017
ORA-23449

ORA-23449 - missing user name
ORA-23449 - missing user name

  • ora-07743 : slemop: incorrect error file attributes
  • ora-30344 : number of child cols different from number of parent level cols
  • ora-01286 : start interval required
  • ora-40202 : column string does not exist in the input table string
  • ora-02723 : osnpui: cannot send break signal
  • ora-30398 : illegal JOIN KEY clause
  • ora-02030 : can only select from fixed tables/views
  • ora-30658 : attempt was made to create a temporary table with EXTERNAL organization
  • ora-13361 : not enough sub-elements within a compound ETYPE
  • ora-33100 : (APABBR02) Value 'number' is not valid for the workspace object option.
  • ora-01699 : tablespace 'string' is being imported for point in time recovery
  • ora-02229 : invalid SIZE option value
  • ora-19043 : Multiply nested XMLROOT function disallowed
  • ora-30446 : valid workload queries not found
  • ora-29382 : validation of pending area failed
  • ora-28140 : Invalid column specified
  • ora-13183 : unsupported geometric type for geometry string.string
  • ora-01019 : unable to allocate memory in the user side
  • ora-27023 : skgfqsbi: media manager protocol error
  • ora-22600 : encountered 8.0.2 (Beta) VARRAY data that cannot be processed
  • ora-12405 : invalid label list
  • ora-25301 : Cannot enqueue or dequeue user buffered messages to a database with version lower than 10.2
  • ora-00118 : Only one of PROTOCOL, ADDRESS or DESCRIPTION may be specified
  • ora-12654 : Authentication conversion failed
  • ora-29299 : Invalid handle for piecewise compress or uncompress
  • ora-07512 : sscggtl: $enq unexpected return for client termination lock
  • ora-07252 : spcre: semget error, could not allocate semaphores.
  • ora-30476 : PLAN_TABLE does not exist in the user's schema
  • ora-09301 : osncon: local kernel only supported in standard mode
  • ora-12631 : Username retrieval failed
  • 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.