IT04669: RENAME TABLE AGAINST AN ALIAS CAUSES THE UNDERLYING TABLE TO TAKE ON THE ALIAS' SCHEMA

DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• For example, suppose table S1.T1 has an alias in a different
  schema, S2.T1_ALIAS. After
  
  rename table S2.T1_ALIAS to T1_NEW
  
  the underlying table is renamed to T1_NEW (this is expected),
  but the table's schema is changed to the alias' schema. S1.T1 no
  longer exists, as it's renamed to S2.T1_NEW, and the alias
  refers to a non-existent table (S1.T1).
  
  The underlying table's schema should remain unchanged.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Update to v10.1 Fix Pack 5.                                  *
  ****************************************************************
  

Problem conclusion

• Fixed in v10.1 Fix Pack 5.
  

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:

  IT04739 IT04740

Fix information

• Fixed component name

  DB2 FOR LUW

• Fixed component ID

  DB2FORLUW

Applicable component levels

• R970 PSN

     UP

• RA10 PSN

     UP

• RA50 PSN

     UP