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.
-
Routines
Compiled routines are upward-compatible from version to version and do
not need to be recompiled unless specified otherwise in the upgrade
notes for a specific release.
Because most versions contain improvements in the routine compiler, in
the generated code, and/or efficiencies in the runtime support,
customers may decide to recompile their routines to take advantage of
new features and meta-routine information. Those customers whose
actions implicitly access this underlying information must recompile
their routines. An example of such access is source-level debugging on
version X of code compiled on version earlier than X.
If you recompile routines, they should be recompiled after classes are
recompiled.
- Classes, SQL, Projections, Proxy Classes
InterSystems requires that all classes be recompiled after an
upgrade. The following command will upgrade and compile the class
dictionaries in every namespace:
Do $SYSTEM.OBJ.CompileAllNamespaces("u")
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 set. You must also purge any cached
queries in any upgraded namespace by issuing the command:
Do $SYSTEM.SQL.Purge()
in that namespace.
- 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.
-
Debugging
InterSystems also recommends recompiling routines and classes for
applications under development. This synchronizes the debugger with
the expected format of the compiled code.
-
Caveat
Because recompiling necessarily updates system data associated with
the routine, users who recompile classes or routines must have write
access to this data (^ROUTINE) in each namespace where the object
being compiled is mapped. Failure to observe this requirement will
result in
ERROR #302: the database is read-only.
Upgrading ECP Configurations
The following guidelines apply to the process of
upgrading ECP configurations:
If your database or application servers hold local
transaction information until the transactions are completed, or if
you have questions or concerns about how to upgrade your ECP
configuration, please
contact
InterSystems
Worldwide Customer Support.
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
- CSP
- CSP.Gateway
- Ensemble
- Ensemble.Adapter
- Installation.Windows
- Networking.ECP
- Security
- SQL.Query Processing
- System
- System.Backup/Restore
- System.Licensing
- System.Trans. Proc.
- Utilities
- Utilities.Configuration
Category: CSP
Platforms: All
DevKey: MAK2814
Summary: Fixes to password change behavior in CSP
Description:
This corrects a situation where Caché would report an error
when changing the CSP password when there was none.
Also in the password change page, Caché will now display an
error message so if the user enters a password that is too short:
ERROR #845: Password does not match length or pattern requirements
Category: CSP
Platforms: All
DevKey: MAK2817
Summary: Handle normalization of the password change page in CSP the same as the login page
Description:
This change corrects a situation where changing the CSP password was
handled differently depending which CSP page was used to effect the
change. Pasword changes are now done the same way for all code paths.
Category: CSP.Gateway
Platforms: All
DevKey: CMT848
Summary: Ensure that the 'Event Log File' directive works as described in the documentation
Description:
This change now makes the
'Event Log File' directive works as
described in the documentation.
In previous Gateway builds, the original (default) log file name and
location would continue to be used
until the Gateway had fully
initialized itself.
Category: CSP.Gateway
Platforms: All
DevKey: CMT866
Summary: Resolve an access violation that can occur in state-aware mode if a queued thread is forcefully interrupted by the hosting web server
Description:
This correction resolves an access violation that
can occur in state-aware mode if a queued thread was forcefully
interrupted by the hosting web server. The CSP Gateway clean-up
functionality has been improved such that these error conditions will
be avoided in future.
Category: CSP.Gateway
Platforms: All
DevKey: CMT868
Summary: Fix a typo in the code responsible for identifying web files indicating a URL requesting Gateway Management forms
Description:
This correction fixes an error in the code
responsible for identifying web files indicating a URL requesting
Gateway Management forms.
Category: Ensemble
Platforms: All
DevKey: MC1087
Summary: Use transaction around copying data to $$$EnsSuspended
Description:
This change ensures that Ensemble will not be in a state where messages
are partially processed if a production is not shut down
properly.
Category: Ensemble.Adapter
Platforms: All
DevKey: HCR157
Summary: Close TCP socket device before [re]opening (Object Gateway)
Description:
This corrects a situtaion where an application was
experiencing disconnection errors in a production that uses the Java
Gateway. This change improves handling of the TCP device when
reconnecting.
Category: Installation.Windows
Platforms: All
DevKey: ALE1944
Summary: Display service credentials dialog when upgrading 2010.1 and 2010.1.1 builds
Description:
This change causes the Windows installation process
to display a service credentials dialog when upgrading 2010.1.0 and
2010.1.1 builds.
Category: Networking.ECP
Platforms: All
DevKey: GK863
Summary: Track ECP rollback journal position
Description:
This change modifies Caché to track the
journal position while a transaction is rolling back.
Prior to this change, if there was a write daemon pass and then a
system failure before an ECP transaction rollback was complete, there
was a small chance of losing that active open transaction; also if
journal-purge could not see the active transaction, the system might
delete the journal while it was being rolled back.
Category: Networking.ECP
Platforms: All
DevKey: GK870
Summary: Added a missing error frame pop in the ECP server
Description:
In very rare conditions, if ECP received a request
that named an invalid database (because, for example, it had been
dismounted), the request may leave an error frame un-popped. After
many of these frames the error frame may overflow with unpredictable
side effects.
This is now corrected.
Category: Security
Platforms: All
DevKey: STC1842
Summary: Fix security hole in $SYSTEM.Security.AddRoles with XECUTE code
Description:
This correction fixes a security hole in the
$SYSTEM.Security.AddRoles() method. Previously, a user could ZLOAD a
privileged routine, ZINSERT some XECUTE code into it, then execute the
ZINSERTed code which would leave the user with the %All role when
execution finishes.
Category: SQL.Query Processing
Platforms: All
DevKey: DPV3690
Summary: SQL: Correction for CAST(x AS NUMERIC(p,s))
Description:
This change corrects a problem where
CAST(value AS NUMERIC(5,2))
would return incorrect results in display mode when
using European-style "," as the numeric decimal separator.
Category: System
Platforms: All
DevKey: JO2339
Summary: Correct recovery of WIJ blocks
Description:
This change fixes a potential problem in cluster failover where:
- if the WIJ of a failed system had blocks to be recovered, and
- if there was only a single block for a given database, and
- that block was the last block listed in the WIJ,
then that block would not be recovered.
The possibility of this set of circumstances occurring is rare, but if
it does happen, database degradation could result.
Category: System.Backup/Restore
Platforms: All
DevKey: SAP1356
Summary: Limit backup map processing to actual maps in file
Description:
After truncation, the maximum number of maps may be
less than shown in the incremental bit maps. This change limits backup processing to
the actual number of maps present.
Category: System.Licensing
Platforms: All
DevKey: RJW1845
Summary: Fix WebLink license problem when ^%mgw1 is remapped
Description:
This changes corrects a problem obtaining a license
for a WebLink connection when the system WebLink routines are remapped
from CacheLib.
Category: System.Trans. Proc.
Platforms: All
DevKey: HYY1592
Summary: Correct ROLLFAIL behavior on ECP server
Description:
This change corrects an issue of "dangling
transaction" on ECP server. In this situation, the journal was
missing the TCOMMIT record for the transaction after the transaction
failed to roll back ("ROLLFAIL") and the system continued from that
point because it was NOT set to freeze on such errors.
Category: Utilities
Platforms: OpenVMS
DevKey: STC1847
Summary: Only keep one CACHE.CPF file on VMS when edited
Description:
Prior to this change, when a CPF file was edited Caché
did not remove older versions of the file. With this correction,
only the most recent version of the file is present; older versions
are removed.
Category: Utilities.Configuration
Platforms: All
DevKey: SML1229
Summary: Fix namespace mapping when System DB location is changed
Description:
This change fixes two issues:
- If a user changed the location of system
databases (CACHE, CACHELIB, CACHEAUDIT or CACHETEMP) by editing the
CPF file or by using the Management Portal, the %SYS namespace mapping
would not get updated.
- If a user changed the location of a non-system
database
using the Management Portal, the namespace mapping associated with this
database would not get updated. (If the database location was changed by editing the CPF file, the mapping would be
updated.)
Category: Utilities.Configuration
Platforms: All
DevKey: SML1231
Summary: Fix routine mapping with non-ALL type got ignored
Description:
This corrects a situation where a routine mapping
with type other than ALL would be ignored.