ORA-13374: SDO_MBR not supported for geodetic data

Cause : The SDO_MBR functionality is not supported for geodetic data.

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

Find an alternative function that can be used in this context.

update : 25-06-2017
ORA-13374

ORA-13374 - SDO_MBR not supported for geodetic data
ORA-13374 - SDO_MBR not supported for geodetic data

  • ora-07840 : sllfop: LIB$GET_VM failure
  • ora-15110 : no diskgroups mounted
  • ora-00206 : error in writing (block string, # blocks string) of control file
  • ora-24904 : invalid callback attribute passed into OCI call
  • ora-24039 : Queue string not created in queue table for multiple consumers
  • ora-24343 : user defined callback error
  • ora-25281 : complete reciever information not provided to non-repudiate reciever
  • ora-04032 : pga_aggregate_target must be set before switching to auto mode
  • ora-36640 : (XSDUNION19) Concat dimension workspace object cannot be changed to UNIQUE because base dimension workspace object does not have a TEXT or ID datatype.
  • ora-16008 : indeterminate control file checkpoint
  • ora-38743 : Time/SCN is in the future of the database.
  • ora-22888 : duplicate SCOPE clauses for a REF column
  • ora-38406 : attribute set string already exists
  • ora-13249 : %s
  • ora-31639 : unexpected data found
  • ora-12674 : Shared server: proxy context not saved
  • ora-02262 : ORA-string occurs while type-checking column default value expression
  • ora-30689 : improper value for ORA_DEBUG_JDWP
  • ora-29295 : invalid mime header tag
  • ora-04045 : errors during recompilation/revalidation of string.string
  • ora-32613 : not a MODEL cell
  • ora-38305 : object not in RECYCLE BIN
  • ora-23365 : site string does not exist
  • ora-30450 : refresh_after_errors was TRUE; The following MVs could not be refreshed: string
  • ora-25200 : invalid value string, QUEUE_NAME should be [SCHEMA.]NAME
  • ora-12827 : insufficient parallel query slaves available
  • ora-01022 : database operation not supported in this configuration
  • ora-16573 : attempt to change configuration file for an enabled broker configuration
  • ora-16219 : This database is not preparing to switch over.
  • ora-31011 : XML parsing 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.