=================================================================

                        RELEASE NOTES
                             FOR
    IBM INFORMIX SPATIAL DATABLADE MODULE, VERSION 8.21.xC4
                       DATE: June 2010

=================================================================


TABLE OF CONTENTS

    I.   OVERVIEW OF RELEASE NOTES
   II.   IBM INFORMIX SERVER COMPATIBILITY
  III.   IBM INFORMIX SERVER CONFIGURATION
   IV.   INSTALLATION AND REGISTRATION
    V.   DATABLADE MODULE UPGRADE AND DOWNGRADE ISSUES
   VI.   SERVER CONVERSION AND REVERSION ISSUES
  VII.   LOGGED DATABASE ISSUES
 VIII.   SBSPACE ISSUES
   IX.   SHAPEFILE UTILITIES
    X.   NEW FEATURES
   XI.   KNOWN PROBLEMS AND LIMITATIONS
  XII.   FIXED PROBLEMS
 XIII.   DOCUMENTATION NOTES AND CORRECTIONS

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

I.  OVERVIEW OF RELEASE NOTES
=============================
The purpose of these release notes is to make you aware of any special
actions required to configure and use the IBM Informix Spatial DataBlade
module on your computer. In addition, this file contains information about
known bugs and their workarounds.

These release notes are not intended to be all-inclusive; they should be
used as an addendum to the "IBM Informix Spatial DataBlade Module User's
Guide," which provides thorough information about product features and
behavior.

These release notes are written for the following audience:

  o System administrators who install the IBM Informix Spatial DataBlade
    module

  o Database administrators who control access to databases that use the
    IBM Informix Spatial DataBlade module

  o Developers who write applications using the IBM Informix Spatial
    DataBlade module

General information about the Informix Spatial DataBlade module are 
available at 
    http://www.ibm.com/software/data/informix/blades/spatial.


II.  IBM INFORMIX SERVER COMPATIBILITY
======================================
Version 8.21.xC4 of the IBM Informix Spatial DataBlade module is compatible
with IBM Informix Dynamic Server version 10 or later.



III.  IBM INFORMIX SERVER CONFIGURATION
=======================================
Before you use the Spatial DataBlade module, note the following
prerequisites:

  o You must increase the STACKSIZE parameter in the IBM Informix Dynamic
    Server ONCONFIG configuration file to 64 (kilobytes).  If you fail to
    do this, you might experience intermittent stack overflow errors.  If
    you must change the ONCONFIG file, stop and restart the server for the
    change to take effect.

  o Before you register the Spatial DataBlade module, you must have a
    default sbspace with at least 8 KB of free space.  An sbspace stores 
    large objects.  The name of the default sbspace is defined by the 
    SBSPACENAME parameter in the ONCONFIG file. Use the onspaces utility 
    to create sbspaces.  See the Administrator's Guide for information 
    on creating an sbspace.

  o Before you register the Spatial DataBlade module, you must define
    the SYSSBSPACENAME parameter in the ONCONFIG file.  This defines the
    system sbspace, which is used by the server to store statistics
    gathered when you run UPDATE STATISTICS MEDIUM or HIGH on a table
    containing one or more spatial data columns.  Both SBSPACENAME and
    SYSSBSPACENAME parameters can have the same value.



IV.  INSTALLATION AND REGISTRATION
==================================
To use the Spatial DataBlade module, you must register it in each 
database in which it will be used.  See the "DataBlade Module
Installation and Registration Guide" for instructions on how to register
DataBlade modules.

The Spatial DataBlade module requires the IBM Informix R-Tree DataBlade
module, which is shipped with IBM Informix Dynamic Server.

If you are using BladeManager and you have not previously registered 
the IBM Informix R-Tree DataBlade module in your database, BladeManager 
prompts you as to whether you want to register it first. If you answer 
no, the registration of the Spatial DataBlade module is canceled.

If you are using the SYSBldPrepare( ) function, the IBM Informix R-Tree
DataBlade module is automatically registered when you register the
Spatial DataBlade module.

The Spatial DataBlade module will create one 8 KB smart large object in
the default sbspace during registration.  To move this smart large object
to a different sbspace, execute the following statements after 
registration:

    ALTER TABLE SE_MetadataTable PUT smd IN (mysbspace);
    EXECUTE FUNCTION SE_MetadataInit();



V.  DATABLADE MODULE UPGRADE AND DOWNGRADE ISSUES
=================================================

Upgrades:
---------
If you have version 8.20 of the Spatial DataBlade module registered
in a database, BladeManager automatically upgrades it
when you register the new version, while preserving any data that 
might already exist in the database.

Alternatively, you can recreate the databases:

1. Export all databases.
2. Drop all databases.
3. Migrate IDS from 32 bit to 64 bit.
4. Import all databases.

Reversions:
-----------
If you have version 8.21 of the Spatial DataBlade module registered in a
database and you want to revert to version 8.20, BladeManager
automatically performs a reversion when you register the old version,
while preserving any data that might already exist in the database.


VI.  SERVER CONVERSION AND REVERSION ISSUES
===========================================

See server release notes.

After server conversion and reversion, register
the target version of the Spatial DataBlade module.


VII.  LOGGED DATABASE ISSUES
============================
IBM recommends that you register the Spatial DataBlade module in a logged
database.

By having logging enabled, you might generate a huge number of log records
if you bulk load a large amount of spatial data into your database.  This
is often unnecessary if your data are relatively static or you will be
doing such a bulk load only once, or both.  To avoid unnecessary log
writes, IBM recommends the following procedure:

   1. Create a logged database.
   2. Register the Spatial DataBlade module.
   3. Turn off logging.
   4. Bulk load data.
   5. Create an R-tree index.
   6. Turn on logging.

See your Administrator's Guide for information about how to turn logging
on and off.


VIII.  SBSPACE ISSUES
=====================
The Spatial DataBlade module uses an sbspace whenever the storage space 
requirements of a geometry exceeds 930 bytes.  (This can happen if a 
polygon or linestring has more than 50 vertices.)  Therefore,
it is important that you create a default sbspace.  The SBSPACENAME 
parameter in the IBM Informix Dynamic Server ONCONFIG file
must point to a valid sbspace.  All geometries exceeding 930 bytes are 
stored in this sbspace unless a different sbspace has been specified 
with a PUT clause in the CREATE TABLE statement.  Use the onspaces 
utility to create sbspaces.  See the Administrator's Guide for 
information on creating an sbspace.

When you create an sbspace, by default, just the smart large object
metadata is logged and smart large object user data is not logged.  
This means that if the sbspace was created without user data logging, only
the smart large object metadata information can be restored, and large 
geometries cannot be restored.

Suppose you insert many values, and the system experiences a major
disk failure. You restore from backup, then apply the logical logs.
The end result will be different depending on how you created the 
sbspace:

   o If the sbspace was created with user data logging enabled,
     then both the smart large objects and the actual large values will 
     be restored.

   o If the sbspace was created with the default, then the smart
     large object metadata will be restored, but the actual values 
     will not.

You can create a logged sbspace with the -Df "LOGGING=ON" option.



IX.  SHAPEFILE UTILITIES
========================
The loadshp, unloadshp, and infoshp utilities can be used to load, unload,
and obtain information about shapefiles.  Refer to Appendix A of the
User's Guide for instructions in their use.

These programs require IBM Informix ESQL/C runtime libraries.  You must
install IBM Informix ClientSDK or IBM Informix Connect, version 2.90.xC4
or higher.

During DataBlade module installation, these programs are copied into the
server $INFORMIXDIR/bin directory.  You might want to copy these programs to
a different machine.  If so, the destination machine must have either IBM
Informix Client SDK or IBM Informix Connect installed.


X.  NEW FEATURES
================
N/A

XI.  KNOWN PROBLEMS AND LIMITATIONS
====================================
This section describes known problems with this release of the Spatial
DataBlade module and shows, where possible, how to work around these
problems.


1. ST_Transform() cannot perform datum transformations
------------------------------------------------------
The geographical coordinate systems of both the source and target spatial
reference systems must be the same.  (The geographical coordinate system
is defined by the spheroid, prime meridian, and angular units.)


2. No implicit coordinate transformations
-----------------------------------------
All functions with two ST_Geometry operands will raise error USE23
(spatial reference conflict) if the SRIDs of the operands are not
the same.  If you want to compare two geometries with different SRIDs
you can explicitly transform one, as in:

   SELECT * FROM tab1 a, tab2 b WHERE
     ST_Intersects(a.shape, ST_Transform(b.shape, ST_SRID(a.shape)));


3. No support for OGIS collections
----------------------------------
ST_GeomFromWKB() and ST_GeomFromWKT() do not support OGIS collections.


4. ST_Centroid() might not compute true centroid
----------------------------------------------
The ST_Centroid() function returns the center point of a polygon's
bounding box.  This might or might not be true centroid of the polygon.


5. SE_Generalize() returns error USE21
--------------------------------------
If the generalization threshold is large compared to the overall size
of the object, SE_Generalize() might return error USE21 (shape integrity
error).  This value has to be small enough for the function to return a 
generalized shape with an area. 


6. Errors in geometry cast do not cause exceptions to occur
-----------------------------------------------------------
As described in ESRI#00091925, casts from supertype to subtype are
implemented as no-op casts and do not raise any errors for casts that
do not make sense.  Furthermore, functions which take a specific subtype
(ST_StartPoint(), for example) will not raise an error if the input
argument is not the correct subtype; instead they will return null.

This design allows you to write queries like:

    SELECT ST_StartPoint(my_geometry_col::ST_LineString) from mytab;

and the query will not stop at the first row which is not an
ST_LineString.  If you want to filter out null values, you should write
queries like this:

    SELECT ST_StartPoint(my_geometry_col::ST_LineString) from mytab
      WHERE ST_GeometryType(my_geometry_col) = 'st_linestring';

7. Known Defects
----------------

CQ 1281
Spatial DataBlade cannot use blademgr to upgrade from 32 bit to 64 bit.


XII. FIXED PROBLEMS
====================
The following problems have been fixed in this release.

idsdb00183550
Memory corruption can occur if primary shape has less coordinate points than secondary shape

idsdb00183884
Excessive virtual segments dynamically allocated when loading spatial data

idsdb00186014
Unable to register spatial.8.21.FC3 over 8.21.FC1

idsdb00186923
unloadshp stores wrong definition for floating point DECIMALs and rounds values to int

idsdb00193870, idsdb00190499
upgrade problems from 8.21.UC2 to 8.21.FC2

idsdb00194268
after run with upgrade shell script, the DataBlade would not be able to further register/upgrade

idsdb00194552
upgrade by using register with 8.21.xC3 failed with "st_geometry_op still in use"

idsdb00194862
SE_EnvelopeAsGML function caused mem exception

idsdb00204700 
Win64: Registration of Spatial DataBlade fails with error -937 and /or memory corruption

idsdb00207280
Better to remove the DR message in the online.log

XIII. DOCUMENTATION NOTES AND CORRECTIONS
==========================================
There are no additional or changed features at this time.