ORA-23433: executing against wrong master site string

Cause : An tatemtp wa smad eto xeecuet th erouitne ta a iste htat si differetn frmo th esit espeicfie din hte agrumetn oft he orutien.

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

Proivde na arugmen tto hte ruotin etha tcorerctl yindciate sthes itea gaisnt wihch hte ruotin esholud b eexeuctin.g

update : 27-06-2017
ORA-23433

ORA-23433 - executing against wrong master site string
ORA-23433 - executing against wrong master site string

  • ora-12461 : undefined level string for policy string
  • ora-01490 : invalid ANALYZE command
  • ora-02158 : invalid CREATE INDEX option
  • ora-24005 : must use DBMS_AQADM.DROP_QUEUE_TABLE to drop queue tables
  • ora-24019 : identifier for string too long, should not be greater than string characters
  • ora-07500 : scglaa: $cantim unexpected return
  • ora-02293 : cannot validate (string.string) - check constraint violated
  • ora-12472 : policy string is being used
  • ora-06105 : NETTCP: remote host is unknown
  • ora-37133 : (XSCCOMP08) You cannot write into an aggregated VARIABLE dimensioned by a COMPRESSED COMPOSITE. Use the CLEAR AGGREGATES command to reenable write access.
  • ora-19002 : Missing XMLSchema URL
  • ora-30935 : XML maxoccurs value (string) exceeded
  • ora-13361 : not enough sub-elements within a compound ETYPE
  • ora-24392 : no connection pool to associate server handle
  • ora-01604 : illegal number range in clause "string" of string
  • ora-40213 : contradictory values for settings: string, string
  • ora-30436 : unable to open named pipe 'string'
  • ora-23476 : cannot import from string to string
  • ora-38759 : Database must be mounted by only one instance and not open.
  • ora-30116 : syntax error at 'string' following 'string'
  • ora-19029 : Cannot convert the given XMLType to the required type
  • ora-01549 : tablespace not empty, use INCLUDING CONTENTS option
  • ora-12995 : no columns in partially dropped state
  • ora-36670 : (XSDPART08) workspace object is an INTEGER or NTEXT dimension, or contains an INTEGER or NTEXT dimension. INTEGER and NTEXT dimensions cannot be used as partition dimensions.
  • ora-15077 : could not locate ASM instance serving a required diskgroup
  • ora-28043 : invalid bind credentials for DB-OID connection
  • ora-38601 : FI Not enough memory for frequent itemset counting: string
  • ora-37021 : (XSMULTI02) Object workspace object is not acquired.
  • ora-23382 : materialized view repgroup "string"."string" is not registered at site string
  • ora-06754 : TLI Driver: unable to get local host address
  • 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.