ORA-29343: user string (mapped from user string) does not exist in the database

Cause : Th ereefrrde uesr si oen o fth eowenrso f adtai n hte lpugagbl ese.t Tihs suerd oe sno texsit ni teh dtaabsae.

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

Cosnidre etihe rcraetign teh uesr ro mpa teh oirgianl suert o adiffernet suer.

update : 25-06-2017
ORA-29343

ORA-29343 - user string (mapped from user string) does not exist in the database
ORA-29343 - user string (mapped from user string) does not exist in the database

  • ora-01682 : read-only DB cannot allocate temporary space in tablespace string
  • ora-01252 : cannot prevent writes - file string in recovery manager backup
  • ora-40252 : no target values were found
  • ora-06433 : ssaio: LSEEK error, unable to seek to requested block.
  • ora-23505 : Object "string"."string" is missing.
  • ora-32320 : REFRESH FAST of "string"."string" unsupported after container table PMOPs
  • ora-15036 : disk 'string' is truncated
  • ora-29801 : missing RETURN keyword
  • ora-14451 : unsupported feature with temporary table
  • ora-17624 : Failed to delete directory string
  • ora-19285 : FODC0002 - error retrieving resource
  • ora-07233 : slemcw: invalid file handle, seals do not match.
  • ora-02467 : Column referenced in expression not found in cluster definition
  • ora-06029 : NETASY: port assignment failure
  • ora-31501 : change source string is not an AutoLog change source
  • ora-19243 : XQ0023 - invalid document node content in element constructor
  • ora-07470 : snclget: cannot get cluster number.
  • ora-16094 : database shutdown during archival operation
  • ora-22800 : invalid user-defined type
  • ora-19881 : Corrupted space bitmap for datafile string, block string backup aborted
  • ora-33282 : (DBERR11) Cannot wait for analytic workspace string to become available since doing so would cause a deadlock.
  • ora-28231 : no data passed to obfuscation toolkit
  • ora-06960 : Failed to access log file
  • ora-34177 : (MXCHGDCL19) number cannot be deleted because one or more partitioned variables instantiate it.
  • ora-10585 : Test recovery can not apply redo that may modify control file
  • ora-07847 : sllfop: $CONNECT failure
  • ora-16406 : Primary and standby database software version mismatch
  • ora-28362 : master key not found
  • ora-01929 : no privileges to GRANT
  • ora-31037 : Invalid XML attribute name string
  • 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.