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.

By default, the cmdb_eng_debug_log.log log file is saved under the ARSystemServerDirectory\ARServer\db folder. You can specify a different location for the log file before you run the installer by setting the value for the CMDB-Log-File-Location parameter to your required location. The parameter is provided in the ar.cfg (Microsoft Windows) or ar.conf (UNIX) file.

The following examples show the log file entries for upgrade from version 8.1 to version 9.0.

Log file entry for base version 8.1

<INFO  > <TID: 0000000278> /* Tue Apr 21 2015 23:41:42.662 */    Starting incremental upgrade
<DEBUG > <TID: 0000000278> /* Tue Apr 21 2015 23:41:42.681 */    Installed CMDB Version is :- [
Application Id =OB00C04FA081BABZlxQAmyflAg1wEA
Application Name =BMC Atrium CMDB
Major Version =8
Minor Version =1
Maintenance Version =0
Patch Number =0
Version Exist ?=true
]

Log file entry for target version 9.0

<DEBUG > <TID: 0000000278> /* Tue Apr 21 2015 23:48:16.407 */    Installed CMDB Version is :- [
Application Id =OB00C04FA081BABZlxQAmyflAg1wEA
Application Name =BMC Atrium CMDB
Major Version =9
Minor Version =0
Maintenance Version =0
Patch Number =0
Version Exist ?=true
]

Log file entry after the upgrade process is complete 

<INFO  > <TID: 0000000278> /* Tue Apr 21 2015 23:55:49.129 */    CMDB Upgrade(UPGR) For 9.0.00 Patch 000 completed.
<INFO  > <TID: 0000000278> /* Tue Apr 21 2015 23:55:49.130 */    Finished incremental upgrade.