Adding POUs Causes A Growing Logfile Including 'YANK INVALID' and 'YANK REJECT' Messages
(Doc ID 1321256.1)
Last updated on MARCH 20, 2019
Applies to:
Oracle Real-Time Scheduler - Version 10.3 to 10.5.0 [Release 10.3 to 10.5]Oracle Utilities Mobile Workforce Management - Version 1.4.5 to 1.5.0 [Release 1.4 to 1.5]
Information in this document applies to any platform.
Goal
POUs were added through the MWM Admin Tool causing SMAuto to max out CPU while logs started growing at an alarming rate with messages as noted below. Within an hour, one logfile grew more than 100 MB consisting mostly of the log entries below. To workaround the issue, Stop ORS, delete POUs through the database and clean both MWM and ORS to get rid of the shifts and POUs. How can this be prevented?
..
<HOSTNAME> 04/04/11 18:00:01.95 [28:40:46.96] PLAN CONTROL: YANK REJECT (SCHED 1.22); i=91605622, r=1, stops: ttl=41, free=0, assigned=9, allocated=7, d=6693, c=3.107e+007
<HOSTNAME> 04/04/11 18:00:01.95 [28:40:46.96] PLAN CONTROL: YANK REJECT (SCHED 1.22); i=91605623, r=1, stops: ttl=41, free=0, assigned=9, allocated=7, d=6693, c=3.107e+007
<HOSTNAME> 04/04/11 18:00:01.95 [28:40:46.96] PLAN CONTROL: YANK INVALID (SCHED 1.22); i=91605624, r=1, stops: ttl=41, free=0, assigned=9, allocated=7, d=6693, c=3.107e+007
<HOSTNAME> 04/04/11 18:00:01.97 [28:40:46.98] PLAN CONTROL: YANK INVALID (SCHED 1.22); i=91605627, r=1, stops: ttl=41, free=0, assigned=9, allocated=7, d=6693, c=3.107e+007
<HOSTNAME> 04/04/11 18:00:01.97 [28:40:46.98] PLAN CONTROL: YANK REJECT (SCHED 1.22); i=91605635, r=1, stops: ttl=41, free=0, assigned=9, allocated=7, d=6693, c=3.107e+007
<HOSTNAME> 04/04/11 18:00:01.97 [28:40:46.98] PLAN CONTROL: YANK INVALID (SCHED 1.22); i=91605637, r=1, stops: ttl=41, free=0, assigned=9, allocated=7, d=6693, c=3.107e+007
<HOSTNAME> 04/04/11 18:00:01.97 [28:40:46.98] PLAN CONTROL: YANK INVALID (SCHED 1.22); i=91605643, r=1, stops: ttl=41, free=0, assigned=9, allocated=7, d=6693, c=3.107e+007
<HOSTNAME> 04/04/11 18:00:01.97 [28:40:46.98] PLAN CONTROL: YANK INVALID (SCHED 1.22); i=91605644, r=1, stops: ttl=41, free=0, assigned=9, allocated=7, d=6693, c=3.107e+007
<HOSTNAME> 04/04/11 18:00:01.97 [28:40:46.98] PLAN CONTROL: YANK REJECT (SCHED 1.22); i=91605647, r=1, stops: ttl=41, free=0, assigned=9, allocated=7, d=6693, c=3.107e+007
<HOSTNAME> 04/04/11 18:00:01.98 [28:40:47.00] PLAN CONTROL: YANK INVALID (SCHED 1.22); i=91605652, r=1, stops: ttl=41, free=0, assigned=9, allocated=7, d=6675, c=3.107e+007
...
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 |
| References |