JR37705: SYBASEOC Stage puts unnecessarily KEY columns in SET clause of UPDATE statement.

APAR status

• Closed as new function.

Error description

• SybaseOC stage unnecessarily puts KEY columns in SET Clause of
  an UPDATE statement causing performance degradation. This is
  because of some unnecessary steps involved in processing
  the query with no extra advantage.
  

Local fix

• Use generated SQL query and modify it by removing KEY columns in
  SET clause of UPDATE statement and using the query as
  user-defined SQL.
  

Problem summary

• SybaseOC stage unnecessarily puts KEY columns in SET Clause of
  an UPDATE statement causing performance degradation. This is
  because of some unnecessary steps involved in processing
  the query with no extra advantage.
  

Problem conclusion

• Corrected SybaseOC stage behaviour at both server and GUI level
  to reflect a query in which only NON KEY columns appear in SET
  clause of an UPDATE statement. However this is applicable only
  in generated SQLs not in user defined SQLs. And this behaviour
  is adopted for performance reasons in execution at database
  side.
  
  Users who wish to see the old behaviour i.e. generating UPDATE
  statement which contains all columns instead of only KEY columns
  in SET clause must set the environment variable
  SYBASEOC_DONT_SKIPKEYCOLS_IN_UPDATE to 1 and rerun their jobs.
  However the GUI still shows the query which has ONLY KEY columns
  in the UPDATE statement.
  

Temporary fix

• Use generated SQL query and modify it by removing KEY columns in
  SET clause of UPDATE statement and using the query as
  user-defined SQL.
  

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

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R810 PSY

     UP