IBM Support

PH29454: REPORTING SCHEMA CAN FAIL IF A FIELD IS ASSOCIATED TO MULTIPLE OBJECTS AND PARTIALLY EXCLUDED FROM THE REPORTING SCHEMA

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Reporting schema modifications can fail if a field is associated
    to multiple object types and then partially excluded from the
    reporting schema. This problem was exposed during the 8.2
    upgrade when attempting to add support for the new multi-actor
    storage model. This is covered in the following collab:
    
    The problem lies with the defsHandler procedure inside
    OP_RPS_METADATA_BLDR. That procedure contains a cursor with an
    exists clause that filters out fields that are excluded:.
    
    The problem is that these checks are simply checking to see
    whether the field is excluded from any object type. In the use
    case where you have associated a field to multiple object types
    but only excluded it from a subset of those types, this means
    that this filter will attempt to exclude the field from all
    object types. The predicates should also filter on the assettype
    id.
    
    This issue is causing the 8.2 upgrade to fail. We have also
    encountered an issue when attempting to associate this field to
    another object type while it is in this state. For the upgrade
    use case the customer encountered the following:
    [exec] ERROR at line 1: [exec] ORA-20555: -16020||472208|NULL
    
    For the issue where you attempt to associate the field to a new
    object type while it was in this state a ROCNBC and the aurora
    log showed:
    Application Error!
    [Default Executor-thread-2316993](LoggingHelper.java:102)
    java.sql.SQLException:
    ORA-20555: -16066||3235|321
    ORA-06512: at "OPENPAGE.OP_RPS_MGR", line 2820
    ORA-06512: at "OPENPAGE.OP_RPS_MGR", line 8519
    ORA-06512: at "OPENPAGE.OP_EXCEPTION_MGR", line 303
    ORA-06512: at "OPENPAGE.OP_RPS_MGR", line 8501
    ORA-06512: at "OPENPAGE.OP_RPS_MGR", line 2727
    ORA-06512: at "OPENPAGE.OP_OBJ_MODEL_MGR", line 4512
    ORA-06512: at "OPENPAGE.OP_OBJ_MODEL_MGR", line 4512
    ORA-06512: at line 1
    

Local fix

  • Workaround for the 82 upgrade issue:
    ? First workaround - Remove exclusion
    Remove any partial subsystem field exclusions for multi-actor
    fields
    Recreate the reporting schema
    Perform the 8.2 database upgrade
    Add the subsystem field exclusions back in
    Recreate the reporting schema
    ? Second workaround - Custom code
    Attempt the database upgrade (which will fail)
    Run a custom PL/SQL anonymous block to upgrade the problem
    fields
    Rerun the database upgrade
    Note - I will publish a technote with the workaround code once
    it is ready.
    
    
    Workaround for the field association issue:
    Remove the partial subsystem field exclusion
    Perform the association
    Add the subsystem field exclusion back in
    Note - For this use case a recreate of the reporting schema is
    not needed. You just need to make sure you do these actions
    within a single sequentially executed SAM session.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * OpenPages Users                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * REPORTING SCHEMA CAN FAIL IF A FIELD IS ASSOCIATED TO        *
    * MULTIPLE OBJECTS AND PARTIALLY EXCLUDED FROM THE REPORTING   *
    * SCHEMA                                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Customers should download OpenPages with Watson 8.2 Fix Pack *
    * 2 (8.2.0.2). See the following document for details on       *
    * obtaining OpenPages 8.2.0.2:                                 *
    * https://www.ibm.com/support/pages/openpages-watson-82-fix-pa *
    * ck-2                                                         *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PH29454

  • Reported component name

    OPENPAGES GRC

  • Reported component ID

    5725D5100

  • Reported release

    820

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-09-14

  • Closed date

    2021-03-26

  • Last modified date

    2021-03-26

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    OPENPAGES GRC

  • Fixed component ID

    5725D5100

Applicable component levels

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFUEU","label":"IBM OpenPages with Watson"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"820"}]

Document Information

Modified date:
27 March 2021