Caché Upgrade Checklists - InterSystems Documentation

Caché 2008.1 Upgrade Checklist8.2.2 Management Portal Changes8.2.2.1 Long String ControlThe location for enabling use of long strings has changed. In prior versions, it was located on the [Home] > [Configuration]> [Advanced Settings] page. In this version of Caché, it has been moved to [Home] > [Configuration] > [Memory and Startup].8.2.3 Operational Changes8.2.3.1 Journal Rollover ChangesSimple journal rollovers, regardless of their issuers, are no longer logged in journal history global(^%SYS("JOURNAL","HISTORY")). They are still logged in cconsole.log, however.Journaling always starts in the primary directory, the primary directory is current directory and the secondary, the alternate.That remains the case until journaling gets an error (say disk full) in current (primary) directory and fails over to the alternate(secondary) directory, at which point the secondary directory becomes current directory and the primary, the alternate.8.2.3.2 Maximum Path For Caché Databases ReducedIn this version of Caché, the maximum path length used to identify Caché databases and other items in the installationdirectory has been reduced from 232 to 227 characters. Customers who were close to the old limit may need to adjust somepathnames to fit within the new limit. To allow for variability in Caché file names, the directory portion of the path shouldbe no longer than 195 characters.CAUTION:If you are installing this version of Caché on a cluster configuration, you will need to:1. Find the pathname of the directory holding the PIJ (Pre-Image Journal) files on each node of thecluster. This is the directory specified as the PIJ directory in the Clusters category in the .cpf file orthe Management Portal page at [Home] > [Configuration] > [Advanced Settings].2. Shutdown the entire cluster cleanly.3. Delete the PIJ files on each node of the cluster. These are files whose names are of the form “*.PIJ*.*”located in the PIJ directory for that node.4. Upgrade each of the nodes to this version;5. Reboot and re-form the cluster.8.2.3.3 When Upgrading An ECP Configuration SQL Provileges May Be Lost From the ClientsAfter converting SQL privileges on the database server, the mpriv global will be deleted. Beginning with this version,Caché no longer saves the privileges in the namespace, but in the (local) SYS database. Therefore, after the conversion,the application server has the privileges, but the application server does not. The privileges will have to manually be seton the client.8.2.4 Parameter File Name Always Defaults to cache.cpfThe default for the optional configuration argument used when starting Caché from the command line has changed. Previously,when a command line such asccontrol start an_instance_name a_config_filewas issued to start Caché, a_config_file.cpf would become the default configuration file used to start later instances.200 Caché Upgrade Checklists