Problem Note 53825: A DB2 -804 error or a "column does not exist" error might occur when you join two DB2 tables in the z/OS operating environment
 |  |  |  |  |
An error might occur when you use an SQL procedure containing READBUFF= and DBSASTYPE= options to query two DB2 tables under z/OS via a LIBNAME engine. The error might look similar to one of the following two errors:
Error 1:
DB2 ERROR:
RESULT OF SQL STATEMENT:
DSN00804E AN ERROR WAS FOUND IN THE APPLICATION PROGRAM INPUT PARAMETERS
FOR THE SQL STATEMENT, REASON 07
A DUMP OF THE SQLCA FOR THE GET DIAGNOSTICS REQUEST FOLLOWS:
ROW NUMBER: 0 ERROR CONDITION: 1 REASON CODE: 7
SQLCODE: -804 SQLSTATE: 07002 SQLERRP: DSNXECP
DB2 ..?-.?.? .EMPLOYEE_ID DATAError 2:
ERROR: (ACCDB2M041E) The column xxxxxx does not exist.
Currently, the only workaround is to select a different value for the READBUFF= option. Which value to use varies per query. The default setting, READBUFF=1, should work for all queries, but it might not be the most efficient setting. Determining the best value requires testing.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | SAS Release | |
| Reported | Fixed* | |||
| SAS System | SAS/ACCESS Interface to DB2 | z/OS | 9.3 TS1M2 | 9.4 TS1M2 |
A fix for this issue for SAS/ACCESS Interface to DB2 9.3_M2 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/J41.html#53825
A DB2 -804 error or a "column does not exist" error might occur when you join two DB2 tables under z/OS when you are using a LIBNAME engine. The problem occurs when you use READBUFF= and DBSASTYPE= options in your SQL procedure query.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2014-12-18 10:04:19 |
| Date Created: | 2014-08-04 14:08:52 |