IBM Support

PM13132: JCR CUMULATIVE FIX 4 FOR PORTAL 6.1

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • JCR CUMULATIVE FIX 4 FOR PORTAL 6.1
    

Local fix

Problem summary

  • JCR Cumulative Fix #4 for Portal 6.1
    

Problem conclusion

  • PM13132
    =======
    
    Problem Description:
       JCR CUMULATIVE FIX 4 FOR PORTAL 6.1
    
    Detailed Problem Description:
    This cumulative fix addresses these issues:
    (PK92772) QUICKR ORACLE CANNOT QUERY AN EMPTY STRING
    (PM02477) QUERIES INVOLVING AN APOSTROPHE ARE NOT ENCODED
    CORRECTLY
    (PM02885) ADD SUPPORT FOR TICKET.WORKSPACEEXISTS
    (PM03149) DELETE NODETYPE CAUSES PROBLEM IN LOCAL NODETYPE CACHE
    (PM03087) DATABASE TRANSFER FOR JCR DOMAIN TOUCHES UNRELATED
    COMPONENTS
    (PM03219) THE LONG INTEGER IS NOT BEING FULLFILLED WHEN CALLING
    NODE.SETPROPERTY WHICH GETS REULT FROM NODE.GETPROPERTY
    (PM04824) StackOverflowError in JCR Query
    (PM04909) JAVA.LANG.STACKOVERFLOWERROR DURING EXPORT/IMPORT
    (PM05189) TO BE ABLE MODIFY THE CMAPI TO MAKE JCR PROPERTIES
    EDITABLE
    (PM05897) JCR INDEX: DOCUMENTS WITHOUT UUID INFO DO NOT GET
    INDEX
    (PM05902) QUERY GENERATING A VALUE LIST LARGER THAN 1000 CAUSING
    ORACLE EXCEPTION
    (PM06844) DSRA9110E ERROR WITH TEXT SEARCH FOR NEW CONTENT
    (PM07908) JCR EXPORT/IMPORT CHANGES THE TEMPLATE MAPPING INSIDE
    A SITEAREA
    (PM08904) REPOSITORY EXCEPTION WHEN TRYING TO DELETE A SITE AREA
    (PM08915) EXECUTING A JCR XPATH QUERY WITH PAGINATION OPTIONS
    RESULTS IN EXCEPTION
    (PM09062) DISABLING THE WCM AUTHORING SYNCHRONIZATION LOCK CAN
    LEAD TO DEADLOCKS IN JCR
    (PM09070) AUTOCOMMITS FOR JCR READ-ONLY OPERATIONS ARE CAUSING
    HIGH RESOURCE UTILIZATION ON DB
    (PM09079) DISABLING THE WCM AUTHORING SYNCHRONIZATION LOCK CAN
    LEAD TO DEADLOCKS IN DB2
    (PM09896) StringIndexOutOfBoundsException in NoConvertor
    (PM11048) PERFORMANCE DURING LIBRARY DELETE ON DB2/Z
    (PM11951) SQLException updating data during DST Correction
    (PM13731) DST CORRECTION EXPOSES SQL SERVER JDBC REGRESSION
    - Database connection enhancements
    - JCR Migration utility enhancements
    - Text Search enhancements
    - Performance enhancements
    
    
    Problem Solution:
      PM13132 contains code changes.
    
    Affected Users:
       All portal users.
    
    Pre-Requisite(s):
       Portal Version: 6.1.0.3
    
    Installation Steps:
       NOTE:  YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN
    ORDER TO INSTALL A FIX.
              The WebSphere Portal Update Installer (PUI) can be
    downloaded from the following link:
    
    http://www.ibm.com/support/docview.wss?rs=688&uid=swg24006942
    
    *Reminder: the version of PUI used varies based on the version
    of WebSphere Portal.
    Ensure the correct version is in use.*
    
    Refer to the "Cluster Maintenance" topic in the 6.1 InfoCenter
    (http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/topic/com
    .ibm.wp.ent.doc_v6101/plan/clus_maint.html)
    for additional information on installing or uninstalling interim
    fixes in clustered environments
    while maintaining continuous availability of your portal.
    
    1. Stop the WebSphere Portal server
    2. Apply the PM09070.jar using the PUI (Portal update
    installer).
       Refer to the PUI readme for further information on using the
    PUI.
    3. Add the following to icm.properties file:
    
    # This flag is used to control transaction usage around jcr read
    only operations.  The intent of this
    # flag is to reduce the overhead introduced by autocommit for
    the DB2 on z/OS database platform.  Setting
    # the value of this property to true will cause JCR to
    encapsulate large blocks of read-only database
    # operations in a transaction.
    # The default value for this property is false except for the
    DB2 z/OS database where it is true.
    #jcr.read.transaction.enabled=true
    
    4. Restart the WebSphere Portal server.
    
    
    Uninstall:
    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.
    
    Use the Portal Update Installer to uninstall the fix:
    
       1. Shutdown WebSphere Portal.
       2. Follow the instructions that are packaged with the Portal
    Update Installer on how to uninstall a fix.
       3. Restart WebSphere Portal.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM13132

  • Reported component name

    WEBSPHERE PORTA

  • Reported component ID

    5724E7600

  • Reported release

    61C

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-04-26

  • Closed date

    2010-06-10

  • Last modified date

    2010-06-10

  • 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

  • R610 PSY

       UP

  • R615 PSY

       UP

  • R61A PSY

       UP

  • R61B PSY

       UP

  • R61C 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.0.3","Line of Business":{"code":"LOB31","label":"WCE Watson Marketing and Commerce"}}]

Document Information

Modified date:
21 December 2021