ORA-29342: user string does not exist in the database

Cause : The referred user is one of the owners of data in the pluggable set. This user does not exist in the database.

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

Consider either creating the user in the database or map the user to a different user via FROM_USER and TO_USER import options.

update : 21-07-2017
ORA-29342

ORA-29342 - user string does not exist in the database
ORA-29342 - user string does not exist in the database

  • ora-02058 : no prepared transaction found with ID string
  • ora-19771 : cannot rename change tracking file while database is open
  • ora-02786 : Size needed for shared region is greater than segment size
  • ora-36608 : (XSAGHOVERFLOW) The depth of the hierarchies encountered while processing a composite dimension in AGGREGATE caused a counter overflow.
  • ora-28046 : Password change for SYS disallowed
  • ora-39954 : DEFERRED is required for this system parameter
  • ora-36992 : (XSRELGID09) A level relation is needed to produce a surrogate dimension gid.
  • ora-33016 : (XSAGDNGL07) In AGGMAP workspace object, workspace object is not a valid operator or variable name.
  • ora-12558 : TNS:protocol adapter not loaded
  • ora-06916 : CMX: error in data read (t_datain)
  • ora-23382 : materialized view repgroup "string"."string" is not registered at site string
  • ora-37030 : (XSMLTMAINT01) You cannot maintain workspace object because it is not ACQUIRED.
  • ora-30557 : function based index could not be properly maintained
  • ora-03134 : Connections to this server version are no longer supported.
  • ora-09772 : osnpmetbrkmsg: message from host had incorrect message type
  • ora-09949 : Unable to get client operating system privileges
  • ora-32009 : cannot reset the memory value for instance string from instance string
  • ora-27126 : unable to lock shared memory segment in core
  • ora-19954 : control file is not current
  • ora-19211 : column 'string', specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type
  • ora-16809 : multiple warnings detected for the database
  • ora-07641 : smscre: Unable to use the system pagefile for the SGA
  • ora-19593 : datafile number string already included as string
  • ora-16092 : dependent archive log destination is not active
  • ora-00225 : expected size string of control file differs from actual size string
  • ora-24501 : invalid UTF16 string passed in
  • ora-09209 : sftget: error reading from file
  • ora-00097 : use of Oracle SQL feature not in SQL92 string Level
  • ora-16177 : media recovery is not required
  • ora-04001 : sequence parameter string must be an integer
  • 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.