PM46317: Slow JDBC-based indexing in RC 5.3

Rational Change Fix Pack 2 (5.3.0.2) for 5.3

APAR status

• Closed as program error.

Error description

• Slow JDBC-based indexing in RC 5.3.
  
  From event.log it looks like all the time is spent in the
  CSapi_get_object_info() call to fetch the attributes of the next
  batch of CRs to be index.
  
  It looks a bit like standard indexing, although search.log
  clearly says 'Indexing database:
  /path/database using JDBC and SQL.'
  
  DEBUG: Finished Accent Command: call
  cs_cmds:CSapi_get_object_info spent 128992 ms in the server.
  DEBUG:
  ACcent Module      : cs_cmds
  ACcent Function    : CSapi_get_object_info
  ACcent Return Code : 0
  ACcent File ID     : -1
  ACcent Is Binary   : False
  Return Message     : []
  
  To ACcent Data:
  ?OBJECT?
          ?DATA?
                  ?NAME?
                          XX1
                  ?/NAME?
          ?/DATA?
          ?DATA?
                  ?NAME?
                          XX2
                  ?/NAME?
          ?/DATA?
  (...)
  
  
  From ACcent String Data:
  (...)
  
  
  There are also two types of unusual messages in event.log during
  indexing:
  
  1) 'The user 'xxx' has a null first or last name.' - This
  message appears only when RC has debug logging on. This is
  because RC did not find the user in RDS (or corporate LDAP)?
  
  The user 'xxx' has a null first or last name.
       First Name: null
       Last Name : null
  
  2) 'getControlType: Invalid Control Type: -1' - This one also
  appears without debug mode and there are around 50+ such
  messages in a row during one index batch.
  getControlType: Invalid Control Type: -1
  ...
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Slow JDBC-based indexing in RC 5.3
  

Problem conclusion

• Fixed in IBM Rational Change Fix Pack 5.3.0.2.
  

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

  TLOGIC CHANGE

• Fixed component ID

  5724V87CG

Applicable component levels

• R520 PSN

     UP