Caché Upgrade Checklists - InterSystems Documentation

Caché 2008.2 Upgrade Checklist7.1.8 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.Beginning with this version, the configuration file will be used only for the current startup. Subsequent start commandswhich do not explicitly specify a configuration file will cause the Caché instance to be started using the cache.cpf configurationfile.7.1.9 Platform-Specific ItemsThis appendix holds items of interest to users of specific platforms.7.1.9.1 UNIX®: Improved InstallationThe “cinstall” package now offers three setup types to replace "Standard" and "Custom".• Development: (the default) install server and all client components.• Server: Install the components for Caché server; but do not install client components, nor anything normally found inthe /dev area.• Custom: Install server components; present a dialog for all client components, allowing them to be individually selected.Furthermore, the install will use a parameters.isc file created from a previous installation to parameterize the install ratherthan by prompting the user.Note:Automatic install scripts may need to be reworked because the order of some of the Caché installation promptshas changed.7.1.9.2 UNIX®: Protection Against Starting Multiple Copies of CachéIn prior versions, the use of .lck files for Caché databases to control failover proved insufficient to prevent multiple instancesof Caché from being started against the same databases under all circumstances. Caché now takes out additional locks forthe control process, write daemon and journal daemon to provide better isolation.As part of this change, information has been removed from the cache.ids file, and is placed in a system-internal file. Theexistence of the cache.ids is all that is used as a marker.7.1.9.3 Macintosh: CShell Effective Id AnomalyThe setregid call used by csh to establish the real and effective group id for executing commands ignores the effectivegroup id (presumably as a security issue). Administrators should use alternatives such as sh, ksh, or bash when administeringCaché from other accounts than the one Caché runs as.This issue appears on all Macintosh supported platforms.7.1.9.4 Windows: License Acceptance DialogThe Windows installer now requires explicit acceptance of the InterSystems license terms as the first step in the installationprocess. This applies to both upgrade and new instance installations. The Next button for the license acceptance dialog isnot enabled until user selects the I accept the license terms choice. The only other action available is to cancel the installation.170 Caché Upgrade Checklists