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 : 24-07-2017
ORA-13112

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

  • ora-31217 : DBMS_LDAP: PL/SQL - Invalid LDAP newparent.
  • ora-06530 : Reference to uninitialized composite
  • ora-24815 : Invalid character set form
  • ora-13116 : [string]_FACE$ table does not exist
  • ora-02837 : Unable to unlink temporary file
  • ora-27473 : argument string does not exist
  • ora-30135 : OCI Thread operation fails
  • ora-12838 : cannot read/modify an object after modifying it in parallel
  • ora-04092 : cannot string in a trigger
  • ora-00706 : error changing format of file 'string'
  • ora-29279 : SMTP permanent error: string
  • ora-10919 : Default temporary tablespace group must have at least one tablespace
  • ora-12057 : materialized view "string"."string" is INVALID and must complete refresh
  • ora-07241 : slemrd: read error.
  • ora-01521 : error in adding data files
  • ora-03261 : the tablespace string has only one file
  • ora-19024 : Cursor expression must be named
  • ora-24096 : invalid message state specified
  • ora-39308 : application or database upgrade internal error: "string"
  • ora-30038 : Cannot perform parallel insert on non-partitioned object
  • ora-07478 : scgcmn: cannot get lock status.
  • ora-29505 : AS keyword is invalid in CREATE JAVA CLASS or RESOURCE
  • ora-25298 : Only immediage visibility mode supported for buffered message enqueue or dequeue
  • ora-36157 : (XSMXAGGRCOMMIT) To use the AUTOCOMMIT keyword, you must also specify the AUTOUPDATE keyword.
  • ora-36706 : (XSRELTBL07) workspace object should be dimensioned by workspace object and one level dimension.
  • ora-01870 : the intervals or datetimes are not mutually comparable
  • ora-26076 : cannot set or reset value after direct path structure is allocated
  • ora-15104 : conflicting CONTENTS options
  • ora-16525 : the Data Guard broker is not yet available
  • ora-39766 : invaid stream specified for column array conversion
  • 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.