Siebel Triggers Disabled When Triggers Should Have Been Enabled (Doc ID 2235504.1)

Last updated on FEBRUARY 22, 2017

Applies to:

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

Goal

The expected process is to disable triggers before executing one monthly job and then to enable the same triggers after completion of the job.
Support team disabled the triggers before the job; however, the triggers were not enabled after completion of the job, as required.

What kind of data loss could happened to the system and how can we  mitigate this from occurring again?

Below are the Triggers:


SIEBEL S_SRM_TASK_HIST_T1 TRIGGER 24-JAN-17 DISABLED

SIEBEL S_ORG_EXT_ESCL_T3 TRIGGER 24-JAN-17 DISABLED

SIEBEL S_INV_PROF_ESCL_T3 TRIGGER 24-JAN-17 DISABLED

SIEBEL S_ORG_EXT_ESCL_T2 TRIGGER 24-JAN-17 DISABLED

SIEBEL S_ORG_EXT_ESCL_T1 TRIGGER 24-JAN-17 DISABLED

SIEBEL S_ORDER_ESCL_T2 TRIGGER 24-JAN-17 DISABLED

SIEBEL S_ORDER_ESCL_T1 TRIGGER 24-JAN-17 DISABLED

SIEBEL S_INV_PROF_ESCL_T1 TRIGGER 24-JAN-17 DISABLED

SIEBEL S_INV_PROF_ESCL_T2 TRIGGER 24-JAN-17 DISABLED

SIEBEL S_CON_ADDR_ESCL_T2 TRIGGER 24-JAN-17 DISABLED

SIEBEL S_CON_ADDR_ESCL_T1 TRIGGER 24-JAN-17 DISABLED

SIEBEL S_CONTACT_ESCL_T2 TRIGGER 24-JAN-17 DISABLED

SIEBEL S_CONTACT_ESCL_T1 TRIGGER 24-JAN-17 DISABLED

SIEBEL S_ALERT_CUT_ESCL_T2 TRIGGER 24-JAN-17 DISABLED

SIEBEL S_ALERT_CUT_ESCL_T1 TRIGGER 24-JAN-17 DISABLED

SIEBEL S_ADDR_PER_ESCL_T2 TRIGGER 24-JAN-17 DISABLED

SIEBEL S_ADDR_PER_ESCL_T1 TRIGGER 24-JAN-17 DISABLED

 

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