Dear Team,
We are observing below behavior;
We have parent scenario to submit actual odi jobs using odistartscen command
Parent scenario runs for every few mins after successful completion of previous. As its real time analtics there would be more CDC batches running per day. Now, more number of jobs are running (~4k) and we see:
All child jobs are in RUNNING state, but when checked in db there are very few sessions like ~100.
Though child job is in RUNNING state, invidiual steps in child scenario are not initiated yet.
Can you pls help with any recommendations to fix above prob. Unable to currently understand why this behavior is?
Appreciate your help.!
--
Regards,
kk