Consultor Eletrônico

Status: Unverified

SYMPTOM(s):

Getting error 1422 performing compact job with OpenEdge Management.

Getting error 1422 performing compact job with Fathom Management.

FACT(s) (Environment):

All Supported Operating Systems
OpenEdge Management 3.1C 32-bit
OpenEdge Management 3.1C 64-bit
OpenEdge Management 3.2x

CAUSE:

Bug# OE00131298

CAUSE:

The Fathom / OpenEdge management database is imprinted with the UTF8 codepage but the collation information shipped within the database is not the UTF8 collation table.

Under some circumstances, clients passing data to the Fathom / OpenEdge trend database may use code page information which can not be properly processed using the collation table which is shipped within the Fathom / OpenEdge database.

FIX:

Steps to correct the 1422 problems.

1) Backup the Fathom / OpenEdge database.
2) Find the table associated with the index name listed by the 1422 error.
(the error should contain the recid and index name which contains the error)
This code should show the corresponding table:
FOR EACH _file,
EACH _index OF _file WHERE _index-name = "put index name here".
DISP _file-name.
END.
3) Export record(s) for tables which reported the 1422 error.
Example of code:
output to ".\records.txt".
find first <table name here> where recid(<table name here>) = <recid in error>.
export <table name here>.
output close.
4) Identify the area the table exists in.
Example of code:
FOR EACH _file WHERE _file._file-name = "<table name here>",
EACH _storageobject WHERE _Object-number = _File-Number NO-LOCK,
EACH _area OF _storageobject WHERE _storageobject._object-type = 1 NO-LOCK.
DISP _file._file-name _storageobject._area-number.
END.
5) Delete the records listed by the 1422 error using proutil and the idxfix option.
Example:
proutil <database name here> -C idxfix
choose option 6
input recid here reported by error 1422
input area number here determined in step 4
6) Use the data dictionary to load a definition file for the database. Load the _tran.df located in the $DLC/prolang/utf directory.
7) Perform a full index rebuild for the database make sure to use the -cpinternal utf8 and -cpstream utf8 startup parameters on proutil.
Example:
proutil <database name here> -C idxbuild -cpinternal utf8 -cpstream utf8

For all future connections to the database use -cpinternal utf8 -cpstream utf8.
8) It may be possible to re-enter the data exported in step 3 at this point.

If this is the only database running on the system, modify the $DLC/startup.pf and make sure the -cpinternal is set to utf8 and that
-cpstream is set to utf8.