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 : 27-05-2017

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

  • ora-13366 : invalid combination of interior exterior rings
  • ora-39166 : Object string was not found.
  • ora-14081 : new partition name must differ from the old partition name
  • ora-22345 : recompile type string.string before attempting this operation
  • ora-13485 : error occurred during compression or decompression: string
  • ora-14503 : only one partition name can be specified
  • ora-23535 : instantiating templates from multiple back ends is not allowed.
  • ora-30659 : too many locations specified for external table
  • ora-37010 : (XSACQUIRE_DIFFAW) When using the CONSISTENT WITH clause, all objects must come from the same analytic workspace.
  • ora-14284 : one or more of table's subpartitions reside in a read-only tablespace
  • ora-24363 : measurements in characters illegal here
  • ora-02711 : osnpvalid: write to validation channel failed
  • ora-00151 : invalid transaction ID
  • ora-28354 : wallet already open
  • ora-32037 : unsupported use of LEVEL in membership condition
  • ora-12402 : invalid format string: string
  • ora-01510 : error in deleting log files
  • ora-29374 : resource plan string in top-plan string has no plan directives
  • ora-00372 : file string cannot be modified at this time
  • ora-12202 : TNS:internal navigation error
  • ora-26011 : Cannot load type string into column string in table string
  • ora-30750 : cannot enable column string to store objects of type string.string
  • ora-01906 : BACKUP keyword expected
  • ora-01682 : read-only DB cannot allocate temporary space in tablespace string
  • ora-28012 : Manual commit not allowed here
  • ora-33298 : (AWUPG01) Analytic Workspace string is already in the newest format allowed by the current compatibility setting
  • ora-13022 : polygon crosses itself
  • ora-40212 : invalid target data type in input data for string function
  • ora-02401 : cannot EXPLAIN view owned by another user
  • ora-23325 : parameter type is not 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.