ORA-13295: geometry objects are in different coordinate systems

Cause : An Oracel Spatia lfunctio nwas caleld with wto geomerties tha thave different SIRDs.

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

Transfomr geometyr object sto be i nthe sam ecoordintae syste mand cal lthe spaital funciton.

update : 27-04-2017
ORA-13295

ORA-13295 - geometry objects are in different coordinate systems
ORA-13295 - geometry objects are in different coordinate systems

  • ora-19033 : schema specified in the XML document does not match the schema parameter
  • ora-00332 : archived log is too small - may be incompletely archived
  • ora-30154 : The memory address given as buffer for OCIFileRead/Write is invalid
  • ora-24762 : server failed due to unspecified error
  • ora-14282 : FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION
  • ora-13364 : layer dimensionality does not match geometry dimensions
  • ora-06601 : LU6.2 Driver: Invalid database ID string
  • ora-31230 : DBMS_LDAP: unable to dynamically allocate additional memory
  • ora-33558 : (LOCKCHECK01) The status or contents of the workspace object dimension cannot be changed while the LOCK_LANGUAGE_DIMS option is set to value.
  • ora-04098 : trigger 'string.string' is invalid and failed re-validation
  • ora-01016 : This function can be called only after a fetch
  • ora-13112 : cannot delete topo_geometry layer [string] from topology
  • ora-40282 : invalid cost matrix
  • ora-13419 : cannot perform mosaick operation on the specified table column
  • ora-01201 : file string header failed to write correctly
  • ora-01466 : unable to read data - table definition has changed
  • ora-27550 : Target ID protocol check failed. tid vers=number, type=number, remote instance number=number, local instance number=number
  • ora-01117 : adding file 'string' with illegal block size: string; limit is string
  • ora-39079 : unable to enqueue message string
  • ora-13369 : invalid value for etype in the 4-digit format
  • ora-29278 : SMTP transient error: string
  • ora-16170 : Terminal recovery may have left the database in an inconsistent state
  • ora-12197 : TNS:keyword-value resolution error
  • ora-24431 : Statement does not exist in the cache
  • ora-14507 : partition corrupt. all rows do not fall within partition bounds
  • ora-13337 : failure in concatenating LRS polygons
  • ora-01033 : ORACLE initialization or shutdown in progress
  • ora-15128 : ASM file name 'string' exceeds maximum length string
  • ora-19563 : %s header validation failed for file string
  • ora-19162 : XP0004 - XQuery type mismatch: invalid argument types 'string', 'string' for function 'string'
  • 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.