When Upgrading A System Service Monitors Agent From 3.2.1 To 4.0, Receive Kdy3008E Message; The Tivoli Data Warehouse Fails And You Either Lose Data Or Have Memory Problems - IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual

setup on a fixed port number. For information on how to setup the Warehouse
Proxy Agent, see the IBM Tivoli Monitoring Installation and Setup Guide
(http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/
com.ibm.itm.doc_6.2.3fp1/itm623FP1_install.htm).
When upgrading a System Service Monitors agent from 3.2.1 to 4.0,
receive KDY3008E message
The previous agent is still running and using the port that is needed for the
upgraded agent. Stop the agent before the upgrade. Once the agent is stopped, the
upgrade is successful.
The Tivoli Data Warehouse fails and you either lose data or have
memory problems
On distributed systems, the data is written to the local file system. When the
Warehouse Proxy Agent receives the data, it copies the data to the Tivoli Data
Warehouse. If the Tivoli Data Warehouse is not available, the collected data could
take up a significant amount of memory.
On z/OS systems, the data is written to the persistent datastore. Maintenance
procedures must be installed and workable to handle cases other then simply
saving copies of the data. These procedures are used to recover corrupted datasets
and to handle migration issues. When the persistent datastore is started, it looks at
the status of a dataset and determines if it has corrupted data. If there is
corruption, it launches maintenance with the options to export the data, reallocate
and initialize the dataset, and then restore the exported data. Also when the
persistent datastore is started, it compares the information in the dataset against
the current configuration to see if any table structures have changed. When it
detects a change, it goes through the same process that effectively does a database
REORG. If you do not have the maintenance procedures installed and usable, the
datasets might become unusable, and therefore there might be a loss of data.
If maintenance is set-up so that the data is rolled-over, the data that would have
been copied to the Tivoli Data Warehouse is copied over after a set period of time.
You can set maintenance to roll off the data. For more information on rolling of
this data so that it is backed up, see the IBM Tivoli Monitoring Configuring Tivoli
Enterprise Monitoring Server on z/OS Guide.
If maintenance is not performed, then the agent stops writing to the Tivoli Data
Warehouse until initialization is performed. Because the agent has stopped writing,
the data is there "forever" until you re-initialize and start again writing from the
top of the first dataset.
If persistent datastore maintenance is allowed to proceed automatically as it is
intended, then the agent starts writing from the top of the first persistent datastore,
therefore wrapping occurs.
The persistent datastore is set up to allow for 24 by 7 data collection even if
maintenance is not specified when configuring the product in ICAT. There are
typically 3 datasets, though having more is allowed.
The minimum of 3 datasets allows for continuous collection, the normal case is
that one dataset is empty, one or more are full, and one is active. When an active
dataset becomes full, the empty dataset is activated for continued writing. When
194
IBM Tivoli Monitoring: Troubleshooting Guide