If a query that is submitted to a Greenplum database is terminated by the Greenplum administrator, the original SAS^® query might return fewer rows than expected. There is no indication of an error or warning, and so the query appears to have completed successfully.  

Sometimes an error is observed in the SAS log. Here is an example:

The Greenplum system logs show the termination, as in this example:

A workaround is to set READBUFF=1 either as a data set option or in the connection options of the LIBNAME or CONNECT statement. This setting does not prevent the wrong number of rows being read, but it does provide an error message in the SAS log that is similar to one of the following:

Note: Adding READBUFF=1 might cause a performance overhead.

Click the Hot Fix tab in this note to access the hot fix for this issue.

The hot fix ensures that an error message is always written to the SAS log when a Greenplum server process is terminated. 

Operating System and Release Information

A fix for this issue for SAS/ACCESS Interface to Greenplum 9.44 is available at:

A fix for this issue for SAS/ACCESS Interface to Greenplum 9.43 is available at:

A fix for this issue for SAS/ACCESS Interface to Greenplum 9.42 is available at: