Kbase P98310: Fathom Dbagent not autostarting with database
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/29/2007 |
|
Status: Verified
FACT(s) (Environment):
Fathom Management 3.0A
Fathom Management 2.x
Progress 9.1D Service Pack 09
OpenEdge 10.0x
OpenEdge 10.0B Service Pack 01
All Supported Operating Systems
SYMPTOM(s):
Fathom Agent does not automatically start when starting the database with dbman
Autostart Agent is checked in Progress explorer.
Dbagent not autostarting with database
Dbagent will start with the Start Agent button in the Management Console
Database is local to the Fathom install
Database is managed by the Fathom/Progress AdminServer
monitored=true is set in the conmgr.properties under the [configuration.dbname.defaultconfiguration] section.
CAUSE:
Bug# OE00107052
CAUSE:
This issue was introduced in a change into how the license is or is not enforced depending on which version of Fathom | Progress 9/OpenEdge 10 is tied to
FIX:
The issue is fixed in Progress 9.1E and OpenEdge 10.0B01 or higher.
As a workaround:
Add the monitorlicensed=true property under the [database.dbname] section of the conmgr.properties file for each database that is being monitored. The dbagent will then automatically start after AdminServer is restarted.
Example:
[conmgr.properties]
[database.<displayname>]
autostart=true
configurations=fathomtrenddatabase.defaultconfiguration
databasename=H:\Fathomdb\fathom.db
defaultconfiguration=fathomtrenddatabase.defaultconfiguration
displayname=FathomTrendDatabase
monitorlicensed=true