Originally posted by: SystemAdmin

My maps are making multiple connections to an Oracle database. They have suddenly stopped dropping these connections, so that the Oracle system table eventually fills up, locking out users.

I have tried to work around this been changing the IdleDB setting to 20, so that once 20 idle connections are reached they will be killed. All this does is stop the maps making any connections at all once the limit has been reached.

I'm working with 6.5.2 on UNIX 4.3.3 with Oracle 8 client.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

From the.ini file,
"IdleXXX is the number of seconds to allow a connection to be idle
before automatically disconnecting. 0 to disable this feature."

i.e. it's not what you're thinking it is.

Ask your Oracle DBA to increase the number of allowable connections from your integration server. On a hih volume system I recently worked on, we had some 400 or so connections available to Mercator/TX.

Try this in your .ini file :

IdleDB=10
SLimDB=20
HLimDB=100
KeepDB=0
MinDB=0
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

If you are still having this problem, try changing the socket setting in your .ini file. We had the same problem in SQL Server. We matched our socket setting to the DB setting.

IdleSOCKET=60
;SLimSOCKET=0
;HLimSOCKET=0
KeepSOCKET=20
;MinSOCKET=0
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

There is no relation between Socket & DB. You might want to set KeepDB to a low number (about 1/2 IdleDB). However, if your connections are being reused and the idle time does not get reached, the connections won't be dropped. If you have IdleDB as 10 (seconds) and your DB map runs every 5 seconds, there is no idle time, or if the map runs every 20 seconds but takes 12 seconds to complete, same thing.
Oracle should be able to handle a lot more connections. SLIM does just about nothing, HLIM is the one to set and use if there is a real limit.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

Here's a copy of what we had in 6.5.2 (windows)

IdleDB=120
SLimDB=45
HLimDB=60
KeepDB=60
;MinDB=0
At the time I believe jsmoley recommended similar setting but suggested I work with our DBA to fine tune. If you want to make sure your connections time-out you could uncomment MinDB but I think the default is zero anyway.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender