By: Sriram Balasubramanian
Abstract: InterBase 2009 Hotfix Update 2 readme html file; contains installation and bug fix information
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 126.96.36.199). You can download the updates from http://cc.codegear.com/reg/interbase
Run the executable InterBase2009Update2_Windows.exe, and then choose one of the following:
Extract the tar file InterBase2009Update2_Linux.tar. After extracting the files, replace the files in the appropriate directory.
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.
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.
The following are resolved defects in this InterBase 2009 Hotfix Update.
Internal Defect #
External Defect # (QC)
Hotfix Update 2: 20-Mar-2009, version 188.8.131.529 (Windows, Linux, Solaris, MacOSX)
Query with explicit and implicit joins results in “no current record for fetch operation” error
Distinct in nested queries can return incorrect results
concurrent delete and select (and probably insert) cause database to be corrupted. "internal gds software consistency check (exceeded index level)" error in interbase.log
Join with Stored Procedure returns incorrect results
Inner Join between two views which both have left joins results in error “no current record for fetch operation”
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.
Rogue TCP packet could cause server crash
Server crash with big SORTMEM_BUFFER_SIZE on restore
OTW: malformed connection string leads to server hang
Invalid data entered into a Unicode column hangs client on retrieval operation
Journaling and encryption combination fails with “decryption of encryption value failed”
Running GBAK as a service incurs high CPU usage in the server
Queries based on fields where the character_set_name and collation_name do not match and there is an index return no records
Security vulnerabilities exploited by rogue clients
InterBase cannot propogate events on both interfaces of a multihomed host
Exceptions only displays first 67 characters. They should display 78 characters
Server crashes with BUS alignment error on Solaris 10
Sweep under some conditions causes error "Maximum user count exceeded" and "Request depth exceeded for IRQ_93" in interbase.log
Many users doing many inserts causes InterBase server crash with seg fault on Windows or Solaris if there are multiple CPUs
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"
InterBase Services API has problems working on Windows Terminal Services
Hotfix Update 1: 23-Sep-2008, version 184.108.40.206 (Windows) : 220.127.116.11 (Linux, Solaris, MacOSX)
Backup/Restore of encrypted databases not supported in IBConsole
Encryption failed when database or column has a character set
Re-encrypting a column crashes the server
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
Following are files in this update:
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.
Trial Download Week!
Click here to download a free 30-day trial of InterBase XE3 Server or ToGo editions. Or download a free non-expiring Developer Edition >
More InterBase Info
InterBase XE3 Product Info
Free Developer Edition download
InterBase on Google+
Follow @InterBase_ on Twitter
Server Response from: ETNASC02