# Troubleshoot the Connector

This section describes how to troubleshoot common problems that might occur when you set up the Oracle Connector.

The number of connections is exceeded when using sub tables

The Oracle Connector opens a new connection to retrieve data from each sub-table that you specify in the connector’s configuration file. However, Oracle might limit the number of connections. If this occurs, you can set the configuration parameter `UseSingleConnectionForSubtables` to `true`. This ensures that the connector uses only one connection for retrieving data from sub-tables.

The connector does not finish tasks / Tasks have a status of "processing" indefinitely

A problem in the Oracle API can prevent the connector successfully opening a connection to the database. This can cause the connector to stop processing.

To resolve this issue, enable Dead Connection Detection on your Oracle server. The Oracle server then terminates connections that do not respond, allowing the connector to open a new connection.

Data is not returned as expected

If the connector does not return the data you expect, use a SQL tool or interface to run the query that you entered in the connector’s configuration file. Check that the data returned matches what you want to retrieve. The connector cannot retrieve XML data types, but you can modify your SELECT statement to convert these data types into strings.

The connector does not populate a document field with the data from a content field

This is expected behavior. The information in the content field (specified by the `ContentField` parameter) is used to populate the document content. If your content field contains a file path and you want to write the path to a document field, you can modify your SQL query to return the column under another name. For example:

    SELECT myfield, myfield AS "anotherfield" FROM tablename...

Then, in your template file, specify the alternate name:

    #DREFIELD MyFieldName="<!--anotherfield-->"

_FT_HTML5_bannerTitle.htm