Hello  Sanjay, I don't want to reopen this issue but I don't know what else I could do.

The search scheduler has the bad habit (since the 4.3.5 of the DP, the first one I've used) to open more the 100 connections and leave them IDLE. Few days ago we started a project using DNN5.1.4. We bought your DP and, with a site of 2 tabs, we faced again this issue. The 4.9.3. hasn't this behavior and works fine with a small site (around 100 tabs).

Actually, we are not planning to use the DNN search engine for this project but this could be a critical point if we would need to use the internal search until the new one will be released.

However, even with the search scheduler disabled, our customers' system administrators reported us about a lot of connections left idle (always around 130 or more).

For the 4.3.5 (and the 4.9.3)we have solved the problem using these parameters in the connection string:

<add name="SiteOracle" connectionString="Data Source=ORACLEDB;User ID=dnnUser;Password=dnnPasword;Enlist=no;Persist Security Info=no;Pooling=yes;Connection Lifetime=20;Max Pool Size=180;Min Pool Size=5; " providerName="System.Data.OracleClient"/> 

Anyway, this could be a temporary patch not a solution.

Please, check the scheduler or any part of the provider that could drive to this issue.

Thanks.

Luigi

p.s.
We are not using modules different from the ones released with the dnn community distribution except our customed modules that don't use different approach to db than the original ones. 

Sanjay,

thank you for your reply. I tried your solution and (on my 5.1.4 empty site) it works fine but I didn't test deeply the search engine. Next week I will start to create all the pages and documents then I will test the search on a real site. Until then I hope to get from you a real patch or just the answer that it was all about two stupid not null.

Bye, Luigi

p.s.
I've got some other errors from different part of the site (administration and host pages) that depends on the Oracle DP, but I'll look for a different thread or I will open a new one.