-------------------------------------------------------------------------------
Oracle8 Spatial Cartridge
Release 8.0.5
-------------------------------------------------------------------------------
TABLE OF CONTENTS
-----------------
Introduction
------------
0.1 Purpose
0.2 Cover Letter and Licensing
0.3 Documentation Available
Fixes and Enhancements
----------------------
1.1 SDO_WINDOW Package
1.2 SDO_GEOM.RELATE Function
Known Restrictions
------------------
2.1 SDO_WINDOW Package
2.1.1 CLEAN_WINDOW Procedure
2.1.2 BUILD_WINDOW Function
2.2 SDO_ADMIN.POPULATE_INDEX and SDO_ADMIN.UPDATE_INDEX Procedures
2.3 SDO_GEOM.VALIDATE_GEOMETRY Function
2.4 SDO_GEOM.RELATE function
Obsolescence Notice
-------------------
3.1 Obsoleted in this release: sdconv,sdload
3.2 Last supported release: SDO_GEOM.INTERACT function
******************
* *
* Introduction *
* *
******************
0.1 Purpose
-----------
This file is relevant only to the release 8.0.5 version of Oracle8 Spatial
Cartridge and its component parts, such as spatial functions and PL/SQL
packages. It lists differences between this version of the product and its
documented functionality. It also lists problems fixed in this release along
with known restrictions, including workarounds where
available.
Each platform on which this release of the Oracle8 Spatial Cartridge is
made available, such as UNIX, DEC VAX/VMS, or Windows NT, may also provide
platform-specific README documentation. There may also be additional README
files for other Oracle products. README files are provided in lieu of release
notes, system bulletins, or similar publications.
0.2 Cover Letter and Licensing
------------------------------
The cover letter included with your Oracle8 package contains important
information about licenses for Oracle8 product options.
0.3 Documentation Available
---------------------------
A??32539 Oracle8 (tm) Server Messages, Release 8.0
A??48124 Oracle8 Spatial Cartridge (tm) User's Guide and Reference,
Release 8.0.5
**************************
* *
* Fixes and Enhancements *
* *
**************************
1.1 SDO_WINDOW Package
-----------------------
Bug 424161
Installation the prvtwin.plb file by any Oracle user other than mdsys causes
the following PL/SQL compilation error -
PLS-00201: identifier 'MDERR.RAISE_MD_ERROR' must
be declared.
Bug 424185
The length used for the SDO_CODE and SDO_MAXCODE columns of the
<win_layer>_SDOINDEX table is always 255, instead of a length which is
appropriate to the definition of the dimensions for
the layer.
1.2 SDO_GEOM.RELATE Function
-----------------------------
Bug 433466
This function returns inconsistent results for two complex geometry types
when the relationship should evaluate to TOUCH.
Bug 433472
This function returns inconsistent results for two complex geometry types
when the relationship should evaluate to EQUAL.
Bug 438638
This function returns inconsistent results for two complex geometry types
when the relationship should evaluate to INSIDE.
Bug 546407
Maximum number of open cursors exceeded when using
"fast" Relate()
1.4 SDO_ADMIN.POPULATE_INDEX and SDO_ADMIN.UPDATE_INDEX Procedures
-------------------------------------------------------------------
Bug 556520
Point data takes too long to tile.
Bug 476044
UPDATE_INDEX_FIXED returns ORA-13011 when GID value is too large (i.e.
greater than a unsigned 4-byte integer)
**********************
* *
* Known Restrictions *
* *
**********************
2.1 SDO_WINDOW Package
-----------------------
2.1.1 CLEAN_WINDOW Procedure
----------------------------
Bug 426458
The Oracle sequence for the user's window layer is not dropped when the
win_layer parameter of this procedure is lowercase. Workaround is to supply
the win_layer parameter in uppercase.
2.1.2 BUILD_WINDOW Function
---------------------------
Bug 426461
This function fails with the following error when the win_layer parameter
is lowercase -
ORA-13158: Oracle object does not exist.
Workaround is to supply the win_layer parameter in
uppercase.
2.2 SDO_ADMIN.POPULATE_INDEX and SDO_ADMIN.UPDATE_INDEX Procedures
-------------------------------------------------------------------
Bug 442489
These procedures fail with the following error when the SDO_TOLERANCE column
of the <layername>_SDODIM table is set to .00000005 -
ORA-13027: GID not in layer.
The workaround is to increase the tolerance value. The error occurs because
the indexing procedures use the tolerance to determine
the tiling resolution.
Bug 667979
Populate_index() and Populate_Index_Fixed() may cause an ORA-600 error
on large <layername>_SDOGEOM tables. The usual cause is that the user has
insufficient rollback segment space. The workaround is to increase the
rollback segment size or use Update_Index_Fixed() in a loop to index the
<layername>_SDOGEOM table in batches of GIDs.
2.3 SDO_GEOM.VALIDATE_GEOMETRY Function
----------------------------------------
This function is not yet fully implemented. It does not completely verify
complex geometric elements of type polygon. Specifically, it will not check
for self-crossing polygons or internal elements (polygon holes or linestrings)
touching the external polygon element. It is the user's responsibility to
verify that all geometric elements of type polygon in the <layername>_SDOGEOM
table are valid.
2.4 SDO_GEOM.RELATE Function
----------------------------------------
This function may return incorrect results when the 'DETERMINE' flag is used
on complex geometries that are equal or nearly equal.
Incorrect results may also occur if vertices in a geometry are very close
to each other. That is, just beyond the distance denoted by the
specified SDO_TOLERANCE value.
The third known situation when erroneous results may occur is when two line
segments share a start or end vertex and are very
nearly paralell.
There is no workaround other than reducing the SDO_TOLERANCE value.
For example, if the SDO_TOLERANCE is 0.5E-07 then
reduce it to 0.5E-06.
***********************
* *
* Obsolescence Notice *
* *
***********************
3.1 Obsoleted in this Release: sdconv,sdload
------------------------------------------
This version of Oracle8 Spatial Cartridge Option is the first release to
exclude the sdconv and sdload utilities. These utilities were used to load
multidimensional point data into partitioned spatial tables. The sdconv
and sdload utilities are superseded by a new spatial partitioning mechanism
called server partitioning in this and all future releases. The server
partitioning functionality is available in the SDO_ADMIN PL/SQL package.
See the Oracle8 Spatial Cartridge User's Guide and Reference for details
regarding this new functionality. For this reason, the status of all
outstanding sdconv and sdload bugs has been changed to 83 (Closed,
Product/Platform Obsolete). There will be no fixes provided for the
following:
Bug 286514
Bug 325765
Bug 325766
Bug 351868
Bug 393130
Bug 401711
3.2 Last Supported Release: SDO_GEOM.INTERACT
------------------------------------------
SDO_GEOM.INTERACT() has been replaced by SDO_GEOM.RELATE with the
'ANYINTERACT' mask. Use SDO_GEOM.RELATE(layer1, gid1, 'ANYINTERACT',
layer2, gid2) in place of SDO_GEOM.INTERACT() wherever possible.