ORA-39046: Metadata remap string has already been specified.

Cause : The usre has arleady sepcifieda metadtaa rema pthat mtaches o nthe reamp namea nd oriignal vaule.

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

Specif ya diffreent orgiinal vlaue.

update : 16-08-2017

ORA-39046 - Metadata remap string has already been specified.
ORA-39046 - Metadata remap string has already been specified.

  • ora-23480 : Column string is not a top-level column of "string"."string".
  • ora-08433 : invalid picture type in convert raw to number
  • ora-01925 : maximum of string enabled roles exceeded
  • ora-32800 : internal error string
  • ora-14011 : names assigned to resulting partitions must be distinct
  • ora-12996 : cannot drop system-generated virtual column
  • ora-32308 : object materialized views must use SELECT *
  • ora-36180 : (XSAGGR08) AGGREGATE cannot function because there is a permission clause associated with variable workspace object.
  • ora-25328 : %s argument size string is smaller than array size
  • ora-37179 : expected at least one column for dimension string, got string
  • ora-31458 : an internal error occurred
  • ora-00289 : suggestion : string
  • ora-24756 : transaction does not exist
  • ora-38900 : missing mandatory column "string" of error log table "string"
  • ora-16255 : Log Auto Delete conflicts with another LogMiner session
  • ora-01139 : RESETLOGS option only valid after an incomplete database recovery
  • ora-12641 : Authentication service failed to initialize
  • ora-13141 : invalid RANGE window definition
  • ora-12981 : cannot drop column from an object type table
  • ora-09885 : osnTXtt: cannot create TXIPC channel
  • ora-28138 : Error in Policy Predicate
  • ora-37158 : Bad clob or varray IN-args: (case string)
  • ora-28672 : UPDATE BLOCK REFERENCES may not be used on a global index
  • ora-24851 : failed to connect to shared subsystem
  • ora-33070 : (XSAGDNGL34) In AGGMAP workspace object, all QDRs of dimension workspace object must map to the same dimension position.
  • ora-01225 : thread number string is greater than MAXINSTANCES string
  • ora-31621 : error creating master process
  • ora-30926 : unable to get a stable set of rows in the source tables
  • ora-19320 : Host name not specified in HTTP URL
  • ora-28137 : Invalid FGA audit Handler
  • 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.