[All]
InterBase 2009 Hotfix Update 2 Readme (version 9.0.2.369)
Por: Sriram Balasubramanian
Resumen: InterBase 2009 Hotfix Update 2 readme html file; contains installation and bug fix information
Updated: 19-Mar-2009
This file contains important information that may not appear in online Help. Read this file in its entirety. This hotfix update is a cumulative hotfix and can be applied to any installation of InterBase 2009. It contains all the fixes done since the first release of InterBase 2009 (version 9.0.0.206). You can download the updates from http://cc.codegear.com/reg/interbase
Installation Instructions
Windows
Run the executable InterBase2009Update2_Windows.exe, and then choose one of the following:
- Server and Client
After you choose an install location; this will replace the binaries in the existing InterBase installation. Make sure to stop the InterBase Server before installing.
- Client only
This will install IBConsole.exe and the type 4 InterBase JDBC Driver.
- Extract Files only
This will extract the hotfix files in a single directory to be installed at a later time by the user.
Linux
Extract the tar file InterBase2009Update2_Linux.tar. After extracting the files, replace the files in the appropriate directory.
Solaris
Extract the tar file InterBase2009Update2_Solaris.tar. After extracting the files, replace the files in the appropriate directory. Note: You must have Solaris 10 Update 3 or later system patches installed before you install this InterBase update.
Mac OSX
Extract the zip file InterBase2009Update2_Macosx.zip. Right-click on the extracted file and select "Open". Follow the installation procedure to update your installation of InterBase 2009. Please make sure you choose the correct folder where you have InterBase installed so the update can replace the correct files.
Resolved Defects
The following are resolved defects in this InterBase 2009 Hotfix Update.
Internal Defect # |
External Defect # (QC) |
Description |
Hotfix Update 2: 20-Mar-2009, version 9.0.2.369 (Windows, Linux, Solaris, MacOSX) |
254988 |
|
Query with explicit and implicit joins results in “no current record for fetch operation” error |
256996 |
|
Distinct in nested queries can return incorrect results |
257272 |
65388 |
concurrent delete and select (and probably insert) cause database to be corrupted. "internal gds software consistency check (exceeded index level)" error in interbase.log |
257670 |
57839 |
Join with Stored Procedure returns incorrect results |
259585 |
|
Inner Join between two views which both have left joins results in error “no current record for fetch operation” |
260489 |
|
If journal files are lost, connecting to the database may fail. Fix notes: A new GFIX switch (-disable wal) is provided to disassociate a database from its journal files. No cleanup of the journal files or journal archive files is attempted and it is the case that committed data may have been lost. This could occur because the lost or inaccessible journals may have committed data that was never applied to the database files proper. However, it becomes possible to attach the database to access existing data contained therein. |
261953 |
|
Rogue TCP packet could cause server crash |
261974 |
|
Server crash with big SORTMEM_BUFFER_SIZE on restore |
263533 |
|
OTW: malformed connection string leads to server hang |
265145 |
|
Invalid data entered into a Unicode column hangs client on retrieval operation |
265481/2 |
|
Journaling and encryption combination fails with “decryption of encryption value failed” |
265601 |
|
Running GBAK as a service incurs high CPU usage in the server |
265824 |
|
Queries based on fields where the character_set_name and collation_name do not match and there is an index return no records |
265905 |
|
Security vulnerabilities exploited by rogue clients |
267372 |
|
InterBase cannot propogate events on both interfaces of a multihomed host |
267433 |
|
Exceptions only displays first 67 characters. They should display 78 characters |
267550 |
|
Server crashes with BUS alignment error on Solaris 10 |
267860 |
70915 |
Sweep under some conditions causes error "Maximum user count exceeded" and "Request depth exceeded for IRQ_93" in interbase.log |
267874 |
|
Many users doing many inserts causes InterBase server crash with seg fault on Windows or Solaris if there are multiple CPUs |
267963 |
|
After connecting to employee.gdb, subsequent validation of the database with gfix results in interbase.log having numerous "Page xxx is use but marked free" |
268016 |
|
InterBase Services API has problems working on Windows Terminal Services |
Hotfix Update 1: 23-Sep-2008, version 9.0.0.226 (Windows) : 9.0.0.228 (Linux, Solaris, MacOSX) |
|
65959 |
Backup/Restore of encrypted databases not supported in IBConsole |
265043 |
|
Encryption failed when database or column has a character set |
265241 |
|
Re-encrypting a column crashes the server |
258311 |
|
Restore using gbak with buffers set high and -o (one at a time) causes server to crash. |
|
|
JDBC: DataBaseMetadata.getTables() does not work with delimited tables/columns |
|
|
JDBC: DataBaseMetadata.getTables() wrong ordering of resultset |
|
|
JDBC: does not recognize InterBase 2009 reserved words |
|
|
|
File List
Following are files in this update:
Windows
- ibserver.exe (bin directory)
- gfix.exe (bin directory)
- IBConsole.exe (bin directory)
- gds32.dll (bin directory)
- interclient.jar (SDK\lib directory)
- readme.html
Linux, Solaris or Mac OSX
- ibserver (bin directory)
- gfix (bin directory)
- libgds (lib directory)
- interclient.jar (lib directory)
- readme.html
Copyright © 2009 Embarcadero Technologies Inc. All CodeGear brand and product names are trademarks or registered trademarks of Embarcadero Technologies in the United States and other countries. All other marks are the property of their respective owners.
Connect with Us