CA ERwin Model Manager Implementation Guide

How to Upgrade the MartHow to Upgrade the MartIt is important to run through the upgrade process in a test environmentbefore attempting to upgrade your production environment. By doing so, youbecome aware of any challenges that exist, and have fewer surprises whenyou actually convert your production environment. To convert your mart asefficiently and as fast as possible, follow these recommendations:■■■■■■■■■■■■■■■Make a full backup of the current database using the backup utility for yourDBMS before upgrading.Open and save all models in your mart using the current version of theclient before you convert to CA ERwin MM r7.3.Ensure that all users check in any off-line models and ensure that thereare no active sessions on the mart and that no models are checked out.Remove obsolete models in the current database to reduce the size, whichimproves the conversion speed.Verify that CA ERwin Data Modeler and CA ERwin Process Modeler modelsare synchronized if you synchronize data.Verify that your client version is compatible with the database version towhich you are migrating.Increase the size of the database to a minimum of three times the size ofthe previous database for temporary conversion objects.Verify there are no outstanding technical support issues related to CAERwin MM.Turn on AUTOEXTEND to automatically extend the CA ERwin MM data filewhen full (Oracle DBMSs only).Make sure the Auto grow file is turned on, with your choice of File Growthand unrestricted File Growth for both data files and transaction logs(SQL2000 DBMSs only).Review the Release Notes file.Run the upgrade during off-peak hours.Truncate the database log file.Start the conversion from the server to eliminate the possibility of networkspeed becoming a bottleneck. Have at least 1 GB on the client, typicallymore memory means faster performance.Log on to your DBMS as either the dbo (Microsoft SQL or Sybase) orschema owner (Oracle) of the database that contains CA ERwin MM.40 Implementation Guide