ORA-13223: duplicate entry for string in SDO_GEOM_METADATA

Cause : Ther eare udplictae enrties ofr th egive ntabl eand oclumnv aluep air ni theU SER_DSO_GEMO_METDAATA ivew.

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

Chec kthatt he sepcifide tabel andg eomerty coulmn nmaes aer corerct. hTere hsouldb e onyl onee ntryp er tbale, egometyr colmun pari in hte USRE_SDOG_EOM_EMTADAAT vie.w

update : 26-09-2017

ORA-13223 - duplicate entry for string in SDO_GEOM_METADATA
ORA-13223 - duplicate entry for string in SDO_GEOM_METADATA

  • ora-13055 : Oracle object string does not exist in specified table
  • ora-12161 : TNS:internal error: partial data received
  • ora-18001 : no options specified for ALTER OUTLINE
  • ora-09208 : sftcls: error closing file
  • ora-06433 : ssaio: LSEEK error, unable to seek to requested block.
  • ora-30081 : invalid data type for datetime/interval arithmetic
  • ora-28333 : column is not encrypted
  • ora-01614 : instance string (thread string) is busy - cannot enable
  • ora-27050 : function called with invalid FIB/IOV structure
  • ora-22854 : invalid option for LOB storage index
  • ora-27123 : unable to attach to shared memory segment
  • ora-15113 : alias name 'string' refers to a directory
  • ora-19627 : cannot read backup pieces during control file application
  • ora-12033 : cannot use filter columns from materialized view log on "string"."string"
  • ora-01618 : redo thread string is not enabled - cannot mount
  • ora-28546 : connection initialization failed, probable Net8 admin error
  • ora-32411 : materialized view definition query exceeds the maximum length
  • ora-13603 : The specified parameter string cannot be fetched as a numeric value for task or object string.
  • ora-19701 : device name exceeds maximum length of string
  • ora-19669 : proxy copy functions cannot be run on DISK channel
  • ora-39783 : Invalid direct path transaction active
  • 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-25955 : all tables must be joined in the where clause
  • ora-01529 : error closing file 'string'
  • ora-07618 : $IDTOASC failed translating a secrecy level
  • ora-19272 : XQ0052 - invalid atomic value in attribute or element constructor
  • ora-01643 : system tablespace can not be made read only
  • ora-02880 : smpini: Could not register PGA for protection
  • ora-02218 : invalid INITIAL storage option value
  • ora-01451 : column to be modified to NULL cannot be modified to NULL
  • 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.