The "JDBCFileLoaderSensor" job is churning out too many similar SQL queries and it is affecting database performance - Support and Troubleshooting

The "JDBCFileLoaderSensor" job is churning out too many similar SQL queries and it is affecting database performance Issue The JDBC File loader sensor detects a sudden surge in the number of SQL queries, causing it to become overwhelmed.

This can affect the database performance and can trigger alerts.

Cause The cause of this issue can be one of the following :-

1. The latest version of the "JDBC File Loader" is not there, which requires an update.

2. This issue occurs when the JDBC file loader is overwhelmed by a certain import set job that is generating a lot of SQL queries in a short interval of time.

In this case, the issue occurs in the following way :

- An import set script is initiated

- The import set script initiates a query based on the customized script mentioned and calls the set of SQL queries

- The query creates a series of SQL statements within a short interval of time.

Resolution The resolution can be done by doing either of the following, as it includes the same fix as mentioned below :

1. Update the JDBC File Loader, as it contains the fix.

2. One can manually update the following Script Include, as this does the same and resolves the issue.

Script Include: ImportSetUtilPlus : sys_script_include.do?sys_id=357980b6d3803100d40e90b53d11f08d - modify the getRowNumber function as follows:

getRowNumber: function (tableName, importSet) {

var row = new GlideRecord(tableName);

row.orderByDesc("sys_import_row");

row.setLimit(1);

row.addQuery("sys_import_set",importSet);

row.query();

if (row.next()) {

var rowNumber = row.sys_import_row + 1;

} else {

var rowNumber = row.sys_import_row = 0;

}

return rowNumber;

},