Oracle Spatial User's Guide and Reference Release 9.0.1 Part Number A88805-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 16-1.
SDO_MIGRATE.FROM_815_TO_81X(
Migrates data from Spatial release 8.1.5 to the current release.
Table with geometry objects.
Number of geometries to migrate before Spatial performs an internal commit operation. If commit_int is not specified, no internal commit operations are performed during the migration.
If you specify a commit_int value, you can use a smaller rollback segment than would otherwise be needed.
See Section A.4 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 format of the current release:
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).
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.from_815_to_81x('ROADS');
SDO_MIGRATE.OGIS_METADATA_FROM
Called at the source database when migrating from one 8.1.5 database to another 8.1.5 database. The procedure migrates OGIS (OpenGIS) metadata entries from schemas owned by MDSYS.
None.
Consider the following when using this procedure:
SDO_MIGRATE.OGIS_METADATA_TO
Used at the destination database when migrating from one 8.1.5 database to another 8.1.5 database. The procedure migrates OGIS (OpenGIS) metadata entries from schemas owned by MDSYS.
None.
Consider the following when using this procedure:
SDO_MIGRATE.TO_734(
Migrates data from a previous release of Spatial Data Option to release 7.3.4.
Schema name of the owner of layer.
Name of the layer to be migrated.
Type of tessellation (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);
SDO_MIGRATE.TO_81X(
layer IN VARCHAR2,
newtabname IN VARCHAR2,
gidcolumn IN VARCHAR2,
geocolname IN VARCHAR2,
layer_gtype IN VARCHAR2,
updateflag IN VARCHAR2);
Migrates data from a previous release of Spatial Cartridge or Spatial Data Option to the current release of Oracle Spatial.
Name of the layer to be migrated.
Name of the new table to which you are migrating the data.
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. If you set the value to POINT and the layer contains any nonpoint geometries, the migration might produce invalid data.
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 in existing rows:
execute sdo_migrate.to_81x('raptor', 'raptor', 'sdo_gid', 'feature',
'point', 'update');
Update nonpoint data in existing rows:
execute sdo_migrate.to_81x('BTU', 'BTU', 'sdo_gid', 'feature',
'notpoint', 'update');
SDO_MIGRATE.TO_CURRENT(
or
SDO_MIGRATE.TO_CURRENT(
SDO_MIGRATE.TO_CURRENT(
layer IN VARCHAR2,
newtabname IN VARCHAR2,
gidcolumn IN VARCHAR2,
geocolname IN VARCHAR2,
layer_gtype IN VARCHAR2,
updateflag IN VARCHAR2);
Migrates data from a previous Spatial release to the current release. The format depends on whether you are migrating from the Spatial relational model (release 8.1.5 or lower) or object-relational model (release 8.1.6 or higher). See the Usage Notes for the model that applies to you.
You are encouraged to use this procedure instead of the SDO_MIGRATE.FROM_815_TO_81X or SDO_MIGRATE.TO_81X procedure.
Table with geometry objects.
Column in tabname that contains geometry objects. If column_name is not specified or is specified as null, the column containing geometry objects is migrated.
Number of geometries to migrate before Spatial performs an internal commit operation. If commit_int is not specified, no internal commit operations are performed during the migration.
If you specify a commit_int value, you can use a smaller rollback segment than would otherwise be needed.
Name of the layer to be migrated.
Name of the new table to which you are migrating the data.
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. If you set the value to POINT and the layer contains any nonpoint geometries, the migration might produce invalid data.
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.
See Section A.4 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 format of the current release:
The procedure also orders geometries so that exterior rings are followed by their interior rings, and saves them in the correct rotation (counter clockwise for exterior rings, and clockwise for interior rings).
Consider the following when using this procedure:
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');
|
Copyright © 1996-2001, Oracle Corporation. All Rights Reserved. |
|