PM57689: RC8 MESSAGE "MANUAL INTERVENTION IS REQUIRED TO RESOLVE THIS CONFLICT" WHEN KEEPTGT USED AND PROCESSING CONSTRAINT FFA20

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The DB2 Object Comparison Tool for z/OS' compare step ends with
  a RC8 and a message:
  .
  Foreign key for table <schema>.>table< to table <schema>.>table<
  not found.
  Column list is :        (<column1>)
  Foreign key for table <schena>.>table< kept because KEEPTGT
  option was specified
    A new constraint with the same has previously been added.
    Manual intervention is required to resolve this conflict
  As the message does not have a message number indicating an
  error, it is not the last message issued and the apply step is
  not executed it is difficult for the customers to find and
  act upon the message.
  

Local fix

• Resolve the naming conflict manually then rerun the compare.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Object Comparison Tool for  *
  *                 z/OS who use the Compare function to         *
  *                 compare objects including unique,            *
  *                 referential, or check constraints.           *
  ****************************************************************
  * PROBLEM DESCRIPTION: In DB2 Object Comparison Tool for z/OS, *
  *                      when using the Compare function to      *
  *                      compare constraints, a warning message  *
  *                      is displayed in the compare job log:    *
  *                                                              *
  *                      'A new constraint with the same name    *
  *                      has previously been added.              *
  *                      Manual intervention is required         *
  *                      to resolve this conflict.'              *
  *                                                              *
  *                      When two REFERENTIAL constraints        *
  *                      have the same name but were             *
  *                      created on two different tables,        *
  *                      they should not conflict.               *
  *                                                              *
  *                      A column list was missing from the      *
  *                      definition of the REFERENTIAL           *
  *                      constraints in the generated            *
  *                      changes files, when one, but not        *
  *                      both of these ignore fields was         *
  *                      specified:                              *
  *                                                              *
  *                      'SYSRELS:RELNAME'                       *
  *                      'SYSFOREIGNKEYS:RELNAME'                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In DB2 Object Comparison Tool for z/OS, when using the Compare
  function to compare constraints, a warning message is displayed
  in the compare job log:
  
  'A new constraint with the same name has previously been added.
  Manual intervention is required to resolve this conflict.'
  
  When two REFERENTIAL constraints have the same name but were
  created on two different tables, they should not conflict.
  
  A column list was missing from the definition of the referential
  constraints in the generated changes files, when one, but not
  both of these ignore fields was specified:
  
  'SYSRELS:RELNAME'
  'SYSFOREIGNKEYS:RELNAME'
  

Problem conclusion

• Program has been changed to generate an error message if there
  is a duplicate in the names of all constraints created on the
  same table, and the program will stop with RC08:
  
  ADB7155E The name duplicate_name of the constraint_type
           constraint on the table_schema.table_name table
           is a duplicate name of another constraint_type
           constraint which is previously specified on the
           same table.
  Explanation: The constraint name must be different from the
               names of any referential, check, primary key, or
               unique key constraints previously specified on
               the table.
  System action: Processing stops.
  User response: Fix the problem by removing the duplicate name
                 from the constraint definition or renaming the
                 constraint with a unique name, and then try
                 again.
  
  duplicate_name:  constraint name which has a duplicate
  constraint_type: type of the constraints which has a duplicate
  table_schema:    schema of the table
  table_name:      name of the table
  

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:

  UK81227

Modules/Macros

•    ADB2CMF  ADB2CMP  ADB2CMR  ADB2CMS  ADB2CMT
  ADB2IGN  ADB7000
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RA10 PSY UK81227

     UP12/08/24 P F208

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.