How to Increase the Default File Descriptor Limit for Oracle Data Gateway

June 10, 2020 | 2 minute read
Ahmed Awan
Director, Customer Excellence, Analytics
Text Size 100%:

Do you use Data Gateway to connect Oracle Analytics Cloud to your remote data sources? If you experience connection issues or Oracle Analytic Cloud becomes unresponsive, you’re probably hitting the Oracle Linux upper file descriptor limit. By default, the maximum number of file descriptors that Data Gateway can open is 1024 and this value is often too low for Data Gateway, even with moderate use.

This document describes how to use the Oracle Linux List Open Files (lsof) command to verify the number of file descriptors your Data Gateway uses and, if required, how to increase the limit from 1024 to 131072.  

Checking open files in Linux

Use the Oracle Linux List Open Files (lsof) command to verify the number of open files and network file descriptors that a specific process is using.

The syntax of the lsof command is as follows:

lsof -p 

Checking open files for Data Gateway

If you run the lsof command immediately after starting the Jetty server on Oracle Linux 7.x where you deployed Data Gateway, it shows that 234 file descriptors were allocated by the Java process (pid 1414) running on the server. This number (234) is far below the default limit of 1024 file descriptors.

For example:

$ lsof -p 1414 | wc -l

If you experience issues, you can run the command again to verify that the problem is because the maximum number of open files available to the Data Gateway Java process has been reached.

Increasing the file descriptor limit for Data Gateway

To work around this issue, you can increase the open file limit (nofile) and the maximum number of process limit (nproc) in the Oracle Linux 7.x configuration file limits.d from 1024 to 131972.  You must use the system administrator user where Data Gateway is running to make the change.

For example:

[root@bi-1]# cd /etc/security/limits.d/

[root@bi-1 limits.d]# vi 99-oracle.conf

add following and save 99-oracle.conf file:

opc soft nofile 131072

opc hard nofile 131072

opc soft nproc 131072

opc hard nproc 131072

Note: In this example, you must replace the user opc with the name of the system administrator user where your Data Gateway is deployed.

Ahmed Awan

Director, Customer Excellence, Analytics

Previous Post

Enhance Your Data Preparation Using Oracle Analytics

Philippe Lions | 9 min read

Next Post

Retrieve Valuable Machine Learning Model Info - Part I

Philippe Lions | 6 min read