PK87468: SYSSYNONYMS.CREATOR IS SET INCORRECTLY FOR CREATE SYNONYM

APAR status

• Closed as fixed if next.

Error description

• SYSSYNONYMS CREATOR field is set incorrectly for CREATE SYNONYM
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 V8 NFM and V9 users of using         *
  *                 SYNONYM.                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: SYSSYNONYMS.CREATOR is incorrectly      *
  *                      set to current schema.                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Starting DB2 V8 NFM, when synonym is used in a dynamic SQL
  statement including DROP SYNONYM, with the value of the
  CURRENT SCHEMA special register being different from the
  value of the CURRENT SQLID special register, DB2 incorrectly
  use the CURRENT SCHEMA instead of CURRENT SQLID as the owner
  of the synonym to search for any existing matching synonym.
  As a result, DB2 fails to locate the matching synonym that
  is owned by the CURRENT SQLID (SYSSYNONYMS.CREATOR = the
  value of the CURRENT SQLID). The problem may cause below
  known symptoms:
  
  1. If there is no matching synonym owned by the
     CURRENT SCHEMA, DB2 incorrectly issues error
     SQLCODE -204 (under DB2 rules) or SQLCODE -551
     (under DB2 standard rules) though there exists
     a matching synonym owned by the CURRENT SQLID.
  
  2. If there exists a matching synonym owned by the
     CURRENT SCHEMA, DB2 incorrectly resolves the
     synonym to such a synonym and processes the
     requested statement.
  
  Starting DB2 V9 NFM, on CREATE SYNONYM that is dynamically
  prepared, DB2 incorrectly sets the owner of the synonym
  (SYSSYNONYMS.CREATOR) to the CURRENT SCHEMA instead of
  CURRENT SQLID.
  

Problem conclusion

Temporary fix

Comments

• The problem will be fixed in future releases.
  

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

• R810 PSN

     UP

• R910 PSN

     UP