Step 5: Run the Upgrade Utility

Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Now that you have a functional environment, you are ready to run the Upgrade Utility. Follow the steps in this step to run the out-of-box upgrade against the data in your development environment and to run your custom upgrade against your test and production environments. You must perform these steps in a Service Manager Windows client, instead of a web client.

Caution If the upgrade fails while the Upgrade Utility is running, fix possible issues and rerun the Upgrade Utility, and you should be able to resume the upgrade from the failure point; if the upgrade process cannot be resumed, you must restore the database to the last backup point and fix possible issues before you can rerun the Upgrade Utility.

The running of the Upgrade Utility involves the following three primary phases:

In the first phase, the Upgrade Utility guides you through several questions and collects information needed for the upgrade.

The second phase is the dbdict update phase, where the utility updates dbdicts.

The third phase is the data update phase, where the utility updates applications data.

To run the Service Manager Upgrade Utility, follow these steps:

From the System Navigator, click System Administration > Ongoing Maintenance > Upgrade Utility > Apply Upgrade to launch the Upgrade Utility.

In the text box, type the fully qualified path to the Upgrade Utility folder, and then click Next.

Example:

Windows: c:\temp\upgrade\

Linux: ~/upgrade/

Note You must have read, write, and execute permission to the folder.

The system displays a series of information for your verification, including Applications version upgrading from, Applications version upgrading to, Applications base version, Full path to the Upgrade Utility files and Language(s) to be upgraded. Verify these information and then click Next to continue.

Note If this screen does not display the correct information, do not continue with the upgrade. Instead contact Micro Focus Software Customer Support.

(Optional) The system prompts you to migrate legacy categories to the corresponding Process Designer-based modules. To move your selection between the legacy categories lists and the Process Designer-based modules lists, select a category and click the arrow button. Click Next.

Note This screen appears only when you are upgrading from the following versions:

Service Manager 9.3x without Process Designer Content Pack installed
Service Manager 9.3x with Process Designer Content Pack 9.30.2 (PDCP3) installed
Service Manager 9.4x Classic

Before you proceed, refer to Appendix A: Additional manual migration tasks on Service Manager 9.61 Hybrid for more information.

The upgrade is now ready to start. Click Next to start the upgrade.

When you are asked whether you want to proceed, click Yes.

The Upgrade Utility displays the status when the upgrade is being processed. The loading process may take a long time.

When you receive an UPGRADE IS COMPLETE message, the Upgrade Utility has finished the data processing and you can follow the instructions in the message to complete the next steps. After you click Finish, you are automatically logged out.

Restart the server and log back in to the client.

Open the scversion table in the Database Manager, and verify that the Applications Version field is 9.61.00xx. If this field displays a value other than 9.61.00xx, check the log files to identify the issue that occurred.

Upgrade Utility logs and error messages

The Upgrade Utility creates a set of log files during the upgrade process. These files reside in the log directory.

List of upgrade log files
Log file	Contents
detail.log	This file contains specific information about the upgrade, including the following: Almost all information in upgrade.log. Name of the file being purged. For example, “dbdict: upgradestatus is purged.” Progress of a file loading. For example, “Adding record # 100 from table upgradeobjects”. Changes made to fields during file processing. For example, “Increasing field length for incidentlib.company in kmquery dbdict from VARCHAR(40) to VARCHAR(70)” Signature of a file and the action on it. For example, “Processing Format Record : cc.get.dependen, signature=(current=3843738292, oob=NONE, upgrade=3843738292), upgraderesult=current”
except.log	This file contains information about any exceptions reported by the upgrade, including the following: Messages about data type mismatches that failed to be resolved, or database dictionaries failed to be upgraded. For example, "dbdict:FolderRights, field:delete, field type is logical -- expected to be:character" See Data type mismatches. Messages about the unique key changes that failed to be resolved. For example, "dbdict:Todo, Unique Key is {"record.id", "itemType"} -- expected to be:{"record.id"}" If there are exceptions logged in this file, we recommend you to resolve them in the "Resolving exceptions and conflicts" phase.
upgrade.log	This file contains information about where the upgrade is at any point. This file contains only the main steps of the upgrade, including the following: Starting and ending of each sub-phase. For example, “** Start Phase [Pre Upgrade Action Update] **” Main activities during each sub phase. For example, “Purging upgrade files...” Number of files to be processed. For example, “There are 608 dbdicts to be processed.” Names of the files being processed. For example, "Processing dbdict, AdvFilter”
pdmigration.log	The log file, which is stored in the Service Manager log directory, includes the following information: A list of Alert definition records that are created based on settings in your Classic categories A list of category, subcategory, and producttype records that are migrated to Process Designer-based tables A list of format level link records that are updated to disable the category, subcategory, and product.type link lines A list of the Classic probsummary and incident objects that are migrated to Process Designer-based objects A list of updated process records

List of upgrade log files

Log file

Contents

detail.log

This file contains specific information about the upgrade, including the following:

Almost all information in upgrade.log.
Name of the file being purged. For example, “dbdict: upgradestatus is purged.”
Progress of a file loading. For example, “Adding record # 100 from table upgradeobjects”.
Changes made to fields during file processing. For example, “Increasing field length for incidentlib.company in kmquery dbdict from VARCHAR(40) to VARCHAR(70)”
Signature of a file and the action on it. For example, “Processing Format Record : cc.get.dependen, signature=(current=3843738292, oob=NONE, upgrade=3843738292), upgraderesult=current”

except.log

This file contains information about any exceptions reported by the upgrade, including the following:

Messages about data type mismatches that failed to be resolved, or database dictionaries failed to be upgraded. For example, "dbdict:FolderRights, field:delete, field type is logical -- expected to be:character"

See Data type mismatches.
Messages about the unique key changes that failed to be resolved. For example, "dbdict:Todo, Unique Key is {"record.id", "itemType"} -- expected to be:{"record.id"}"

If there are exceptions logged in this file, we recommend you to resolve them in the "Resolving exceptions and conflicts" phase.

upgrade.log

This file contains information about where the upgrade is at any point. This file contains only the main steps of the upgrade, including the following:

Starting and ending of each sub-phase. For example, “**** Start Phase [Pre Upgrade Action Update] ****”

Main activities during each sub phase. For example, “Purging upgrade files...”
Number of files to be processed. For example, “There are 608 dbdicts to be processed.”
Names of the files being processed. For example, "Processing dbdict, AdvFilter”

pdmigration.log

The log file, which is stored in the Service Manager log directory, includes the following information:

A list of Alert definition records that are created based on settings in your Classic categories
A list of category, subcategory, and producttype records that are migrated to Process Designer-based tables
A list of format level link records that are updated to disable the category, subcategory, and product.type link lines
A list of the Classic probsummary and incident objects that are migrated to Process Designer-based objects
A list of updated process records

Connect

Micro Focus Marketplace

ITSM Blog for IT Service Management

ITSM Community

Documentation Forum

Learn

Software Support Online

Software Support Downloads

Software Education Services

Contact

Send Help Center feedback

Submit Service Request

View Service Requests