Kbase P101907: Getting corrupted fathom.odb resource database when starting AdminServer after upgrade to Fathom Man
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.1D
Fathom Management 3.0A
SYMPTOM(s):
Migration from Fathom Management 2.x
Unable to start AdminServer
Unable to start Fathom
Getting from with fathom.odb resource database when starting AdminServer
Error starting Fathom probe: "Error opening project Fathom database: /prso/dlc/fathom/config/fathom.odb" (10148)
Exception at Sun Jan 30 19:29:59 GMT+01:00 2005:
java.lang.NullPointerException
Message (throw): Error starting Fathom probe.
Message (excp): null
Stack Trace:
java.lang.NullPointerException
at
com.progress.fathom.management.rule.AbstractBaseThresholdRule.postLoadInit(A
bstractBaseThresholdRule.java:105)
at
com.progress.fathom.management.rule.BaseThresholdRule.postLoadInit(BaseThres
holdRule.java:133)
at
com.progress.isq.ipqos.ProjectStorage.StorageProject.postLoadInitResources(S
torageProject.java:408)
at com.progress.isq.ipqos.Probe.createResources(Probe.java:967)
at com.progress.isq.ipqos.Probe.start(Probe.java:523)
at com.progress.isq.ipqos.plugin.Fathom.start(Fathom.java:344)
at com.progress.isq.ipqos.plugin.FathomPlugIn.run(FathomPlugIn.java:460)
at java.lang.Thread.run(Thread.java:484)
fathom.odb file is present and exist
CAUSE:
This is a known issue.
FIX:
1) Export configuration as XML file in Fathom Management 2.x.
2) Upgrade to 3.0A01
3) Remove the FATHOM/config/fathom.o* files.
4) Start the AdminServer
5) Import XML file with configuration.
6) Redefine jobs since not in XML export file due to known issue.