Instead of merely increasing your maximum, a more pertinent question might be why should I increase my maximum and when?
- If oracle has 8096 tasks running simultaneously, is that normal and a expected outcome?
- Has the DBA explained why it does this and what conditions lead to it?
- Do you agree that this behaviour should be normal for this data load?
If it is, you can increase the limit knowing what the point of the number of tasks are, as you've factored it into the running design of its configuration.
The default limits tend to be set abnormally high for most work loads, if you're exceeding them the first thing I'd be asking is why you would be doing so and if there is another way to do what you're doing that isn't as resource greedy.
You should think of the soft limits as a means for a user to recognise an anomaly in whatever they are running and respond by increasing it manually (hence potentially understanding why the resource is so large) or fixing the underlying issue that uses up so many resources.
Also, some programs do automatically raise the limits outside of the hard limit when they start (looking at you MySQL open file limit). Again as its expected in its design to exceed most normal workloads.
