JR30392: CUSTOMER WOULD LIKE THE CAPABILITY TO TOGGLE THE ALGORITHM USED BY THE PARTITION TABLE OPTION IN THE ORACLE ENTERPRISE STAGE.

APAR status

• Closed as program error.

Error description

• Customer is upgrading from DataStage 7.0 to 7.5.3. In the newer
  release, the algorithm used with the parition table option in
  the Oracle Enterprise stage has been changed.  The new algorithm
  causes massive performance degredation for this customer based
  on the way their oracle tables are layed out. The customer would
  like an option which would allow them to toggle back to the
  previous algorithm to avoid the performance penalty.
  

Local fix

• Customer can visit each job and remove the partition table
  option. However this will require signficant manual effort as
  there are a lot of jobs, and the customer had good results with
  the previous method and does not want to be forced to change
  their jobs just to complete the upgrade to the newer version.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  7.5.3 Oracle Operator Read users.
  ****************************************************************
  PROBLEM DESCRIPTION:
  Old Oracle EE read partitioning algorithm was removed and
  replaced by the new improved version.
  ****************************************************************
  RECOMMENDATION:
  Upgrade to latest version of the Oracle EE stage to obtain this
  fix.
  ****************************************************************
  

Problem conclusion

• For 7.5.3 Oracle EE read stages, set environment variable
  APT_ORAREAD_PARALLEL_ALGORITHM to ROUND_ROBIN to enable the new
  algorithm. The old algorithm will now be enabled by default
  unless reading from an IOT, view, or no select access has been
   granted to sys.dba_extents. The old algorithm never worked with
  IOT's, views and required select access to dba_extents so we
  now check for these required conditions before using the old,
  and if any are not true, we revert to the new algorithm.
  
  For example, If reading from a view and
  APT_ORAREAD_PARALLEL_ALGORITHM is not explicitly set to
  ROUND_ROBIN, we will still use the new Round Robin algorithm
  because the old algorithm did not work with views.
  

Temporary fix

Comments

• This change is included in 8.0.1 Fix Pack 2.
  

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

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R753 PSN

     UP