Name: PK29999
=============
 
Summary:
   Creating a new portlet instance or component using xml access leads to error EJPDB0046E (DuplicateNameException).
 
Problem Description:
   In some special cases the unique name of a portlet instance is not deleted when the portlet instance itself is deleted. When creating a new portlet instance of with this unique name following exception is thrown:
        com.ibm.wps.command.xml.XmlCommandException: EJPXA0142E: Unique name wp.component2.PK29999 is already used in the portal. [component _7_0830M4HTFF0AIJ6G_S5 uniquename=wp.component2.PK29999]
      		 at com.ibm.wps.command.xml.items.AbstractConfigItem.updateUniqueName(AbstractConfigItem.java:182)
      		 at com.ibm.wps.command.xml.items.ComponentItem.update(ComponentItem.java:480)
      		 at com.ibm.wps.command.xml.items.ComponentItem.create(ComponentItem.java:394)
           ...
      Caused by: com.ibm.wps.services.identification.DuplicateNameException: EJPDB0046E: The unique name to be set, wp.component2.PK29999, is a duplicate.
      		 at com.ibm.wps.datastore.impl.UniqueNameDescriptorImpl.storeUniqueName(UniqueNameDescriptorImpl.java:125)
      		 at com.ibm.wps.services.identification.IdentificationService.setUniqueNameInternal(IdentificationService.java:269)
      		 at com.ibm.wps.services.identification.IdentificationService.setUniqueName(IdentificationService.java:162)
      		 at com.ibm.wps.command.xml.items.AbstractConfigItem.updateUniqueName(AbstractConfigItem.java:178)
      		 ... 37 more
      Caused by: com.ibm.wps.util.DataBackendException: EJPDB0001E: Error occurred during database access. Last SQL statement is [INSERT INTO UNIQUE_NAME (UNIQUE_NAME, RES_TYPE, OID, VP_DESC_OID) VALUES (?, ?, ?, ?)].
      		 at com.ibm.wps.datastore.impl.DataStoreContext.handleException(DataStoreContext.java:145)
      		 at com.ibm.wps.datastore.impl.ResourcePersister.storeNew(ResourcePersister.java:201)
      		 ...
      Caused by: com.ibm.websphere.ce.cm.DuplicateKeyException: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint defined on 'UNIQUE_NAME(UNIQUE_NAME,VP_DESC_OID)'.
      		 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
      		 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java(Compiled Code))
      		 ...
      Caused by: SQL Exception: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint defined on 'UNIQUE_NAME(UNIQUE_NAME,VP_DESC_OID)'.
      		 at db2j.ai.j.generateCsSQLException(Unknown Source)
      		 at db2j.ai.g.wrapInSQLException(Unknown Source)
      		 at db2j.ai.g.handleException(Unknown Source)
           ...
   
 
Problem Solution:
   The invalid uniquename is deleted.
 
Failing Module(s):
   XML Access
 
Affected Users:
   Administrators that use XmlAccess
 
Version Information:
    Portal Version(s): 5.1.0.4
     Pre-Requisite(s): 
      Co-Requisite(s): ---
 
Platform Specific:
   This fix applies to all platforms.
 
Installation:
   NOTE:  YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
          The Portal Update Installer can be downloaded from the following link:
          http://www.ibm.com/software/genservers/portal/support
 
   1. Create temporary "fix" directory to store the jar file.
   2. Copy jar file to this directory.
   3. Shutdown WebSphere Portal.
   4. Follow the fix installation instructions that are packaged with
      the Portal Update Installer on how to install the fix.
   5. Restart WebSphere Portal.
   6. The temporary directory may be removed.
 
Un-Installation:
   NOTE:  FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE
          A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.
          YOU MAY REAPPLY ANY REMOVED FIX.
 
   1. Shutdown WebSphere Portal.
   2. Follow the instructions that are packaged with the
      Portal Update Installer on how to uninstall the fix.
   3. Restart WebSphere Portal.