ORA-27477: "string.string" already exists

Cause : nAa ttmetpw sam da eotc erta enao jbce tiwhta n ma ehttah saa rlaeydb ee nsudeb ynatoeh rboejtci nht easems hcme.a

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

eRsius eht eocmmna dsuni g aidffrene tanemo rcseham.

update : 23-04-2017
ORA-27477

ORA-27477 - "string.string" already exists
ORA-27477 - "string.string" already exists

  • ora-00972 : identifier is too long
  • ora-30965 : fragment does not fit into the VARCHAR2 VALUE column
  • ora-00348 : single-process redo failure. Must abort instance
  • ora-24041 : propagation schedule exists for QUEUE string and DESTINATION string
  • ora-01291 : missing logfile
  • ora-00215 : must be at least one control file
  • ora-12024 : materialized view log on "string"."string" does not have primary key columns
  • ora-19566 : exceeded limit of string corrupt blocks for file string
  • ora-12728 : invalid range in regular expression
  • ora-28341 : cannot encrypt constraint column(s) with salt
  • ora-38775 : cannot disable flash recovery area - flashback database is enabled
  • ora-00401 : the value for parameter string is not supported by this release
  • ora-29304 : tablespace 'string' does not exist
  • ora-31004 : Length string of the BLOB in XDB$H_INDEX is below the minimum string
  • ora-13067 : operator requires both parameters from the same topology
  • ora-39019 : invalid operation type string
  • ora-19902 : incarnation key string not found
  • ora-00453 : backgroud process 'string' is dead
  • ora-24029 : operation not allowed on a single-consumer queue
  • ora-16740 : redo transport service for standby database "string" incorrectly set to ALTERNATE
  • ora-09330 : Session terminated internally by Oracle or by an Oracle DBA
  • ora-16195 : DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined
  • ora-31416 : invalid SOURCE_COLMAP value
  • ora-13856 : Service name must be specified
  • ora-16814 : incorrect redo transport setting for AlternateLocation for standby database
  • ora-13369 : invalid value for etype in the 4-digit format
  • ora-23358 : invalid remote user
  • ora-32512 : type 'string' is unknown
  • ora-26513 : push error: master proc. string$RP.string failed for trans:string seq:string
  • ora-39023 : Version string is not supported.
  • 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.