My Oracle Support Banner

How to change Campaign Load 'Record Size' (Doc ID 2188933.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Marketing - Version 15.10 [IP2015] and later
Information in this document applies to any platform.

Goal

During the Marketing Campaign Load, the following sql is observed in IP13 and later:

  UPDATE dbo.S_CAMP_CON
SET MODIFICATION_NUM = MODIFICATION_NUM+1,
  LAST_UPD = ?,
  LAST_UPD_BY = ?,
  DB_LAST_UPD_SRC = ?,
  DB_LAST_UPD = GETUTCDATE(),
  CAMP_LD_WAVE_ID = ?
  WHERE ROW_ID IN ( SELECT
  T1.ROW_ID
  FROM
  dbo.S_CAMP_CON T1
  WHERE
  (T1.LOAD_NUM = ? AND T1.CAMP_LD_WAVE_ID IS NULL AND T1.DCP_ID = ? AND T1.SRC_ID = ? AND T1.ROW_ID >= ? AND T1.ROW_ID <= ?) )

So when a campaign load of 700K records is performed, it was noticed this statement is executing 700 times sequentially, i.e the update of 1000 records is carried out by a single thread and hence is taking time to finish the complete load process.

Wanted to understand if the Record Size value of 1000 is a standard value which siebel uses for campaign load or can we reduce it to 500 so as to fasten the load process ?
 

Solution

To view full details, sign in with your My Oracle Support account.

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


In this Document
Goal
Solution


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.