PM32598: ORACLE DRIVER INSERTS INVALID TIMESTAMP INTO THE DATABASE

APAR status

• Closed as program error.

Error description

• There are occasions when, under heavy load, Oracle is inserting
  an invalid timestamp into the database.  This breaks the
  StaleValue processing in JCR because the invalid timestamp
  cannot be correctly read and  processed by the JVM.  The net
  result to the customer is that they have a node which they
  cannot change without getting a StaleValueException from JCR.
  
  This scenario is most noticed because the stale message from JCR
  shows both the retrieved date and the expected date.  In the
  case of this failure, both of these dates are the same.
  Opened for release 6105
  

Local fix

Problem summary

• An invalid timestamp inserted into the database will cause JCR
  date comparisons to fail.
  

Problem conclusion

• PM32598
  =======
  
  Problem Description:
     Oracle inserts invalid timestamps into the database
  
  Problem Solution:
    PM32598 contains code changes.
  
  Affected Users:
     All portal users.
  
  Pre-Requisite(s):
     Portal Version: 6.1.0.5
     Portal Fixes:   ---
  
  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 "Maintaining the cluster" topic in the 6.0
  InfoCenter
  (http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/index
  .jsp?topic=/com.ibm.wp.ent.doc/wpf/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 PM32598.jar using the PUI (Portal update
  installer).
     Refer to the PUI readme for further information on using the
  PUI.
  3. 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 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

• R60E PSY

     UP

• R60G PSY

     UP

• R60H PSY

     UP

• R60J PSY

     UP

• R60K PSY

     UP

• R60M PSY

     UP

• R610 PSY

     UP

• R61A PSY

     UP

• R61B PSY

     UP

• R61C PSY

     UP

• R610 PSY

     UP