Hallo Herr Schwefel, Herr Thomas, Herr Frei,
ich hoffe, Sie sind am Mittwoch noch gut nach Hause gekommen. Hier die versprochenen Tips inkl. neuester Solution zur Journalisierung:Please find here the anwer to your question about how to prevent errors with
finalisation:1. How to prevent errors from happening ?
2. How to solve the errors when they occur ?
1. How to prevent errors from happening ?
A heavy workload and low performance can create these kind of problems. If you
want to prevent the error you can take the following actions:
- Use transactions with update mode "finalisation" (less locks on the history
tables).
- Do not finalise all the batches at the same time/ time period. (Not all
before lunch, after lunch or before going home.) - Use smaller batches.
- Make sure users do not turn off their machines while the background process
has not finished yet. (Let them wait for the unix-dollar sign).
- Use finalisation mode for integration transactions.
- Make sure you use recent software for the finalisationproces (solution 14745)
2. How to solve the errors when they occur ?
In your situation a batch was unsuccesfully finalized. Part of the batch was
still in tfgld102 and part was in tfgld106.
What can you do in a similar situation? In this case it is hard to avoid using
ttaad4100 ! Baan has created a correctionprogram, but if you want to run this
program, you have to set some statusses in tfgld100, tfgld101 and tfgld109.
When a finalization is aborted and the batch is partly in tfgld102 and partly
in tfgld106, you should use correctionprogram otfcor0203: Restart Finalisation
Process. This correction program is made for Update mode:- Real time
- End of session
You can also use this programm for Update mode 'finalization', but then the
backgroundproces must have been run (for update mode finalistion: the
backgroundproces is started first and after that the moving of the records from
102 to 106 starts).However, there are some conditions for using otfcor0203:
- the batch should have transactions in tfgld102 and tfgld106
- the batch should have batchstatus 'finalization in proces' (in tfgld100) and
the finalisation status should be "selected for finalisation" (tfgld100).
Further, the status in tfgld101 should be "finalisation in process".
- the finalization runnumber should have the status 'in use (2)'. Check this in
tfgld109.
If these settings are correct, then you can start the program and this will
move the remaining records from tfgld102 to tfgld106.
As the finalisation proces is interrupted, we always advise customers to run
Rebuild History tfgld3203m000 for the period of the runnumber concerned.