Connection request keeps timing out when connecting to Oracle RDBMS

[CaitlinLee]

Hi all, I am currently using the Oracle MDA Utility VBO present on DX to connect to an Oracle database, and mainly uses the "Get Collection" action to run the SQL queries. So far, the Oracle MDA VBO works fine for any attempts to connect to a staging version of the Oracle database and is able to get the desired collection data. The issue here is that when attempting to do the same with a production version of the Oracle Database, I kept facing an issue where, whenever the code stage "Open" is executed to open a connection to the database, it always returns "Connection request timed out". 

Attempts were also made to increase the connection timeout for as long as 5 minutes, but the same timeout message was returned as well. The firewall layer has been whitelisted for the runtime resources that runs the code to connect to the Oracle database, but no such luck, as the issue persists as well. Database permissions between the staging version and production version of the Oracle databases are matched, so that rules out any possibility of the issue stemming from the database itself.

Would also like to note that when checked on the database's side, it has stated that the connection between Blue Prism and the database is also established successfully. So, it is quite perplexing on how the connection can be established database side, but still returns a connection timed out message back on Blue Prism's side.

Would highly appreciate for any guidance on how to resolve this "Connection request timed out" issue.

Thanks!

[GeoffHirst]

Hi Caitlin,

Could you try setting Pooling=False in the connection string?

Also, is there any chance there could be a tnsnames.ora file lurking around anywhere that could be overriding the connection string parameters?

thanks

Geoff Hirst
DX Engineer EMEA

[CaitlinLee]

Hi Geoff and Eric,

Thanks for taking to help out with my issue, however it seems that my team has already found a way to resolve it!

I did try to do as both of you suggested, which was adding the "Pooling=False" to the connection string, which sadly didn't work, and there was nothing additional to note when looking in the Windows Event Viewer either. However, my team has provided a suggestion to use a service name instead of an SID in the connection string, and the bots are finally able to connect to the production database. 

Once again, thank you for taking the time to answer my questions.

Best regards,
Caitlin

[GeoffHirst]

Hi Caitlin,

I am pleased to hear that you have a solution.

Good luck in all your endeavours with Blue Prism.

regards

Geoff Hirst
DX Engineer EMEA.