Reviewing upgrade log files
The installer writes status messages to a log file, giving a detailed account of all changes made to your data model during the upgrade. If the upgrade fails and you have to run the installer again, it resumes after the last operation it completed rather than repeating operations that have already been completed.
The log file is named cmdbengdebug.log, and by default is written to ARSystemServerDirectory\ARServer\db.
To specify a different location, edit the ar.cfg (Microsoft Windows) or ar.conf file (UNIX) before running the installer and change the value of the CMDB-Log-File-Location parameter.
The following messages are displayed in the log file:
[WARNING] [TID: 004092] : UpdateCacheInfo -- Error Retrieving Federation
Update information.... error code: 303
[WARNING] [TID: 004092] : UpdateCacheInfo -- Error Retrieving Dataset
Update information.... error code: 303
[ INFO ] [TID: 001160] : Finished upgrade to version 7.5.00
[WARNING] [TID: 001160] : WARNING: 8037 Index length longer than 255 bytes --
[WARNING] [TID: 001160] : may not work on all databases
[ INFO ] [TID: 001160] : Finished incremental upgrade.
[WARNING] [TID: 001160] : WARNING: 8037 Index length longer than 255 bytes --
[WARNING] [TID: 001160] : may not work on all databases
These warnings are normal, and you can ignore them.
Tip
Make a copy of the cmdbengdebug.log file to view after a successful upgrade. Even though the upgrade succeeded, you can use the log file to find out which instances you must migrate manually to keep your data in the Common Data Model. It also tells you which classes the upgrade installer was unable to delete due to the existence of subclasses you created.
Comments