Official documentation for patch 12964

From PTAGISWiki

Jump to: navigation, search
Patch 12964 for Ingres 2006 Release 2 Service Pack 1 (9.1.1) on Sun Solaris UltraSPARC


Patch 12964 for Ingres 2006 Release 2 Service Pack 1 (9.1.1) on Sun Solaris UltraSPARC
  1.0 Welcome
  2.0 Installation Considerations
    2.1 Installation on UNIX platforms
    2.2 Uninstalling on UNIX Platforms
    2.3 Installation on Windows platforms
    2.4 Uninstalling on Windows platforms
    2.5 Installation on AlphaVMS platforms
    2.6 Uninstalling on AlphaVMS Platforms
  3.0 General Considerations
  4.0 Contacting Technical Support

1.0 Welcome

Welcome to Patch 12964 for Ingres 2006 Release 2 Service Pack 1 (9.1.1) on Sun Solaris UltraSPARC. This patch.html contains important information about patch 12964. Instructions to install / uninstall patches are provided for all platforms. This patch may only be installed over II 9.1.1 (su9.us5/103). Please follow the instructions for the associated platform. This patch.html also contains a list of all the bugs that this patch addresses, and technical support contact information. Please visit the Ingres Relational Database product page at http://ingres.com/ for more information.

2.0 Installation Considerations

Please be sure to read the release notes for the following bugs as they require additional steps for remediation over and above applying the patch:

      118405
      119428
      119632
      119712
      119826
      119961

If there are no bugs listed above, please ignore this section.

For sites using the Spatial Object Libraries a separate SOL patch may be required in order to maintain installation consistency. This will only be required if a SOL patch exists for this patch level.

A SOL patch does not exist for this patch level.

If required, installation instructions are exactly the same as described below with the only difference being that the string p12964 is replaced with p12964_SOL and patch12964 is replaced with patch12964_SOL.

2.1 Installation on UNIX/Linux platforms

To install this patch on UNIX/Linux platforms:

   1.

      Log onto your system using the installation owner account.
   2.

      Change directory to the root directory of the Ingres installation or use a previously created directory.

      cd $II_SYSTEM/ingres

      or

      cd <patch_directory>

   3.

      Load the patch media into the tape or cdrom drive, or copy the downloaded p12964.tar.Z file into the current directory and uncompress.
   4.

      Read in the patch media with the following commands:

      umask 022
      tar xf [device_or_p12964.tar] patch12964

      Note: If the device name is not known the system administrator should be contacted.

      This will create the directory:

      $II_SYSTEM/ingres/patch12964

      or

      <patch_directory>/patch12964

   5.

      Stop all Ingres processes with the "ingstop" utility.

      ingstop

   6.

      Change directory to the patch directory.

      cd patch12964

   7.

      Within the patch directory, run the command

      ./utility/iiinstaller

      which will perform the following actions:
          *

            Determine which Ingres packages are installed [see Note 1]
          *

            Verify the contents of the patch directory
          *

            Temporarily save the files that will be over-written [see Note 2]
          *

            Copy all files from the patch directory to the appropriate Ingres directories
          *

            Verify the installed files
          *

            Automatically relink the iimerge if any of the following three conditions are true:
                o The file $II_SYSTEM/ingres/files/iilink.opt exists.
                o The file $II_SYSTEM/ingres/files/iilink.rsp exists.
                o The installation uses a shared library DBMS. 

      Note 1: If additional Ingres packages are installed subsequent to the application of patch p12964, then the patch must be re-applied to attain a coherent and supported installation. Otherwise the newly installed packages may be missing changes from the patch that would be required for consistency with the previously installed and patched packages. Once p12964 has been successfully re-applied the installation will be in a consistent state.

      Note 2: By default, this command will back up every currently installed file in the installation. To disable, supply the "-i" flag.
   8.

      Relinking iimerge

      For sites not using UDTs (User-defined Data Types), proceed to the next step.

      Relink the iimerge binary by entering the following command:

      iilink

      This step can be automated by creating an options and/or a response file for use with iilink. The existence of either file will cause iiinstaller to automatically run iilink during patch installation.
          * If you pass command line options to iilink add them to a single line text file called $II_SYSTEM/ingres/files/iilink.opt. Linux users need to create an empty file otherwise the installer will default to "iilink -noudt". To test the options file run:
                o iilink `cat $II_SYSTEM/ingres/files/iilink.opt` 
          * User responses to iilink prompts can be automated by creating a text file called $II_SYSTEM/ingres/files/iilink.rsp. To test the response file run:
                o cat $II_SYSTEM/ingres/files/iilink.rsp | iilink <options> 
          * The user is responsible for the creation, use and testing of options/response files. 

      Note: For full details of the use of iilink and its parameters, see the Ingres Relational Database documentation.

   9.

      Restart the Ingres installation with the "ingstart" utility.

      ingstart

2.2 Uninstalling on UNIX/Linux Platforms

Providing the patch was installed with a backup made, the patch may be uninstalled using the following procedure:

   1. Change directory into the directory used as the backup during patch installation. For example, $II_SYSTEM/ingres/install/backup/pre-p12964_1.

      For AIX platform, run OS command "slibclean" to remove any unused modules in the shared library region.

   2. Run the following command to restore the files contained in the backup:

          * tar cf - . | ( cd $II_SYSTEM/ingres; tar xvf - )

                o If any of the following files were restored the protection level will need to be reset

          * chmod 4755 $II_SYSTEM/ingres/bin/iimerge

          * chmod 4755 $II_SYSTEM/ingres/bin/upgradedb

          * chmod 4755 $II_SYSTEM/ingres/bin/verifydb

          * chmod 4755 $II_SYSTEM/ingres/utility/csreport

          * cd ..; rm -rf $II_SYSTEM/ingres/install/backup/pre-p12964_1

          * rm -rf $II_SYSTEM/ingres/install/control/*p12964_1.dat 

      If you have multiple backup directories from multiple patch installations care should be taken when deciding which backup directory to use. For example, if patch 1 was installed, and then later patch 2, uninstalling using the patch 1 backup will cause both patch 1 and 2 to be uninstalled. If you have any doubts please contact your local Ingres Technical Support.

      WARNING: Installation of additional Ingres packages from the Ingres distribution media will invalidate your patch backups. Following the installation of an additional Ingres package from the distribution media you should re-apply patch p12964 to ensure the additional packages are patched correctly. Taking a new installation backup is required.

2.3 Installation on Windows platforms

To install this patch on Windows platforms:

   1.

      Log on to your Windows machine. To install this patch on the Ingres DBMS, you must log on as the installation owner. For client installations you can log on as any user.
   2.

      The Ingres patch installer will attempt to stop all Ingres processes for the specified Ingres instance before installing the patch. Alternatively this can be done manually using the INGSTOP utility or through the Ingres Visual Manager (IVM). You will also need to stop IVM either by issuing the command "ivm -stop" or by right clicking on the IVM icon and choosing the Exit menu option. You should also shutdown any non-Ingres application(s) that may be connected to, or using any of the files in the specified Ingres instance.
   3.

      If the patch has been supplied on CD media then load the CD into the drive. If you have downloaded the patch from the Ingres web site or if
      the CD you received contains a ZIP file, then you should first un-ZIP the ZIP file into a temporary directory.
   4.

      Run PatchUpdate.exe from the CD drive or from the temporary directory. Note: PatchUpdate.exe takes several parameters:
           /id <installation id> will bypass the dialog that allows you to choose installation id where you patch will be installed.
           /id <installation id> /silent will run silent installation on installation specified via installation id.
   5.

      Follow the instructions displayed on the screen to complete the patch installation.
   6.

      If this patch includes a fix for dotnet provider drag and drop II_SYSTEM/ingres/dotnet/assembly/v1.1 into %SystemRoot%\assembly.
   7.

      If required, restart the Ingres IVM process.
   8.

      Restart the Ingres instance.

During installation the following options are available:

   1.

      "Install" - This option installs the patch.
   2.

      "Exit Installation" - This option will terminate the patch installation without installing the patch.

2.4 Uninstalling on Windows Platforms

To uninstall this patch on Windows platforms:

   1.

      Open Control Panel Dialog.
   2.

      Open Add/Remove Programs Dialog.
   3.

      Find the target instance of Ingres in the Add/Remove Programs Dialog and select "Change/Remove" button.
   4.

      At Modify/Repair/Remove dialog choose Repair option and click Next.
   5.

      After the files are restored click the Finish button. The installation will now be at its original unpatched state.
   6.

      At this point you can reinstall any previously supplied patch.

2.5 Installation on AlphaVMS platforms

To install this patch on AlphaVMS platforms:

   1.

      Log onto your system using the installation owner account.
   2.

      Change directory to the root directory of the Ingres installation, or to a previously created directory.

      $ SET DEFAULT II_SYSTEM:[INGRES]

      or

      $ SET DEFAULT <patch_directory>

   3.

      Load the patch media into the tape or cdrom drive, or copy the downloaded p12964.zip file into the current directory.

      If the patch has been provided on CD, then mount the CD with the following command;

      $ MOUNT/OVERRIDE=IDENTIFICATION/MEDIA=CDROM/UNDEFINED=(FIX:CR:32256) <cd dev>

      If the patch has been provided by FTP, then unzip the p12964.zip file using the following command;

      $ UNZIP P12964.ZIP

   4.

      Patch P12964 can be installed using the provided IIPATCH.COM or using the IIPATCH.COM distributed inside the P12964.BCK saveset.

      Copy IIPATCH.COM into the II_SYSTEM:[INGRES.UTILITY] or extract IIPATCH.COM from the save set using the following command;

      $ BACKUP P12964.BCK/SAV /SELECT=[INGRES.UTILITY]IIPATCH.COM  /NEW_VERSION II_SYSTEM:[INGRES.UTILITY]

   5.

      To install the patch use the following command

      $ @II_SYSTEM:[INGRES.UTILITY]IIPATCH.COM INSTALL P12964.BCK

      This command will perform the following actions:
          *

            Optionally save the files that will be over-written
          *

            Stop Ingres before installing the required files.
          *

            Copy files for the installed packages from the patch to the appropriate Ingres directories
          *

            Prompt whether the Ingres installation should be started once the new files are installed.

      Note: By default, this command will back up those files in the installation, which will be overwritten by the patch. To disable, supply the "-T" flag.

      For more information on the IIPATCH utility use.

      $ @II_SYSTEM:[INGRES.UTILITY]IIPATCH.COM HELP

2.6 Uninstalling on AlphaVMS Platforms

Providing the patch was installed with a backup made, the patch may be uninstalled using the following procedure:

   1.

      Change directory into the directory that contains the uninstall saveset created during the installation. For example, II_SYSTEM:[INGRES]
   2.

      Run the following command to restore the files contained in the backup:

      $ @II_SYSTEM:[INGRES.UTILITY]IIPATCH.COM UNINSTALL P12964.UBK
          

3.0 General Considerations

The following reported bugs have been resolved with this patch. For reference, each bug is listed with its published bug identifier, and the operating systems to which it applies.   

 
Bugs addressed with this patch
Bug 101117 (GENERIC)

Failures during usermod can lead to non-persistent objects being dropped without warning.
Bug 102500 (GENERIC)

Errors E_QE0242 E_IC003C reported from accessdb when extending a database to a work location and then altering that work location to an auxiliary location. Error E_LQ006A can also be reported when you try to extend a database to a work location and then alter it.
Bug 110505 (GENERIC)

The output from auditdb shows the incorrect column value for the NEW record when updating a column from a non-null value to a nullable value.
Bug 110708 (GENERIC)

The WITH CHECK OPTION should not be specified on a non-updateable view. Allowing such views to be created by disabling the WITH CHECK OPTION may cause reloading a database abort due to the \nocontinue contained in the copy.in script.
Bug 110870 (GENERIC)

Attempting to add a foreign key constraint referencing a column beginning with 'ii' fails with E_US0981 `<column-name>' is not a valid parameter/local variable name. Name must not start with `ii'.
Bug 111911 (GENERIC)

The blocking sid/pid reported in the E_DM9043_LOCK_TIMEOUT error message is sometimes the same sid/pid as the reporting session's sid/pid.
Bug 115495 (GENERIC)

E_DM9043_LOCK_TIMEOUT lock timeout error message displays "?" instead of the table owner.
Bug 115857 (GENERIC)

Integer value zero is sometimes replaced by a random value or a NULL in a DB procedure call, if it is the first statement in the calling procedure.
Bug 116547 (GENERIC)

A session which is interrupted, then COMMITTED may report an E_QE0002 error followed by an SIGSEGV.
Bug 116600 (GENERIC)

Sessions die with an E_QE0002 error followed by a Segmentation Violation (SIGSEGV), eventually the DBMS Server will also die. Stack trace either qeq_validate, qen_qp,qea_fetch, qen_qp, qea_fetch, qeq_query, qef_call, scs_sequencer & CSMT_setup, or : qea_fetch, qen_qp, qea_fetch, qeq_query, qef_call, scs_sequencer & CSMT_setup. Occurs as a result of a cursor query using >15 parameters.
Bug 116911 (UNIX & WINDOWS)

Ingres needs a portable GUI tool for generating Ingres installation response files.
Bug 117217 (GENERIC)

copydb does not include page_size modifications to primary key constraints.
Bug 117218 (GENERIC)

Executing a CASE statement with a subselect crashes the session out of the DBMS server with E_SC0206.
Bug 117555 (VMS)

In a heavily concurrent cluster environment with two or more nodes, the distributed deadlock thread of the Recovery server may cause the Ingres installation to hang.
Bug 117590 (WINDOWS AND UNIX ONLY)

Remove invocation of gethostbyaddr() for network listens via TCP on the Comm Server, the JDBC Server, and the DAS Server. This can improve performance and lessen the chances of query timeouts.

NOTE: on Windows, the II_WINTCP_LOG_REM_HOST and II_TCPIP_LOG_REM_HOST environment variables are no longer supported.
Bug 118211 (GENERIC)

select dbmsinfo('charset') returns a blank row.
Bug 118233 (GENERIC)

The RCP server doesn't deregister with name server when it exits, message "E_GC0155_GCN_SRV_FAILURE" occurs in errlog.log during ingstop.
Bug 118366 (GENERIC)

Server returns wrong result when selecting from a view with a where clause which restricts data from a column in the view to 'is null'. The view is defined as an outer join on a table with another union view, which is defined as a union of user query(s).
Bug 118387 (GENERIC, CLUSTER)

Support the documented "-NODENUMBER n" command line option. Modify to support running IIMKCLUSTER with node number specified. (E.g. IIMKCLUSTER -NODENUMBER 2) will set the node number (cluster_id) in config.dat to 2.
Bug 118402 (VMS)

The current version limit of 20 for CONFIG.DAT is sufficient to exhaust the history of the file as several versions are generated, and making reversion to a good earlier version impossible.

Modify IISUNODE to not purge CONFIG.DAT file at the end to retain older versions of the file.
Bug 118405 (ATTENTION, GENERIC)

A SELECT query containing more than one IFNULL() with an aggregate operand, or more than one aggregate operand and an IFNULL(), fails with E_OP0681_UNKNOWN_NODE if used in a view, with a global temporary table, or with a cursor.

Note: Views affected by this bug must be dropped and recreated after the application of the patch.
Bug 118421 (GENERIC)

The header files added by the esqlc precompiler (such as eqdef.h, eqsqlca.h etc.) should contain the usual #ifndef wrappers to avoid warnings from the C-compiler if included twice.
Bug 118452 (WINDOWS)

Ingres Export Assistant incorrectly adds a space between columns in fixed width export.
Bug 118462 (LINUX)

CBF and REPMGR encounter a SIGSEGV when attempting to display 'pop-up' confirmation box. (Windows Only) VCBF is unable to display context sensitive help for DB2, Oracle and MSSQL Gateways.
Bug 118503 (GENERIC)

The copydb command can include erroneous second "with page_size=" clauses in the generated copy.in script.
Bug 118591 (GENERIC)

Optimizedb intermittently produces statistics which are not monotonically increasing, resulting in queries generating E_OP03A2 consistency check.
Bug 118779 (Windows Only)

Ingres 2006 release 2 and up. Removed OpenROAD and Enterprise Access documentation on upgrade.
Bug 118854 (GENERIC)

Journal entries are printed twice in rfpdb.dbg when using rollforwarddb -verbose
Bug 118877 (GENERIC)

verifydb can be called so that it sets user & group ownership of the verifydb log file to be ingres & the calling user's group respectively, with rw permissions to both.
Bug 119031 (GENERIC)

Incorrect results returned running a complex query against a union view with an inner join when hash join is used. The query itself contains several inner joins between other involved tables and a left join between the view and another table.
Bug 119066 (AMD64 SOLARIS ONLY)

ipcclean does not remove shared memory with keys shorter than eight digits.
Bug 119123 (Windows Only)

On Windows 2000, combo boxes for character set and time zone are broken.
Bug 119218 (LINUX)

Upgrading an Ingres r3 instance where bridge and jdbc packages are installed fails with dependency errors.
Bug 119259 (GENERIC)

DBEVENT eventtime is generating unexpected fractional seconds.
Bug 119276 (GENERIC)

lockstat does not display -statistics using lockstat -help
Bug 119318 (GENERIC)

"set date_format" within SQL utility does not support full range of date formats supported using II_DATE_FORMAT.
Bug 119326 (GENERIC)

Selecting data from a view and table fails with E_OP04C1 Greedy enumeration produced a plan that wouldn't solve the query.
Bug 119345 (GENERIC)

DBMS reports ULE_FORMAT: Couldn't look up message 50e03
Bug 119374 (GENERIC)

E_AD1012 error produced when using STDDEV_SAMP() function.
Bug 119411 (LINUX)

iimonitor can display some thread-ids as negative values.
Bug 119419 (UNIX)

Enable a core_enabled dbms server parameter to toggle core generation for exceptions.
Bug 119428 (ATTENTION, GENERIC)

Cannot use DBMSINFO to determine date format. The following are now possible through DBMSINFO in sql and isql:

select dbmsinfo('DECIMAL_FORMAT')

select dbmsinfo('MONEY_PREC')

select dbmsinfo('MONEY_FORMAT')

select dbmsinfo('DATE_FORMAT')
Bug 119432 (GENERIC)

set date_format and set money_format do no affect the format of data returned to SQL in the same way that setting II_DATE_FORMAT and II_MONEY_FORMAT do. Note that this only applies to sql and isql - not to any other client tools.
Bug 119446 (A64_SOL)

Running optimizedb with option '-zv' may receive error "E_OP095B" and SIGSEGV on AMD/Solaris platform.
Bug 119447 (A64_SOL)

Syscheck failed to identify the allocated swap space when the locale is set to foreign languages.
Bug 119448 (A64_SOL)

Recovery server failed to start with errors "E_CL121D_ME_BAD_PARAM" and "E_DM9012_BAD_LOG_OPEN" if the file handler hard limit is set to unlimited by using projmod.
Bug 119452 (GENERIC)

DATE_TRUNC() function returns the last non-blank value when it should return a blank string.
Bug 119458 (GENERIC)

date_part() in a CASE statement leads to E_AD9999, E_SC0216 and E_SC0206.
Bug 119486 (VMS)

Some VMS Process Quotas for BE detached processes are defaulting to the system UAF specified values for the Ingres installation owner.
Bug 119487 (GENERIC)

E_RW13F0 is produced by the Report Writer when carriage return is pressed on a parameter prompt without entering any value.
Bug 119503 (UNIX)

When II_GC_PROT is UNIX /tmp/ii.YYYY socket files are not removed during an ingstop.
Bug 119509 (GENERIC)

E_OP0927 produced by statdump when both composite and normal histograms exist for the same table.
Bug 119527 (GENERIC)

An API-originating FETCH that effectively asks for 0 rows can get program exceptions (SEGV, BUS) on 64-bit servers.
Bug 119532 (GENERIC)

Unmappable unicode characters have no substitution support in tm apparently truncating the data in the record or allowing buffer overrun. The data displayed differs depending on whether the data is nchar or nvarchar.
Bug 119538 (A64_SOL)

Error "awk: insufficient memory for string storage" may occur during syscheck on AMD/Solaris if /usr/xgp4/bin/awk is used and the file handler hard limit is set to be unlimited by projmod.
Bug 119545 (GENERIC)

Transaction log file size changes are not logged to config.log
Bug 119550 (GENERIC)

On a fast CPU with relatively slower disks, and running with two DBMS servers, attempting to connect to a database immediately after running 'repcat' may result in error E_US0014 Database not available at this time.
Bug 119555 (WINDOWS)

The Visual tools on Windows could not display data from tables that contained any ANSI data or otherwise unrecognised data types.
Bug 119563 (GENERIC)

RD0060 errors reporting "non-recoverable DMT_SHOW errors" when multiple tables are created and destroyed rapidly across many sessions.
Bug 119565 (GENERIC)

When an ODBC application fails to convert a query parameter, the error "Query cannot be closed in the current state, it can only be cancelled" is returned, but attempts to cancel or roll back the query result in more errors
Bug 119577 (HPUX)



On i64.hpu, syscheck does not cope correctly with values of shmmax above 2GB.
Bug 119583 (GENERIC)

E_OP03A2 error produced using statistics with either collation sequence on character data or float data within an index.
Bug 119584 (GENERIC)

Prepared update fails with E_OP0280 consistency check when run a second or subsequent time.
Bug 119585 (GENERIC)

"MODIFY table partition part TO RECONSTRUCT" fails and returns E_QE0018.
Bug 119624 (GENERIC)

ALTER TABLE ALTER COLUMN produced SC0206 and stops the server when the column name does not exist within the table.
Bug 119632 (ATTENTION,GENERIC)

Millisecond values are being erroneously retained from ANSI time and timestamp data types when converted into Ingresdate. Under normal data entry conditions these will not normally be seen.

This is most likely to affect users using the Ingres JDBC driver in combination with ingresdates, since the JDBC driver coming with Ingres 2006 R2 maps the Java SQL timestamp to ansi timestamp and the dbms has to convert it to ingresdate.

If present, they can appear to cause queries to fail when the fractional seconds become significant in comparisons.

This fix corrects the conversion routine. It does not change the data already stored in the database. If you suspect an Ingresdate column to be affected in this manner, it can be checked with a query using the nanosecond function. This will identify any fractional seconds that may be present.

To correct any found, either perform an ascii unload/reload or update the Ingresdate column using the following SQL:

UPDATE tablename SET datecol = INGRESDATE(VARCHAR(datecol)) WHERE NANOSECOND(datecol)<>0

where datecol and tablename represent the affected ingresdate column and its parent table name.
Bug 119634 (GENERIC)

E_QE0033 invalid tid produced in a delete ... where not exists query.
Bug 119637 (UNIX, VMS)

An ABF application which uses an integer expression fails with E_AB001E, error: 'i8' undeclared. The definition is missing from the oslhdr.h file.
Bug 119639 (WINDOWS)

Command prompts briefly appear during patch installation
Bug 119648 (GENERIC)

ABF application which calls beep() followed by a message with style=popup generates a popup box with a corrupted top line.
Bug 119653 (GENERIC)

The Ingres error log file fills with E_CL2514_CS_ESCAPED_EXCEPTION followed by stack trace output for scu_information, scf_call, ule_doformat, sc0e_put.
Bug 119655 (WINDOWS)

Windows patch backup directory gets created in the wrong location due to directory name truncation.
Bug 119659 (GENERIC)

The unloaddb tool produces an extra WITH clause when default page_size is not 2048.
Bug 119661 (GENERIC)

If using internal threads, MODIFY table WITH CONCURRENT_UPDATES may cause the DBMS server to hang.
Bug 119662 (UNIX)

System while idle goes into high cpu loop with gettimeofday on many thread stacks.
Bug 119663 (GENERIC)

The transaction logging process reserves far more space than is required for recovery, especially when the transaction log file has a large buffer size.
Bug 119664 (VMS,CLUSTER)

Simultaneous ckpdb's in a VMS cluster all fail with E_DM1131_CPP_LK_FAIL "Error occurred requesting LK services", instead of one of them succeeding and the other(s) reporting E_DM1124 (indicating multiple online backups cannot be done at the same time), as happens with simultaneous ckpdb's in a non-cluster situation.
Bug 119665 (GENERIC)

B119665 E_DM9049_UNKNOWN_EXCEPTION Segmentation violation (SIGSEGV) if you CTRL-C abort an online modify while it is waiting for a lock on the table.
Bug 119671 (WINDOWS)

Visual tools in 9.x.x do not always correctly recognise databases of other 9.x.x platforms.
Bug 119681 (VMS)

The scripts generated by UNLOADDB on OpenVMS contain the UNIX command "#!/bin/sh".
Bug 119687 (GENERIC)

When doing a 'complete' Ingres install, Linux GUI installer may attempt to install documentation package even though such package does not exist. The installer will terminate with error message "No such file or directory".
Bug 119712 (ATTENTION, GENERIC)

The DBMS Server crashes when using an invalid set of statistic. 'optimizedb' generates an invalid set of statistics that contains 0.NaN / 0.Inf.

Attempting to dump out the invalid statistics using 'statdump -o' causes the process to consume all disk spaces before it fails.

To implement the solution to this problem optimizedb must be run on all numeric columns that currently have statistics defined to ensure that the possibility of having invalid statistics defined is removed.
Bug 119724 (GENERIC)



If an ODBC application selects an ingresdate column, and then references the same column via SQLBindParameter(), the query associated with SQLBindParameter() fails. The ODBC reports "Error in assignment".
Bug 119725 (GENERIC)

E_QE0033 An invalid TID was specified when using a rule AFTER an UPDATE.
Bug 119726 (GENERIC)

E_QE011D error when referencing blob value in AFTER DELETE rule.
Bug 119727 (GENERIC)

The status bitmask for an ingresdate entered as time only (the date part then defaults to today) is set to X'21' instead of X'3D'. This causes some comparisons of apparently identical values to fail so that queries return the wrong results.

This appears to only affect queries that are resolved with HASH JOINS.
Bug 119729 (GENERIC)

Report writer loses the last two characters of an undefined parameter.
Bug 119730 (GENERIC)

The ODBC driver fails to insert Unicode data into long varchar columns. The application aborts with an access violation.
Bug 119736 (GENERIC)

E_GW0668_UNEXPECTED_EXCEPTION and server crash during a COPY INTO of any IMA table.
Bug 119760 (GENERIC)

extenddb -lLOC DBNAME -Uwork fails with "E_US008D The location's area cannot be for both work and auxiliary work." when the underlying area is not already being used for auxiliary work.
Bug 119768 (GENERIC)

unextenddb leaves the wrong locations in infodb. After this corruption, accessing the database causes E_SC0206.
Bug 119772 (Windows Only)

Ingres needs to be ported to FTJam 2.5.2 on Windows.
Bug 119778 (GENERIC)

Do not have page_size on copydb if NOINDEX or BASE TABLE STRUCTURE is used.
Bug 119799 (VMS)

When installing Ingres, iishlib fails with a "Selective Purge" error when there is only one version of CONFIG.DAT as there is no lower version to compare against.
Bug 119800 (GENERIC)

ODBC applications that use forward-only scrollable cursors abort with ACCVIO if the cursors are updatable.
Bug 119802 (AIX)

Connection times can be very slow through Ingres/Net.
Bug 119804 (GENERIC)

Checkpoint never completes on highly active database.
Bug 119811 (GENERIC)

COPYDB over NET to an Ingres installation that does not have context sensitive parsing will fail with: E_US0F06 line 1, Syntax error on 'max'.
Bug 119815 (GENERIC)

E_SC0206 with stack showing ulm_closestream, qen_hjoin, qea_haggf.
Bug 119825 (GENERIC)

copydb hangs or fails with E_UG0009 when a procedure is 2048 bytes long.
Bug 119826 (ATTENTION, GENERIC)

CONVTOUNI generates scripts that fail if character columns are key columns, character columns are used in secondary indices and when the character expansion to unicode causes a table that does not have rows that span pages to exceed the existing table page size. Errors include E_US07FD, E_DM00A6 and E_DM00A7. CONVTOUNI will now upgrade the page size of a table if the new row width exceeds the current page size and the table was not created with tuples that span pages.
Bug 119844 (HP-UX)

ON HP-UX 64-bit Itanium platform, mkrawlog fails with error "/usr/lib/hpux64/dld.so: Unable to find library 'libcompat.1.sl".
Bug 119851 (GENERIC)

DBEVENT eventtime is generating datetime shifts of 2-4 days
Bug 119852 (GENERIC)

Updating an empty, not nullable, blob field gave rise to an inconsistent state in a supporting table.
Bug 119853 (GENERIC)

An optimizedb may fail with E_OP095B when generating the statistics for a nullable character key column.
Bug 119856 (GENERIC)

Compiling a *.sc program fails with: E_EQ0244 Syntax error on 'using'.
Bug 119859 (GENERIC)

Function NCHAR(st [,len]) does not accept a second parameter.
Bug 119865 (Linux ONLY)

GUI install sometimes fails with "The directory: $II_SYSTEM/ingres is not owned by root"
Bug 119874 (GENERIC)

qbf host::dbname/oracle fails with E_UI0029 Cannot start program; must upgrade catalogs. The advised upgradefe command also fails. This prevents all character based tools from running against gateway databases. The upgradefe should work against gateway databases so that CBTs can be used.
Bug 119877 (GENERIC)

"optimizedb -zk -zna md00125131 -rbnd_dur" hangs or fails with exceptions (usually SIGSEGV).
Bug 119878 (GENERIC)

Aggregate statistic functions can cause E_SC0206 on encountering NULL values.
Bug 119880 (WINDOWS)

Performance Monitor fails under VDBA. 'Log Information' summary shows all values '0'. Selecting 'Header' or 'Log File' gives message "Query Detail Object Failed". Note that the fix for this bug is required on the installation(s) that VDBA is connecting to.
Bug 119881 (GENERIC)

Outer join union view query containing ifnull() aggregate could fail with either E_OP0082, E_OP03A6, or E_OP0901 error.
Bug 119882 (GENERIC,CLUSTER)

Cluster node recovery may sometimes fail to acquire a needed cache lock.
Bug 119892 (UNIX)

setuid bit is not required on verifydb.
Bug 119899 (GENERIC)

An INSERT into a table using a UNION SELECT could insert corrupt date especially VARCHAR sometimes resulting in optimizedb or copydb failing as well as clients when selecting such data. The problem would be seen if column defaults were used or the column insert order differed from the table definition order.
Bug 119900 (GENERIC)

Session hangs in OPF with CS_CPU_MASK. If you try to remove it it goes to CS_IRPENDING_MASK,CS_CPU_MASK and the server has to be shutdown to remove the session. Only happens with composite statistics (optimizedb -zcpk).
Bug 119901 (VMS)

ingstop fails to stop the RMCMD server when multiple sets of the RMCMD tables exist (each set is owned by a different user). The tables must be owned by the '$ingres' user.
Bug 119902 (GENERIC)

NVARCHAR() & NCHAR() cannot cope with ANSI time forms or LONG VARCHAR, NCHAR(LONG NVARCHAR) fails and specifying the length as 1 character returns no data.
Bug 119908 (GENERIC)

A misspelt interval name could cause the server to hang.
Bug 119920 (GENERIC)

The DBMS hits a SIGSEGV when trying to report an attempt to extend a table beyond its maximum size. The errlog.log contains "E_DM92BF_DM1P_TABLE_TOO_BIG Error extending table past maximum table size of 8388608, Database hanal04, Table ingres.test, Current size *** ERslookup() ERROR: Missing or bad parameter for this message. ***"
Bug 119927 (GENERIC)

Statdump does not print or delete sampled statistics if sampled values contain only null values.
Bug 119934 (GENERIC)

abf is not compatible with integer calculations returning the result as an i8.
Bug 119937 (GENERIC)

A UDF aggregate function using non-UDTs does not allow the UDF to access the result data value structure.
Bug 119938 (GENERIC)

Wrong results for outer join query where an unflattened view is involved in an outer join. QEP shows a temporary table created for the view.
Bug 119943 (GENERIC)

SUM and AVG aggregate functions give wrong results when used with dates or intervals columns.
Bug 119961 (ATTENTION,GENERIC)

Checkpoint dump file entry cannot be deleted by ckpdb -d or alterdb -delete_invalid_ckp Note that alterdb -delete_oldest_ckp, alterdb -delete_invalid_ckp and ckpdb -d will now remove dump files associated with checkpoints which are not listed in infodb (i.e. the most recent 100). If for any reason these files are still needed, either copy them to a safe location, or do not run these commmands.
Bug 119967 (GENERIC)

Copy table from file where file was generated by auditdb -file -table fails with "E_C00032 Copy: Bad data value for column..., E_CO002A Copy has been aborted". Table contains blob column where the blob column is not the last column in the table.
Bug 119968 (GENERIC)

Inserting the MAXFLOAT value into a float4 / f4 column, then using unloaddb -c to create an unload.ing and reload.ing causes error E_CO0039 COPY: Error processing row 1. Cannot convert column 'col1'
Bug 119975 (GENERIC)

ODBC queries using date escape sequences ( { d 'YYYY-MM-DD' } ) fail if the target column is of type ingresdate.
Bug 119976 (GENERIC)

If a VARCHAR, or other VAR type, length prefix gets corrupted for whatever reason, attempts to transfer the column data via GCA invariably ends with massive data corruption that in some circumstances like copydb or optimizedb can crash the dbms.
Bug 119995 (GENERIC)

The ANSI standard allows one character to be specified in the trim operator. If more than one character is present the standard requires an error to be raised.
Bug 119999 (VMS,CLUSTER)

Enhance lockstat to display DLM lock information in cluster installations.
Bug 120021 (VMS)

Ingres ABF console reports an error during imgae'ing of an abf APP with i8 returned on VMS.
Bug 120030 (UNIX)

The Ingres/NET configuration utility (iisunet) hangs while configuring Ingres/NET from a NFS client machine using 'ingmknfs' utility.
Bug 120034 (GENERIC)

A simple select with a NOT IN sub-select returns the wrong number of rows - it matches nulls with the NOT IN which it shouldn't.
Bug 120041 (GENERIC)

E_OP0945 error reloading character-based statistics with length > 8.
Bug 120043 (GENERIC)

The arithmetic operators '*' and '/' do not work with date intervals and neither do the unary operators '+' and '-'.
Bug 120052 (VMS,CLUSTER)

Running two conflicting sets of inserts from two different nodes in a cluster, can cause a deadlock situation that results in aborting both transactions, instead of letting one of them complete.
Bug 120053 (VMS,CLUSTER)

In a heavily concurrent cluster environment with multiple nodes, the recovery process deadlock threads stall with numerous "CXppp_write timeout" messages seen in the respective iircp.log files.
Bug 120056 (GENERIC)

No warning given when precision is insufficient for statistics.
Bug 120058 (GENERIC)

Select from IMA table ima_lgmo_lgd no longer returns any rows.
Bug 120068 (GENERIC)

SIGSEGV or dbms hang during parallel query execution with >2Gb data.
Bug 120074 (GENERIC)

It is not possible to determine from the ODBC driver what release of Ingres it is for; this is important because the driver can be patched or installed separately from Ingres and must match the Ingres release that it was built for.

Change the version scheme of the ODBC driver from 3.50.0000.nnnn to 3.50.IIII.nnnn, where "IIII" is the Ingres version number.
Bug 120078 (GENERIC)

A Complex query involving 10 views sporadically reports E_OP0889 no eqc available.
Bug 120084 (GENERIC)

A Query containing an OUTER JOIN returns incorrect results. The QEP shows a cartesian product join and a TID join in the outer nodes of the outer join.
Bug 120097 (GENERIC)

Some repeat (static or dynamic) queries that use parallel query execution may get program exceptions (SEGV, ...) or incorrect results.
Bug 120103 (AIX)

Syscheck failed with error "Can't get shared memory data for OS version 6 release 1." on AIX 6.1.
Bug 120106 (Windows Only)

Microsoft redistributables and cazipxp are not submitted in treasure.
Bug 120125 (GENERIC)

Replication server fails to replicate a transaction and needs restart. This occurs when a single transaction contains two or more amendments to the same database row, and when that transaction (or a transaction that this transaction is dependent upon) gets a DEADLOCK error during an attempt to replicate it by the Replication server.
Bug 120138 (GENERIC)

Optimizedb does not allow the specification of a synonym through the -r option.
Bug 120141 (GENERIC)

Optimizedb only generates composite key histogram when both key (-zk) and composite key (-zcpk) are requested.
Bug 120147 (SOLARIS)

Syscheck failed to identify the swap space when the locale is set to traditional Chinese or simplified Chinese.
Bug 120175 (GENERIC)

If an aggregate view is joined to at least 2 other tables in a query, incorrect results may be seen.
Bug 120177 (WINDOWS ONLY)

Microsoft Access documents that "pass-through" queries are read-only. However, Access allows data modification commands, such as update or insert, on pass-through queries. By contrast, the Ingres ODBC driver disallows data modification commands in all read-only queries. In order to allow data modification commands in Access "pass-through" queries, a configuration option and command string attribute have been added to the Ingres ODBC driver and configuration page. The configuration option is named "Allow update when using a pass-through query in MS Access". The connection string attribute is named "ALLOWUPDATE". When the configuration option is checked, or "ALLOWUPDATE" is set to "Y", data modification commands are allowed in pass-through queries in Microsoft Access; otherwise, the Ingres ODBC driver rejects attempts to execute data modification commands. This option will be ignored when using Ingres ODBC read only driver.
Bug 120206 (GENERIC)

The ODBC catalog function SQLTables() fails to fetch tables containing one or more double quotes embedded in the table name. For example, the table name "table"with_dquote" is not fetched.
Bug 120223 (VMS,CLUSTER)

In a cluster, multiple sessions repetitively executing DDL operations such as CREATE TABLE, CREATE INDEX or DECLARE GLOBAL TEMPORARY TABLE, may cause the DBMS to terminate or issue spurious errors.
Bug 120230 (VMS)

Ingres installation procedure gives an error "%VMSINSTAL-W-NOFILE, File Disk:[TIDEVAA.INGRES.LIBRARY]IIAPI.OLB-LIBRARY does not exist".
Bug 120254 (GENERIC)

UNLOADDB and COPYDB of a database with large numbers of tables is very slow.
Bug 120258 (GENERIC)

Rows are not replicated when number of rows exceeds the QBT limit.
Bug 120259 (WINDOWS)

CKPDB no longer lists the files copied during the checkpoint.
Bug 120264 (GENERIC)

arcclean fails with E_US0834 table x owned by y does not contain column z
Bug 120270 (GENERIC)

An INSERT ... SELECT (in fact, the SELECT by itself) with a combination of EXISTS/NOT EXISTS subselects and derived tables in the FROM clause fails with E_OP0886 and E_QS0018 errors.
Bug 120294 (GENERIC)

A LIKE predicate against a string literal containing no pattern matching characters e.g. col1 LIKE 'foo', gives a row estimate of 50% rather than 0% (1 row).
Bug 120300 (LINUX)

Error "E_MO003C Unknown exception 00010A65: current query program aborted" on exit from sql terminal monitor following use of '\script'.
Bug 120306 (GENERIC)

DBMS hangs during optimisation of query requiring cartesian product.
Bug 120327 (GENERIC)

DBMS crash under high concurrency, stack showing dm2t_tcb_reclaim.
Bug 120328 (GENERIC)

SQL like predicate will allow '%___%' to match c,varchar and text columns that are shorter than the number of '_' characters present. Affects both standard and with collation specified.
Bug 120329 (UNIX)

updating a blob column may cause OS to raise a "unaligned access" message to the shell where 'ingstart' was run. For example: iidbms: unaligned access to 0x200000001b7fae87, ip=0x2000000000c02250.
Bug 120333 (GENERIC)

Comments for views are not produced in unloaddb or copydb
Bug 120336 (GENERIC)

SELECT interval FROM mytable; fails with E_US09C5 line 1, Syntax error on 'from'. The context sensitive parser fails to recognise interval as an object name. Interval is only accepted as the beginning of a ANSI interval type or as a reference to the interval() function.
Bug 120339 (GENERIC)

If an ODBC application executes a database procedure that returns a message, the message is not visible if SQLGetDiagRec() is called.
Bug 120340 (GENERIC)

Add the ability to execute queries via SQLPrepare() and SQLExecute() that cannot be prepared in Ingres.
Bug 120342 (VMS,CLUSTER)

In a cluster, under some circumstances a rollforwarddb may hang waiting for the lock to open the database.
Bug 120346 (GENERIC)

An outer join may return a wrong result, when a hash join is used and one of the hashed coulumn is an ingresdate. This happens only, if the timezone is different from GMT and the ingresdate values are without timestamp.
Bug 120349 (GENERIC)

The Transaction Logfile Status listed by LOGSTAT and displayed by IPM can sometimes appear to display conflicting information.
Bug 120356 (WINDOWS ONLY)

Linked tables with Unicode columns are displayed as "#Deleted" in Microsoft Access if the columns are designated as a primary key.
Bug 120359 (GENERIC)

The ESQLC parser reports "E_EQ0244 Syntax error" for queries that contain references to columns named 'interval'.
Bug 120369 (GENERIC)

If the dd_input_queue is corrupted all connections fail trying to process the dd_input_queue before the connection is completed. This includes connections made by utilities like verifydb. "sql -A1 dbname" allows a user connection to skip processing of the dd_input_queue when establishing a connection to the DBMS.
Bug 120371 (UNIX)

ingstop -show fails with a "cannot shift" error. On platforms that ignore the shift error ingstop -show will startup an iigcn and leave it running if the iigcn was not already running.
Bug 120373 (GENERIC)

alterdb is unable to preserve n valid checkpoints. "alterdb -keep=n <dbname>" is required.
Bug 120380 (GENERIC)

A select query with long "OR" clause fails with error E_OP0901. Error E_OP08A2 will also be reported to front end. Stack trace reported to errlog.log suggests a SIGBUS error happened on either opc_bgmkey() or opc_make_mcnsttab().
Bug 120386 (GENERIC)

Added the ODBC DSN option "Disable underscore wild-card search characters in catalog function" as an ODBC connection string attribute "DISABLEUNDERSCORE=Y".
Bug 120407 (GENERIC)

Use of the optional precision for "interval day to second" fails with E_US0A1B line 1, Syntax error on '(' when used in a database procedure.
Bug 120412 (WINDOWS ONLY)

Multi-threaded ODBC applications hang if SQLPrepare() is invoked on a non-preparable query and multiple threads share the same statement handle.
Bug 120429 (GENERIC)

COPYDB/UNLOADDB of a database that has many tables with "SAVE UNTIL" is very slow.
Bug 120430 (GENERIC)

ODBC returns NULL for SQLGetInfo() on SQL_USER_NAME if SQLConnect() call doesn't provide username.
Bug 120437 (GENERIC)

The Ingres ODBC driver fails to return rows for a searched query with a LIKE predicate if the source data is Unicode and the target column is a char or a varchar.
Bug 120442 (GENERIC)

Log Sequence Numbers (LSNs) are often displayed as signed integers rather than unsigned integers.
Bug 120454 (GENERIC)

E_QS001E_ORPHANED_OBJ and E_QS0014_EXLOCK errors reported to the errlog when a tuxedo server starts and stops.
Bug 120483 (UNIX AND LINUX ONLY)

The iisuodbc script reports failure to write to the default path /usr/local/etc, even though the specified destination path is not /usr/local/etc.
Bug 120492 (GENERIC)

Server generates a set of less efficient ADF code for an "update ... set ..." query. The problem ADF code contains an unnecessary MEcopy() instruction.
Bug 120498 (GENERIC)

Quel pattern matches with ranges present fail to apply lower bound if II_COLLATION is set and the database is enabled for collation.
Bug 120506 (NON-WINDOWS ONLY)

The path and file name specified for ODBC tracing in iiodbcadmin is ignored for unixODBC applications. Instead, the trace is written to the default /tmp/sql.log.
Bug 120516 (NON-WINDOWS ONLY)

If ODBC is configured with ODBCSYSINI defined, and another application runs without a valid definition for ODBCSYSINI, the application aborts with a segmentation violation.
Bug 120520 (GENERIC)

E_DM9049 reported producing E_SC0206 on screen doing modify. Stack reports failure in dm1cn_compress.
Bug 120526 (GENERIC)

E_OP0783_ADI_FICOERCE when querying a table with partitions
Bug 120537 (GENERIC)

E_OP04C0_NEWENUMFAILURE with nested outer joins
Bug 120553 (GENERIC)

update xa a set rc=-1 where xxx = 0 and exists( select 1 from xb b where b.nr=a.nr group by by b.nr having count(b.nr) != 1); This query updates 2 rows rather than 0 rows.
Bug 120554 (GENERIC)

Certain queries return E_OP0082 consistency check error.
Bug 120565 (GENERIC)

When running with 'system_isolation = read_committed' attempting to start Tuxedo results in E_QE0082 'Error closing a table'.
Bug 120572 (GENERIC)

Incorrect results from query involving aggregate of view of union
Bug 120584 (GENERIC)

E_AD2003 reported when using copydb via NET from 2.6 to Ingres 9.1.1
Bug 120639 (GENERIC)

copydb crashes when views have permissions granted to them
Bugs fixed in previous builds
Please refer to Knowledgebase document 415346 for a list of bugs fixed.

4.0 Contacting Technical Support

For online technical assistance and a complete list of locations, primary service hours, and telephone numbers, contact technical support at http://ingres.com/support.

Copyright 2008 Ingres Corporation
All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.
Personal tools