Old thread, but since there was no solution, and since I could fix this when it happened to me, here is my take. My query looked like this: proc sql outobs=1 ;   connect using ORALIB;   select * from connection to ORALIB ( ... ); The log displayed: ORACLE_326: Prepared: on connection 0 select * from TABLE ORACLE_327: Executed: on connection 0 SELECT statement ORACLE_326 WARNING: Statement terminated early due to OUTOBS=1 option. ORACLE: Pipelined I/O thread did not timely terminate ORACLE: Pipelined I/O thread terminated on 2nd attempt Because I used both - the OUTOBS= option - SQL pass-through the connection to oracle seems to get interrupted and Oracle complains. Only when these 2 features are used does the message appear.   Replacing the OUTOBS= option with a filter on ROWNUM in the Oracle where clause removed the Oracle messages.             ... View more