| | TroubleshootingProcedure 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
视图, 参考, 操作 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 视图, 参考, 操作 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
继续.
Trace level If you set the DUE_TRACE environment variable to 1, an
additional
跟踪级别 field is displayed 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 - 无额外记录
- 1 - 部分详细资料
- 2 - 更多详细资料
- 3 - 所有详细资料
For details on how to set environment variables, see
Infor10 ERP Enterprise Server (LN) Technical Manual (U8172 US). | |