Kbase 22066: Fathom Alert: Fathom Cannot Reach the Trend Database
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  6/5/2002 |
|
SUMMARY:
This Knowledge Base Solution summarizes changes that Fathom Management users may need to make to the java_env file for Progress Versions 9.1C and 9.1D.
EXPLANATION:
Fathom uses $DLC/bin/java_env to communicate with the SQL Server through the JDBC driver each time it writes data to the Fathom Trend database. Due to a problem in the java_env script, the shared library path variable might not be set correctly on platforms where Progress does not ship the JDK/JRE. This would prevent Fathom from reaching the Trend database.
Progress currently does not ship the JDK/JRE on Compaq Tru 64 and Linux, so on these platforms, you should do the following the steps below before starting the AdminServer.
SOLUTION:
1) Make a backup copy of the $DLC/bin/java_env file.
2) Open $DLC/bin/java_env in a text editor.
3) Move to the section of the java_env file specific to your
operating system. For example "OSF1" or "Linux".
4) Change the line:
JREHOME=$JDKHOME
to:
if [ -d $JDKHOME/jre ]
then
JREHOME=$JDKHOME/jre
else
JREHOME=$JDKHOME
fi
5) On Linux, change the LD_LIBRARY_PATH setting to:
LD_LIBRARY_PATH=$JREHOME/lib/$ARCH:$JREHOME/lib/$ARCH/${THREADS_FLAG}_threads:$JREHOME/bin:$JREHOME/lib/$ARCH/$VMTYPE:$LD_LIBRARY_PATH
Without this change you will see a Fathom Alert similar to the following:
Fathom cannot reach the trend database at jdbc:jdbcprogress:T:localhost:4455:fathomdb. Check the log
file for more information. (9892)
In the fathom.lg file, you will see this message:
18:23:32 BROKER 0: SQL server process terminated. (8841)
If this continues for several hours, it might cause the AdminServer to crash.