If the backup of the cell fails, verify:
Ensure that the trace messages of the mccomp command are not redirected to a log file. To check the trace messages, perform the following steps:
To verify or troubleshoot the KB migration process, you can review log files and reports.
You can find the log files under installationDirectory\server\SIEMupgrade\log. Look for the me.log and the navi.log files. The report file is located at installationDirectory\server\SIEMupgrade\report. Report names follow this syntax: PHASE_ID_TIME_STAMP, where PHASE_ID refers to the upgrade operation. For example, the report for the pre-upgrade phase would be named PreUpgradeChecks_ TIME_STAMP.
If you cannot execute the KB Migration Wizard because of connectivity issues, you can manually execute the mmigrate utility. The mmigrate utility is a BMC component that migrates older KBs to the latest KB formats.
BMC recommends that only experienced and knowledgeable users execute mmigrate utility.
For information about the mmigrate utility, see Using mmigrate utility.
You find the following error in the \pw\pronto\logs\ProactiveNet.log file:
You can encounter this entry in the log file if the index pointing to the primary key is corrupted. To overcome this problem, you must drop the index and re-create it.
On the computer that has Oracle Database, run the following query:
tableName is the name of the table that has the primary key.
The primary key is dropped.
Run the following query:
tableName is the name of the table that has the primary key, and columnName is the name of the column to which the primary key is created.
You find the following error in the \pw\pronto\logs\ProactiveNetPRUNER.log file:
You can encounter this entry in the log file if JServer has not initialized completely after the upgrade. It does not cause any problem for the pruner. The table partitions that are not removed get pruned in the next run of the pruner. You can safely ignore this error.