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 : 26-04-2017

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

  • ora-10663 : Object has rowid based materialized views
  • ora-19679 : RMAN configuration number string is outside valid range of 1 through string
  • ora-32408 : materialized view log on "string"."string" already has new values
  • ora-19563 : %s header validation failed for file string
  • ora-30688 : maximum program calling depth exceeded
  • ora-14516 : subpartition corrupt. all rows do not fall within subpartition bounds
  • ora-25209 : invalid value string, EXPIRATION should be non-negative or NEVER
  • ora-01501 : CREATE DATABASE failed
  • ora-30969 : invalid syntax for PARAMETERS
  • ora-14309 : Total count of list values exceeds maximum allowed
  • ora-31028 : Resource metadata length string exceeded maximum length string
  • ora-02814 : Unable to get shared memory
  • ora-32518 : cannot wait for ORADEBUG command completion (waited number ms for process string); total wait time exceeds number ms
  • ora-02737 : osnpcl: cannot tell orapop to exit
  • ora-23614 : Script string does not exist
  • ora-21613 : key does not exist
  • ora-06593 : %s is not supported with natively compiled PL/SQL modules
  • ora-28345 : cannot downgrade because there exists encrypted column
  • ora-39085 : cannot update job string for user string
  • ora-00037 : cannot switch to a session belonging to a different server group
  • ora-37028 : (XSMLTRESYNC03) Object workspace object cannot be resynced without modified object workspace object because they share a modified dimension map.
  • ora-03206 : maximum file size of (string) blocks in AUTOEXTEND clause is out of range
  • ora-19332 : Invalid column in the CREATE_DBURI operator
  • ora-00133 : value of string is too long
  • ora-16765 : Redo Apply is unexpectedly online
  • ora-24094 : invalid transformation, target type does not match that of the queue
  • ora-01060 : array binds or executes not allowed
  • ora-01254 : cannot end online backup - file string in recovery manager backup
  • ora-39042 : invalid transform name string
  • ora-14072 : fixed table may not be truncated
  • 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.