PM65056: Teradata SQL index syntax not correct from DB Schema Generation.

APAR status

• Closed as Permanent restriction.

Error description

• Configuration:
  -------------
  Environment = Windows
  Tool = Rational System Architect
  Version = 11.4.0.1
  
  Description:
  -----------
  The generation of a Teradata DB schema results in incorrect
  syntax for the index. It should be a unique primary index.
  
  Expected Result:
  ---------------
  In the ddl file after a Create Table, the following line for
  example.
  UNIQUE PRIMARY INDEX (somename);
  
  Actual Result:
  -------------
  In the ddl file after a Create Table, the following line for
  example.
  CREATE UNIQUE INDEX MyEntity_PK (somename) ON MyEntity;
  
  Steps to Reproduce:
  ------------------
  1) On a Teradata enabled encyclopedia with a Teradata PDM.
  2) Select Tools -? DB Schema Genration.
  3) Select Target DBMS as Teradata.  Click next.
  4) Select a Destination SQL DDL file. Click Next.
  5) On the Indexes/Constraints tab select the options as follows
     Generate primary keys as
         Indexes.
     Generate foreign Keys as
        Indexes.
     Generate indexes
        Generate unique indexes.
          As indicated in table.
        Generate non-unique indexes.
  5) Click Finish.
  ==? you'll get a generated ddl file containing the full output
  but notice
      for the indexes they are not as expected for Teradata SQL
  
  WORKAROUND:
  ----------
  After the file is generated, edit the file so it contains
  CREATE UNIQUE INDEX
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The generation of a Teradata DB schema results in incorrect
  syntax for the index. It should be a unique primary index.
  

Problem conclusion

• No plan to fix. The issue has been around for a long time
  and would take some considerable effort to fix. The user has
  a "workaround" of manually editing the generated ddl file so
  it has the proper syntax. The Rational System Architect team
  is not aware of other users using Teradata. The client has
  agreed to close the case.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels