• Print |
• E-mail  |
• Bookmark

When the libname options READ_LOCK_TYPE=, READ_ISOLATION_LEVEL=,
CONNECTION=, and READ_MODE_WAIT= are present along with the data set
option DBKEY=, incorrect syntax for the lock statement is passed to
Teradata.

The SQL that should be generated should look like the following (exact
syntax will depend on the values of the above options):

   USING ("deptno" INTEGER) LOCK TABLE "dept" FOR ACCESS MODE NOWAIT
   SELECT "DEPTNO","DNAME","LOC"
   FROM "dept"
   WHERE "deptno"=:"deptno"

What gets passed instead is one of the following:

   LOCK TABLE "dept" FOR ACCESS MODE NOWAIT USING ("deptno" INTEGER)
   SELECT "DEPTNO","DNAME","LOC"
   FROM "dept"
   WHERE "deptno"=:"deptno"

   or

   LOCK TABLE "dept" FOR ACCESS USING ("deptno" INTEGER)
   SELECT "DEPTNO","DNAME","LOC"
   FROM "dept"
   WHERE "deptno"=:"deptno"

This results in an error.  One of several different errors can be
received depending on the exact statement sent above.  Below are
just a sample of a few:

   ERROR: Teradata row not delivered (trget): Syntax error, replace
   'USING' that follows 'NOWAIT' with a 'ROLLBACK' keyword.

        or

   ERROR: Teradata row not delivered (trget): Syntax error: expected
   something between the word 'ACCESS' and the 'USING' keyword.

        or

   ERROR: Teradata row not delivered (trget): Syntax error, replace
   'FOR' that follows the word 'dept' with a 'SELECT' keyword.


A Technical Support hot fix for Release 8.2 (TS2M0) for this
issue is available at:

http://www.sas.com/techsup/download/hotfix/82_sbcs_prod_list.html#011547

Operating System and Release Information

A fix for Release 8.2 (TS2M0) for this issue is available at: