OBIEE Connectivity Error

Connectivity

OBIEE Connectivity Error

Have a issue with OBIEE reports. This particular example is inconsistent - while it runs succesful one day and fails next few days. 

 

Odbc driver returned an error (SQLExecDirectW). Error Codes: OPR4ONWY:U9IM8TAC:U9IM8TAC:U9IM8TAC:U9IM8TAC:U9IM8TAC:OI2DL65P State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. (HY000) State: HY000. Code: 43113. [nQSError: 43113] Message returned from OBIS. (HY000) State: HY000. Code: 43119. [nQSError: 43119] Query Failed: (HY000) State: HY000. Code: 16001. [nQSError: 16001] ODBC error state: 08S01 code: 110 message: [Teradata][Unix system error] 110 Socket error - No response received when attempting to connect to the Teradata server. (HY000) State: HY000. Code: 16014. [nQSError: 16014] SQL statement preparation failed. (HY000) SQL Issued: SELECT 0 s_0, "FSG Analytics - Inspection"."Inspection Customer"."Active" s_1, "FSG Analytics - Inspection"."Inspection Customer"."Alliance Id" s_2, "FSG Analytics - Inspection"."Inspection Customer"."Customer Name" s_3, "FSG Analytics - Inspection"."Inspection Customer"."Customer Number" s_4, "FSG Analytics - Inspection"."Inspection Customer"."Master Number" s_5, "FSG Analytics - Inspection"."Inspection Customer"."VBUName" s_6, "FSG Analytics - Inspection"."Inspection"."Estimated Inspection Date" s_7, "FSG Analytics - Inspection"."Inspection"."Inspection Instructions" s_8, "FSG Analytics - Inspection"."Inspection"."Inspection Remarks" s_9, "FSG Analytics - Inspection"."Inspection"."Inspector Id" s_10, "FSG Analytics - Inspection"."Inspection"."Inspector Name" s_11, "FSG Analytics - Inspection"."Inspection"."Manager Name" s_12, "FSG Analytics - Inspection"."Inspection"."Schedule Status" s_13 FROM "FSG Analytics - Inspection" WHERE (("Inspection Customer"."Alliance Id" IN ('CDFUS', 'PLRIS')) AND ("Inspection"."Schedule Status" = 'Pending') AND ("Inspection"."Estimated Inspection Date" > (CURRENT_DATE)) AND ("Inspection"."Inspection Instructions" <> ' ')) FETCH FIRST 300001 ROWS ONLY 

 

Any suggestions on this?

 

Thanks

1 REPLY
Highlighted
Teradata Employee

Re: OBIEE Connectivity Error

A low-level TCP socket error like this could be indicative of an actual sporadic network error, or could be the result of idle sessions in a middle-tier connection pool having been aborted by some automated monitoring process. Neither the Teradata ODBC driver nor the database itself would "time out" idle sessions.

 

Also FETCH FIRST n ROWS ONLY is not valid Teradata syntax (looks like DB2). This particular statement should always fail on Teradata, with a 3706 syntax error.