From PTAGISWiki
Ingres Corporation
Ingres® 2006 Release 2 Service Pack 2
1.0 Welcome
2.0 Operating System Support
3.0 Installation Considerations
3.1 Upgrading ABF Applications
4.0 General Considerations
4.1 Features Not Included in Ingres 2006 Release 2 Service Pack 2
4.2 ANSI Date/Time Data Types
4.3 Behavioral Changes from Ingres Release 2.6 and Ingres 2006 to Ingres 2006 Release 2 Service Pack 2
4.4 OpenROAD® Support
4.5 Enterprise Access Support
4.6 ODBC Support
4.7 Unicode Support in Terminal Monitor
4.8 Selecting or Updating New Data Types from an Older Client
4.9 Web Deployment Option
5.0 Fixed Issues
6.0 Known Issues
6.1 DBMS Server and DBA Tools Issues
6.2 Web Deployment Option
6.3 Windows Installation Issues
6.4 Linux Installation Issues
7.0 Documentation
8.0 Your Support Options
1.0 Welcome
Before you start using the software, you should review this readme file for important information on the installation and use of the product.
The information provided here is for use with the following Ingres guides:
* Release Summary
* Quick Start Guide
* Installation Guide
* Migration Guide
For up-to-date information that is specific to your operating system, visit Ingres Technical Support at http://www.ingres.com/support.
Make sure that copies of this readme are distributed to the system administrator, database administrator, and
applications developers using Ingres at your site. This document contains information of interest to each of
these users.
2.0 Operating System Support
This version of Ingres is supported by the following operating system.
Click the link below to see important information specific to your platform:
Sun Solaris UltraSPARC
Please make sure that your operating system is supported by this version.
For complete information about all Ingres products and the platforms and operating system releases that they
run on, see the Product Availability Matrix at http://www.ingres.com/products/prod-availability-matrix.php.
3.0 Installation Considerations
Pay particular attention to the information in the Migration Guide section on preserving existing customizations
including config.dat parameters. Use the information in this readme in conjunction with the Installation Guide.
Note: Information in the readme supersedes information in the Installation Guide.
3.1 Upgrading ABF Applications
As part of column collation support added in Ingres r3 3.0.2, and included in this release, the data descriptor
used throughout the Ingres system has changed. This data descriptor is also compiled into imaged ABF applications.
All ABF applications created using Ingres r3 or earlier need to be re-imaged after upgrading. This is done by
deleting the contents of the ABF object directory, $ING_ABFDIR/<database-name>/<app-name>, and re-imaging.
4.0 General Considerations
4.1 Features Not Included in Ingres 2006 Release 2 Service Pack 2
Due to some unresolved problems, the following features are not currently supported in Ingres 2006 Service
Pack 2, but will be supported in a future release:
* International Language Message File Support
* Ingres Cluster Solution (Active-Active Only, the Failover Cluster Solution is supported)
The following feature is no longer available in Ingres:
* JDBC Server
4.2 ANSI Date/Time Data Types
The new date/time data types, while technically compliant with the ANSI specification, do not have the same
rich functionality as Ingres dates. We are reviewing enhancements to extend the functionality of the new types
for consistency and compatibility with prior releases and other database products. We welcome your input in
this process.
4.3 Behavioral Changes from Ingres Release 2.6 and Ingres 2006 to Ingres 2006 Release 2 Service Pack 2
Note the following behavioral changes when moving to Ingres 2006 Release 2 Service Pack 2 from Release 2.6
or 2006.
Installer Changes
This release includes a graphical installation wizard on Linux and Windows. Please reference the correct
platform readme for wizard startup instructions.
DAS Server Replaces JDBC Server
The functionality provided in prior releases by the JDBC Server has been moved to the Data Access Server (DAS).
The DAS provides greater functionality as it also provides connectivity from .NET Applications to Ingres.
The JDBC Server was deprecated in Ingres r3/2006 and is no longer distributed with the product. When Ingres
2006 r2 is installed, the JDBC Server configuration will be automatically migrated to the DAS Server. If the
DAS Server startup count is currently set to 0, it will set to 1 and the JDBC Server configuration information
will be removed from the configuration file (config.dat). For more information on the DAS Server, see the
Connectivity Guide.
Ingres Internal Threads on Linux
Internal threads are no longer supported on Linux. The II_THREAD_TYPE setting will be ignored, and Ingres
will default to Operating System threads.
Cache Memory Usage Increased
The DBMS server cache size defaults have been increased in Ingres 2006. This means that more virtual storage
will be required to run Ingres.
Ingres JDBC Driver Cursor Mode
The default cursor mode is now READONLY rather than allowing the DBMS to determine the mode. The original
behavior can be selected using the URL attribute CURSOR=DBMS or setting the property
ingres.jdbc.property.cursor_mode=dbms in the driver property file.
Ingres JDBC Driver Package
The original Ingres JDBC Driver and DataSources classes contained in the Java archive iijdbc.jar under the
Java package path of "ca.ingres.jdbc" are moved to the package path of "com.ingres.jdbc". The iijdbc.jar
archive included with Ingres 2006 also contains the original classes for backward compatibility. The original
"ca.ingres.jdbc" package path and classes will be removed from iijdbc.jar in the next major release. Existing
references to "ca.ingres.jdbc" classes will continue to work, but should be changed when convenient. New
references should use the package path of "com.ingres.jdbc".
4.4 OpenROAD® Support
This version of Ingres supports OpenROAD 2006 running in the local instance.
This version of Ingres does not support OpenROAD 4.1 running in the local instance. We recommend that OpenROAD
4.1 applications be run through Ingres Net.
For more information, visit http://www.ingres.com/support or contact technical support.
4.5 Enterprise Access Support
This version of Ingres does not support Enterprise Access 2.1 or 2.6 running in the local instance. For more
information, visit http://www.ingres.com/support or contact technical support.
4.6 ODBC Support
The Ingres ODBC driver can be used with the Ingres ODBC Call-level interface (CLI) or with a supported third-party
ODBC driver manager. For more information, see the Connectivity Guide.
4.7 Unicode Support in Terminal Monitor
The terminal monitor now supports displaying query results from Unicode columns by coercing them to local character
set. It will return an error if the Unicode character cannot be coerced to the local character set.
4.8 Selecting or Updating New Data Types from an Older Client
When connecting from an older version of the client to Ingres 2006 Release 2 Service Pack 2, if a query attempts to
select or update a new data type not supported by the client (for example, ANSI date/time types), you will receive
error E_US10F0.
4.9 Web Deployment Option
The Web Deployment Option is a deprecated feature and will be removed in a future release of Ingres.
5.0 Fixed Issues
For a list of bugs fixed since Ingres 2006 Release 1, see Knowledge Base document 415346. Note the version
identifier in this notice; it is required to access the document.
Knowledge Base Document 415346
6.0 Known Issues
For an informational solution or to see if a patch is available for the following known issues, visit
http://www.ingres.com/support or contact technical support.
6.1 DBMS Server and DBA Tools Issues
Reference Description
086877 Ingres Replicator does not work with partitioned tables.
110051
(Linux only) Database events may be lost if sent in quick succession between two sessions both connecting from the same ESQL program.
115716 SET IO_TRACE does not work when used along with SET PARALLEL
115717 Command “sql <database> -R<role>” prompts for a password even if the role is not assigned a password.
115718 MODIFY TABLE returns error E_QE0083 when modifying a table in a raw database location.
115721 XMLIMPORT utility failed to import UUID data that was generated with the GENXML utility. The error message generated during the XMLIMPORT phase, reads: [Fatal Error at file xmlout.xml, Message: Invalid character (Unicode: 0x19)]
115722 The XMLIMPORT utility fails to apply table or row level constraints to database objects generated with the GENXML utility.
116992 UNION SELECT on partitioned table returns wrong results. Same select on unpartitioned table returns correct results.
117345 Tuxedo test fails with locking problem. E_QS001E_ORPHANED_OBJ An orphaned Query Text object was found and destroyed during QSF session exit.
117479
(Windows only) Ingres Export Assistant will not export data with Unicode data types.
117866 The fraction portion of INTERVAL day to second literals is truncated to 6 places. Maximum allowable is 9.
117872
(Windows only) Error E_OP0791_ADE_INSTRGEN consistency check is returned from the following syntax: update junk set a1=a1-date('1 months') where a1='1-10'
117873 The maximum size of a sequence is 2147483647, even though it is possible to specify BigInt.
117874 Shutting down Ingres using a userid other than the Ingres Administrator displays a FATAL ERROR message, where a permission denied warning would be more appropriate.
117875 Configuration Manager fails to restore the original DATE_TYPE_ALIAS value when the RESTORE button is used.
118250 The MKRAWLOG script fails when HPUX /etc/default/security option SU_DEFAULT_PATH is set. MKRAWLOG will return errors "No such file or directory: ipcclean" and "csinsatll: command not found"
118493 In a concurrent processing environment, error "E_DMA42F_LG_UNMUTEX An error was encountered releasing mutually exclusive access to a logging system data structure" may occur. The configuration settings in CBF are; 100MB dual log, 2 DBMS servers, 2k page size and per_tx_limit=1000 for locking. The error was seen in Tru64 and HP-Itanium platforms. To avoid the error, increase the number for locking.
6.2 Web Deployment Option
Reference Description
115720 The Ingres Web Deployment Option does not currently support the Apache 2.x Web Server.
115723
(Linux Only) When the Web Deployment Option has been installed, shutting down the Data Access Server results in error “*** glibc detected *** free(): invalid pointer: ***”
6.3 Windows Installation Issues
Reference Description
117476 A dual transaction log fails to be created when a customized install requests one.
117478 Help missing from the install "Installation type" dialog.
117933 Setting DMF cache parameter to exceed 2Gig on Windows results in a SEGV, and after that Ingres Service Manager hangs and it must be restarted and Ingres has to be stopped.
6.4 Linux Installation Issues
Reference Description
115724 As of the time this readme was published, the installation of Ingres requires RPM with a version in the range 3.0.6 through 4.4.2, except for RPM version 4.1. If RPM 4.1 is installed, it must be upgraded to version 4.1.1 or higher before you can install Ingres.
RPM 4.1 fails to set environment variable RPM_INSTALL_PREFIX. Attempting to install Ingres with RPM 4.1 will lead to numerous “cannot find file” errors, and a failed install. For further details on this RPM bug, see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=75057.
117861 The GUI installer allows II_SYSTEM to be left blank and does not validate its value.
117871 The GUI installer for Linux does not install on x86 64-bit Linux systems.
117876 The Linux GUI installer incorrectly allows an install with only the "core" package selected, which results in an unusable installation.
7.0 Documentation
The Ingres documentation is provided in Portable Document Format (PDF). This documentation is available as a gzip
archive for all environments or as an installable RPM package for Linux.
For Linux platforms the Ingres documentation RPM will be installed to the /usr/share/doc directory.
The documentation can be downloaded from http://esd.ingres.com/product/docs.
8.0 Your Support Options
Enterprise customers with active maintenance and support contracts have full access to Ingres Support, including
telephone support and online use of our call tracking system and knowledge base, Service Desk. For Customer Support
contact details, see http://www.ingres.com/support/contact.php.
If you have an active support contract and want to register for access to Service Desk
(https://servicedesk.ingres.com ), use the enrollment form at http://www.ingres.com/users/register.php. (Your
six-digit Account Number/Site ID is required.)
If you do not have a support agreement for Ingres Corporation products and are interested in purchasing support,
contact us at sales@ingres.com.
For more information about support options, visit http://www.ingres.com/support.php.
Free support is available from the Ingres Open Source Community. Community members may obtain assistance for Ingres
Corporation products by registering with the Ingres Community Site and using the available tools. To register, go to
http://community.ingres.com/forums/home.php and click Register in the upper right corner of the page.
The Community Forums also provide Ingres Open Source Community members the opportunity to ask questions and interact
with other community members and Ingres Corporation technical staff. For more information, visit
http://community.ingres.com/forums/index.php.
Copyright © 2009 Ingres Corporation. All rights reserved.
