Last updated on OCTOBER 13, 2015
Applies to:Siebel System Software - Version 7.5.3  to 18.104.22.168 [Release V7]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 22.214.171.124  Com/Med
Database: Oracle 126.96.36.199
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Compaq Tru64 UNIX
This document was previously published as Siebel SR 38-1182507314.
Customer reported the following:
Why if an active Repeating Component Request (RCR) was canceled the instances for the canceled component continue to run indefinitely?
Steps to reproduce this matter:
1) Create a Repeating Component Request
Site Map > Server Administration > Enterprise Operations > Repeating Component Requests
Submit Date = 2/6/2004 04:13:38 PM
Repeating Start = 2/6/2004 04:13:38 PM
Repeat Interval = 5
Repeat Unit = Minutes
Repeat From = Scheduled Start
Delete Unit = hours
Delete Interval = 2
Expiration = 2/6/2004 05:30:23 PM
2) Please navigate to Site Map > Server Administration > Enterprise Operations > Repeating Component Requests Detail
a) The Status of some RCR INSTANCE are "error" and one is "queued"
b) In the "Repeating Batch Job List Applet" go to menu and click "Cancel Repeating Request"
b1) The Status of the RCR Parent goes to "Cancelled"
b2) The status "error" of the RCR Instances didn't change
b3) The Status of the RCR instance from "queued" goes to "to "cancelled" too.
3) When the Expiration time was reached, the RCR was not deleted
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms