Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 62 Insurance
- 536.1K On-Premises Infrastructure
- 138.2K Analytics Software
- 38.6K Application Development Software
- 5.7K Cloud Platform
- 109.4K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71.1K Infrastructure Software
- 105.2K Integration
- 41.6K Security Software
Inactive Session in ODI Repository

Hello,
We have developed 10 mappings. All of these mappings are one to one mapping. They are no expression or conversion. The data is in CSV file (i.e. source system) and target is oracle ADW (i.e. target system). We have create a simple load plan to trigger all the mapping in parallel mode to load the data.
Before start the load plan we have observed no of inactive session for ODI repository is 4. After trigger the load plan the no of inactive session increased to 30. Once the load plan successfully completed out of the 30 inactive session only 12 got closed , remaining 18 inactive session are still in inactive mode. Those are not closed at all.
The no of inactive session are getting increase every time we trigger the data load process,
Any idea on this issue.
ODI Version is ODI Market place V12.2.1.4.210321.
Thank you all in advance.
Best Answer
-
Hi,
Apply Patch 32708064: Inactive ODI sessions not releasing DB connections
Adrian
Answers
-
Hi,
Apply Patch 32708064: Inactive ODI sessions not releasing DB connections
Adrian
-
Hi Adrian
we have an issue in our ODI similar to above, we are seeing 1000s of sessions just lingering in the database on an idle wait event
SQL> col event format a30
SQL> col state format a30
SQL> /
EVENT STATE COUNT(*)
------------------------------ ------------------------------ ----------
SQL*Net message from client WAITING 1943
SQL*Net message from client WAITED KNOWN TIME 72
Do you think this patch will help us as well ?
we are on 12.2.1.4
-
Hi,
If the idle sessions refer to ODI, apply the patch.
Adrian
-
Hi Adrian
Thank You very much for your reply.
We found that the patch is already applied in our production environment.
regards