Kbase P21559: Errors attempting to start Job within Fathom.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/5/2010 |
|
Status: Verified
SYMPTOM(s):
Errors attempting to start Job within Fathom.
Alert! Alert Name: FathomTrendingUnavailable, Resource Name: Fathom,
Severity: 3, Message: Fathom cannot reach the trend database at
jdbc:jdbcprogress:T:localhost:2002:fathomdb. Check the log file for more
information. (9892)
[Fathom] * message: [JDBC Progress Driver]:Too many values specified (7531)
[Fathom] * An SQL Exception occured during an insert into the trend database. SQLState: 21S01
[Fathom] * statement: INSERT INTO
PUB.Cf_Task_Detail values (270,''HVDEV01'',22,''FaxPoller'',''Poll for Fax
Results'',''d:\dlc\bin\prowin32.exe -basekey ini -ini
d:\sciidev\avcard-batch.ini -pf d:\sciidev\avbatch.pf -param "BRPSINET" -p
System/FaxPoller.p'','''',''c:\fathom\work'','''',''d:\sciidev\avcard\FaxPoller.
out'',''d:\sciidev\avcard\FaxPoller.err'',''3/18/2003'',41921,''3/18/2003'',4192
1,123,-1 ); (9494)
** Attempt to modify schema during run-time or query session. (484)
FACT(s) (Environment):
Fathom 2.0A
Progress 9.1D
Progress 9.1C
CHANGE:
Upgraded from 1.0A to 2.0A.
CAUSE:
Bug# 20020925-021
CAUSE:
If the only Progress license on the machine, other than Fathom, is a deployment license, such as Client Networking, the necessary updates to the Fathom tables are not made when upgrading the 1.0A install of Fathom. In the migration subfolder of the Fathom installation, there should be a migration.log file with the following entry:
** Attempt to modify schema during run-time or query session. (484)
One other way to tell is if the Alert_ID field is missing from the Cf_Task_Details table.
FIX:
To fix the problem:
1) Shut down the Fathom database.
2) Connect to the Fathom.db in single user mode and apply the Fathom20a.df file in located in the DB subdirectory of the Fathom install (eg. c:\program files\fathom\db).
3) Restart the Fathom database from the command line with any available TCP port.
4) Connect to the Fathom database with the SQLExplorer and run the update20a.sql.
5) Proshut the Fathom database
6) Restart Fathom normally.