Kbase P103149: Fathom Management: FathomTrendingUnavailable due to Character string is too long (8184)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
03/11/2008 |
|
Status: Verified
SYMPTOM(s):
Fathom Management: Character string is too long (8184)
A data collection failure occurred for the system resource: <Fathom resource name>. (9856)
FathomTrendingUnavailable: Fathom cannot reach the trend database at <machine:port>. Check the log file for more information. (9892)
An SQL Exception occured during an insert into the trend database. SQLState: HY000
message: [JDBC Progress Driver]:Character string is too long (8184)
vendor: -20152
statement: INSERT INTO PUB.Cf_Status values (333,''srnmgmt01'',''3/21/2005'',51375,''The following resource has been disabled. Resource: {0}'',167625,'''' ) (9494)
no-matches in associated log files
no-matching exception evidence
FACT(s) (Environment):
Fathom Management 3.0A
All Supported Operating Systems
CAUSE:
This issue is related to SQL Width error(s) in the fathom.db
FIX:
Fix SQL-Width error(s) with the dbtool utility as follows:
1.) dbtool <dir/fathom/db/>fathom
<Select> Options
9. Enable/Disable File Logging
2. SQL Width Scan w/Fix Option
<connect>: (0=single-user 1=self-service >1=#threads)? 1
<table>: (Table number or all)? all
<area>: (Area number or all)? all
<display>: (verbose level 0-3)? 0
The resuting "dbtool.out" should show "***" next to the tables affected. In this particular case it was: [ _File; _Field; PUB.Cf_Status.Status_Status],
and second run of dbtool, with the Options 9 and 1, should then report no errors.
Add database startup parameter -SQLStmtCache 300 to increase the number of cached prepared statements to take effect the next time the FathomTrendDatabase is started.