|
|
|
InterSystems Documentation
|
|
Caché Maintenance Kit Release Notes
|
The release notes are available in the
\Docs subdirectory of
your installation.
Late-breaking information about this kit can be found
in: \relnotes\readme.1st
Release notes from prior kits are combined in the file: \relnotes\cache\relnotes.htm
This document provides a list of the changes between version
2008.1.4
and Caché
2008.1.5.
Topics include:
General Announcements
Upgrading From Prior Released Versions
Customers running on any prior released version of
Caché may upgrade to this version of Caché
during
installation.
When upgrading across multiple versions, intermediate
upgrade steps may be necessary depending on the inter-release
compatibility requirements. The release notes for the intervening
releases will contain that information.
After each upgrade step, the following conditions apply:
- Routines
Unless specified in the upgrade notes for a specific release, routines
are upward-compatible and do not need to be recompiled. However,
customers may decide to recompile them to take advantage of new
features, improvements in generated code and the corresponding
efficiencies in runtime support.
- Classes, SQL, Projections, Proxy Classes
InterSystems requires that all classes be recompiled after an
upgrade. This is accomplished by running the following command in each
namespace where application classes reside:
Do $system.OBJ.UpgradeAll("c")
You must regenerate any proxy classes used in the upgraded instance by
following the instructions in the appropriate guide(s) in
the Caché Language Bindings documentation.
-
Exported XML
Unless specified in the
upgrade notes for a specific release, exported XML files can be
imported into later releases.
The reverse is NOT true. Later versions could be using new features
not present in earlier versions, and could have a different class
dictionary version number which alters how these classes are stored
internally that can not be undone when importing to a previous
version.
Upgrading ECP Configurations
The following guidelines apply to the process of
upgrading ECP configurations:
- Unless explicitly noted for a particular version,
the protocol used to communicate among ECP systems is fully compatible
across versions.
- For ECP configurations consisting of database
servers and application servers, InterSystems recommends that the
application servers be stateless and independent.
- A server is stateless when it treats each
request as an independent transaction that is unrelated to any prior
or future request. It does not need to preserve data for use in a
later transaction or worry about freeing it if a client dies in
mid-transaction.
- A server is independent when it does not
depend on the internal state of another application
server.
Assuming that these conditions are met, an ECP configuration may be
updated incrementally, system by system. The application servers
should be upgraded to the new version first. Once all application
servers have been upgraded, the database servers can be serially
upgraded.
-
Debugging
InterSystems also recommends recompiling routines and classes for
applications under development. This synchronizes the debugger with
the expected format of the compiled code.
Restricted Rights Legend
Use, duplication, or disclosure by the Government is subject to
restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in
Technical Data and Computer Software clause at DFARS 252.227-7013.
InterSystems Corporation
One Memorial Drive
Cambridge, MA 02142
When acquired by the Government, commercial computer software and
related documentation bearing this legend are subject to the
following:
- Title to and ownership of the software and documentation shall
remain with the Contractor.
- Use of the software and documentation shall be limited to the
facility for which it is acquired.
- The Government shall not provide or otherwise make available the
software or documentation, or any portion thereof, in any form, to any
third party without the prior written approval of the Contractor.
Third parties do not include prime contractors, subcontractors and
agents of the Government who have the Government's permission to use
the licensed software and documentation at the facility, and who have
agreed to use the licensed software and documentation only in
accordance with these restrictions. This provision does not limit the
right of the Government to use software, documentation, or information
therein, which the Government has or may obtain without
restrictions.
- The Government shall have the right to use the computer software
and documentation with the computer for which it is acquired at any
other facility to which that computer may be transferred; to use the
computer software and documentation with a backup computer when the
primary computer is inoperative; to copy computer programs for
safekeeping (archives) or backup purposes; and to modify the software
and documentation or combine it with other software. Provided that
the unmodified portions shall remain subject to these restrictions.
END OF LEGEND
InterSystems News, Alerts and Advisories
From time to time, InterSystems publishes items of immediate
importance to
users of our software. These include
alerts, mission critical issues, important updates, fixes, and release
announcements.
The most current list can be obtained from the
InterSystems Website.
Users should check this list periodically to obtain the latest information on
issues that may have an effect on the operation of their site.
Online Documentation
As a convenience to our users, InterSystems provides
online access to documentation for recent product versions at the
InterSystems Website.
From the home page, choose the
Support & Education tab, then
choose the
Support menu item for the product you are interested
in, for example,
Caché Support.
Links to the available documentation can be found on the support page
for each product.
Description of a Change Report
To help you assess the impact of this maintenance kit on your
applications, the remaining topics in this document describe each
modification in detail.
If you need assistance evaluating the effect on your application(s),
system(s), or related plans, please contact the
InterSystems Worldwide Support Center:
- Phone: +1 617 621-0700
- Fax: +1 617 734-9391
- Email: support@intersystems.com
- Networking.ECP
- SQL
- Studio
- System
- System.Shutdown
- System.System Tray
Category: Networking.ECP
Platforms: All
DevKey: GK665
Summary: Modified ECP server not to wait for jrn sync when the request buffer does not insert any jrn entry
Description:
Performance enhancement: To support ECP recovery the
data server journal syncs its activities before the client can drop them.
Also unintentionally, it forced a journal sync on purge block
notifications too.
This change modifies the algorithm
to not journal sync when the request does not insert any journal
entry.
Category: Networking.ECP
Platforms: All
DevKey: GK666
Summary: Modified ECP client request flushing rule
Description:
In rare conditions in low load environments, the ECP
client may delay flushing pending requests. This change modifies the
ECP client to flush requests as soon
as possible.
Category: SQL
Platforms: All
DevKey: DPV3117
Summary: Fix <UNDEFINED> when field in mapsub expression swapped with RowID erroneously
Description:
A problem has been corrected where a single-field
IDKEY field defined in a Map Subscript expression, for example,
$$Tag^Routine({MyIDKeyField})
was specified for the map subscript
expression in a child table.
Category: SQL
Platforms: All
DevKey: JLF242
Summary: Add NOT NULL test to <> ANY svso aggregate operand
Description:
This changes corrects an issue with the ANY and SOME predicates.
Under some circumstances, the use of these predicates on data
containing NULLs could result in incorrect results being returned.
Category: Studio
Platforms: All
DevKey: DVU2478
Summary: Debugger attach fail with 2007.1.6 server
Description:
This corrects an error caused by incorrect version
checking in the Caché server. The error message that resulted
was
class '%Studio.Debugger', method 'Attach': too many arguments
It is present in the version 2007.1 server
when the maintenance version is higher then 5.
Category: System
Platforms: All
DevKey: GK681
Summary: Routine load to prevent the current/active namespace from releasing
Description:
When searching for a routine to load, if any
namespace is reconfigured, the unused namespace is released.
The freed namespace name, however, remains associated with the current routine
context. If the freed memory is reused for something else, and if the
routine namespace context is required for $text or error trap, the
consequences are unpredictable.
This change corrects the behavior so the proper associations are established.
Category: System
Platforms: All
DevKey: SAP1058
Summary: Fix mailbox race condition that causes timeout to be ignored
Description:
Prior to this change, multiple processes doing $zu(88) cause system
degradation, and continually get NOJOB errors. This change corrects
the situation.
Category: System
Platforms: All
DevKey: SAP1163
Summary: Jobserver loops forever after getting a <STORE> error
Description:
Using a simple routine to exhaust memory will cause
a JobServer to loop forever. For example, the Objectscript commands
cause such behavior. This change corrects the
JobServer bahavior.
Category: System.Shutdown
Platforms: All
DevKey: SAP1159
Summary: %ZSTOP causes shutdown to hang due to switch 19
Description:
Routines that start a transaction to modify objects
or execute an SQL query may hang if called via %ZSTOP during shutdown.
This change prevents that from happening.
Category: System.System Tray
Platforms: Windows
DevKey: RJW1662
Summary: 'Access denied' trying to start Cache through the cube on Non-English Windows Vista
Description:
A problem has been corrected that could cause
starting a
Caché
instance from the cube to fail with an "Access Denied" error message.
The problem occurred on Windows Vista and possibly Windows Server 2008
with a non-English locale.
This problem was present on all Windows Vista capable
versions of Caché (2007.1 forward).