IBM E027SLL-H - Tivoli Monitoring - PC, Troubleshooting Manual

Page: 60 / 310

<Message Id="AMXUT2504I" Severity="INFO">
<Time Millis="1121977824199"> 2005.07.21 15:30:24.199 CST </Time>
<Server Format="IP">YFELDMA1.austin.ibm.com</Server>
<ProductId>AMXAMX</ProductId>
<Component>ScanTMR</Component>
</Component>1</ProductInstance>
<LogText><![CDATA[AMXUT2504I The software is creating a new baseline file
C:\PROGRA~1\Tivoli\db\YFELDMA1.db\AMX\shared\analyze\scans\
1889259234.xml.]];
</LogText>
<TranslationInfo Type="JAVA"
Catalog="com.ibm.opmt.utils.messages.MigrationManager_
msgs"
MsgKey="AMXUT2504I"><Param>
<![CDATA[C:\PROGRA~1\Tivoli\db\YFELDMA1.db\AMX\shared\analyze\scans\
1889259234.xml]];
</Parm></TranslationInfo>
<Principal></Principal>
</Message>
Reading RAS1 logs
The RAS1 trace log lists details related to the health of an ODBC data provider
application.
This topic provides an example of the universal agent RAS1 trace logs. By default,
the universal agent RAS1 trace log lists the following details about the ODBC data
provider application:
v
Whether the ODBC tables come online during startup.
v
Whether the ODBC table data is collected.
v
Errors with the ODBC-related status messages, including informational messages
about when each ODBC connection completes.
v
Errors that occur during ODBC data provider data retrieval, including errors in
the ODBC driver code.
v Independent Software Vendor (ISV) API errors. (The universal agent makes API
calls to the ISV ODBC driver to implement the connections and SQL select
statements.)
The following RAS1 log excerpt lists ODBC status messages using default tracing:
KUMP_ProcessStartUpConfig") Loading metafile
<f:\candle\cma\metafiles\TIVOLI_DATA_WAREHOUSE.mdl>
from startup config file
f:\candle\CMA\WORK\KUMPCNFG_INST1
"DCHserver::dp_register") Application TIVOLI_DATA_WAREHOUSE
successfully registered"KUMP_ProcessStartUpConfig")
1 application metafile(s) processed from startup
config
file f:\candle\CMA\WORK\KUMPCNFG_INST1
"KUMP_StartDataProvider") Starting ODBC Data Provider...
"KUMP_WaitODBCsourceReadyForMonitor")
Reusing connection handle for ODBC source
TIVOLI_DATA_WAREHOUSE table <syscharsets>
"KUMP_ODBCserver") Successfully connected to ODBC source
TIVOLI_DATA_WAREHOUSE table <syscharsets>
"KUMP_WaitODBCsourceReadyForMonitor") Reusing connection handle
for ODBC source TIVOLI_DATA_WAREHOUSE table <syscomments>
The
Reusing connection handle
messages indicates the ODBC provider is reusing
resource to conserve memory. The ODBC data provider allocates a connection for
each metafile with multiple attribute groups that connect to the same data source
42
IBM Tivoli Monitoring: Troubleshooting Guide