I was looking for this info few years back and later I found that it was a bug with older versions of OIM 11g. Oracle provided the fix in OIM 11.1.1.3.8 and OIM 11.1.1.5.2 but couldn't look into this. Here are the steps:
Property : Scheduler.disabled
scheduler.disabled=true -> If you don want to run scheduler on any node
Restart the server using node manager so that the newly added property is picked up. Restarting from the Command-Line Interface does not work.
Ref: Oracle Docs
Property : Scheduler.disabled
scheduler.disabled=true -> If you don want to run scheduler on any node
- Log in to the WebLogic Administrative Console > Environment -> Servers
- Select the managed server where you want to add the scheduler.disabled=false property.
- Click "Lock and Edit" and go to Configuration -> Server Start.
- In the Arguments box, type the -Dscheduler.disabled=true property, and click Save.
- Click Activate Change and Restart the managed server
Restart the server using node manager so that the newly added property is picked up. Restarting from the Command-Line Interface does not work.
Ref: Oracle Docs