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

For IBM Tivoli Monitoring v6.2.2 Fix Pack 2 or higher, you can set it in the
command environment , using SET/export, or you can set it in the environment
files (KUIENV on Windows systems, or the $CANDLEHOME/bin/tacmd shell
script on UNIX and Linux systems).
The portal server and Warehouse Proxy Agent fail to connect to the
database on a 64-bit Windows system
The ODBC control panel available in the Windows Start menu is for 64-bit ODBC
configuration. Since the portal server and the Warehouse Proxy Agent are 32-bit
applications the 32-bit ODBC control panel must be used. Launch the 32-bit ODBC
window from C:\Windows\SysWOW64\odbccp32.cpl and manually create the
"ITM Warehouse"/"TEPS" ODBC source by going to the System DSN tab and
clicking
Add .
Failed to log on as sysadmin with portal server LDAP enabled
When LDAP authentication is enabled for the Tivoli Enterprise Monitoring Server,
the
sysadmin
ID must be defined in the LDAP server. However, when LDAP is
enabled for the Tivoli Enterprise Portal Server, the sysadmin ID should exist in the
monitoring server's local OS user registry, but should not be defined in the LDAP
server, otherwise, the sysadmin ID will not be able to log in.
On AIX systems, newly created users with auto-expire passwords
cause installation failures
When installing on AIX systems, security policies for newly created users
auto-expire the password after the first use and require you to set a new (or same)
password as a permanent password. The Tivoli Enterprise Portal Server
configuration interface allows you to create a new user ID for the portal server and
warehouse database, but using the interface always fails because the user
password is not set and is expired. You must ssh/telnet into the same server, using
the target user ID, and set the password appropriately.
Linux portal server unable to FTP catalog/attribute files
Linux portal server unable to FTP catalog/attribute files with Manage Tivoli
Enterprise Monitoring Server. A monitoring server is needed along with the portal
server (on the same system) to be able to seed a z/OS monitoring server.
Upgrading the Tivoli Enterprise Portal Server takes a long time
Performing a Tivoli Enterprise Portal Server upgrade, depending on the efficiency
of the hardware platform, can take anywhere from 30 minutes to over an hour.
Running the Tivoli Management Services Discovery Library Adapter,
results in a book that does not contain the fully qualified host name
Edit the resulting xml file and change the shortname to the fully qualified host
name.
148
IBM Tivoli Monitoring: Troubleshooting Guide