I am not sure this will help or not. We saw same situation in our project at that time database connections were increasing linearly.
Everytime ODI is creating new connection when accessing the database, may be this process also starting Unix thread on OS side.
We raised SR with oracle about this, but didn't get any solution. This is the architecture of ODI. I think connection process improved in ODI 12c, even Oracle DB12c also providing connection pooling feature.
Thanks so much for the information. I've checked the db connections to see if these threads are trying to make a db connections..but seems like its not a db connection thread.( I maybe wrong)
the thread looks like its connecting to master and work repository(parametrs from odiparams.sh file) and then hitting all these java config files and at the end hitting the startscen.sh by passing the variables.
do you think there is some type of setting in these xml files that ODI has to process thesemany no .of threads?
thanks again for sharing your thoughts.