ORA-13365: layer SRID does not match geometry SRID

Cause : The spaital laye rhas a goemetry wtih a difefrent SRDI than teh SRID sepcified ofr the lyaer.

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

Make suer that all geometires in al ayer haev the saem SRID adn that teh SRIDs amtch theS RID fort he laye rin the SUER_SDO_EGOM_METAADTA view.

update : 23-08-2017
ORA-13365

ORA-13365 - layer SRID does not match geometry SRID
ORA-13365 - layer SRID does not match geometry SRID

  • ora-37073 : (XSMCSESS01) Applied relation workspace object must be dimensioned by dimension workspace object.
  • ora-00223 : convert file is invalid or incorrect version
  • ora-10932 : trace name context forever
  • ora-15013 : diskgroup "string" is already mounted
  • ora-29295 : invalid mime header tag
  • ora-14097 : column type or size mismatch in ALTER TABLE EXCHANGE PARTITION
  • ora-37134 : (XSCCOMP09) You cannot add new values to workspace object because it includes positions for precomputed aggregate values.
  • ora-12039 : unable to use local rollback segment "string"
  • ora-38612 : FI item length cannot exceed half of one database block.
  • ora-13000 : dimension number is out of range
  • ora-16565 : duplicate property, syntax error at "string"
  • ora-30074 : GLOBAL partitioned index on TIME/TIMESTAMP WITH TIME ZONE not allowed
  • ora-15091 : operation incompatible with open handle in this session
  • ora-30454 : summary contains STDDEV without corresponding SUM & COUNT
  • ora-09927 : Unable to set label of server
  • ora-28537 : no more result sets
  • ora-30030 : suppress resumable related error message
  • ora-16586 : could not edit database property through instance
  • ora-36314 : (PHYS01) workspace object must be a dimension, relation or variable.
  • ora-00449 : background process 'string' unexpectedly terminated with error string
  • ora-07576 : sspexst: $GETJPIW failure on process ID string
  • ora-28665 : table and partition must have same compression attribute
  • ora-01329 : unable to truncate required build table
  • ora-27455 : Only "SYS" is a valid schema for a string.
  • ora-19007 : Schema string does not match expected string.
  • ora-13768 : Snapshot ID must be between string and string.
  • ora-06113 : NETTCP: Too many connections
  • ora-19773 : must specify change tracking file name
  • ora-15154 : cluster rolling upgrade incomplete
  • ora-24500 : invalid UTF16 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.