Sunday, March 23, 2014

Random children going into 'inactive'-'nomanager'

Ever happened that a request is fired which spawns many children and boom , one or two of them go into 'inactive' -'nomanager'. You have no clue why is that happening because when you see , you still have many managers available to cater to those requests.

Well , the reason is simple , an FND view needs to be rebuild. Without saying more , i suggest you go through the below metalink note :


Concurrent Program Spawns Child That is Going to Inactive No Manager (Doc ID 1621537.1)


Cheers
Orafolks :)

No comments:

Post a Comment