From PTAGISWiki
Patch 13585 for Ingres 2006 Release 2 Service Pack 2 (9.1.2) on Sun Solaris UltraSPARC
Patch 13585 for Ingres 2006 Release 2 Service Pack 2 (9.1.2) 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 13585 for Ingres 2006 Release 2 Service Pack 2 (9.1.2) on Sun Solaris UltraSPARC. This patch.html
contains important information about patch 13585. Instructions to install / uninstall patches are provided for all
platforms. This patch may only be installed over II 9.1.2 (su9.us5/100). 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:
116958
120004
120730
121159
121873
121949
122317
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 p13585 is replaced with p13585_SOL and patch13585 is replaced with patch13585_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 p13585.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_p13585.tar] patch13585
Note: If the device name is not known the system administrator should be contacted.
This will create the directory:
$II_SYSTEM/ingres/patch13585
or
<patch_directory>/patch13585
5.
Stop all Ingres processes with the "ingstop" utility.
ingstop
6.
Change directory to the patch directory.
cd patch13585
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 p13585, 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 p13585 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-p13585_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-p13585_1
* rm -rf $II_SYSTEM/ingres/install/control/*p13585_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 p13585 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 p13585.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 p13585.zip file using the following command;
$ UNZIP P13585.ZIP
4.
Patch P13585 can be installed using the provided IIPATCH.COM or using the IIPATCH.COM distributed inside the P13585.BCK saveset.
Copy IIPATCH.COM into the II_SYSTEM:[INGRES.UTILITY] or extract IIPATCH.COM from the save set using the following command;
$ BACKUP P13585.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 P13585.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 P13585.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 90678 (GENERIC)
The replicator manager does not recognise vnode names passed down through the command line during the setup process
Bug 99758 (GENERIC)
If default_page_size is 2048, copydb generates scripts that do not include "page_size=..." with clause. If scripts
are run on an installation in which default_page_size is greater than 2048, the tables are created using the
default_page_size.
Bug 101117 (GENERIC)
Failures during usermod can lead to non-persistent objects being dropped without warning.
Bug 110029 (GENERIC)
Intermittent problem when running 'qbf db_name -t': Unsupported Datatype Detected -1st column is defined with a
datatype which is not supported by the Ingres Forms-based tools (E_QF0176). Spurious SEGVs may be reported instead
of the E_QF0176 error.
Bug 110832 (GENERIC,STAR)
CASE expressions don't work on STAR databases. Error message is: E_UL0303 Unexpected query tree node
E_OP068A_BAD_TREE consistency check NULLIF(), COALESCE() and IP() functions are also affected.
Bug 112144 (GENERIC)
Under daylight saving time, query contains an AM/PM specification returns an hour difference from the expected
result. For example, query: select date('04/04/2004 1:00pm') will return '04-apr-2004 14:00:00'.
Bug 114324 (GENERIC)
Query fails with E_DM93AF and E_DM9335 during a group read.
Bug 115719 (WINDOWS ONLY)
The Performance Monitor Wizard hangs with the "Obtaining Ingres counter information..." message if the Ingres
Performance Counters have never been installed.
Bug 116958 (ATTENTION, GENERIC)
COPYDB and UNLOADDB do not provide a mechanism for excluding REPLICATOR objects from the generated copy.in file. A
new -no_rep options has been added to COPYDB and UNLOADDB to provide this ability.
Bug 117256 (GENERIC)
Sequence operations produce incorrect results.
Bug 117460 (GENERIC)
Updated Documenation for Ingres 2006 Release 2
Bug 117737 (GENERIC)
Ingres fails to start in hybrid 64-bit installations if Kerberos is configured as the default security mechanism.
The error log reports "E_GC1006_SEC_MECH_FAIL GCF security mechanism could not be loaded."
Bug 118129 (GENERIC)
Logstat shows one session in log free wait and the remaining active sessions in log BCP wait.
Bug 118384 (GENERIC)
Repeated select gives E_OP0890 error - "Too many bases added to a QEN_ADF structure" when using "shift" function on
parameters.
Bug 118454 (GENERIC)
DBMS terminates with E_DM9397_CP_INCOMPLETE in a multi-dbms shared cache, fast commit installation.
Bug 118611 (GENERIC)
Negative time intervals in ingresdate types are interpretted incorrectly.
Bug 118962 (GENERIC)
SELECT ... FROM D0 FULL JOIN D1 ON ... FULL JOIN D2 ON ... LEFT JOIN L20 ON ... produces E_OP0901 & E_OP08A2 with
SIGSEGV in ade_instr_gen, opc_adinstr , opc_cojnull , opc_ojnull_build, opc_hjoin_build , opc_qentree_build ,
opc_jinouter.
Bug 119021 (VMS ONLY)
Attempting to start 'custom' configurations of the Ingres/Net, Bridge or JDBC server via 'ingstart -iigcc/iigcb
/iijdbc=config_name' result in a 'default' configuraton of the component being started. This is also the case when
starting full installations via 'ingstart'.
Bug 119064 (GENERIC)
Subtractions of timestamp or time values with non-zero nanoseconds fields in which the number of ns in the 2nd
operand is more than the number of ns in the 1st will produce incorrect results.
Bug 119254 (GENERIC)
A negative day time interval literal with a seconds fraction portion is incorrectly interpreted. The problem query
inserted such a value and returned an incorrect result when retrieved, but the problem can also be seen by simply
selecting the literal as a constant.
Bug 119325 (GENERIC)
Selecting a row using a date column in the where clause whose value is a date interval gives E_OP03A2, E_OP04AA.
Bug 119586 (GENERIC)
The session_cpu field in the IMA table ima_server_sessions_extra does not return the cpu usage for the session,
contrary to the documentation, but always returns 0.
Bug 119642 (WINDOWS)
The Performance Monitor Wizard hangs with the "Obtaining Ingres counter information..." message if the Ingres
Performance Counters have never been installed.
Bug 119685 (GENERIC)
E_OP04C0 returned from query involving multiple FULL JOINs.
Bug 119777 (GENERIC)
Length qualified coercion functions like CHAR(c,i) and so on do not propagate the correct length especially if used
as source to a CREATE TABLE x AS statement. (GENERIC) Length qualified coercion functions like CHAR(c,i) and so on
do not propagate the correct length especially if used as source to a CREATE TABLE x AS statement.
Bug 119835 (HP-UX)
'dataldr' crashes after hitting SIGBUS/SIGSEGV errors. It may also load no data into a database after it terminates
without reporting any errors.
Bug 120004 (ATTENTION,GENERIC)
Timezones are not being correctly determined or stored resulting in incorrect timezone offsets being calculated.
This problem relates to the storing of such dates without being normalized to GMT. The affected date datetypes are
TIMESTAMP WITH TIMEZONE and TIME WITH TIMEZONE. Comparisons will usually perform correctly but certain forms of join
can treat as different two dates from different timezones representing the same point in time. To correct any
existing data, it will be necessary to update the affected column as follows: UPDATE <table> SET <column> =
<column>; This will ensure that the column data will be replaced with data normalised to GMT. The presentation of
the data will remain adjusted to the associated time zone, the update only affects the internal representation. The
dbms is able to distinquish between the two data forms so there will not be an issue if this update were applied
more than once.
Bug 120027 (LINUX ONLY)
On Linux Ingres should support more than 1024 file descriptors (e.g. 8192 as on other Unix-type systems). This
facilitates the setup of Ingres installations to support a higher number of users.
Bug 120057 (WINDOWS)
In the service dialog of the Ingres Installer, an Ingres Installer Information - Error 2809 popup will appear when
the passwords to start the Ingres service as a different user does not match.
Bug 120076 (GENERIC)
ANSI intervals do not convert correctly with ingresdate intervals. For instance, SELECT
INTERVAL_DTOS(INTERVAL'1'DAY+DATE('1 year')); loses the significant year. Answer should be: '366 00:00:00.000000000'
but what we get is a result of '1 00:00:00.000000000'
Bug 120183 (GENERIC)
Subtraction of ANSI datetime forms with INGRESDATE return incorrect result type, usually the type of the LHS but
should be an INGRESDATE as result depends on whether a date or interval were subtracted.
Bug 120239 (GENERIC)
Unicode six digit literal specification U&'\+xxxxxx' gives incorrect results.
Bug 120284 (GENERIC)
CURRENT_TIME/STAMP and LOCAL_TIME/STAMP do not adjust correctly for timezone and the LOCAL forms should return
TIME/STAMP WITH LOCAL TIME ZONE and not TIME/STAMP WITH OUT TIME ZONE.
Bug 120357 (GENERIC)
A select which joins two views, both of which are based on the same 'group by' aggregate view, returns an incorrect
number of rows.
Bug 120374 (GENERIC)
'delete' statement on a heap structure table runs longer than on earlier version of Ingres release.
Bug 120460 (GENERIC)
Ingres crashes when a huge IN-clause is used in a where clause linking on a key field in an embedded SQL query.
Bug 120493 (GENERIC)
SEGV inserting into btree table having a blob column , created 'with noduplicates'
Bug 120562 (LINUX)
iilink displays warnings that functions getwd() and mktemp() are dangerous and should not be used.
Bug 120571 (GENERIC)
Enable use of "set trace point sc930 1" to turn on session tracing. Also allow "set trace record '<filename>'" to
specify file location.
Bug 120593 (GENERIC)
Rollforwarddb +j may report E_DM966C on iiattribute, during redo of drop non-journaled table.
Bug 120660 (GENERIC)
Rollforwarddb fails to undo an open transaction in which a "create table as select" was performed where
default_journaling is OFF and result_structure is cheap. E_DM966D_DMVE_ROW_MISSING is reported in rfpdb.dbg.
Bug 120702 (GENERIC)
Spurious errors and/or SIGSEGV under opc_cqp_continue() whilst trying to create a DBP immediately after a previous
create procedure statement had failed with legitimate parser errors. E_OP0886 or E_QS0001, E_QS0018 the most
frequently observed errors.
Bug 120730 (ATTENTION,GENERIC)
Upper/Lower functions do not operate properly on some high position characters (0x80+) in the WIN1250 charset. The
current charset does not follow the charset posted by Microsoft as of May 1st 2005. Where the Upper or Lower
functions have been previously used on characters from the upper range, a sanity check should also now be performed.
This does not effect lower range character map (0x00 - 0x7F).
Bug 120852 (UNIX)
On all Unix platforms except Solaris, when fd_affinity is set to 'thread' an information-only message is output to
the dbms log stating that this setting is not (yet) supported.
Bug 120853 (UNIX)
System hangs and no new sessions can start. Stack trace shows one thread blocked on a mutex call from
DI_free_insert, with DIlru_flush also in the stack.
Bug 120875 (GENERIC)
Unicode codepoints > 0xFFFF are not stored correctly when using the extended Unicode literal format U&'\+xxxxxx'.
Bug 120907 (UNIX)
iimonitor shows the session-id and the thread library thread-id only, not the OS thread-id.
Bug 121021 (GENERIC)
logdump reports "COPY FROM 54f303ad" as user name for begin transaction when performing a copy in statement.
Bug 121033 (GENERIC)
ABF - Inside a blank menu the function keys attached to the menu don't work.
Bug 121046 (GENERIC)
Using zero length query parameter within a Dynamic SQL whilst updating a long-varchar causes duplicate keys to occur
in the extended table.
Bug 121051 (GENERIC)
When all columns from a query are in a secondary index, the QEP uses this secondary index even when using the base
table would be more efficient.
Bug 121063 (GENERIC)
E_OP03A2_HIST_INCREASING when a composite non-char key is used with statistics in a database with collation.
Bug 121112 (GENERIC)
On a concurrent environment, create index fails with error E_US138D.
Bug 121113 (GENERIC)
The logging system may hang when initiating a Consistency Point when there are a large number of active log
transactions.
Bug 121125 (GENERIC)
Write behind threads give errors E_DM93A9 and E_DM9202 for temporary tables, followed by crashes or session hangs.
Bug 121136 (UNIX)
The CBF parameter unix_priority has a dbms.crs file minimum of -19 but CBF will not allow negative values to be
assigned.
Bug 121140 (GENERIC)
If the archiver is dead, alterdb dbname -next_jnl_file goes into a loop reporting "Switching to the Next Journal for
Database". The errlog.log shows: E_DM1144_CPP_DEAD_ARCHIVER, E_DMA476_LGALTER_DBSTATE, E_DM1144_CPP_DEAD_ARCHIVER,
E_DMA476_LGALTER_DBSTATE repeatedly. If allowed to continue the errlog.log also contains:
E_DMA43D_SBK_LIMIT_REACHED, E_DMA437_NOT_ENOUGH_SBKS, E_DMA439_LXB_ALLOC_FAIL, E_DMA440_LGBEGIN_NO_LXBS,
E_CL0F14_LG_EXCEED_LIMIT.
Bug 121159 (ATTENTION,GENERIC)
Complex query containing several subselects is ignoring an obvious secondary index resulting in poor query
performance compared to earlier Ingres versions.
The fix for this bug has been implemented via the new configuration parameter opf_greedy_factor. This new parameter
will adjust plan fragment costs, allowing optimal query plans to be chosen. The default value is 1.0, which has no
affect. Setting opf_greedy_factor to < 1.0 will allow plan fragments to be considered that are more expensive than
the current best plan fragment.
Use "iisetres 'ii.<node_name>.dbms.<config_name>.opf_greedy_factor' <value>". In this case, a value of 0.75 is
suitable.
Bug 121164 (GENERIC)
One unknown table in auditdb should not stop the whole auditdb running
Bug 121190 (GENERIC)
sysmod dbname fails with "E_US081C Syntax error. Last symbol read was: 'set'." if ING_SET contains a "set" statement
such as "set logdbevents".
Bug 121205 (GENERIC)
ABF Function key from screen caused incorrect activation section to be executed
Bug 121209 (GENERIC)
E_US0902 preparing "create table as" statement with parameters
Bug 121222 (GENERIC)
E_US0B63 produce when using CASE NOT value IS NULL in GROUP BY clause
Bug 121225 (GENERIC)
Incorrect number of rows in outer join with "is not null" under OR clause.
Bug 121228 (GENERIC)
Add capability to coerce ODBC date sequences { d 'YYYY-MM-DD' } to Ingres date syntax 'YYYY_MM_DD' in the Ingres ODBC driver.
A new configuration option has been added to the "Advanced" section of the ODBC data source configuration page. If
the "Coerce to Ingres date syntax" box is checked, all ODBC date escape sequences will be treated as Ingres dates.
Dynamic parameters with a SQL_TYPE_DATE destination type will also be treated as Ingres dates.
Bug 121229 (GENERIC)
TRIM(TRAILING ... FROM ...) behaves like TRIM(BOTH ... FROM ...).
Bug 121244 (GENERIC)
SIGSEGV during execution of hash join.
Bug 121245 (GENERIC)
select first n inside an embedded SQL routine does not return correct number of rows on second iteration when usign
a REPEATED query.
Bug 121248 (GENERIC)
Spurious exceptions and/or errors when using ALTER TABLE. Stacks may include rdf_unfix(), rdf_call(),
pst_rng_unfix(), pst_clrrng(), psq_cbreturn(), psq_parseqry(). Errors may include E_RD0125. The problem is
exacerbated by setting ulm_pad_bytes to an odd numeric value.
Bug 121249 (GENERIC)
Server hangs after attempt to modify temporary table to have partitions.
Bug 121252 (GENERIC)
Grant execute on a procedure with an input set parameter fails with E_PS0558. E_US098A appears in the errorlog.log
Bug 121262 (GENERIC)
'set trace output' statements need more verbose error messages
Bug 121297 (GENERIC)
With ANSI dates and INGRES dates having differing structure date parsing sometimes causes problems where context is
not clear for example: SELECT DATE_TRUNC('days', DATE'2008-11-04') - '90 days';
Bug 121322 (GENERIC)
Need a way to report those columns, not in the SELECT list, that do not have optimizer statistics.
Bug 121331 (GENERIC)
A cursor using a "select first N" statement in ESQLC returns at most N-1 rows.
Bug 121332 (GENERIC)
Following a Security Audit file switch an ACCVIO or an E_SX102C error may be reported. Security Auditing is then disabled.
Bug 121338 (GENERIC)
The Microsoft SQL Server Interactive Service fails to import Ingres tables if the table has columns containing empty
varchar strings.
Bug 121341 (GENERIC)
Under heavily multi-threaded situations some of the STAR sessions to DBMS server hang, being shown in IPM as
CS_COMPUTABLE with an activity of "Terminating session", and the STAR server process needs to be killed to remove
the hung sessions in the STAR server.
Bug 121349 (GENERIC)
Modifying a table to a large number of partitions may result in a E_DM9054_BAD_LOG_RESERVE, E_DM922C_DM0L_MODIFY.
Bug 121352 (GENERIC)
Different results from query when connect_limit changes.
Bug 121356 (GENERIC)
E_OP0901 error running a query with a complex series of aggregate subqueries.
Bug 121358 (GENERIC)
The ODBC function SQLFetch() reports the error "Invalid number of columns or parameters specified" if the previous
fetch did not retrieve all of the segments of an unbound column.
Bug 121372 (GENERIC)
Wrong results returned select tid using an "in" clause.
Bug 121373 (GENERIC)
FULL JOIN returns wrong results if a WHERE clause is used (as opposed to an ON clause).
Bug 121384 (64-BIT SOLARIS ONLY)
SQLGetTypeInfo() returns a result set with invalid values for the COLUMN_SIZE member if the data type is SQL_CHAR,
SQL_VARCHAR, SQL_BINARY, or SQL_VARBINARY.
Bug 121385 (GENERIC)
E_OP03A2 consistency check when using collation sequence and composite key involving non-character data types.
Bug 121393 (GENERIC)
SQLGetTypeInfo() should return a precision of SQL_MAX_NVCHR_COLUMN_LEN and SQL_MAX_NCHR_COLUMN_LEN in
iidbcapabilities, if known, instead of the default value 16000, for SQL_WCHAR and SQL_WVARCHAR data types.
Bug 121394 (GENERIC)
Sessions hang in qso_wait_for.
Bug 121406 (GENERIC)
The ODBC function SQLNumResultCols() returns the number of dynamic parameters, rather than the number of result
columns, on a query prepared via SQLPrepare(), if SQLDescribeParam() is invoked before executing the query.
Bug 121411 (GENERIC)
Create Sequence not allowed as a prepared statement giving a syntax error.
Bug 121418 (GENERIC)
The ODBC function SQLGetInfo() does not indicate support for conversions of numeric data types, even though
conversions of numeric types are supported.
Bug 121419 (GENERIC)
Incorrect results with multiple case statements in aggregate, at least one of which contains an IN clause.
Bug 121426 (GENERIC)
E_UL0304_ADI_OPNAME when inserting data through STAR.
Bug 121442 (GENERIC)
A bad query plan is chosen when an outer join exists in the query. Specifically, when an outer join of the form
"FROM A LEFT JOIN B on A.x = B.x, C, D... where C.x = A.x" exists and the outer join is resolved by using a join
between C.x and B.x, then the optimiser will not be able to join A directly onto the result.
Bug 121471 (GENERIC)
Empty INGRES DATE values from an earlier release of Ingres that have been unloaded in binary format and reloaded
into a later release of Ingres may be incorrectly displayed as an interval value. For example: '21 yrs 4 mos 65536
days' instead of the expected empty value.
Bug 121484 (GENERIC)
COPYDB/UNLOADDB do not maintain the precision of TIME, TIMESTAMP and INTERVAL DAY TO SECOND column types. For
example TIME(4) becomes TIME.
Bug 121493 (GENERIC)
Incorrect result set returned from UNION query including col=col in where clause.
Bug 121495 (GENERIC)
E_OP03A2 returned using ingresdate values including NULLs with statistics.
Bug 121500 (GENERIC)
E_QE000D QEF out of memory error returned running query with hash join.
Bug 121512 (GENERIC)
ABF reports E_AB001E syntax errors whilst trying to compile an application. The syntax error is for a malformed
FRAME declaration in which the form name only contains digits which is illegal.
Bug 121519 (GENERIC)
After a table/index is created with an ID of 67,108,863, the next table ID rolls to 0. Trying to access this table
will cause Ingres to generate error messages including an E_DM9C8B for table (0,0).
The Table ID limit has been increased, also as the Table ID approaches this limit, E_DM0026 warning messages will be
generated. Once the last Table ID is used, all subsequent attempts to create a table/index will fail with E_US082D.
Bug 121521 (GENERIC)
In STAR ingresdate is used when creating temporary tables for queries even when connecting to Ingres 9.0.4 and
below, resulting in E_US07DE CREATE or ALTER TABLE: invalid column format 'ingresdate'.
Bug 121545 (WINDOWS)
Pages tab in VDBA produces 'System Error 34' for large ISAM table.
Bug 121564 (GENERIC)
When row auditing is enabled for Ingres, inserts are never audited.
Bug 121568 (GENERIC)
Poor query plan chosen for query involving an outer join and a secondary index.
Bug 121570 (GENERIC)
Query constant functions produce incorrect results on 64bit platforms. For example: SELECT
DATE('10:00')-DATE('09:00'); Should return 1hr but doesn't.
Bug 121598 (WINDOWS)
VDBA shows database procedures multiple times if they have the same name and are owned by different users.
Bug 121608 (GENERIC)
Conversion utility convtouni does not recognise long table.column names
Bug 121615 (GENERIC)
Query with view and aggregate query does not use available restriction to enhance the query plan, but performs a
full table-scan instead. Note that the query has an inner join constructed using the syntax: "FROM A JOIN B ON A.a =
B.b".
Bug 121617 (GENERIC)
II_DATE_CENTURY_BOUNDARY acts inconsistently for front end programs on 64 bit installations.
Bug 121621 (UNIX)
On Unix systems data for the admin thread is not returned from IMA tables such as ima_server_sessions_extra.
Bug 121627 (GENERIC)
Rollforwarddb may fail with E_DM133D_RFP_UNDO_INCOMPLETE, E_DM0100_DB_INCONSISTENT during undo processing of a
"create table as select..." open transaction. Default_journaling = OFF.
Bug 121633 (UNIX)
iimonitor does not show the OS tid of the admin thread.
Bug 121642 (GENERIC)
Default value does not get filled in when using "copy" statement. Only occurs when the missing column has another
column's name as its first segment (e.g. the field abcdef where a field abc exists in the table as well).
Bug 121649 (GENERIC)
A memory leak occurs in the Ingres ODBC driver when a select query is prepared and then executed multiple times, if
the transaction mode is autocommit.
Bug 121652 (GENERIC)
Space Management Schema errors such as E_DM92CB, E_DM92DD, E_DM92CD, E_DM92D5 or E_DM92D4 are reported after making
use of "MODIFY TO ADD EXTEND". The table itself does not get damaged and the errors can be resolved by modifying the
table.
Bug 121668 (VMS)
New sessions cannot be established with the DBMS server following a restart of the Name Server (IIGCN).
Bug 121673 (GENERIC)
Rollforwarddb of an online checkpoint may fail after dump file processing with errors E_DM93A9, E_DM9202, E_DM920E,
E_DM9371.
Bug 121674 (GENERIC)
Include database parameter names in SC930 tracing in case only some of the parameters have been included.
Bug 121688 (GENERIC)
Ingres allows the creation of single partition tables.
Bug 121699 (GENERIC)
When using a role with db_admin privileges for a specific database, a user can not use the '-u' flag to connect to
that database
Bug 121702 (GENERIC)
Crystal Reports fails to display long byte columns. The error returned from the ODBC driver is "Invalid number of
columns or parameters".
ATTENTION: The fix for this problem requires specification of the ODBC "Advanced" configuration option "Fetch entire
long data columns", or specification of the ODBC connection string attribute FETCHWHOLELOB. If "Fetch entire long
data columns" is checked, or if FETCHWHOLELOB is assigned a value of "Y", each invocation of SQLFetch() reads all of
the data for each long data column in a row. If unspecified, SQLFetch() reads only the first long data segment when
SQLFetch() is invoked, provided that no other columns in the row are bound.
WARNING: Specification of "Fetch entire long data columns" or FETCHWHOLELOB may have an adverse impact on
performance if the long data columns are very large in size, for example, over 100 megabytes.
Bug 121728 (GENERIC)
With II_DATE_FORMAT set to ISO or ISO4 the following, SELECT DATE('20090120'),SELECT DATE('90120') and SELECT
DATE('120') all fail with E_US10CE. 2-digits years work fine.
Bug 121734 (GENERIC)
With timezone set to other than GMT, SELECT TIMESTAMP('') returns '0000-00-00 00:00:00.000000000'
Bug 121754 (GENERIC)
DBMS crashes with E_DM9449, E_QE009C during an update to a blob column in a table that was created with NODUPLICATES.
Bug 121764 (WINDOWS)
Using SQL Assistant to create a view fails with dialog "Create view failed" and error "E_LQ00BA Attempt to connect
to existing database session 3".
Bug 121768 (GENERIC)
SIGBUS in rdf_invalidate on installations with multiple servers started.
Bug 121772 (VMS ONLY)
Client applications such as the Terminal Monitor hang if the DBMS server aborts while the client is connected to the DBMS.
Bug 121780 (WINDOWS)
Error message "Failed to create an SQL Assistant COM Object" after clicking on the "Assistant" button in VDBA.
Bug 121784 (WINDOWS)
Patch installer at 9.1 and later installs .crs files even when the corresponding product has not been installed.
Bug 121785 (GENERIC)
The Ingres ODBC driver converts ingresdate intervals to string incorrectly. For example, instead of "14 yrs 3 mos",
the driver returns "14 y-??-mo yrs 3 mo".
Bug 121792 (GENERIC)
Select from nested view fails to use key field of the underlying base table, though the where clause puts
restriction on the first key column. For example: select * from view where first_key_column_in_table = 1.
Bug 121805 (GENERIC)
Sequence values assigned in an Update/From statement do not work.
Bug 121807 (GENERIC)
SIGSEGV in rdf_readtuple() when trying to create a DBP that makes use of derrived tables.
Bug 121830 (GENERIC)
Queries involving Date/Time in non-GMT timezones are returning incomplete result sets.
Bug 121838 (GENERIC)
Add driver support for SQLGetFunctions(). Implementation of SQLGetFunctions() allows the Ingres ODBC driver to
report support of certain functions, such as SQLDescribeParam(), conditionally contingent on the support
capabilities of the connection target.
Without support for SQLGetFunctions(), applications such as Excel fail with the error "DESCRIBE INPUT not supported"
if a database query includes criteria parameters and the target database cannot support DESCRIBE INPUT.
Bug 121842 (HP)
utcom.def specifies compiler optimization level +O1. This is a debug level not suitable for deployed applications.
utcom.def should be using +O2 to achieve file-level global optimization.
Bug 121844 (GENERIC)
Queries involving Date/Time in non-GMT timezones are returning incomplete result sets.
Bug 121852 (GENERIC)
During a copy into table with a blob(long byte) column, the copy does not abort when the work location disk space is
exhausted. Error messages E_DM9713_SR_WRITE_ERROR, E_DM9703_SR_WRITE_ERROR appear in errlog.log, but the front end
completes as if all rows were successfully copied.
Bug 121869 (GENERIC)
Incorrect results returned when using two aggregate subqueries where one involves select distinct and the other is
either a straight non-distinct aggregate or a distinct using a different column.
Bug 121873 (ATTENTION, GENERIC)
opf_new_enum is not automatically added to the config.dat when Ingres is installed and there is no associated help
file for opf_new_enum in CBF. To add opf_new_enum to the config.dat with a default of ON run 'iiinitres
opf_new_enum' the setting can then be toggled using CBF.
Bug 121878 (GENERIC)
DATE_GMT( '13/07/2009') is not returning '2009_07_13 00:00:00 GMT' when the II_TIMEZONE_NAME is not GMT. The
TIMEZONE's delta from GMT is being applied to the value returned.
Bug 121882 (GENERIC)
A query with a kjoin is returning too many rows
Bug 121884 (GENERIC)
The recovery server returns errors E_GCFFFF and E_GC0024 during an ingstop and does not shut down
Bug 121896 (GENERIC)
E_OP04C0 error produced in error log.
Bug 121900 (GENERIC)
NCHAR(NVARCHAR) and NVARCHAR(NCHAR) operations are returning the incorrect length of data.
Bug 121906 (GENERIC)
IIapi_getDescriptor always returns zero for ds_precision for DECIMAL columns
Bug 121912 (GENERIC)
Auditdb displays a hex dump of tuple data for partitions.
Bug 121931 (UNIX)
With II_GC_PROT=UNIX ingstop fails to remove socket files (named /tmp/ii.<pid>) for the IIGCN and RMCMD processes.
Bug 121949 (ATTENTION, GENERIC)
Ingres Dates entered using "DATE('TODAY')" in Ingres 2.0 or earlier (including updates using IngresNet ) are stored
in tables with a different (internal) representation from the same Ingres Date entered using Ingres 9.2. The value
retrieved from the Database will be displayed correctly. However when Ingres 9.2 checks for equality the same date
is not considered equal if one is in the old format and the other in the new.
The above behavior is only of concern where an Ingres date column is used as part of a unique key, as the behavior
described above will allow identical rows to be entered.
Please refer to knowledgebase document 417983 for further information and corrective action.
Bug 121950 (GENERIC)
No rows returned for query involving min() and a column listed twice.
Bug 121953 (GENERIC)
Parser returns generic E_SC0206 internal error when Unicode coercion fails due to missing Unicode mapping files.
More specific error message is expected.
Bug 121963 (GENERIC)
Repsvr no longer honours CDDS configuration error mode setting skip-row whilst in collision mode is set to
last-row-wins.
Bug 121967 (GENERIC)
All server registrations are lost when the IIGCN is restarted.
Bug 121991 (GENERIC)
HDRPATTERN doesn't pick up all inclusion headers inside the source code.
Bug 122014 (GENERIC)
QBF incorrectly applies column defaults if the table contains system maintained keys and/or user defined datatypes.
Bug 122016 (VMS)
The name server terminates. The only evidence that the GCN has terminated is a
%SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=0000000000000004
message in the ERRLOG.
Bug 122024 (GENERIC)
File handle leak during SC930 tracing using parameterised DB procedures.
Bug 122062 (GENERIC)
When using SC930 tracing under a heavy load some messages may appear in incorrect log files, or even in log files on
their own.
Bug 122065 (GENERIC)
Time interval calculations may return the incorrect results for day light saving zones.
Bug 122075 (GENERIC)
Connecting to any database could cause an access violation error and crash the server.
Bug 122105 (GENERIC)
Intermittent, spurious, incorrect results using front-end tools such as VIFRED and VISION.
Bug 122113 (GENERIC)
E_SC0206 and dbms crash when inserting a duplicate record into a hash table when the row is sufficiently large to
span pages.
Bug 122164 (GENERIC)
Sequence operations appearing in an order by clause are not flagged as errors.
Bug 122172 (GENERIC)
SC930 tracing issues A QUERY trace line is produced whenever a database procedure is reparsed due to being flushed
from cache. A parameter of >2048 bytes causes a DBMS crash. Datetimes do not include the timezone adjustment.
Duplicate output after a syntax error. Blank date - date('') - appears as INTERVAL 0/0/0 0:0:0
Bug 122177 (GENERIC)
'auditdb dbname -table -f' reports E_DM1212_ATP_DISPLAY if journal files contain open transactions.
Bug 122206 (GENERIC)
SELECT AVG(INGRESDATE_COL) returns a blank row when an ingresdate interval value is expected.
Bug 122217 (GENERIC)
ANSI date and time forms should treat blank or empty strings as a syntax error.
Bug 122263 (GENERIC)
Reporting utility, iiresutl, returns incorrect information for sum of log writer threads.
Bug 122276 (GENERIC)
E_AB001E compilation failures after a COPYAPP IN which lead to Objects receiving a new Object ID that had more
digits than their old Object IDs. The compilation errors are a result of incorrect code being generated. The code
has "FRAME * = {" where it should be "FRAME * identifier = {".
Bug 122284 (GENERIC)
Performance degradation involving threads waiting on ULM QEF mutexes.
Bug 122299 (GENERIC)
Date values are not correctly printing in SC930 tracing.
Bug 122317 (ATTENTION, GENERIC)
The command 'set [no]journaling on <table>' does not correctly update the journaling status of partitions in
partitioned tables. This results in data in partitioned tables not being journaled after 'set journaling on
<table>', or continuing to be journaled after 'set nojournaling on <table>' is used.
Note that the journaling status on partitions is correctly set at table creation time with the 'create table...[with
[no]journaling]' command. It is only subsequent changes using the 'set [no]journal' command that can cause the
incorrect behaviour.
Note also that the copy.in command file produced by copydb/unloaddb uses the 'set journaling' commmand when creating
journaled tables even if the copied table was originally set up with 'create table...with journaling'. Therefore
databases with journaled tables set up via the default copy.in from copydb/unloaddb will be affected by this problem.
If you have partitioned tables that have had their journaling status changed by using 'set [no]journaling', you will
need to apply this fix. After applying this fix, you must rerun the most recent 'set journaling' or 'set
nojournaling' command on these tables. You will then need to take a checkpoint to enable/disable journaling on these
tables.
To identify all partitioned tables and determine their journaling status, you can use the following sql:
select a.table_name, a.partition_dimensions, a.table_reltid, a.is_journalled from iitables a, iitables b where
b.partition_dimensions > 0 and a.table_reltid = b.table_reltid order by a.table_reltid, a.partition_dimensions desc
This will return a list of partitioned tables, sorted into base table record followed by its partitions. The
'is_journaled' column should have the same value for the base table as for its partitions.
Bug 122326 (GENERIC)
A select query that joins a partitioned table fails with E_US11FD.
Bug 122337 (GENERIC)
When comparing Ingresdates, Normalised and unnormalised DATE+TIMEs for the same date+time are not considered as
equal.
Bug 122374 (GENERIC)
Rollback of an update in which a rule BEFORE UPDATE triggers a procedure which updates a column that is not in the
original update statement set list reports E_DM966C, E_DM9636 in errlog.log.
Bug 122393 (GENERIC)
E_LQ002D Associated to the dbms has failed. Caused by using accessdb/createdb/destroydb (the latter two only when
the trace point sc930 is switched on).
Bug 122410 (GENERIC)
SC930 tracing does not print large object or long floating-point variables correctly
Bug 122509 (GENERIC)
"set trace point sc930 2" logs query plans to the sc930 tracing log.
Bug 122528 (UNIX)
Should the archiving subprocess for 'ckpdb #mN' fail, ckpdb does not report the problem back to the user.
Bug 122544 (GENERIC)
SC930 trace output is skipping the first parameter of EXECUTE.
.
Bug 122549 (GENERIC)
Segmentation fault occurs on queries involving tables with default values in a high concurrency environment. Stack
includes rdf_unfix and usually rdu_drop_attachments, pst_rng_unfix, or psl_check_defaults.
Bug 122613 (GENERIC)
Outer join containing an "IS NULL" OR-ed with other restrictions in the where clause causes server to return wrong
results. An example query is: select .. from t0, t1 left join s2 on ...., where ... and s2 is null or t1.col =
s2.col. Query plan shows server does a 't0' left join from 's2' first, then a join of the result with 't1'.
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.
