Multiple updates to the same property on the two systems might cause a
mismatch.
Symptoms
A problem can occur when the FileNet® Image Services export_log
becomes backlogged, and both FileNet Image Services and Content Platform Engine change a property to the same value before the first change is
processed. Subsequent changes on Content Platform Engine can become
mismatched after the FileNet Image Services export_log finally catches up.
Stopping the FileNet Image Services dispatchers can also create a FileNet Image Services backlog in the export_log table.
Diagnosing the problem
When a federated document is cataloged on both Content Platform Engine and
FileNet Image Services, multiple updates to the same property from each system
might cause a mismatch if the export_log table is full or if the FileNet Image Services dispatcher is stopped.
When a property mismatch occurs, the
FileNet Image Services elog file
contains entries similar to the following
example:
2011/01/14 03:45:16.749 90,6,54 HGFCG0054W <msar> INXs (2828.4412.354 0xb0c.113c) ... [WARNING]
Mismatch doc_id=1000009319 index=STR_K_M_180 ce_os_id=1003
Doctaba Index value:
<< index(#70) type(50=ASCII), size(1), value =
62000000 00000000 00000000 00000000 ( b??????????????? ) >>
CE old Index value:
<< index(#70) type(50=ASCII), size(1), value =
61000000 00000000 00000000 00000000 ( a??????????????? ) >>
CE New Index value:
<< index(#70) type(50=ASCII), size(1), value =
62000000 00000000 00000000 00000000 ( b??????????????? ) >>
Resolving the problem
As a general practice, update or correct properties from either Content Platform Engine or FileNet Image Services consistently.
If updates are to be made from both systems for corrections, allow time for updates to take effect
before you update again. Also, ensure that the FileNet Image Services
dispatchers are started.