Unable To Locate The File Name Of An Exported Situation That Begins With Numerals; Tivoli Enterprise Portal Data For Unix Os And Linux Os Agents Is Not Updated After Stopping The Disk; Testing The Connection To The Tivoli Data Warehouse Database Is Valid Even With An Invalid Password; Configured Non-Root User Agent Starts Up As Root - IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual

Unable to locate the file name of an exported situation that begins with
numerals
Situations created with a name starting with a numeral are stored with a full name
based on your input and a situation name generated by the system. The situation
name is comprised of the letter Z followed by numerals. When you export
situations using the bulkexport sit command, the situations are exported by
situation name. The full name is stored inside the xml exported file. To avoid
losing track of your exported situations, do no use numerals to begin situation
names.
Tivoli Enterprise Portal data for UNIX OS and Linux OS agents is not
updated after stopping the disk
For the UNIX OS and Linux OS agents, the Tivoli Enterprise Portal data is not
updated after stopping the disk. The Tivoli Enterprise Portal Server provides GPFS
data gathered by AIX OS df command. Data gathered by the mmdf command might
conflict with the data displayed within a Tivoli Enterprise Portal view.
Testing the connection to the Tivoli Data Warehouse database is valid
even with an invalid password
A test of the connection shows that the connection to the Tivoli Data Warehouse
database as valid even if the password is incorrect. The first N characters of the
password entered in the Warehouse Proxy Agent and the Summarization and
Pruning Agent configuration are actually used, where N is the password length
defined in the operating system. Any trailing characters are ignored, even though
the password is incorrect.
This behavior is true for ODBC, JDBC, and for DB2, using an OS user. This
behavior is not true for MSSQL or Oracle, not using an OS user, but rather a DB
user.

Configured non-root user agent starts up as root

After configuring the agent to run as non-root, whenever it is restarted, the agent
restarts as root. This is a present issue with the Solaris operating system.

Large historical collections slow monitoring agents

If historical collection is turned on for an attribute group, it can produce a large
volume of data. Either turn off historical collection for the attribute group, or set
the pruning for the attribute group to 1 hour to avoid long-term problems.

Unable to access History Collection Configuration for any agent

You are unable to access History Collection Configuration from the Tivoli
Enterprise Portal for any agent, and you receive the following message:
Cannot Load Product Configuration Data
If you find that the Tivoli Data Warehouse database does not contain a
WAREHOUSEPRUNE table, and if in the portal server database the
KFWWHISTDATA table has been renamed KFWWHISTDATABAK, rename the
KFWHISTDATABAK table to KFWWHISTDA in the portal server, and then
176
IBM Tivoli Monitoring: Troubleshooting Guide