IBM Support

PM25544: ORPHANED CUSTOM UNIQUE NAMES ARE NOT CLEANED UP

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In a situation where a custom unique name remains while the
    corresponding resource has been deleted, the custom unique name
    cannot be re-assigned unless it has been removed manually. The
    asynchronous cleanup job, which is started regularly and also
    can be triggered manually using XMLAccess input script
    "Task.xml" does not clean up these orphaned custom unique names.
    XMLAccess input scripts that define new resources with the
    identical custom unique name cannot be executed successfully,
    unless the unique name has been removed.
    
    The XMLAccess output contains:
    
    <status element="[...
    uniquename=unique.name.1 name=Name1]" result="failed">
    <message
    id="EJPXA0142E">com.ibm.wps.command.xml.XmlCommandException:
    EJPXA0142E: Unique name unique.name.1 is already used in the
    portal.
    [... uniquename=unique.name.1 name=Name1]</message>
    <message
    id="EJPDB0046E">
    com.ibm.wps.services.identification.DuplicateNameException:
    EJPDB0046E: The unique name to be set, unique.name.1, is a
    duplicate.</message>
    

Local fix

  • Manually delete orphaned unique names using the administrative
    portlet "Custom unique names".
    

Problem summary

  • In a situation where a custom unique name remains while the
    corresponding resource has been deleted, the custom unique name
    cannot be re-assigned unless it has been removed manually. The
    asynchronous cleanup job, which is started regularly and also
    can be triggered manually using XMLAccess input script
    "Task.xml" does not clean up these orphaned custom unique names.
    XMLAccess input scripts that define new resources with the
    identical custom unique name cannot be executed successfully,
    unless the unique name has been removed.
    

Problem conclusion

  • The asynchronous cleanup job also checks custom unique names for
    their validity and removes orphaned ones.
    
    Failing Module(s):
       Database
    
    Affected Users:
       Administrative users
    
    Version Information:
       Portal Version(s): 7.0.0.0
        Pre-Requisite(s): ---
         Co-Requisite(s): ---
    
    Manual Steps:
       None
    
    Platform Specific:
       This fix applies to all platforms.
    
    PM25544 is part of PM25191 (CF001 for Portal 7000).
    
    You can retrieve the download from the link on the Recommended
    Updates page for WP/WCM V7.0, here:
    http://www.ibm.com/support/docview.wss?uid=swg24027857
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM25544

  • Reported component name

    WEBSPHERE PORTA

  • Reported component ID

    5724E7600

  • Reported release

    615

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-11-02

  • Closed date

    2010-12-22

  • Last modified date

    2010-12-22

  • 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

    WEBSPHERE PORTA

  • Fixed component ID

    5724E7600

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHRKX","label":"WebSphere Portal"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1.5","Line of Business":{"code":"LOB31","label":"WCE Watson Marketing and Commerce"}}]

Document Information

Modified date:
21 December 2021