oi_connector Not Closing Database Connections

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

The `oi_connector` probe (versions <= 2.03 ) fails to close database connections, leading to the following error in the `data_engine.log` and potential UIM service outages:

`OCI_ERROR - ORA-12516: TNS:listener could not find available handler with matching protocol stack`

Customers may observe a high count of `JDBC Thin Client` connections in the Oracle database that do not disappear until the `oi_connector` probe or the Primary Hub is restarted.

Environment

- DX UIM 23.4 or higher
- Oracle Database
- oi_connector probe versions <= 2.03

Cause

A product defect in the `oi_connector` probe caused a connection leak where active database connections were not returned to the pool, eventually exhausting the Oracle session limit.

Resolution

1. Upgrade the Probe:
   Deploy oi_connector version (v2.11) or higher. This version contains the engineering fix for connection pool management.

2. Verify Deployment Location:
   Ensure the oi_connector is installed on a dedicated remote robot connected to the Primary Hub, rather than on the Primary Hub robot itself.

3. Apply Configuration Keys (Raw Configure):
   Deactivate the probe and set the following keys in the `setup` section:
   - `skip_second_pass_ci_fetch = true`
   - `enable_alive_time_batches = false`

4. Database Cleanup:
   If the session limit is already reached, work with your DBA to identify and kill inactive sessions or restart the Primary Hub to release them.