Product Name: Oracle Data Integrator, recently upgraded in Test environment from 12.2.1.4.200618 to 12.2.1.4.240405 via patch 36487966 (which also required an upgrade of our repository).
Recently, I performed the above patching in our Test environment, and after it was complete, I restarted to give a clean startup and then tested a mapping that normally takes about two minutes to complete. It took about 32 minutes. I tried various combinations of settings in the mapping (SQL → Oracle, SQL → Oracle Built-In, SQL → SQL, SQL → SQL Built-In, etc.), with no luck - still about 15x as long as our Production environment. Any suggestions as to how to proceed in diagnosing?
I did do a little searching and found an older post about some performance issues, but supposedly the patch I applied cleared that bug up.
I also did do a comparison between what was running in our Prod versus our Test, and it was the same code being run (when using the same LKM as Prod).
The one thing that I did see was different is on the Details page of the Session Task. Makes me think there was an extra step following the repository upgrade that I might have missed? But before this, Test was running about as long as Prod.
Update 5/1/2024: Upon further testing, our connection to Blackboard/PostgreSQL seems to be the one that is not working as hoped. All connection information matches between our Test and Prod environment match. All other sources and targets seem to be unaffected.
Prod environment:
Source OdiDMSource-1344487-90-0: Started On 12:08:48.136: Provided 23937866 rows in 139.850 secs. Wait=50.114 secs.
Target OdiDMTarget-1344487-90-0: Started On 12:08:48.136: Processed 23937866 rows in 139.850 secs. Execute=78.570 secs. Wait=29.715 secs.
Test environment:
Source OdiDMSource-315078-90-0: Started On 09:28:36.856: Provided 23931147 rows in 1847.908 secs. Wait=1788.598 secs.
Target OdiDMTarget-315078-90-0: Started On 09:28:36.856: Processed 23931147 rows in 1847.904 secs. Execute=42.026 secs. Wait=0.019 secs.