ORA-13112: cannot delete topo_geometry layer [string] from topology

Cause : It was not possible to delete the specified topo_geometry layer from the topology.

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

Check USER_SDO_TOPO_METADATA to see if the specified topo_geometry layer is part of the topology. Only those topo_geometry layers which are part of the topology can be deleted from it.

update : 25-09-2017

ORA-13112 - cannot delete topo_geometry layer [string] from topology
ORA-13112 - cannot delete topo_geometry layer [string] from topology

  • ora-36176 : (XSMXAGGR25) Relation workspace object must be a one-dimensional self-relation to be used as a weight for AGGREGATE.
  • ora-06141 : NETTCP: no privilege for user
  • ora-06709 : TLI Driver: message send failure
  • ora-02169 : FREELISTS storage option not allowed
  • ora-36290 : (EIFMAKEF14) You cannot export object workspace object, because EIFVERSION is set to number. That version does not support dimensions of type NUMBER.
  • ora-34059 : (MSEXECUT12) You cannot delete non session-only dimension values from unique concat dimension workspace object.
  • ora-38411 : invalid datatype for the column storing expressions
  • ora-00446 : background process started when not expected
  • ora-00319 : log string of thread string has incorrect log reset status
  • ora-28044 : unsupported directory type
  • ora-00065 : initialization of FIXED_DATE failed
  • ora-08264 : ora_addr: cannot close nameserver
  • ora-28184 : global user cannot have proxy permissions managed in the directory
  • ora-25118 : invalid DUMP DATAFILE/TEMPFILE option
  • ora-00162 : external dbid length string is greater than maximum (string)
  • ora-32412 : encrypted column "string" not allowed in the materialized view log
  • ora-28651 : Primary index on IOTs can not be marked unusable
  • ora-38435 : missing elementary attribute value or invalid name-value pairs
  • ora-09914 : Unable to open the ORACLE password file.
  • ora-19106 : invalid XQueryX: expected string - got string
  • ora-37040 : (XSACQUIRE_DEP_LOCKED) Composite, concat, dimension map, or internal partition workspace object is locked by another user.
  • ora-02813 : Unable to make temporary file name in order to get key
  • ora-30033 : Undo tablespace cannot be specified as default user tablespace
  • ora-31465 : cannot obtain a lock on the subscription
  • ora-06023 : NETASY: port open failure
  • ora-03281 : invalid ALLOCATE EXTENT option
  • ora-13195 : failed to generate maximum tile value
  • ora-30476 : PLAN_TABLE does not exist in the user's schema
  • ora-06805 : TLI Driver: could not send datagram SAP packet for SPX
  • ora-26714 : User error encountered while applying
  • 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.