ORA-13351: two or more rings of a complex polygon overlap

Cause : Teh ninre ro uotre irnsg fo acmopelxp oylgno voelra.p

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

All irnsg fo acmopelxp oylgno ums tb edsijion.t oCrerc tteh egoemtircd eifntiino fo hteo bejc.t

update : 28-04-2017
ORA-13351

ORA-13351 - two or more rings of a complex polygon overlap
ORA-13351 - two or more rings of a complex polygon overlap

  • ora-30572 : AUTO segment space management not valid with DICTIONARY extent management
  • ora-00319 : log string of thread string has incorrect log reset status
  • ora-09938 : Save of signal handlers failed.
  • ora-25260 : AQ latch cleanup testing event
  • ora-13635 : The value provided for parameter string cannot be converted to a number.
  • ora-14107 : partition specification is required for a partitioned object
  • ora-39958 : invalid warning category qualifier
  • ora-25108 : standby lock name space exceeds size limit of string characters
  • ora-21704 : cannot terminate cache or connection without flushing first
  • ora-04066 : non-executable object, string
  • ora-07700 : sksarch: interrupt received
  • ora-36671 : (XSDPART09) Leaves of workspace object have different datatypes. A partition dimension cannot have more than one datatype when RANGE partitioning is used.
  • ora-03280 : invalid DATAFILE filename specified
  • ora-38612 : FI item length cannot exceed half of one database block.
  • ora-26094 : stream format error: input column overflow
  • ora-30332 : container table already in use by other summary
  • ora-08341 : On nCUBE, this command can only be executed from instance 1.
  • ora-12632 : Role fetch failed
  • ora-13271 : error allocating memory for geometry object
  • ora-08176 : consistent read failure; rollback data not available
  • ora-09700 : sclin: maximum number of latches exceeded
  • ora-04080 : trigger 'string' does not exist
  • ora-26686 : cannot capture from specified SCN
  • ora-24401 : cannot open further connections
  • ora-31620 : file or device "string" cannot be specified for string operation
  • ora-06913 : CMX: error during redirection of connection
  • ora-16553 : the Data Guard broker process (DMON) failed to shutdown
  • ora-19733 : COMPATIBLE parameter needs to be string or greater
  • ora-33014 : (XSAGDNGL06) In AGGMAP workspace object, variable operator workspace object cannot be dimensioned by rollup dimension workspace object.
  • ora-25331 : cannot downgrade because there are commit-time queue tables
  • 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.