IBM E027SLL-H - Tivoli Monitoring - PC, Руководство по устранению неисправностей, Страница: 91 / 310

For example, consider an environment in which the monitoring agent for DB2 and
the Linux OS agent V6.2.3 are installed on the same computer. The DB2 agent
connects to the RTEMS 1 monitoring server and the OS agent connects to the
RTEMS 2 monitoring server. After the upgrade, the DB2 agent connection is to
RTEMS 2 rather than RTEMS 1. The same problem occurs when agents at V6.2.3 or
earlier are updated using group deploy or single deploy.
If you have a Tivoli Monitoring V6.2.3 (or earlier) OS agent installed on the same
computer as a product monitoring agent and both agents connect to different
monitoring servers, upgrade the OS agent to V6.2.3 Fix Pack 1 or later version
before upgrading the other monitoring agent. Otherwise, a remote deployment
upgrade of the monitoring agent causes the monitoring server connection to
change to the same monitoring server that the OS agent connects to.
Receive duplicate insert errors (SQL1 return code 80) after an
agent switches away from the remote monitoring server and then
switches back
When a Global Access List hub monitoring server is installed with a previous
version of a remote monitoring server, you will see duplicate insert errors (SQL1
return code 80) after an agent switches away from the remote monitoring server
and then switches back. These messages do not indicate an environment execution
error.
Upgrade SQL file not found when installing application
support on the standby hub
When adding application support to the hubs in a hot standby setup, after the first
hub has been seeded, you might receive an error message similar to the following
about the
productcode_upg.sql
file not being found while seeding the second hub:
Seeding support for Monitoring Agent for Microsoft SharePoint Server [8 of 10]
KCIIN1602E ERROR - file not found:
/boadata/IBM/ITM/tables/cicatrsq/SQLLIB/kqp_upg.sql
Option "-f install|upgrade" can be used with the "itmcmd support" command to force
using the pristine installation or upgrade support file for the product’s
application support. Seeding failed.
Seeding support for Monitoring Agent for Microsoft Virtual Server [9 of 10]
KCIIN1602E ERROR - file not found:
/boadata/IBM/ITM/tables/cicatrsq/SQLLIB/kqr_upg.sql
Option "-f install|upgrade" can be used with the "itmcmd support" command
to force usingthe pristine installation or upgrade support file for the
product’s application support. Seeding failed.
This error is not necessarily a fatal error. It simply means the application did not
provide an upgrade seeding file. There are generally two types of seeding files:
install and upgrade. The installer determines which one to apply by checking to
see if there are already situations belonging to the application on the target hub. If
no situation is found, then the installation seeding file is chosen, otherwise the
upgrade seeding file is used if provided. In a hot standby setup, as soon as one
hub is seeded, the other hub can copy the situations immediately. So when seeding
is applied to the second hub, the installer detects existing situations and looks for
the upgrade seeding file instead. Even though some applications do not provide
upgrade seeding files, because the hubs automatically synchronize seeded data, it
is generally not a serious issue. Seeding can still be forced on the second hub by
using the -f option.
Chapter 5. Installation and configuration troubleshooting
73