IBM Support

QSYS2.EVALUATE_PENDING_REPLICATION_DEPENDENCIES()

News


Abstract

The EVALUATE_PENDING_REPLICATION_DEPENDENCIES table function evaluates the database object dependency relationships for objects in a pending replication criteria group and identifies dependent objects on the local node that may require attention before the apply-label group is committed.

Content

Db2 Mirror


Three categories of potential problems are identified.

  1. EXCLUDE violations
     
    A base physical file in the pending group has a pending replication inclusion state of EXCLUDE. If any dependent object (a logical file, SQL index, SQL view, or MQT) remains included in replication and is not already covered by an EXCLUDE rule in this pending group, that dependent object is flagged. Leaving a dependent object replicated while its underlying base file is not replicated can cause queries against the dependent object to return different results depending on which node the query is executed from.
  2. INCLUDE gaps — missing dependent objects
     
    A base physical file in the pending group is being added to replication by an INCLUDE rule. If any dependent object (a logical file, SQL index, SQL view, or MQT) is not currently included in replication or part of this pending group as INCLUDE, that dependent object is flagged. Adding a base file without its dependent objects will leave those objects absent from the other node.
  3. INCLUDE gaps — missing base physical file
     
    Replicating a view or index without its base physical file will result in each node resolving the dependent object against its own local copy of the base file. Query results from the dependent object will differ between nodes, and index operations may fail if the base physical file is not present on both nodes.

For complete detail, view the IBM Documentation page: EVALUATE_PENDING_REPLICATION_CRITERIA table function


Updates

  • Introduced new service with IBM i 7.6 [SF99961 Level 4 and SF99960 Level 4]; IBM i 7.5 - [SF99951 Level 13 and SF99950 Level 13]; and IBM i 7.4 - [SF99668 Level 30 and SF99704 Level 34]:


Examples

  • Review all database object dependency relationships for the pending group identified by apply-label MAINT01 before committing the group.

    SELECT *
        FROM TABLE(SYSIBMADM.EVALUATE_PENDING_REPLICATION_DEPENDENCIES(IASP_NAME   => '*SYSBAS',
                                                                       APPLY_LABEL => 'MAINT01'))
        ORDER BY LIBRARY_NAME, SQL_OBJECT_TYPE, OBJECT_NAME;
  • Identify only the dependent objects that are currently included in replication but whose base physical file is being excluded by the pending group MAINT01. Queries against these dependent objects may return different results depending on which node the query is executed from once the pending group is applied.

    SELECT LIBRARY_NAME, OBJECT_NAME, SQL_OBJECT_TYPE, EVALUATION_DETAIL
        FROM TABLE(SYSIBMADM.EVALUATE_PENDING_REPLICATION_DEPENDENCIES(IASP_NAME   => '*SYSBAS',
                                                                       APPLY_LABEL => 'MAINT01'))
        WHERE SQL_OBJECT_TYPE <> 'PHYSICAL FILE'
        ORDER BY LIBRARY_NAME, OBJECT_NAME;

[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SSLLPF","label":"IBM Db2 Mirror for i"},"ARM Category":[{"code":"a8m0z0000001hExAAI","label":"DB2 Mirror"}],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.4.0;and future releases"},{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000001hExAAI","label":"DB2 Mirror"}],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.4.0;and future releases"}]

Document Information

Modified date:
27 October 2026

UID

ibm17294264