Errors Found in Log Files
Change Assistant scans log files that are generated when various processes run, such as SQL, Data Mover, SQR, CopyDatabase and so on. The following table describes what logs are produced and what Change Assistant determines to be an error:
The log files generated by Process Scheduler are not parsed for warnings or errors. Therefore, even though Change Assistant may show a status of Complete for a Process Scheduler step type, you should review the generated log files for more details.
|
Processes |
Log File |
Error |
Warning Status |
|---|---|---|---|
|
Application Engine |
<process name>_out.log |
Restart Failed. Invalid, Error. Abended. Abort. Not Defined. |
Warning. |
|
Build Project CompareAndReport CopyDatabase CopyFromFile CopyToFile CreateProject |
<process name>.log |
Error. Invalid PeopleCode. Copy process cancelled. Project <xxx> does not exist. |
Warning. |
|
DataMoverBootstrap DataMoverTools DataMoverUser LoadBaseData |
<process name>_out.log Note: Any logs generated by the Data Mover SET LOG statement will also be available. |
Unsuccessful. PSDMTX Error. |
Warning. |
|
DBTSFIX SQRReport |
<process name>_0.out <process name>_out.log |
TNS Error. Program Aborting. Not Defined Error. |
NA |
|
Deploy File |
<process name>_out.log |
Failure.
Warning status. |
NA |
|
DSAutoGeneration DSCompile DSCustomReport DSPatchCorrection DSPatchImport |
<process name>_out.log <process name>.log |
Failed. Warning status. |
NA |
|
DSGetLogs DSInitialImport DSRunJob |
<process name>_out.log <process name>_detailed.log <process name>.log |
Failed. Warning status. |
NA |
|
ProcessScheduler |
The log files generated by Process Scheduler are not parsed for warnings or errors. Therefore, even though Change Assistant may show a status of Complete for a Process Scheduler step type, you should review the generated log files for more details |
||
|
SQLCommand SQLScript UpdatePeopleTools |
<process name>.log |
DB2 z/OS and DB2 UDB:
Oracle: ORA. Microsoft SQL Server:
|
Warning. |