Kbase P70909: Getting error with fathom.odb resource database when starting AdminServer
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  12/08/2008 |
|
Status: Verified
SYMPTOM(s):
Unable to start AdminServer
Unable to start Fathom
Getting error 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 Mon Mar 08 17:05:39 CET 2004: com.progress.isq.ipqos.ProbeException
Message (throw): Error starting Fathom probe.
Message (excp): Error opening project Fathom database: /prso/dlc/fathom/config/fathom.odb
Stack Trace:
com.progress.isq.ipqos.ProbeException: Error opening project Fathom database: /prso/dlc/fathom/config/fathom.odb
at com.progress.isq.ipqos.Probe.loadProject(Probe.java:1998)
at com.progress.isq.ipqos.Probe.createResources(Probe.java:820)
at com.progress.isq.ipqos.Probe.start(Probe.java:448)
Exception at Mon Mar 08 17:05:39 CET 2004: com.odi.FatalInternalException
Message (throw): Error opening Fathom configuration database: /prso/dlc/fathom/config/fathom.odb
Message (excp): getOTEDataFileOffset(): when file offset not allocated. OID:0
Stack Trace:
com.odi.FatalInternalException: getOTEDataFileOffset(): when file offset not allocated. OID:0
at com.odi.imp.pro.ObjectTable$CachedObjectTable.getOTEDataFileOffset(ObjectTable.java:4207)
at com.odi.imp.pro.ObjectTable.readObject(ObjectTable.java:1298)
at com.odi.imp.pro.GenericObject.fetch(GenericObject.java:27)
at com.odi.imp.ObjectManager.initializeObjectFromDB(ObjectManager.java:2708)
fathom.odb file is present and exist
FACT(s) (Environment):
IBM AIX
Progress 9.1D
Fathom for Management 2.1A
Fathom Management 3.0A
CAUSE:
Corrupted fathom.odb (fathom resource database)
FIX:
1) Stop the AdminServer
2a) estore Resource database ($FATHOM/config/fathom.o* files) from a backup and start again the AdminServer.
or
2b) If backup is not present - the only way is to recreate resource database from scratch.
On Unix, issue the command:
rm $FATHOM/config/fathom.o*
On Windows, issue the command:
del %FATHOM%\config\fathom.o*
3) Restart the AdminServer.