Alter Session Statements For DB2 LUW?

(Doc ID 2023995.1)

Last updated on JUNE 29, 2017

Applies to:

Siebel CRM - Version 8.1.1.11.11 [IP2013] and later
Information in this document applies to any platform.

Goal

Alter Session statements for DB2 LUW?

When working with an Oracle RDBMS, Oracle recommends the following:

When testing and verifying the SQL performance of a Siebel client in that is running in an Oracle Cost Based Optimizer (CBO) environment, it is important to first run the following alter session statements to have the same session environment:

alter session set optimizer_mode = first_rows_10; 
alter session set hash_join_enabled = false;
alter session set "_optimizer_sortmerge_join_enabled" = false;
alter session set "_optimizer_join_sel_sanity_check" = true;

These are the same session parameters that the Siebel Oracle CBO client will set.


What statements are necessary when working with a DB2 LUW RDBMS to have the same session environment?
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms