Collaborations that have an execution schedule are running twice at the specified schedule time. (Doc ID 1029117.1)

Last updated on JULY 31, 2013

Applies to:

Sun e*Gate - Version 4.1.2 and later
Information in this document applies to any platform.
Information in this document applies to any platform.
Checked for relevance on 31-JUL-2013

Symptoms

Collaborations that have an execution schedule specified are running twice at the specified schedule time.

For example,
15:37:01.798 API I 6972 (workitems.cxx:1988): Collaboration colWmsTblOutptOutbdLoadExtract is about to run, waiting for start signal
15:37:05.267 API I 6972 (workitems.cxx:1988): Collaboration colWmsTblOutptOutbdLoadExtract is about to run, waiting for start signal
15:42:03.452 API I 6972 (workitems.cxx:2009): Collaboration colWmsTblOutptOutbdLoadExtract got start signal, running the collaboration
15:42:04.843 API I 6972 (workitems.cxx:2206): Collaboration colWmsTblOutptOutbdLoadExtract ran only once due to schedule option. This collaboration will sleep till next scheduled time.
15:42:09.281 API I 6972 (workitems.cxx:2221): Collaboration colWmsTblOutptOutbdLoadExtract got start signal, running the collaboration
15:42:09.390 API I 6972 (workitems.cxx:2206): Collaboration colWmsTblOutptOutbdLoadExtract ran only once due to schedule option. This collaboration will sleep till next scheduled time.

From the above, the same collaboration with the same thread number is set to run twice in a few seconds rather than every 5 minutes as it is scheduled.

Cause

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