Oracle Spatial User's Guide and Reference - InfoLab

SDO_MIGRATE.TO_CURRENT
Usage Notes for Object-Relational Model Upgrade
All geometry objects in tabname will be upgraded so that their SDO_GTYPE and
SDO_ETYPE values are in the format of the current release:
■ SDO_GTYPE values of 4 digits are created, using the format (dltt) shown in
Table 2–1 in Section 2.2.1.
■ SDO_ETYPE values are as discussed in Section 2.2.4.
The procedure also orders geometries so that exterior rings are followed by their
interior rings, and saves them in the correct rotation (counterclockwise for exterior
rings, and clockwise for interior rings).
Usage Notes for Relational Model Upgrade
Examples
Consider the following when using this procedure:
■ The new table must be created before calling this procedure.
■ The procedure converts geometries from the relational model to the
object-relational model.
■ A commit operation is performed by this procedure.
■ If any of the upgrade steps fails, nothing is upgraded for the layer.
■ layer is the underlying layer name, without the _SDOGEOM suffix.
■ The old SDO_GID is stored in gidcolumn.
■ SDO_GTYPE values of 4 digits are created, using the format (dltt) shown in
Table 2–1 in Section 2.2.1.
■ SDO_ETYPE values are created, using the values discussed in Section 2.2.4.
■ The procedure orders geometries so that exterior rings are followed by their
interior rings, and saves them in the correct rotation (counterclockwise for
exterior rings, and clockwise for interior rings).
The following example changes the definitions of geometry objects in the ROADS
table from the release 8.1.5 or higher format to the format of the current release.
SQL> execute sdo_migrate.to_current('ROADS');
17-4 Oracle Spatial User’s Guide and Reference