IBM E027SLL-H - Tivoli Monitoring - PC, Troubleshooting Manual

Page: 90 / 310

-x profilemanagers/DM_TEST_PM.xml
Specifies the name and location of the output file that resulted from the
assessment of the DM_TEST_PM profile manager.
-r Indicates that the purpose of this command is to perform a rollback.
-f scans/baseline.xml
Specifies the name and location of the baseline file to use as input for
this command.
3. Restart the Windows endpoint.
The rollback option can also be used to roll back an endpoint upgrade or a profile
upgrade independently. By rolling back the profile manager upgrade, you roll back
all upgrades (profile manager, profile, and endpoint) in one step.
“SQL1_OpenRequest status = 79” return code occurs during when upgrading an
agent:
The return code
SQL1_OpenRequest status = 79
occurs in the agent log
when the application support is added during an upgrade. This return code results
from an attempt to delete a table entry that does not exist in the table. When you
add application support for a V6.1 agent, the return code is expected behavior
because the agent application support data does not exist in the table.
Installation of OS agent on a Microsoft Windows Server 2003
fails with this error: “Unable to establish BSS1 environment,
can't continue”
This error is caused by the deletion of the gskit directory, whether intentionally or
by accident, without clearing the registry information. If gskit was previously
installed by another product and has a dependency on it, for example DB2 9.1,
then let that product reinstall it, or if there are no other products that depend on
the version of that gskit, then you can clear the GSK7 entry in the registry that can
be found under
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\IBM\GSK7
. Then rerun
the IBM Tivoli Monitoring installation to allow the gskit to be reinstalled.
Note: Create a backup of the registry before editing it.
Unable to update the Tivoli Data Warehouse agent by using the
command line interface
When using remote deployment to upgrade the Tivoli Data Warehouse agents
(Warehouse Proxy Agent and Summarization and Pruning Agent), you must use a
specific workaround to ensure that the upgrade is successful.
On UNIX and Linux systems, you must add the following variable to the
hd.ini
file for the Warehouse Proxy Agent or the
sy.ini
file for the Summarization and
Pruning Agent, and then restart the agent:
CTIRA_SYSTEM_NAME=$RUNNINGHOSTNAME$
On Windows systems, you must add the following line to the
KHDCMA.INI
file for
the Warehouse Proxy Agent or the
KSYCMA.INI
file for the Summarization and
Pruning Agent, and then reconfigure and restart the agent:
CTIRA_SYSTEM_NAME=%computername% .TYPE=REG_EXPAND_SZ
Monitoring server connection information is changed after
upgrade
A Tivoli Enterprise Monitoring Agent that connects to a different Tivoli Enterprise
Monitoring Server than the one that the OS agent connects to might have its
monitoring server changed after the monitoring agent is upgraded to a new
version using remote deployment.
72
IBM Tivoli Monitoring: Troubleshooting Guide