IBM Support

IO09730: CUSTOMER GETTING DGL0306A OBJECT IS NOT UNIQUE ERROR TRYING TO IMPORT A DOCUMENT VIA PCLIENT AND KOFAX

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer is trying to import a new document and gets DGL0306A
    error.
    
    DGL0306A Object is not unique.
    Explanation: The key of an item added to a collection
                 is not unique.
    Component:   Java or C++ APIs.
    
    This problem appears to be unique to C++ connector. If we import
    an item whos item type is associated with a certain collection
    the connector code looks up this collection information in a
    hash table. If the collection already exists it throws an  error
    for the C++ side. The Java connector updates the collection
    information and continues.
    
    L2 and L3 cannot recreate the issue. The code has been in place
    for a long time and no other customers are experiencing this
    problem.  This customer sees this failure consistenly after
    upgrading a PTF to their HTTP server. LibSrv and ResMgr on zOS
    830.
    

Local fix

Problem summary

  • When Content Manager Client for Windows is used to import a
    document part, the import fails with the following error:
    [LOC]:
    (D:/sbroot/src/eip/dk/common\pkeycollection_imp.hpp:RedBlackTree
    <class KString>::add):722
    [MSG]: DGL0306A: Object is not unique :
    
    This error occurs after the object is successfully stored on
    resource manager, and the API attempts to store the returned
    information into the DKReplicaInfoICM class's updateRMInfo()
    method.
    
    This is from PMR 57053,082,000.
    

Problem conclusion

  • Problem conclusion:
    In the DKReplicaInfoICM.cpp class, the addRMInfo() and
    updateRMInfo() methods were modified so that if the key already
    exists in the hash table, the API updates the entry rather than
    adding the entry again. If the key does not exist in the hash
    table, then the API adds the entry.
    
    The problem was fixed in DB2 Content Manager Version 8.3 Fix
    Pack 10.
    

Temporary fix

  • n/a
    

Comments

APAR Information

  • APAR number

    IO09730

  • Reported component name

    II4C CM CONNECT

  • Reported component ID

    5724B43A1

  • Reported release

    830

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2008-11-05

  • Closed date

    2008-12-18

  • Last modified date

    2008-12-18

  • 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

    II4C CM CONNECT

  • Fixed component ID

    5724B43A1

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCTVDL","label":"Db2 Information Integrator for Content"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"830","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
18 December 2008