Fix list for IBM solidDB V6.3 and IBM solidDB Universal Cache V6.3

Product documentation


Abstract

This document provides a cumulative summary of fixes made in the solidDB and solidDB Universal Cache since the 6.3 General Availability (GA) release. It also contains links to APARs included in each fix.

Content




IBM solidDB 6.3 server versions for fix packs and interim fixes
Fix solidDB server version
Interim Fix 11 06.30.0056
Interim Fix 10 06.30.0055
Interim Fix 9 06.30.0054
Interim Fix 8 06.30.0053
Interim Fix 7 06.30.0052
Fix Pack 8 06.30.0049
Interim Fix 6 06.30.0048
Fix Pack 7 06.30.0047
Interim Fix 5 06.30.0046
Fix Pack 6 06.30.0044
Interim Fix 4 06.30.0042
Fix Pack 5 06.30.0040
Fix Pack 4 06.30.0039
Interim Fix 3 06.30.0038
Fix Pack 3 06.30.0037
Interim Fix 2 06.30.0034
Fix Pack 2 06.30.0033
Interim Fix 1 06.30.0031
Fix Pack 1 06.30.0029


Interim Fix 11 (06.30.0056)
Fix release date: 23 August 2013
Last modified: 23 August 2013
Status: Available

Download information
APAR Description
IC94043 Procedure call with omitted parameters causes soliddDB to shutdown with unhandled exception (CVE-2013-3031)



Interim Fix 10 (06.30.0055)
Fix release date: 3 April 2013
Last modified: 3 April 2013
Status: Available

Download information
APAR Description
IC89171 Missing rows after PRIMARY ALONE and catchup (refix)




Interim Fix 9 (06.30.0054)
Fix release date: 22 January 2013
Last modified: 22 January 2013
Status: Available

Download information
APAR Description
IC89171 Missing rows after PRIMARY ALONE and catchup
IC94045 Redundant WHERE condition can cause abnormal shutdown





Interim Fix 8 (06.30.0053)
Fix release date: 13 September 2011
Last modified: 13 September 2011
Status: Available

Download information
APAR Description
IC78222 Duplicate primary key values can be inserted simultaneously from concurrent connections




Interim Fix 7 (06.30.0052)
Fix release date: 29 June 2011
Last modified: 13 September 2011
Status: Available

Download information
APAR Description
IC77190 solidDB V6.3 on AIX asserts with failure on MME1INDEX.C
PMR 52048,000,672 ODBC TC reprepared statement execution causes crash (prepinf == NULL)
- HSB netcopy fails because final file flush takes too long to complete




Fix Pack 8 (06.30.0049)
Fix release date: 15 November 2010
Last modified: 13 September 2011
Status: Available

Download information

=======================
06.30.0049 - Fix Pack 8
=======================

BUGS FIXED..: PMR 80562,130,702 + 3 others
PLATFORMS...: l2x, l2x64, w32, w64
RELEASE DATE: 2010-11-15

FIXES
-----

Fix ID: None
Description: Accelerator server crashes when shut down during netcopy

Fix ID: None
Description: Communication layer resets client connect timeout

Fix ID: None
Description: Security vulnerability with modified login RPC message
(CVE-2011-1208 )

Fix ID: PMR 80562,130,702
Description: SQLPutData() function fails to pass dynamic string parameter for numeric columns if data length exceeds column length (right truncation)





Interim Fix 6 (06.30.0048)
Fix release date: 10 September 2010
Last modified: 13 September 2011
Status: Available

Download information

==========================
06.30.0048 - Interim Fix 6
==========================

BUGS FIXED..: PMR 14201,L6Q,000; PMR 20218,140,702
PLATFORMS...: s0x, s0x64
RELEASE DATE: 2010-09-10

FIXES
-----

Fix ID: PMR 14201,L6Q,000
Description: Documentation correction: IndexFile.DirectIO and
   Logging.DirectIO parameters are not applicable in Windows environments

Fix ID: PMR 20218,140,702
Description: Incorrect dense sequence behavior when sequence object is used
   within another SQL statement.





Fix Pack 7 (06.30.0047)
Fix release date: 8 August 2010
Last modified: 13 September 2011
Status: Available

Download information

=======================
06.30.0047 - Fix Pack 7
=======================

BUGS FIXED..: PMR 20215,140,702; PMR 24635,000,672; PMR 35181,082,000;
           : + 2 others
PLATFORMS...: a5x64, l2x, l2x64, s0x, w32
RELEASE DATE: 2010-08-27

FIXES
-----

Fix ID: PMR 20215,140,702
Description: Concurrent access to dense sequence may cause an internal
   error or unhandled exception in server.

Fix ID: None
Description: Sequence in a stored procedure cannot be referenced if the
   sequence was dropped and recreated within the procedure

Fix ID: None
Description: Security vulnerability with invalid connection request

Fix ID: PMR 24635,000,672
Description: New rval can be inserted into an empty page





Interim Fix 5 (06.30.0046)
Fix release date: 17 June 2010
Last modified: 13 September 2011
Status: Available

Download information


===============================
06.30.0046 - Interim Fix 5
===============================

PRODUCT.....: IBM solidDB 6.3
VERSION.....: 06.30.0046
BUGS FIXED..: PMR 35181,082,000
PLATFORMS...: l2x, l2x64, w32
RELEASE DATE: 2010-06-17

FIXES
-----

Fix ID: PMR 35181,082,000
Description: HSB secondary with accelerator crashes during netcopy






Fix Pack 6 (06.30.0044)
Fix release date: 28 May 2010
Last modified: 13 September 2011
Status: Available

Download information

===============================
06.30.0044 - Fix Pack 6
===============================

PRODUCT.....: IBM solidDB 6.3
VERSION.....: 06.30.0044
BUGS FIXED..: PMR 35181,082,000, PMR 76774,L6Q,000
PLATFORMS...: l2x, l2x64, h1x64, hia64, w32
RELEASE DATE: 2010-05-28

FIXES
-----

Fix ID: PMR 35181,082,000
Description: HSB secondary with accelerator goes down with error code 30150
   on netcopy

Fix ID: PMR 76774,L6Q,000
Description: Database conversions to 6.3 prior to 06.30.0042 did not
   migrate HSB log position IDs (LPID) correctly. LPIDs can be migrated
   retroactively with the command line option 'solid -x convertlpid'
   (migrates LPIDs permanently after the next checkpoint).

Fix ID: PMR 76774,L6Q,000
Description: HSB related dbcounters are not migrated correctly from 4.5 to
   6.3





Interim Fix 4 (06.30.0042)
Fix release date: 30 April 2010
Last modified: 13 September 2011
Status: Available

Download information

===============================
06.30.0042 - Interim Fix 4
===============================

PRODUCT.....: IBM solidDB 6.3
VERSION.....: 06.30.0042
BUGS FIXED..: 2 (PMR 76774,L6Q,000 + 1 other)
ENHANCEMENTS:
PLATFORMS...: w32, l2x64
RELEASE DATE: 2010-04-30

FIXES
-----

FIX ID: None
DESCRIPTION: Printouts of machine id information for JDBC
   connections do not contain IP address

FIX ID: PMR 76774,L6Q,000
DESCRIPTION: HSB connect fails with error message 14525 after an
   upgrade from 4.5x to 6.3x






Fix Pack 5 (06.30.0040)
Fix release date: 28 February 2010
Last modified: 13 September 2011
Status: Available

Download information

===============================
06.30.0040 - Fix Pack 5
===============================

PRODUCT.....: IBM solidDB 6.3
VERSION.....: 06.30.0040
BUGS FIXED..: 9 (PMR 80423,130,702; PMR 20151,140,702; PMR 26621,49R,000;
           :    PMR 20150,140,702; PMR 03973,140,702; PMR 07016,SGC,724;
           :    PMR 20158,140,702; + 2 others)
ENHANCEMENTS:
PLATFORMS...: w32, l2x, l2x64, s0x, s0x64
RELEASE DATE: 2010-02-28

FIXES
-----

FIX ID: PMR 80423,130,702
DESCRIPTION: Server crash when migrating pre-6.0 database.

FIX ID: PMR 20151,140,702
DESCRIPTION: SQLDriverConnect does not handle logintimeout properly.

FIX ID: None
DESCRIPTION: TRUNCATE TABLE leaves temporary table as garbage if
   truncate fails to delete the table.

FIX ID: PMR 26621,49R,000
DESCRIPTION: Error message formatting error: error message displays
   when log file deletion has a formatting error.

FIX ID: 20150,140,702
DESCRIPTION: An SQL query involving SELECT COUNT(*) and LEFT OUTER JOIN causes
   the server to crash.

FIX ID: PMR 03973,140,702; PMR 07016,SGC,724
DESCRIPTION: Numeric literal to SQL BINARY data type conversion
   semantics changed between version.For historical reasons solidDB
   has supported implicit conversion to a BINARY type from integer
   types.  Default data type for numeric literals now often is
   DECIMAL, and the implicit conversion was extended to that as long
   as conversion to BIGINT succeeds without loss of precision and the
   result is non-negative.

FIX ID: PMR 20158,140,702
DESCRIPTION: SELECT statement causes a crash.

FIX ID: None
DESCRIPTION: Wrong result or wrong order with M-tables: In some cases
   MERGE JOIN or ORDER BY query could get wrong results or wrong
   order with M-tables.






Fix Pack 4 (06.30.0039)
Fix release date: 18 December 2009
Last modified: 13 September 2011
Status: Available

Download information

===============================
06.30.0039 - Fix Pack 4
===============================

PRODUCT.....: IBM solidDB 6.3
VERSION.....: 06.30.0039
BUGS FIXED..: 12 (PMR 20133,140,702; PMR 20124,140,702; PMR 20138,140,702;
           :     PMR 09331,49R,000; PMR 07162,49R,000; PMR 03735,140,702;
           :     PMR 20140,140,702; PMR 20122,140,702; PMR 20115,140,702;
           :     PMR 20116,140,702; + 2 others)
ENHANCEMENTS:
PLATFORMS...: w32, w64, l2x, l2x64, a5x64, hia64, s0x, s0x64, s0xi, s0xi64
RELEASE DATE: 2009-12-18

FIXES
-----

FIX ID: PMR 20133,140,702
DESCRIPTION: Cannot start server if database file size is a multiple
   exactly 4 GB.

FIX ID: PMR 20124,140,702
DESCRIPTION: Server asserts on Solaris 10 SPARC due to unhandled SIGFPE.

FIX ID: None
DESCRIPTION: Checkpoint causes delays in writing.

FIX ID: PMR 20138,140,702
DESCRIPTION: SELECT MAX() returns wrong value when statement is re-executed.

FIX ID: PMR 09331,49R,000
DESCRIPTION: Server assert at 1147@mme1index.c.

FIX ID: PMR 07162,49R,000
DESCRIPTION: Server crash.

FIX ID: PMR 03735,140,702
DESCRIPTION: HSB connection handled incorrectly.

FIX ID: None
DESCRIPTION: soldd exports sequence values incorrectly if the current
  value is greater than maximum allowed for INT.

FIX ID: 20140,140,702
DESCRIPTION: In some cases server incorrectly outputs unrequested
   SQLInfo output.

FIX ID: PMR 20122,140,702
DESCRIPTION: Segmentation violation in ODBC library.

FIX ID: PMR 20115,140,702; PMR 20116,140,702
DESCRIPTION: CONNECT BY query using a PRIOR clause returns different
   results on second execution.





Interim Fix 3 (06.30.0038)
Fix release date: 19 October 2010
Last modified: 13 September 2011
Status: Available

Download information

===============================
06.30.0038 - Interim Fix 3
===============================

PRODUCT.....: IBM solidDB 6.3
VERSION.....: 06.30.0038
BUGS FIXED..: 2
ENHANCEMENTS:
PLATFORMS...: l2x, l2x64
RELEASE DATE: 2009-10-19

FIXES
-----

FIX ID: None
DESCRIPTION: With M-tables and foreign keys, ALTER TABLE ... SET SYNCHISTORY
   failed when it should not and also gave an incorrect error message
   ("13205: Cannot change STORE for a table with foreign keys.").

FIX ID: None
DESCRIPTION: ODBC connection attribute SQL_ATTR_CONNECTION_DEAD is always
   SQL_CD_FALSE even if the connection is broken.





Fix Pack 3 (06.30.0037)
Fix release date: 6 October 2009
Last modified: 13 September 2011
Status: Available

Download information

===============================
06.30.0037 - Fix Pack 3
===============================

PRODUCT.....: IBM solidDB 6.3
VERSION.....: 06.30.0037
BUGS FIXED..: 7 (PMR 12685,057,649; PMR 20098,140,702; PMR 43097,999,000;
           :    PMR 01327,O00,760; PMR 06752,SGC,724; PMR 06778,SGC,724)
ENHANCEMENTS: 3
PLATFORMS...: a5x64, hia64, l2x, l2x64, s0x, s0x64, s0xi, s0xi64, w32, w64
RELEASE DATE: 2009-10-06

FIXES
-----

FIX ID: PMR 01327,O00,760
DESCRIPTION: solidDB runs out of memory with EXPLAIN PLAN with CONNECT
   BY in it.

FIX ID: PMR 12685,057,649
DESCRIPTION: Freeing ODBC handle causes a crash: calling SQLFreeHandle()
   on a statement handle that has already been freed implicitly by
   calling SQLDisconnect() on the associated connection causes a crash.

FIX ID: PMR 20098,140,702
DESCRIPTION: UPDATE causes an incorrect foreign key violation.

FIX ID: PMR 43097,999,000
DESCRIPTION: CREATE TABLE with ON DELETE CASCADE caused solidDB to
   crash.

FIX ID: PMR 06752,SGC,724
DESCRIPTION: Long query truncated in trace output: output length is
   limited to 256 characters (changed to 20000).

FIX ID: PMR 06771,49R,000
DESCRIPTION: Malicious application makes solidDB assert.

FIX ID: PMR 06778,SGC,724
DESCRIPTION: Query caused solidDB to crash.

FIX ID: None
DESCRIPTION: Query with OFFSET larger than 2^31-1 causes assertion.
   With this fix, server outputs an error instead:
   SOLID Table Error 13070: Numerical overflow.


ENHANCEMENTS
------------

DESCRIPTION: New parameters introduced for checking of deadlocks.

   Srv.HealthCheckEnabled = Yes/No
   Srv.HealthCheckInterval = <seconds>, default 30.
   Srv.HealthCheckTimeout = <seconds>, default 60.

   Interval determines how often the check is done and Timeout how
   long the check will wait before outputing a message to solerror.out
   and then aborting the server.

DESCRIPTION: A new parameter Logreader.Silent introduced to quiet
   down Logreader output to solmsg.out.

   Logreader.Silent = Yes/No, default is No.

DESCRIPTION: solidDB on HPUX is now built with the -N flag which makes
   the binaries use the MPAS memory model (unshareable), thus
   allowing more memory for 32-bit processes.


Note for HPUX users
-------------------

With version 6.3.37 we have upgraded the compilers to
 Itanium: HP C/aC++ B3910B A.06.20
 PA-RISC: HP92453-01 B.11.11.20

This was necessary to support MPAS.






Interim Fix 2 (06.30.0034)
Fix release date: 3 August 2009
Last modified: 13 September 2011
Status: Available

Download information

===============================
06.30.0034 - Interim Fix 2
===============================

PRODUCT.....: IBM solidDB 6.3
VERSION.....: 06.30.0034
BUGS FIXED..: 5 (PMR 06751,SGC,724, PMR 06752,SGC,724, PMR 22014,999,706,
                PMR 33908,000,672, PMR 58780,000,672)
ENHANCEMENTS: 0
PLATFORMS...: hia64
RELEASE DATE: 2009-08-03

FIXES
-----

FIX ID: PMR 06751,SGC,724
DESCRIPTION: A new admin command 'indexusage' created; it prints
   index access counter values for each buffered relation..

FIX ID: PMR 06751,SGC,724
DESCRIPTION: solidDB returns excess number of fractional digits: solidDB
   returns by default 52 fractional digits.
   In the previous versions the default was 16 digits.
   A new parameter
      SQL.DecFloatPrecision16=yes/no ;Factory value: no
   can be used to force the precision of the default DECIMAL type
   (decimal float) to 16.

FIX ID: PMR 06752,SGC,724
DESCRIPTION: Long queries are truncated in soltrace.

FIX ID: PMR 22014,999,706
DESCRIPTION: 3-Merge join produces incorrect result (bug in merge join,
   workaround was to use loop join instead.).  

FIX ID: PMR 33908,000,672
DESCRIPTION: solidDB memory leak. Fixed by optimizing internal data structures,
   which decreases the bnode memory usage reported.

FIX ID: PMR 58780,000,672
DESCRIPTION: solidDB returns wrong result of query sometimes, possibly because
   a retry in a search for the next row skips a row as reported.






Fix Pack 2 (06.30.0033)
Fix release date: 16 June 2009
Last modified: 13 September 2011
Status: Available

Download information

===============================
06.30.0033 - Fix Pack 2
===============================

PRODUCT.....: IBM solidDB 6.3
VERSION.....: 06.30.0033
BUGS FIXED..: 7 (PMR 06111,999,000, PMR 06426,SGC,724, PMR 06619,SGC,724,
                PMR 20059,140,702, PMR 33901,000,672, PMR 79004,999,000,
                PMR 63639,49R,000)
ENHANCEMENTS: 0
PLATFORMS...: a5x64, hia64, l2x64, l2x, s0x64, s0x, s0xi64, s0xi, w32, w64
RELEASE DATE: 2009-06-16

FIXES
-----

FIX ID: PMR 06111,999,000
DESCRIPTION: Performance problem with a query. Fixed by adding a new
   method of handling OR conditions, specifically in a
   situation where a LEFT OUTER JOIN is not handled well.

FIX ID: PMR 06426,SGC,724; PMR 79004,999,000
DESCRIPTION: Performance problem with SELECT statements.

FIX ID: PMR 06619,SGC,724
DESCRIPTION: solidDB 4.5.166 and later is not able to find an existing record.
   The problem is related to scroll-sensitive flag handling
   in search cursor when the same row is updated multiple times.

FIX ID: PMR 20059,140,702
DESCRIPTION: Procedure cache problem with triggers/procedure cache
   cleanup routines.

FIX ID: PMR 33901,000,672
DESCRIPTION: solidDB may take a long time to finish a checkpoint: searches that
   performed full table scans and did not return any rows locked
   checkpoint operation in some cases.

FIX ID: PMR 63639,49R,000
DESCRIPTION: solload does not support multibyte character column names.





Interim Fix 1 (06.30.0031)
Fix release date: 14 August 2009
Last modified: 13 September 2011
Status: Available

Download information

===============================
06.30.0031 - Interim Fix 1
===============================

PRODUCT.....: IBM solidDB 6.3
VERSION.....: 06.30.0031
BUGS FIXED..: 1 (PMR 74176,L6Q,000)
ENHANCEMENTS: 0
PLATFORMS...: w32, w64
RELEASE DATE: 2009-04-17

FIXES
-----

FIX ID: PMR 74176,L6Q,000
DESCRIPTION: Windows service installation problem: starting solid as a
   Windows service with a "net start <service name>" command reported
   failure even though server started properly.
   The cause of the problem is that Windows service manager waits for
   SERVICE_RUNNING signal from the started service application. With
   this fix, solid reports status change to service manager correctly.





Fix Pack 1 (06.30.0033)
Fix release date: 16 June 2009
Last modified: 13 September 2011
Status: Available

Download information

===============================
06.30.0029 - Fix Pack 1
===============================

PRODUCT.....: IBM solidDB 6.3
VERSION.....: 06.30.0029
BUGS FIXED..: 9 (PMR 05422,211,788, PMR 05472,211,788, PMR 10007,SGC,708,
                PMR 20051,140,702, PMR 20058,140,702, PMR 20132,344,000,
                PMR 20244,060,678, PMR 51250,999,000, PMR 62700,49R,000)
ENHANCEMENTS: 0
PLATFORMS...: a5x64, hia64, l2x64, l2x, s0x64, s0x, s0xi64, s0xi, w32, w64
RELEASE DATE: 2009-03-31
 
FIXES
-----

FIX ID: PMR 05422,211,788
DESCRIPTION: SELECT statement using a very long text may fail and return
   error 13037: parsing very long text chars causes a buffer overflow.
 
FIX ID: PMR 05472,211,788
DESCRIPTION: Executing a query terminates the server process (bug in the
   SQL interpreter.
 
FIX ID: PMR 10007,SGC,708
DESCRIPTION: The Master registration process behaves differently between
   Versions 4.5 and 6.3. In solidDB 6.3 the COMMIT WORK operation is
   necessary after SET SYNCHISTORY on tables, otherwise the following SET
   HISTORY COLUMNS operation fails. In solidDB 4.5 the COMMIT was not
   required. With this fix, SET SYNCHISTORY works the
   same way as in version 4.5.
 
FIX ID: PMR 20051,140,702
DESCRIPTION: Problem with NUMERIC datatype and procedures. With this fix,
   the default behaviour of NUMERIC datatype has changed; now
   the default scale is 0 instead of 2.
   Stored procedures are now converted correctly when old database
   files are opened with the latest solidDB version.

FIX ID: PMR 20058,140,702
DESCRIPTION: Assertion failure 1512@rs0aval.c (bug in
   ON DELETE/UPDATE SET DEFAULT referential action).
 
FIX ID: PMR 20132,344,000
DESCRIPTION: CREATE TABLE fails with error 'SOLID Database Error 10033'.
   During recovery, it is possible that an internal counter
   is updated incorrectly. This causes CREATE TABLE to fail with an
   unique constraint violation error.

FIX ID: PMR 20244,060,678
DESCRIPTION: solidDB refers to a wrong column (pseudocolumn ROWID)
   on cascading delete (bug in the internal data structures ).

FIX ID: PMR 51250,999,000  
DESCRIPTION: Full merge does not start properly: if quick merge limit
   is always reached first, it can prevent the start of full merge.
 
FIX ID: PMR 62700,49R,000
DESCRIPTION: The CPU consumption of the solid process in the Primary
   increases. A bug prevents the execution of the merge process.
   The internal merge check task was not properly initialized
   after hsb netcopy.





Change history

  • 23 August 2013: Added Interim Fix 11.
  • 3 April 2013: Added Interim Fix 10.
  • 22 January 2013: Added Interim Fix 9.
  • 13 September 2011: Created fix list page.

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM solidDB

Software version:

6.3

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:

7023014

Modified date:

2013-08-23

Translate my page

Machine Translation

Content navigation