Table of Contents
Advertisement
The tacmd removeBundles command is used to remove one or more deployment
bundles from the local agent deployment depot. The tacmd removeBundles
command requires double the size of the bundle disk space free in the depot. The
kdyjava.log file in the system temp directory provides additional information about
the problem.
tacmd executecommand command run against subnode fails
Subnodes are not enabled for the tacmd executecommand command to execute the
system command provided in the given command. The subnode might be
registered to run on a system or environment different from that of the the agent.
In this case, the monitoring agent does not track where the subnode is running, or
how to execute a command on that specific system or environment.
By not enabling the enhanced command execution for subnodes, you can avoid
this issue. Instead, you can use the tacmd executecommand command against a
subnode manager agent that controls the subnode.
The krarloff command returns an error message
The krarloff rolloff program can be run either at the Tivoli Enterprise Monitoring
Server or in the directory where the monitoring agent is running, from the
directory where the short-term history files are stored.
For more information about the krarloff command, see the topic on converting
files using the krarloff program in the IBM Tivoli Monitoring Administrator's Guide
(http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/
com.ibm.itm.doc_6.2.3fp1/adminuse/itm_admin.htm).
Unexpected KUIC02013E error message
When running on an operating system that is configured for locales that do not
conform to the Language_Locale convention, the tacmd command returns the
following message: KUIC02013E: The software did not run the command because
of a internal system error. Contact the system administrator.
The IBM Tivoli Monitoring command line environment expects the system to be
running in the Language_Locale convention, and is currently limited from
understanding other conventions. You can verify this problem by viewing the
kuiras1 log and looking for entries similar to the following:
(4C765377.008E-1:nls2.c,491,"NLS2_GetLocale") Entry
(4C765377.008F-1:nls2.c,494,"NLS2_GetLocale") Input parameters: languageId 0,
codepage 0, options 0.
(4C765377.0090-1:nls2.c,507,"NLS2_GetLocale") Zero language Id and codepage defined.
(4C765377.0091-1:nls2.c,3888,"NLS2_allocateLocale") Entry
(4C765377.0092-1:nls2.c,3907,"NLS2_allocateLocale") Preparing to initialize
(4C765377.0093-1:nls2.c,3980,"NLS2_initLocaleObject") Entry
(4C765377.0094-1:nls2.c,3983,"NLS2_initLocaleObject") Get the current native locale.
(4C765377.0095-1:nls2.c,3991,"NLS2_initLocaleObject") Locale returned is turkish.
(4C765377.0096-1:nls2.c,4000,"NLS2_initLocaleObject") Getting the locale basename.
(4C765377.0097-1:nls2.c,4022,"NLS2_initLocaleObject") Locale basename is turkish.
(4C765377.0098-1:nls2.c,4024,"NLS2_initLocaleObject") Locate locale basename in
(4C765377.0099-1:nls2.c,4042,"NLS2_initLocaleObject") Basename not found in table.
(4C765377.009A-1:nls2.c,4043,"NLS2_initLocaleObject") Exit: 0x25
202
IBM Tivoli Monitoring: Troubleshooting Guide
Locale structure.
table.
Not valid Locale name.
Advertisement
Table of Contents
Troubleshooting
