API_Request provides two ways to troubleshoot the issues:
- Syslog, All error and important information is written to syslog of the database node;
- Problems can be debugged using the same UDF debugging techniques available.
Steps for Debugging
- Create a temporary trace table in the session.
CREATE GLOBAL TEMPORARY TRACE TABLE FNC_Trace( Mandatory_Column1 BYTE(2), Mandatory_Column2 INTEGER, Trace_Output VARCHAR(1000)) ON COMMIT PRESERVE ROWS;
- Turn on tracing for the session.
SET SESSION FUNCTION TRACE USING '2' FOR TABLE FNC_Trace;
- Run the test query with debug NVP.
- Review the trace.
sel * from FNC_Trace order by 1,2;
Common Issues and Causes
- Wrong AWS authorization keys.
- Wrong content_type argument.
- Difference between Teradata table or query columns and column requirement for SageMaker endpoint.
Input requirement for SageMaker model must match the number of columns, datatype and the order of Teradata Input Table or Query.