Oracle Spatial User's Guide and Reference Release 8.1.6 A77132-01 |
|
The procedures described in this chapter let you upgrade geometry tables from previous releases of Spatial Cartridge or Spatial Data Option.
This chapter contains descriptions of the migration procedures shown in Table 8-1.
Migrates data from Spatial release 8.1.5 to the current release.
SDO_MIGRATE.FROM_815_TO_81X(
Table with geometry objects.
See Section B.5 for important information about migrating from Spatial release 8.1.5.
All geometry objects in tabname will be migrated so that their SDO_GTYPE and SDO_ETYPE values are in the release 8.1.6 format.
The following example changes the definitions of geometry objects in the roads table from the release 8.1.5 format to the format of the current release.
SQL> execute sdo_migrate('ROADS');
Migrates data from a previous release of Spatial Data Option to release 7.3.4.
SDO_MIGRATE.TO_734(
Schema name of the owner of layer.
Name of the layer to be migrated.
Type of tesselation (indexing) to be used: FIXED or VARIABLE.
Parameter whose significance depends on tess_type:
None.
For fixed-size tessellation:
SQL> execute sdo_migrate.to_734('HERMAN', 'ROADS', 'FIXED', 10);
For variable-sized tessellation:
SQL> execute sdo_migrate_to_734('HERMAN', 'ROADS', 'VARIABLE',4);
Migrates data from a previous release of Spatial Cartridge or Spatial Data Option to Oracle Spatial release 8.1.5.
SDO_MIGRATE.TO_81X(
layer IN VARCHAR2,
newtabname IN VARCHAR2,
gidcolumn IN VARCHAR2,
geocolname IN VARCHAR2,
layer_gtype IN VARCHAR2,
updateflag IN VARCHAR2);
Name of the layer to be migrated.
Name of the new table to which you are migrating the data.
The name of the column in which to store the GID from the old table.
Name of the column in the new table where the geometry objects will be inserted.
One of the following values: POINT or NOTPOINT (default).
If the layer you are migrating is composed solely of point data, set this parameter to 'POINT' for optimal performance; otherwise, set this parameter to 'NOTPOINT'.
One of the following values: UPDATE or INSERT (default).
If you are migrating the layer into an existing populated attribute table, set this parameter to 'UPDATE'; otherwise, set this parameter to 'INSERT'.
Consider the following when using this procedure:
Insert point-only data into new rows:
execute sdo_migrate.to_81x('raptor', 'raptor', 'sdo_gid', 'feature', 'point');
Insert nonpoint data into new rows:
execute sdo_migrate.to_81x('BTU', 'BTU', 'sdo_gid', 'feature');
Update point-only data into existing rows:
execute sdo_migrate.to_81x('raptor', 'raptor', 'sdo_gid', 'feature',
'point', 'update');
Update nonpoint data into existing rows:
execute sdo_migrate.to_81x('BTU', 'BTU', 'sdo_gid', 'feature',
'notpoint', 'update');
Called at the source database when migrating from one 8.1.5 database to another 8.1.5 database. The procedure migrates OGIS metadata entries from schemas owned by MDSYS.
SDO_MIGRATE.OGIS_METADATA_FROM
None.
Consider the following when using this procedure:
Used at the destination database when migrating from one 8.1.5 database to another 8.1.5 database. The procedure migrates OGIS metadata entries from schemas owned by MDSYS.
SDO_MIGRATE.OGIS_METADATA_TO
None.
Consider the following when using this procedure:
|
![]() Copyright © 1999 Oracle Corporation. All Rights Reserved. |
|