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 : 22-06-2017

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

  • ora-13869 : Instance-wide SQL tracing on instance string is already enabled
  • ora-09362 : Windows 3.1 Two-Task driver unable to deallocate context area
  • ora-36862 : (XSTFRC02) Column number for this SQL Cache must be between 1 and number. Specified column number number is invalid.
  • ora-02308 : invalid option string for object type column
  • ora-09872 : TASDEF_CREATE: create failure in creating ?/dbs/tasdef@.dbf.
  • ora-39777 : data saves are not allowed when loading lob columns
  • ora-12637 : Packet receive failed
  • ora-14270 : table is not partitioned by Range or Hash or List method
  • ora-07826 : sspscm: SYS$GETDVIW failure
  • ora-16120 : dependencies being computed for transaction at SCN string
  • ora-13153 : invalid high water mark specified
  • ora-39309 : schema sync operation failed
  • ora-30483 : window functions are not allowed here
  • ora-22153 : source variable-length array is not initialized
  • ora-19916 : %s
  • ora-22870 : ALTER TYPE with REPLACE option a non-object type
  • ora-00370 : potential deadlock during kcbchange operation
  • ora-31186 : Document contains too many nodes
  • ora-06720 : TLI Driver: SID lookup failure
  • ora-19801 : initialization parameter DB_RECOVERY_FILE_DEST is not set
  • ora-01685 : max # extents (string) reached in index string.string partition string
  • ora-16088 : archive log has not been completely archived
  • ora-01139 : RESETLOGS option only valid after an incomplete database recovery
  • ora-14186 : number of sub-partitions of LOCAL index must equal that of the underlying table
  • ora-30369 : maximum number of columns is 32
  • ora-31619 : invalid dump file "string"
  • ora-39078 : unable to dequeue message for agent string from queue "string"
  • ora-25321 : enqueue failed, user property specified but queue string.string is not an 8.1 style queue
  • ora-24072 : cannot execute MIGRATE_QUEUE_TABLE procedure; must own queue table
  • ora-09987 : unable to attach to SGA in READ-ONLY mode
  • 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.