Caché Upgrade Checklists - InterSystems Documentation

AdministratorsPrior Version MappingB* –> SAMPLESA:G –> USERB:C –> SAMPLESA:G –> USERA –> SAMPLESA:G –>USERA* –> SAMPLESA:G –>USERA:G –> USERB:H –> SAMPLESConverted Mapping For 2009.1A:B –> USERB:C –>SAMPLESC:G –> USERA:B –> USERB:C –>SAMPLESC:G –> USERA –>SAMPLESB:G –> USERA:B –>SAMPLESB:G –> USERA:G –> USERG:H –> SAMPLESBecause the conversion process produces non-overlapped mappings, the order of the mapping is no longer important.In 2009.1, overlapped mappings can still be present in the CPF file or entered into the Management Portal as long as theyform proper subsets. This means that mappings such as those in the first column of the last row of the table will be convertedas shown when upgrading to version 2009.1. However, this same set will result in errors if found once the system has beenupgraded.Important:Before upgrading a system from 2008.2 to 2009.1, sites are strongly urged run the CPF validator to determineif the configuration file it intends to use is correct. The ways to do this were described in a preceding section.Sites that have overlapped mappings are strongly encouraged to test the converted mappings to make surethat all previous data remains accessible and that new data is stored where it was intended.It is good practice to validate all the CPF files a site intends to use before they are first employed in production.If a site switches to an alternate CPF file without converting it, the CPF file will be converted tothe new format when it is used for the first time.If you need assistance with the conversion process, please contact InterSystems Worldwide ResponseCenter (WRC).Management Portal ChangesBecause of the new rules for resolving overlaps, the order of the mappings in a configuration file no longer matters. Forthis reason,• Mappings will be displayed in the Management Portal in the order of the collation for the current locale.• The move down and move up buttons have been removed because they no longer apply.6.1.2.1 Other Mapping ChangesThe mappings of the ^oddPROJECT, ^CacheMsg, and ^CacheMsgNames globals have been changed; they will be storedin the default ROUTINE database for a namespace, rather than in the default GLOBAL database for a namespace. On somesystems where the global is already defined, and the namespace had separate routine and global databases for the namespace,Caché Upgrade Checklists 131