Hi.
We are beating our heads against the wall over here after applying the 11.6.1 patch on Linux 64-bit.
Fathom refuses to start so we cannot access via OpenEdge Explorer.
Any ideas on where to start looking? It usually "just works" and was working until this morning.
Was this morning when you installed 11.6.1? Is there anything unusual with the way you've installed 11.6 or is it all default settings?
Oh and I'd be contacting tech support as well.
Yes, this morning was the patch installation. No problems starting prior to that.
When trying to start fathom manually, getting an error creating OpenEdge Management configuration database..
[State Info]
nPlatformId=43
targetDir=/dlc/11.6
workDir=/dlcwrk/11.6
oemtargetDir=/dlc/oemgmt_11.6
oemworkDir=/dlcwrk/oemgmt_11.6
archiveDir=/dlc/install/11.6
docRootDir=
scriptsDir=
javaHome=/dlc/11.6/jdk
jfcHome=/dlc/11.6/jfc
cpinternal=ISO8859-1
cpcoll=Basic
cpcase=Basic
dateFormat=mdy
numberFormat=
numsep=44
numdec=46
folderName=
defaultLanguage=English - American
defaultCountry=
Error in my admserv.log:
[2016/03/11@10:53:22.607-0600] [0] [Fathom] * Error starting Fathom probe: "Error loading the activity database: Error opening OpenEdge Management activity database: /dlcwrk/oemgmt_11.6/cachedata/cachedb, Reason: Cluster with id 39 already belongs to class PartitionSummary" (10148)
proenv
proadsv -stop
cd /dlcwrk/oemgmt_11.6/cachedata/cachedb/
rm -rf *
proadsv -start
Thank you. That seemed to be the magic trick. What was the deal?
It is an orientdb bug: github.com/.../3434.
Supposed to have already been fixed a while ago prior to the version we use.
I suppose if you carried over your cache database from pre 11.6, it may have already been triggered? Impossible to know at this point since you wiped out the database :)