This document is the Caché 4.1.15 change summary. It provides an overview
of changes in this maintenance release. For
detailed information on getting started, see the Caché 4.1
Release Notes (also located off the Caché installation directory
in the file Docs/GCRN/GCRN.html); for information on previous 4.1
maintenance kits, see the previous
change summary document (also located off the Caché installation
directory in the file Docs/GCRN/prenotes.htm).
| Special Note Regarding Clustered Databases on OpenVMS |
Category: Clusters
Platform(s): OpenVMS
Description: In OpenVMS cluster configurations, 8-KB formatted databases are preferred to 2-KB formatted databases. 8-KB formatted databases have additional recoverability in the event of a cluster node crash while multiple nodes are updating the same block simultaneously.
| Special Note Regarding Linux ODBC |
Category: ODBC
Platform(s): Linux
Description: The Caché ODBC client driver for Linux is not automatically installed. For detailed instructions on how to install the client ODBC component on Linux, see the provided ODBC Configuration document (odbcconf.txt, which is located on the installation media for Linux in the /dist/ODBC/ directory). This does not affect configurations in which Caché on Linux is serving ODBC requests from other clients.
| Special Note Regarding Mag Tape Backup Performance Upgrade for Windows | [LRS675] |
Category: System.Backup/Restore
Platform(s): Windows
Description: This Caché maintenance kit includes a revision in the backup utility that significantly improves performance for certain tape devices on Windows platforms. This may, however, render Caché unable to read backups from previous maintenance kits and versions.
For tape drives such as a DLT4, the backup block was being written out as a series of much smaller blocks. This revision significantly improves performance by ensuring that a single contiguous block is written, but it also means that a backup generated on the same hardware before this fix cannot be restored by a version of Caché with this fix.
| Caution: Backups made on certain kinds of tape drives on previous versions under Windows might not be able to be restored by a version with this revision. Customers should make a new backup immediately after upgrading and/or retain a Caché instance of the prior production version. |
| Likelihood of happening |
Risk
this change introduces new problems |
Distributed
in ad hoc release and installed in production |
This
change is an enhancement |
| Medium | Medium | Yes | Yes |
| Fixed Field List for Outer Join | [AK501] |
Category: SQL.Query Processing
Platform(s): All
Description: Previously, certain kinds of outer joins could cause incorrect code generation resulting in <UNDEFINED> errors at runtime. This has been corrected.
| Likelihood of happening |
Risk
this change introduces new problems |
Distributed
in ad hoc release and installed in production |
This
change is an enhancement |
| Low | Low | No | No |
| Addressed LOCKTAB Display of DTM Locks | [DAS453] |
Category: System
Platform(s): All
Description: Previously, LOCKTAB was not displaying locks from DTM clients properly. This has been corrected.
| Likelihood of happening |
Risk
this change introduces new problems |
Distributed
in ad hoc release and installed in production |
This
change is an enhancement |
| Low | Low | Yes | No |
| Fixed %GSIZE Use of Alternate Device | [LFT974] |
Category: Utilities
Platform(s): All
Description: Previously, if you specified an alternate device for the %GSIZE report but got an error message because the global had no data, then the output would not display correctly on the alternate device, but instead would switch to the console. This has been corrected.
| Likelihood of happening |
Risk
this change introduces new problems |
Distributed
in ad hoc release and installed in production |
This
change is an enhancement |
| Low | Low | No | No |
| Fixed Cluster Failover Potential Hang | [SML357] |
Category: System
Platform(s): All
Description: When jobs were issuing delock requests during cluster failover, there was a slight possibility of processes hanging after the failover was complete.
| Likelihood of happening |
Risk
this change introduces new problems |
Distributed
in ad hoc release and installed in production |
This
change is an enhancement |
| Low | Low | Yes | No |
| Fixed Erroneous Blocks Copied Field in GBLOCKCOPY | [STC454] |
Category: System
Platform(s): All
Description: When using GBLOCKCOPY to copy data from one database to another database or namespace, an error might have been reported that the number of blocks copied did not match the calculated number of blocks to copy. This false error report was incorrect. The data was fully copied. This error has been eliminated.
| Likelihood of happening |
Risk
this change introduces new problems |
Distributed
in ad hoc release and installed in production |
This
change is an enhancement |
| Low | Low | No | No |
© 2003, InterSystems Corporation. All rights reserved.
Change summary for earlier Caché 4.1.x versions
Copyright © 2001-2003, InterSystems Corporation.
All Rights Reserved.
Please contact InterSystems Worldwide Response Center at support@intersystems.com if you would like to know more about any of these items.