Step 3: Perform preparatory tasks

You must prepare your system before upgrade. To do this, perform the following tasks:

1. Check the locale information and make sure it is English, especially when the SM Server is running on the Linux platform. You need to run the locale command on the Linux platform to get the locale information, and then set it to en_US.UTF-8 as necessary.

2. Increase the value of the shared_memory parameter in the sm.ini file to a value over 256000000.

3. Use the Windows client to disable the Client side load/unload option. To do this, click Window > Preferences, and then click to clear the option.

   Caution Failure to disable this option will cause the upgrade process to fail.

4. Disable Development Audit. To do this, navigate to Tailoring > Audit in the System Navigator, and then click Turn Auditing On/Off. Clear the Do you want to audit development changes? option if it is selected, and then save the change.

5. Clean up any records in the following log files:

   • Msglog

   • Syslog

   • Errorlog

   Note Back up the table data if you need it later. If the tables contain too many records, the upgrade process will be slow.

6. Clean up the following messaging files:

   • Mail

   • Eventin records

   • Eventout records

   Note Back up the table data if you need it later. If the tables contain too many records, the upgrade process will be slow.

7. Clean up any files in the systemperform table.

   Note Back up the table data if you need it later. The systemperform dbdict will be converted from lob columns to real database columns. Therefore, if there are too many records in the systemperform table, transfer.bin will load very slowly.

8. Update the Service Manager configuration files.

   The following tables list the changes that you need to make to the Service Manager configuration files before running the Upgrade Utility. Record all changes that you have made so that you can revert them to the original status after the upgrade.

   Stop the Service Manager server, apply the required changes to the configuration files, and then restart the Service Manager server.

   sm.cfg

   Parameter	Changes	Description
   sm system.start	If this parameter exists, comment it out by changing it to: #sm system.start	Commenting this parameter out disables the background processes.
   sm -sync	Add this parameter to the end of the file if it does not exist yet.	This parameter starts the sync process, which identifies and releases locks owned by inactive processes and shared memory that is not in use.
   sm -httpPort	If there is more than one instance of the sm -httpPort parameter, keep only one instance.	Each sm -httpPort parameter starts a Service Manager server process that can handle a certain number of client sessions (see the Service Manager Help Center documentation for more information). Keeping one process alive will be enough for the upgrade process.
   Other parameters	Comment out all other parameters except the ones mentioned in this table.	Commenting out those parameters disables all the other Service Manager processes that are not required during an upgrade.

    

   sm.ini

   Parameter	Changes	Description
   ir_disable:1	Add this parameter to the end of the file if it does not exist.	This parameter disables all IR keys on your existing Service Manager system. This will make the upgrade process run faster.
   sessiontimeout:1200	Add this parameter to the end of the file if it does not exist. If this parameter already exists, update it to an appropriate value.	This parameter defines the number of minutes that the server waits for a client heartbeat signal before the server assumes that the client session has timed out and closes the connection. A value of 1200 sets the timeout to 20 hours (1200 minutes), a period that should be enough for an upgrade phase to complete in a typical scenario.
   shared_memory:256000000	Replace the default shared_memory:32000000 with shared_memory:256000000.	This sets the shared memory size to 256 MB. However, if you have a large database, you may need to allocate more shared memory to accommodate the upgrade processing.
   heartbeatinterval:120	Add this parameter to the end of the file if it does not exist.	This parameter controls the client heartbeat frequency. If the server does not receive a heartbeat from the client within the time-out limit as defined by the sessiontimeout parameter, the server terminates the client. All unsaved data is lost and the client must establish a new connection.

Restart the Service Manager server before you perform the upgrade in order for these tasks to take effect.