13.07.2015 Views

Caché Upgrade Checklists - InterSystems Documentation

Caché Upgrade Checklists - InterSystems Documentation

Caché Upgrade Checklists - InterSystems Documentation

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

AdministratorsGMHEAP Defaults Increased On <strong>Upgrade</strong>This version of <strong>Caché</strong> will increase the gmheap to a minimum value when the system is upgraded. This minimum value is4800KB for all non-HP platforms; on HP platforms the default is 9600KB.• If the size of the gmheap is found to be less than the default, the upgrade installation process will increase it to thatvalue.• If the size of the gmheap is more than the default, upgrade writes a message to the cconsole.log file advising that itshould be increased by an additional 1600KB.5.1.3.4 Licensing Added To CacheProviderClient licensing is now standardized in this version to provide consistency in license usage between ODBC, and DotNet.5.1.3.5 Exporting Classes To XML Omits Generated ClassesWhen exporting classes to XML format, <strong>Caché</strong> now removes any classes that are generated by other classes already in theexport/compile list. The reason for this is that compiling the class that generates this other item will recreate the omittedclass. Often these generated classes are things such as classes for SQL projection which are also marked as deployed. Beforethis change, an attempt to export a package which contained a persistent class with a collection property would result inan error message about not being able to export deployed classes. Now this deployed class is automatically removed fromthe export list and no error is reported.5.1.3.6 Check For Global Name Errors On TruncationWhen a global name is longer than 31 characters, <strong>Caché</strong> truncates the name to 31 characters for all operations. This canresult in the last character of the name being a period which is invalid as the last character. In prior releases, <strong>Caché</strong> was notdetecting this condition and using the invalid global name in the global or LOCK operation which resulted in errors. In thisversion, <strong>Caché</strong> will return a error when the long name is truncated.The behavior in previous versions can be restored for the system by setting the GlobalNameTruncated property in the class,Config.Miscellaneous.5.1.3.7 Counters For SNMP And WMI ChangedThis version, eliminates the use of a class of metric counters which had to be specially enabled, and substitutes counterswhich are always "on" and more closely integrated into the system code. This should noticeably improve the overhead ofusing either SNMP or WMI for monitoring. The Lines counter is replaced by Commands; GlobalSets becomes GlobalUpdates;GlobalKills has been eliminated. The changes are documented in the MIB and MOF.Note:^PATROL has been changed to use the new counters. The old behavior and variable names are available byactivating $$Light^Patrol(0).5.1.3.8 Changes To Temporary File ManagementBeginning in this release, <strong>Caché</strong> has improved the handling of its temporary files to the point that deleting them at startupis no longer necessary. Therefore, <strong>Caché</strong> startup will no longer delete any files in the Temp directory.Important:Startup will no longer delete any user files in the Temp directory. If an application uses this directory tostore temporary files, it is the responsibility of the application to manage the files it creates across systemrestarts.<strong>Caché</strong> <strong>Upgrade</strong> <strong>Checklists</strong> 97

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!