Kbase P135924: OpenEdge Management does not start due to the fathom.od* database reaching max number of objects
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
19/04/2011 |
|
Status: Unverified
SYMPTOM(s):
OpenEdge Management does not start
Errors in the admserv.log file
Errors in the ads0.exp file
Fathom.od* file size totals more than one gigabyte.
[*UnexpectedError*] * recorded as exception #407 in file ads0.exp.
[Fathom] * Error starting Fathom probe: "There is no transaction associated with this thread." (10148)
Exception at Fri Oct 10 16:38:51 EDT 2008: com.odi.AbortException
Message (excp): PSE Pro can store a maximum of 16777212 objects. Committing this transaction will exceed that limit.
Stack Trace:
com.odi.AbortException: PSE Pro can store a maximum of 16777212 objects. Committing this transaction will exceed that limit.
at com.odi.imp.pro.ObjectTable.writeObject(ObjectTable.java(Compiled Code))
FACT(s) (Environment):
UNIX
Windows
OpenEdge 10.x
CAUSE:
Bug# OE00176285
FIX:
As a workaround, assuming care has been taken to backup the OpenEdge Management configuration, remove/move the fathom.od* files and copy in the configuration backup file as fathom.xml and restart the AdminServer.