We have a legacy application (ERP) that, because of technical issues, spawns a new OS process (.exe - ms windows clients) for each screen requested by the user. Also, each company branch (> 20) has its own schema, and the application deals using 1 connection for each. Since each user may open as many screens they deserve to, it is quite common that some users reach > 30 sessions.
That will result in opening many connections to Oracle. In last report, we got 861 sessions for 87 users (~10 sessions/user).
My customer's DBA is saying that this will knock the database performance down, and demand heaps (really huge amounts) from the server's RAM & CPU.
Does this statement make sense?
- What are the side effects of raising the
- What is the cost of a open process (even if idle) in the server?