The Process Analyzer
databases must be restored if either they or
the Process Engine
database has become corrupted. If the Process Analyzer
databases are corrupt, you must restore the
Process Analyzer
databases and manually resynchronize the Process Engine
and Process Analyzer
databases, as explained in the procedure below.
NOTE If
only the Process Engine
database has become corrupted, you must stop
both Process Analyzer
and Process Engine
and restore the respective databases. (See the
procedure below for information on restoring
Process Analyzer.)
In addition, if the Process Engine
and Process Analyzer
databases were not backed up at the same time,
they must be manually resynchronized as explained
in Step 4 below.
To restore Process Analyzer
Stop the Process Analyzer
server. To stop the Process Analyzer,
stop the AEEngine.exe and the Pubsvc.exe Windows
Services.
Restore the following Windows Registry
key:
HKEY_LOCAL_MACHINE\Software\FileNet\Process
Analyzer Engine
Restore the Process Analyzer
database
Synchronize the Process Engine
and Process Analyzer
databases. To synchronize the databases, reset
the F_AEXMitStat to 1 for all events with
F_AEXMitStat equals to 2 and the time stamp
(F_TimeStamp) of the events is greater or
equal to the timestamp of the last event received
by the Process Analyzer.
To reset F_AEXMitStat, complete the following
steps.
For each event log in the
Process Engine
database, determine the timestamp of the
last recorded event using the following
SQL script:
select
top 1 EventTimestamp from F_Events order
by EventTimeStamp desc;
Convert the event timestamp
to the number of seconds using the Convert
function of vwtool. See Welcome
to vwtool for more information on
using this utility.
Reset the F_AEXMitStat to 1
using the following SQL script:
update
<event_log_name> set F_AEXMitStat
= 1 where F_AEXMitStat = 2 and F_TimeStamp
>= <timestamp_in_seconds>
For example:
update
f_sw.vwlog1_135 set F_AEXMitStat = 1 where
F_AEXMitStat = 2 and F_TimeStamp >=
1067587200