JR34524: ERROR MESSAGE WITH DB2 CONNECTOR WHEN USING PARTITIONED DATABASE.

APAR status

• Closed as fixed if next.

Error description

• You receive the error message "The connector has attempted to
  change the node map that was defined in the job definition. Once
  a node map constraint has been defined, it cannot be changed
  dynamically at runtime" when using the DB2 connector with a
  partitioned database and one or more node pools specified in the
  configuration file.
  
  This problem occurs when using the DB2 Connector with a
  partitioned database.  If there are more nodes defined in the
  configuration file (also known as the .apt file) than there are
  partitions in the database, then the connector will dynamically
  reduce the number of nodes to match the number of partitions.
  The DB2 connector job will fail with the error message "The
  connector has attempted to change the node map that was defined
  in the job definition. Once a node map constraint has been
  defined, it cannot be changed dynamically at runtime" if there
  are any node pools defined in the configuration file, even if
  the node pools are not specified on the DB2 connector stage(s)
  in your job.
  

Local fix

• There are two workarounds to the problem.  Either reduce the
  number of nodes (that are not in node pools) in the
  configuration file to match the number of partitions in the
  database, OR remove all node pools from the configuration file.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  ALL
  ****************************************************************
  PROBLEM DESCRIPTION:
  If you are using the DB2 Connector with a partitioned DB2
  database, and there are one or more node pools specified in the
  DataStage configuration file, then you may receive the
  following error message when the job is run: "The connector has
  attempted to change the node map that was defined in the job
  definition. Once a node map constraint has been defined, it
  cannot be changed dynamically at runtime".
  ****************************************************************
  RECOMMENDATION:
  There are two workarounds to the problem.  Either reduce the
  number of nodes (that are not in node pools) in the
  configuration file to match the number of partitions in the
  database, OR remove all node pools from the configuration file.
  
  ****************************************************************
  

Problem conclusion

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

• R810 PSN

     UP