readme_spatial.txt

Debian中文参考手册,系统介绍了Debian系统

-------------------------------------------------------------------------------

                          Oracle9i Spatial 
                          Release 9.2.0.1 Production 

-------------------------------------------------------------------------------


TABLE OF CONTENTS
-----------------

Introduction
------------

0.1  Purpose
0.2  Cover Letter and Licensing
0.3  Documentation Available

Installation Notes
--------------------
1.1  Dependency on objects and extensible indexing
1.2  Manual installation 

Sample programs
------------------
2.1 OCI examples and MOTIF/NT viewers

Obsolescence Notice
-------------------

3.1  Last supported release: For all Relational interfaces

New Features in 9iR2
-------------------

4.1 New Functionaltiy and Features in 9iR2



******************
*                *
*  Introduction  *
*                *
******************

0.1 Purpose
-----------

   This file is relevant only to the release 9i version of Oracle9i Spatial
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. 

   Each platform on which this release of the Oracle9i Spatial 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 Oracle9i package contains important
information about licenses for Oracle9i product options.

0.3 Documentation Available
---------------------------

Oracle Spatial User's Guide and Reference 
Part Number A86770-01


***********************
*                     *
* Installation Notes  *
*                     *
***********************


1.0  Manual installation 
-------------------------
Manually installing Oracle9i Spatial after database creation involves the
following steps:
(i) Ensure that the Objects Option has been installed and catodci.plb 
    has been run.
(ii) Connect as SYSTEM AS SYSDBA and create the MDSYS user. 
     Run the $ORACLE_HOME/md/admin/mdprivs.sql file.
(iii) Connect as MDSYS and run 
      the script catmd.sql. This script is in $ORACLE_HOME/md/admin.
     This will install the Spatial product.


***********************
*                     *
* Sample programs     *
*                     *
***********************

2.1 OCI programs and viewers
-----------------------------
The ORACLE_HOME/md/demo directory contains subdirectories that have:
(i) some sample OCI programs in the directory demo/examples. These programs
    demonstrate the use the object type SDO_GEOMETRY and one possible means of
    transforming spatial data from the relational to object-relational 
    representation.
(ii) a simple MOTIF based viewer for spatial data that demonstrates the
     use of the spatial procedures and functions supported by the relational
     implementation of Oracle9i Spatial. This viewer works only on Unix
     platforms since it uses Motif libraries. The source is in 
     demo/unix/motif and its subdirectories. The makefiles were tested using
     GNU make and hence users may need to modify these Makefiles.



***********************
*                     *
* Obsolescence Notice *
*                     *
***********************

3.1 Last Supported Release
------------------------------------------
All the Relational model interfaces will not  be supported from the
next major release. So this will be the last
supported release for all the relational model interfaces.

3.2 SDO_CS.VIEWPORT_TRANSFORM to_srname Parameter Not Supported 

*************************
*                       *
* New Features in 9iR2  *
*                       *
*************************

1. Validation with Context 

You can now validate a geometry or a layer and obtain additional information 
about the context (the coordinate, edge, or ring) that causes any 
geometry to be invalid. 

2. Utility Functions 

A new Spatial utility package (SDO_UTIL) is provided, with the following 
functions. 

  The SDO_UTIL.EXTRACT function returns the geometry that represents a 
  specified element (and optionally a ring) of the input geometry. 

  The SDO_UTIL.GETVERTICES function returns the coordinates of the vertices 
  of the input geometry. 

3. Partitioned Spatial Indexes: Splitting and Merging Supported 

4. Exchanging Partitions Including Indexes 

5. Parallel Index Creation and Rebuilding 

6. Deferred Modifications to an Index 

 Geodetic data support:
 ======================

From 9i, Spatial has a new computational geometryengine which will 
understand geodetic data and the geodetic operations are done instead
of cartesian operations for geodetic data.

This introduces a whole new set of functionality for geodetic data in 9i 
(refer to the documentation for more detils).

The tolerance is treated differently for geodetic compared to
what it was for cartesian data.
If you have geodetic data in a 8i release of the product and
would like to take advantage of all the new functionality for geodetic
data in 9i, you need to drop and recreate your spaital indexes.
The metadata also needs to be updates with appropriate tolerance
for the geodetic data.



 Other enhancemetns (in 9iR1):
 ====================

    The SDO_GTYPE element of the SDO_GEOMETRY type has a new format
    that identifies the linear referencing dimension (if any). 

    Methods are provided for the SDO_GEOMETRY type: GET_GTYPE, 
    GET_DIMENSIONS, GET_LRS_DIMS.

    Spatial aggregate functions are provided: SDO_AGGR_MBR, SDO_AGGR_UNION,
    SDO_AGGR_BUFFER, SDO_AGGR_CONVEXHULL. 

    The SDO_GEOMETRY type can be embedded in a user-defined data type. 

    Partitioned indexes are supported. 

    Coordinate system support has been enhanced: storage and conversion of 
    coordinates in any datum and projection; new system tables for supported 
    angle units, datums, ellipsoids, and projections; local
    coordinate systems; and user-defined coordinate systems. 

    Linear referencing support enhancements include support for additional 
    kinds of geometric segments (multiple line strings and 2D polygons, 
    in addition to line strings), _3D function formats,
    monotonically decreasing as well as increasing measure, several new 
    functions, and aggregate concatenation. 

    The new SDO_MIGRATE.TO_CURRENT procedure is provided to migrate from 
    previous Spatial releases to the current release. 

    R-tree index administration functions are provided, to check the quality 
    of the index and minimize query performance degradation. 

    Columns have been added to the spatial index views 
    (xxx_SDO_INDEX_METADATA).

    New views are provided for retrieving basic information about 
    spatial indexes: xxx_SDO_INDEX_INFO. 

    Unit of measurement support (for example, MILE for distance units 
    in miles) is provided for relevant Spatial functions and operators. 

    A function to return the minimum bounding rectangle of a geometry 
    (SDO_GEOM.SDO_MBR) is provided. 

    A commit interval can be specified when validating a layer.


    The SDO_VERSION function returns the Spatial release (version) number. 

    The 18-character limit for spatial index names is removed. 
 
    Layer level type constraints can now be enforced through a spatial
    index. During the index creation, the layer_gtype can be set to
    any of the vlaid type names and this type will be enforced for
    all data for that layer. Inserts and updates will be type checked
    for consistency.
    In addition, when the data is POINT only, it is strongly recommended
    that the layer_gtype=POINT constraint be used. Setting this 
    constraint for POINT only data would give
    better performance for most of the spatial operations.