ORA-13401: duplicate entry for string in USER_SDO_GEOR_SYSDATA view

Cause : The RASTER_DATA_TABLE and RASTER_ID columns contained the same information in two or more rows in the USER_SDO_GEOR_SYSDATA view.

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

Ensure that the RASTER_DATA_TABLE and RASTER_ID columns in the USER_SDO_GEOR_SYSDATA view contain the correct information, and that the value pair is unique for each row.

update : 17-08-2017
ORA-13401

ORA-13401 - duplicate entry for string in USER_SDO_GEOR_SYSDATA view
ORA-13401 - duplicate entry for string in USER_SDO_GEOR_SYSDATA view

  • ora-36204 : (XSAGOP04N) In AGGMAP workspace object, the NAOPERATOR string must be HFIRST, HLAST or HEVEN.
  • ora-07208 : sfwfb: failed to flush dirty buffers to disk.
  • ora-32739 : Hang analysis aborted due to failed heap re-grow
  • ora-25502 : concurrent ALTER SYSTEM QUIESCE/UNQUIESCE command is running
  • ora-29397 : cannot grant/revoke switch privilege for string
  • ora-16799 : Redo Apply is offline
  • ora-07707 : error in archive text: need tape label name
  • ora-13415 : invalid or out of scope point specification
  • ora-26718 : transaction limit reached
  • ora-02090 : network error: attempted callback+passthru
  • ora-36970 : (XSRELTBL12) workspace object must be a self-relation.
  • ora-19555 : invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value
  • ora-02171 : invalid value for MAXLOGHISTORY
  • ora-26035 : Error attempting to encrypt or decrypt column
  • ora-30556 : functional index is defined on the column to be modified
  • ora-16125 : large transaction string string string is waiting for more data
  • ora-39107 : Master process string violated startup protocol. Master error:
  • ora-26534 : collision: tranID number ignored and purged
  • ora-01262 : Stat failed on a file destination directory
  • ora-39754 : FULL PARTITIONED OUTER JOIN is not supported
  • ora-12047 : PCT FAST REFRESH cannot be used for materialized view "string"."string"
  • ora-24788 : cannot switch to specified transaction (server type)
  • ora-01325 : archive log mode must be enabled to build into the logstream
  • ora-29870 : specified options are only valid for altering a domain index
  • ora-06519 : active autonomous transaction detected and rolled back
  • ora-16570 : operation requires restart of database "string"
  • ora-24045 : invalid agent address string, agent address should be of the form [SCHEMA.]NAME[@DATABASE LINK]
  • ora-12465 : Not authorized for read or write on specified groups or compartments
  • ora-23367 : table string is missing the primary key
  • ora-29273 : HTTP request failed
  • 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.