What's new in Embarcadero InterBase XE7 Server 12.0.3.337
Jun 25, 2015
- Fixes:
- InterBase crashes in isc_database_info() via use of info item isc_info_read_seq_count on hundreds of tables.
- Performing repeated incremental backups with continuation files will eventually cause InterBase to hang.
- Index corruption reported at non-leaf level of non-unique index in ODS 16 database.
- After installing this update, you can validate your existing XE7 related ODS 16 database with "gfix -v -f -no_update" to find if your database is affected by this corruption. If it is, you will want to either rebuild the specific corrupted index, or, backup and restore the whole database so all indexes are restored/created without any corruption with the new engine.
- Field Collation setting is not respected when comparing/sorting values with prepared parameters.
- Fetching from a subscribed Change View table followed by a ROLLBACK hangs the database engine.
- Make XE7 Change View SQL keywords unreserved.
- String concatenation operators puts unexpected padding spaces for variable length multi-byte charset CHAR fields.
- Android IBToGo cannot fetch data for record size larger than 32KB.
- IBConsole crashes instead of displaying error from an execute statement stored procedure.
- IBConsole SQL Window parsing problem with CREATE DATABASE with USER/PASSWORD.
New in Embarcadero InterBase XE7 Server 12.0.2 (Jun 25, 2015)
- Fixes:
- Multiple updates to the same record in a single transaction followed by a ROLLBACK does not restore original data.
- During transaction isolation tests it was found that a second or third update to the same record were not saved during a rollback and the subsequent update data was abandoned.
- Querying TMP$Attachments when joined to another persistent table causes AST Deadlock errors.
- Parameterized query with placeholder question mark placed at LHS of IN clause returns error "Data type unknown".
- When Selected Client Only, vcredist_x64.exe and vcredist_x86.exe are not installed.
- It is not possible to an OSX application in an App Sandbox running IBLite/IBToGo.
- Error Status message for new statement contains erroneous text from previous Execute Statement call.
- Server crash when querying Performance Monitoring tables for database attachments that had Execute Statement exceptions inside Stored Procedure calls.
- Change View (INSERT, UPDATE, DELETE) with hundreds of subscriptions cause server crash or hang.
- Erroneous call to an execute statement stored procedure causes memory leak.
- Cannot see deleted changes with subscription setup after pre-existing records.
- Bug in stored procedure causes server crash.
- When the disk containing journal files runs out of disk space, the active journal file cannot be accessed.
New in Embarcadero InterBase XE7 Server 12.0.1 (Jun 25, 2015)
- Fixes:
- Using deleted subscription name again cause some unexpected state.
- DROP DATABASE request through multi-hop claims "Invalid request handle".
- Infinite loop run by worker thread when executing CREATE INDEX statement against subscribed table.
- The example ibserverd file cannot be run on Linux.
- Request Synchronization error when executing commit with active subscription with subscriber against altered table subscription.
- Stored procedure that uses Execute Statement crashes InterBase when called multiple times.
- Important: Starting with InterBase XE7 Update 1, there is a new requirement on FOR EXECUTE STATEMENT to match every item in the SELECT list with a corresponding item in the INTO list.
- Comparing indexed CHAR fields with INTL charset requires padding space also.
- InterBase XE7 ibguard.exe does not work on Windows XP/2003.
- Combining group by and casting empty string to CHAR makes crash the Linux server.
- Order by with subscription can report wrong type of change.
- Error "cannot find tip page" during journal recovery.
- IBEvents not working properly with 64 bit Delphi Application.
New in Embarcadero InterBase XE7 Server 12.0.0 (Feb 20, 2015)
- Change View Feature:
- The Change View feature uses InterBase's multigenerational architecture to capture changes to data. This feature allows you to quickly answer the question, "What data has changed since I last viewed it?"
- Previously it involved triggers, logging, and/or transaction write-ahead log scraping. This was time-consuming for the developer and affected the database performance for a certain transaction load or change volume. Now with Change View, there is no performance overhead on existing transactions because it maintains a consistent view of changed data observable by other transactions.
- Linux 32-bit and 64-bit:
- The Linux kits, 32-bit and 64-bit, were introduced in the InterBase XE7 release.
- InterBase Built with Visual Studio 2013:
- Note that the previous versions of InterBase were built with VS2005.
- •VS2013 redistributables installed automatically by installer on each InterBase system
- •Please note some VS2005 built 64-bit UDF libraries have not worked with the new InterBase servers. If you have any old UDF libraries, please do extra testing of these with the new InterBase version. Or, rebuild your UDF 64-bit libraries with VS2013 toolchain.
- Performance Enhancements:
- Many performance enhancements have been implemented for this release.
- Performance Monitoring Counters:
- The performance monitoring counters have been scaled up from 32-bit to 64-bit values. It includes all data stored on tables within the database. IBConsole has been updated for this release. However, please refer to [Known Issues] when using older clients.
- Partial Segment Selectivity:
- InterBase currently maintains a single selectivity value per index (whether single or composite key). The values are stored in descending order and track information on how many duplicates exist in the whole index – but only first level. InterBase XE7 can now track information on lower levels.
- 64-bit Transaction IDs:
- InterBase XE7 scales transaction IDs to 64-bit (actual 48-bit) so databases now can accommodate more transactions without the old limitations. It limits itself to 48-bit, as to be aware of future transaction ID growth.
- ODS 16 Changes:
- It is now allowed for a database backup to be restored to a particular older ODS version.
- OpenSSL Upgrade:
- OpenSSL libraries included in InterBase XE7 are upgraded from version 1.0.0d to version 1.0.1i with Security Vulnerability fixes. OpenSSL is used for Encryption and OTW/SSL features in InterBase.
- Services API Support for Online Dump and Journal Archive Operations:
- •Online Dump: Services API online dumps and incremental dumps have been implemented so a pure IBX application can continue to do backup actions via InterBase Services API support.
- •Journal Archive: Previously, no Service API support existed that applications could invoke. However, now by using the cluster identifiers isc_action_svc_backup, isc_action_svc_restore, or isc_action_svc_properties, you can request that the Services Manager perform various operations on InterBase Journal Archives.
- Bugs Fixes:
- When opening "Local Server" node, IBConsole reports exception "Store RDB$FIELDS failed" with "Attempt to modify database from a readonly transaction"
- New IBConfig parameters from versions XE and XE3 not returned in isc_info_svc_get_config item to isc_service_query() API.
- SPB parameter isc_spb_instance_name is not consumed properly, if provided, for Service API calls
- Slow query performance on XE3 as compared to 2007/2009 versions of InterBase
New in Embarcadero InterBase XE7 Server 11.0.0.356 (Sep 14, 2012)
- High Performance:
- Built-in symmetric multiprocessing (SMP)
- Utilize multi-core CPUs and multi-CPU systems
- Optimized performance
- Multiplatform Support:
- Windows 8 support
- Heterogeneous O/S connectivity
- Security and Access Control:
- High level of granularity
- Support for Advanced Encryption Standard (AES)
- Support for Data Encryption Standard (DES)
- Disaster Recovery:
- Log-based journaling for short term recovery
- Journal archiving for long term recovery
- Online backup of database files
- Point-in-time recovery from archives
- Put your database on the Cloud or go local:
- Deploy in a Cloud computing environments
- Keep it local for higher security and performance