Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
|A single word||
||Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".|
You can specify that the search results contain a specific phrase.
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.
Two or more words in the same topic
|Either word in a topic||
|Topics that do not contain a specific word or phrase||
|Topics that contain one string and do not contain another||
|A combination of search types||
- Upgrade the applications from a version earlier than 9.60
- Process of a major upgrade
- Upgrade the applications
- Applications major upgrade overview
- Planning an upgrade
- Upgrade tasks on the development environment
- Upgrade tasks on the test environment
- Upgrade tasks on the production environment
- Appendix A: Additional manual migration tasks on Service Manager 9.60 Hybrid
- Appendix B: Data migration
- Appendix C: Run the SQL compare utility
- Appendix D: Troubleshooting
- Appendix E: Mapping between legacy security profiles and current PD security roles
Appendix C: The SQL compare utility
The SQL compare utility is an informational tool that compares your existing table fields and unique key information with those of the Service Manager version you are upgrading to, and then reports the new and modified fields and unique keys that will merge into the existing tables. You can use the list of the fields and unique keys produced by the SQL compare utility to determine whether any fields or unique keys in your current system differ from those in the new version. You can also use the report to determine which new fields and unique keys you must add to RDBMS-mapped files if you choose to make the changes manually during the applications upgrade.
After running the SQL compare utility on the table fields, refer to the following table for the result types and the recommended actions.
|Result type||Recommended actions|
|(Null)||The related field is on the id field in the licenseinfo dbdict. No further action is necessary.|
|Nonexistent in Service Manager 9.60 fresh installation||This field is added by tailoring. No further action is necessary.|
|Not to be modified to other field type by the Upgrade Utility||Manually modify this field type according to the matching solution described in Data type mismatches.|
|Not to be modified to other field database type by the Upgrade Utility||Manually modify this field type according to the matching solution described in Data type mismatches.|
|Not to be moved to alias table by the Upgrade Utility||Manually modify this field type according to the matching solution described in Data type mismatches.|
|To be modified by the Upgrade Utility||This field type modification will be done automatically by the Upgrade Utility during the upgrade process. You can also manually modify this field type before the upgrade to improve the upgrade performance.|
|To be modified by the Upgrade Utility, and the original field name xxxx will be renamed to xxxx.old||This field type modification will be done automatically by the Upgrade Utility. No further action is necessary.|
|To be added by the Upgrade Utility||This new field will be added automatically by the Upgrade Utility during the upgrade process. You can also manually add this new field manually before the upgrade to improve the upgrade performance.|
After running the SQL compare utility on the table unique keys, refer to the following table for the result types and the recommended actions.
|Result type||Recommended actions|
|Nonexistent in Service Manager 9.60 fresh installation||This key normally is added by tailoring. Check this key to see whether it includes any field of added primary key or unique key.|
|Exist in Old OOB, and will be removed by the Upgrade Utility||This key exists in Old OOB only, but does not exist in Service Manager 9.60. The Upgrade Utility will remove this key automatically. No further action is necessary.|
|To be added by the Upgrade Utility||This key does not exist in Old OOB, but exist in Service Manager 9.60. The Upgrade Utility will add this key automatically. No further action is necessary.|
|To be ignored by the Upgrade Utility||The field is added as a unique key because Service Manager does not support operations on tables with primary keys when the applications version is earlier than 9.32. You can manually change the key type to primary key after the system upgrade.|
Note If you are going to accept the new DBDICTS and the changes made to the DBDICTS in the upgrade, you do not need to run this utility.