If all jobs are slow, this could indicate that the Teradata Database system and nodes are too busy to be responsive to specific requests. Generally, this happens when the nodes reach 70% or higher CPU utilization. Another cause can be orphaned arcmain processes that continue to run on the DSA administrative servers, keeping sessions active and tying up resources.
- To collect 24 hours of node CPU usage data, type #sar -u on every Teradata Database node.
- To look at current node CPU usage data, type #sar -u 5 5 on every Teradata Database node. This provides 5 iterations of sar -u at 5 second intervals.
- If the data indicates CPU usage at more than 70%, reduce the system load.
- If CPU usage data does not indicate system overload, kill any orphaned arcmain processes.