Accepted Solutions (1)
Hi Andrew,
We've seen this recently also... the problem is most DB's have enabled Connection Pooling and CR by default does a disconnect. But due to the way Clients work now they do not send a complete disconnect so the Servers Connection pooling keeps the connection open.
I believe ODBC does disconnect and if you are using OLE DB you can add/change this property in CR Designer Set Location properties. But OLE DB does have issues with Stored Procedures.
You should see this property:
Change that value to -4 and that should tell the client to do a complete disconnect.
PS - this is an old report so do not use the MS Oracle driver, it only support Oracle 7.
Also, we did update our native Oracle driver but not sure if the fix made it into SP 14 so I pinged the Developer to get more info.
In the mean time see if there is some setting on Oracle that can disable Connection Pooling.
And try ODBC to see if that releases them....
Don
Answers (1)
| User | Count |
|---|---|
| 84 | |
| 10 | |
| 9 | |
| 8 | |
| 6 | |
| 6 | |
| 6 | |
| 5 | |
| 3 | |
| 3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.