IBM Support

IJ02262: RULES IMPORTED FROM A SYSTEM WITH CONFIGURED DOMAINS TO A SYSTEM WITHOUT DOMAINS CAN SEE REFERENCE SET DATA ISSUES

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

  • It has been identified that when a rule is imported to a QRadar
    environment (using the Content Management Tool) that has no
    domains configured, and that rule has a response to add data to
    a domain specific reference set, QRadar does not add the
    reference set data.
    
    Messages similar to the following might be visible in
    /var/log/qradar.error when this issue is occuring:
    
    [tomcat.tomcat] [ReferenceDataUpdateServiceThread_1]
    com.q1labs.core.shared.referencedata.ReferenceDataManager:
    [ERROR] [NOT:0000003000][127.0.0.1/- -] [-/-
    -]ReferenceDataManager.addToReferenceDataCollection()
    rdata=name=referenceSetName size=4 {domain 0:[data]}
    [tomcat.tomcat] [ReferenceDataUpdateServiceThread_1]
    com.q1labs.core.shared.referencedata.ReferenceDataUpdateServiceT
    hread: [ERROR] [NOT:0000003000][127.0.0.1/- -] [-/-
    -]ReferenceDataUpdateServiceThread An unexpected exception was
    encountered processing name=referenceSetName size=4 {domain
    0:[data]}
    [tomcat.tomcat] [ReferenceDataUpdateServiceThread_1]
    com.q1labs.core.dao.referencedata.light.RefDataDomainRestriction
    Exception: Can't use domains for Reference Data. This system
    has no domains.
    [tomcat.tomcat] [ReferenceDataUpdateServiceThread_1]    at
    com.q1labs.core.dao.referencedata.RefDataDomainRestrictions.veri
    fyWriteAccess(RefDataDomainRestrictions.java:183)
    [tomcat.tomcat] [ReferenceDataUpdateServiceThread_1]    at
    com.q1labs.core.dao.referencedata.light.RefDataDomainProtection.
    addElement(RefDataDomainProtection.java:38)
    [tomcat.tomcat] [ReferenceDataUpdateServiceThread_1]    at
    com.q1labs.core.shared.referencedata.ReferenceDataManager.addToR
    eferenceDataCollection(ReferenceDataManager.java:756)
    [tomcat.tomcat] [ReferenceDataUpdateServiceThread_1]    at
    com.q1labs.core.shared.referencedata.ReferenceDataUpdateServiceT
    hread.run(ReferenceDataUpdateServiceThread.java:100)
    

Local fix

  • Edit the rule in question, and save it without making changes.
    Doing this overrides the domain behaviour of the rule.
    

Problem summary

  • This issue was fixed in QRadar QRM QVM release of 728 Patch 12
    and 731 Patch 5.
    

Problem conclusion

  • This issue was fixed in QRadar QRM QVM release of 728 Patch 12
    and 731 Patch 5.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ02262

  • Reported component name

    QRADAR SOFTWARE

  • Reported component ID

    5725QRDSW

  • Reported release

    728

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-11-29

  • Closed date

    2018-07-27

  • Last modified date

    2018-07-27

  • 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

    QRADAR SOFTWARE

  • Fixed component ID

    5725QRDSW

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"}, "Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"728","Edition":""}]

Document Information

Modified date:
27 July 2018