| | Troubleshooting (OP-CE)Procedure Use this procedure if one or more upgrade programs fail during a Data Upgrade Run. - Start the Data Upgrade Runs (ttspt2500m000) session.
- Select the run and, on the appropriate menu, select Data Upgrade Tasks. The Data Upgrade Tasks (ttspt2520m000) session starts.
- Select View > Sort
By > Upgrade Tasks by Real
Status.
- Navigate to the upgrade tasks with Real Run Status Failed.
- Double-click a task. The Data Upgrade Tasks (ttspt2520m100) details session starts.
- In the Files by Data Upgrade Task tab,
double-click a log file.
- View the contents of the log file.
- Solve the problem that caused the failure. For example:
- Create a correction program.
- Contact Infor Support.
- Contact a consultant.
- If the problem is solved, ensure the task is restarted.
- If the Data Upgrade Run is still running, set the Real Run Status of the task to Ready for Retry. You must perform this action in the Data Upgrade Tasks (ttspt2520m100) details session.
- If the Data Upgrade Run does not run anymore, restart the
run and ensure the failed task is started:
- Select the run in the Data Upgrade Runs (ttspt2500m000) session.
- On the appropriate menu, select Data Upgrade Engine. The Data Upgrade Engine (ttspt2201m000) session starts.
- Select the Include failed upgrade tasks check box.
- Fill out the remaining fields and click Continue.
Trace level You can set an additional Trace Level in the Data Upgrade Engine (ttspt2201m000) session. The trace level indicates the amount of information that will
be written to the $BSE/log/log.due file. This information provides insight in the scheduling and the
communication between the multiple bshells. You can select these trace levels: - 0 - No Extra Logging
- 1 - Some Details
- 2 - More Details
- 3 - Full Details
Performance and finetuning You can optimize the performance of the Data Upgrade Engine. See
the "Performance and finetuning" section in this guide. | |