Late-breaking information about this kit can be found in: \relnotes\readme.1st

• General Announcements
• Restricted Rights Legend
• InterSystems News, Alerts, and Advisories
• Online Documentation
• Description of a Change Report
• Change Reports for This Maintenance Kit

Prior to beginning an upgrade of a Caché instance, InterSystems recommends that the be shut down normally.

• 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

  vUnless 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.
  

• 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 stateless, independent database and application servers, 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.
  

• Config Mgr
  • LIST^%SYS.NAMESPACE should always return enabled status if type=5
• Object
  • When releasing locks on ^rINDEX/^rINDEXCLASS use immediate mode
  • Correct up to date checking for MAC routines
• Object.CacheProvider
  • Only make literals with plain constants inside SQL double parentheses
• Object.DotNet
  • Binding server: use a process private global to turn on/off output redirection
• Object.Gateway
  • OPEN commands in %Net.Remote.Gateway to check for timeout
• Object.Library
  • CacheSSH: Update to libssh2-1.3.0
  • Trap errors in stream object inside %Net.FtpSession
• Object.Storage
  • Object Storage - fix bug in %Delete that caused a failed referential action to be ignored
• SQL
  • SQL: Correct class definition optimistic concurrency locking with SQL LockTimeout=0
• System
  • Fix alignment violation with long property names
  • Fix name table issues with low memory
  • Fixed a class cache invalidation race condition
  • Fixed large object destruction hang
  • Preserve mode when editing replacement string of modal translation
  • Preserve virtual string stack for callin clients
  • Release virtual string stack in freesstack() for USETHREAD
  • Fixes to avoid corruption due to interaction between expansion and compaction/defragmentation or $prefetchon
  • Fix possible hang and expansion freeze in create, delete, or dismount database
  • Fix EXPDMN writing multiple messages to cconsole.log for the same database
  • Put back support for $VIEW options -5 and /-6 for 2K block size for 2011.1.x
• System.Cluster Specific
  • Allow rollback to mount dismounted databases during cluster recovery
• System.Journaling
  • Ensure system is frozen on journaling issues in a timely, accurate fashion
  • Fix journal.log corruption caused by failed expansion
  • Adapt JD monitor timeout to WD freeze timeout for backup
  • Allow user to stop journaling on system set to freeze on journal error
  • Prevent WD from consuming 100% CPU when system is frozen on journal issues
• System.Mirroring
  • Correct coordination between mirror dejournal jobs and mirror backup shutdown/disconnection process
  • Fix problem when failover member was removed and recreated
• System.Monitoring
  • Correct calls in System.Dashboard to prevent SYSLOG errors
• System.Shadowing
  • Address a shadowing issue with journal file name prefix
• System.StartUp
  • Fix locking shared memory (memlock) failure on AIX
  • Default libpath to "" if not found in .cpf file
• System.Very Large Systems
  • Change retry logic in Integrity checking when possibly false positives

select COUNT ((1)), fCQname from QueryTest

SELECT count(*)
    FROM SAMPLE.PERSON
    WHERE ((Age = 20 and Name='A') or Age=30)

SELECT count ( * ) 
    FROM SAMPLE.PERSON 
    WHERE ( ( Age = ? and Name = ? ) or Age = ? )

*** Warning - Cache was unable to lock shared memory ***