Kbase P128903: alerts generated with 11246 message resource when adminserver is started
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
17/07/2008 |
|
Status: Verified
SYMPTOM(s):
alerts are generated with 11246 message when adminserver is started
Resource name contains non-ASCII characters. This is not supported by Fathom. No Fathom monitor was created for this resource. Resource name: <name> (11246)
The resource name is not a database resource
resource is not visible in the OEM browser
FACT(s) (Environment):
Fathom Management 3.0A
OpenEdge Management
CAUSE:
The resource was created with non-ascii character in the name. Special characters are not currently supported.
FIX:
The first steps are to dump the current fathom resource configuration, edit out the special characters and then let Fathom re-create the Object Store database on startup with the edited configuration.
NOTE: if the resource name listed in the 11246 Alert is a database resource, please refer to Solution P128896, "alerts generated with 11246 message on database resource when adminserver is started"
Steps:
1a) To dump the configuration you need to have both Fathom and AdminServer running at the same time or shutdown at the same time, so let's ensure both are running:
$ proadsv -query
$ fathom -query
1b) then use an online dump while your Admin/OE Management are running:
fathom -dump fathom.xml -httpport port
# port of the Fathom Web server, as listed in the admserv.log startup: "Listening for HTTP connections on port 9190"
2b) Edit the fathom.xml to remove special characters.
Note; these are all stored in the <fathomInstallDir>/config/fathom.od* database),
3) shutdown the Fathom AdminServer
$ proadsv -stop -port 20931
4) rename the fathom.od* files in the fathomInstallDir/conf directory
5) Copy the fathom.xml created in Step 1b into the config directory (e.g. <fathomInstallDir>/config/fathom.xml )
6) restart the Fathom AdminServer
$ proadsv -start -port 20931
The Fathom Adminserver log file (admserv.log) can be interrogated as to the success or failure of individual resource import:
EXAMPLE:
At start up, Fathom will recognize that there is no fathom.od* files and so will rebuild the fathom.od* (PSE pro database) project from the fathom.xml file on the fly:
[Fathom] Opening Fathom configuration database: c:\fathom\30a\config\fathom.odb (11027)
[Fathom] Fathom configuration database not found: c:\fathom\30a\config\fathom.odb (11029)
[Fathom] Loading Fathom project file: c:\fathom\30a\config\fathom.xml (10185)
[Fathom] Loading Fathom project templates. (10193)
...
[Fathom] Creating Fathom configuration database: c:\fathom\30a\config\fathom.odb (11036)
[Fathom] Fathom configuration database created. (11037)
Pay special attention to any 10315 messages:
Conflicting resource not imported: localhost:library.action.compound.Default_Action (10315)
Finally, a listing of the <fathomInstallDir>/config/fathom.od* will show the sucessful creation of:
fathom.odb
fathom.odf
fathom.odt