Sample Error Log File
The following table describes the contents of an error log file.
| Column | Description |
|---|---|
| Time | Time the log entry was made in hhmmss format where hh=hour, mm=minutes, and ss=seconds. |
| Component | Abbreviated name of the Teradata Query Scheduler component or subcomponent when Teradata Query Scheduler logged the entry. See Component Identifiers for a list of identifiers. |
| Process ID | Process ID that logged the entry. A Process ID is the numeric ID assigned by the system to a particular instance of a program running on that system. |
| Function | Name of the function in the Teradata QS code where the condition being logged occurred. |
| Activity | Description of the activity or interface called by the Teradata Query Scheduler function that caused the entry to be logged. |
| Errno | Current system error number for the process. |
| Status | Teradata QS status value, or in some cases, the numeric value of a variable or a condition. See Status Codes for details. |
| Request ID | Request ID of the scheduled request for which the error was logged. This field is optional; it is logged only for database errors pertaining to the execution of a specific job. |
| Job ID | Job ID of the scheduled request for which the error was logged. This field is optional; it is logged only for database errors pertaining to the execution of a specific job. |
| Message | Log entries can be followed by one or more lines of text. A text message is included when the logging of a status or errno value is insufficient, such as database errors. |