Kbase P142749: CRC errors attemtping to run Database Area Status or Database Index Usage OE Management report
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
13/03/2009 |
|
Status: Unverified
SYMPTOM(s):
Error attemtping to run Database Area Status OE Management report
Error attemtping to run Database Index Usage OE Management report
CRC for Db_AreaStatus does not match CRC in src/dbareastatus. Try
recompiling. (1896)
Report is created from a template
FACT(s) (Environment):
UNIX
Windows
OpenEdge Management 3.1C 32-bit
OpenEdge Management 3.1C 64-bit
CAUSE:
The field postions of IndexStat_IdxNum of Ar_IndexStat, AreaStatus_Freenum of DB_AreaStatus, AreaStatus_Rmnum of DB_AreaStatus, and IndexStat_IdxNum of DB_IndexStat are different than the default Fathom Trend Database.
FIX:
The dbareastatus.r and dbindexstat.r files need to be recompiled. A development license is needed to do this.
1) Backup or move (or rename) the existing dbareastatus.r file away from the <fathominstall>/src directory
2) Extract the dbareastatus.p file from the fathom4gl-p.pl file into <fathominstalldir>/src directory by running:
prolib fathom4gl-p.pl -extract dbareastatus.p
3) Create a <fathominstalldir>/src/include directory
4) Extract the definitions.i file from the fathom4gl-p.pl file by running:
prolib fathom4gl-p.pl -extract definitions.i
5) Connect a prowin32 session to the trend database:
proenv>prowin32 c:\fath31c\db\fathom -U trending -P trending
for unix:
proenv>mpro /fathom31c/db/fathom -U trending -P trending
6) Tools -> Application Compiler
7) Click the Add button and add the fathom/src/dbareastatus.p file (include sub directories). Highlight the dbareastatus.p line and click compile.
There may be some errors, but a .r file should be created.
If a development license is not available, stop the FathomTrendDatabase, back it up, remove it, and restore from the existing Fathom.bak.