When you run the SORT procedure against a Netezza table, the schema specified with the SCHEMA= LIBNAME option might be ignored. This behavior might result in errors referencing the table in the ADMIN schema rather than the one you specified, or it might cause incorrect results.

Example 1

In the following example, the expected results are that the sort of the Netezza table TEST.MYSCHEMA.TESTSORT is written to a new Netezza table TEST.MYSCHEMA.TESTSORTOUT.

The following error occurs when the SAS generated query does not include the schema and the table TESTSORT does not exist in the ADMIN schema:

The error "CLI execute error: ERROR: Relation 'TEST.ADMIN.TESTSORTOUT' does not have attribute 'varname'" might occur if the following conditions are true:

• The Netezza table TESTSORT is in both the ADMIN schema and the MY-SCHEMA schema.
• The Netezza table TESTSORTOUT is present in only the ADMIN schema.
• TESTSORTOUT has a different set of variables from TESTSORT.

Example 2

In the following example, the expected results are that the sort of the Netezza table TEST.MYSCHEMA.TESTSORT is written to the SAS data set WORK.TESTSORTOUT.

However, when the Netezza table TESTSORT is in both the ADMIN schema and the MY-SCHEMA schema, but the data in the two tables is different, the output from the sort might be from the ADMIN.TESTSORT.

Workaround

To work around the above behaviors, set the system option SQLGENERATION to NONE as shown below:

Operating System and Release Information