Search Results drop_topo_map

Overview

The MDSYS.SDO_TOPO_MAP package is a component of Oracle Spatial and Graph topology support. It exposes a Java-backed PL/SQL interface for creating, loading, editing, and persisting in-memory topology maps. A topology map is a working copy of a portion of a spatial topology — a network of nodes, edges, and faces — that can be edited programmatically before the changes are validated and committed back to the underlying topology tables. In the context of Oracle EBS 12.1.1 and 12.2.2, the package is owned by MDSYS and classified as OTHER under the APPS synonym framework. It is not an EBS business API in the conventional sense; rather, it is infrastructure used by spatial and network-oriented applications (for example, GIS-enabled utilities, telecom, transportation, or field service layouts) that store and edit topological geometry.

Because the package relies on Java stored procedures (LANGUAGE JAVA), its use requires an Oracle JVM within the database, and the invoking database user must have appropriate privileges on MDSYS objects. EBS customers typically encounter it only where Oracle Spatial is licensed and topology data models are in use.

Key Procedures and Functions

ETRM 12.2.2 documents 87 procedures and functions. The principal routines include:

• SET_MAX_MEMORY_SIZE — Configures the maximum JVM memory available for topology map operations.
• CREATE_TOPO_MAP — Creates a named topology map, optionally pre-sizing it by number of edges, nodes, and faces.
• LIST_TOPO_MAPS / GET_TOPO_NAME — Enumerate existing topology maps and resolve the topology associated with a given map.
• LOAD_TOPO_MAP — Loads a window of topology data (bounded by X/Y extents) into memory, with options to allow updates and build indexes.
• CREATE_EDGE_INDEX / CREATE_FACE_INDEX — Build R-tree indexes over edges and faces to accelerate spatial searches.
• UPDATE_TOPO_MAP / COMMIT_TOPO_MAP / ROLLBACK_TOPO_MAP / CLEAR_TOPO_MAP — Persist edits, discard changes, or reset the working map.
• DROP_TOPO_MAP / VALIDATE_TOPO_MAP — Remove a map or verify its topological consistency.
• SEARCH_FACE_RTREE_TOPO_MAP / SEARCH_EDGE_RTREE_TOPO_MAP — Perform indexed spatial searches within the map.
• GET_NODE_CHANGES / GET_EDGE_CHANGES / GET_FACE_CHANGES / GET_NODE_ADDITIONS / GET_EDGE_ADDITIONS — Return the change sets accumulated against the in-memory map, supporting audit and synchronization workflows.

Tables Accessed

The ETRM record lists no APPS-synonym tables referenced by this package. Internally, topology maps operate against MDSYS-owned topology metadata and feature tables (for example, the node, edge, and face tables created when a topology is defined). Because these are accessed through MDSYS, EBS synonym mappings are not documented, and direct references from the APPS schema are not expected.

Usage Notes

SDO_TOPO_MAP is custom-code oriented. It is not invoked by standard EBS forms or concurrent programs, and it is referenced by zero other packages per the ETRM record. It is typically called from custom PL/SQL, EBS-hosted Java, or database jobs that need to edit spatial topology programmatically — for example, loading a map, editing node/edge geometry, validating, and committing. The frequently searched term sdo_number_array relates to the MDSYS.SDO_NUMBER_ARRAY type used with Spatial coordinate arguments; it is not itself a member of this package, but it appears alongside topology editing routines when coordinates are passed. Administrators should confirm Spatial licensing, JVM availability, and MDSYS execute privileges before relying on these routines in an EBS environment.