cancel
Showing results for 
Search instead for 
Did you mean: 

Error in commit scan queue (TNS: address already in use )

Andres_Ronderos
Confirmed Champ
Confirmed Champ

Hi there:

For some time we get an error when a commit is made in a Scan queue.

The ScanQ is configured to trigger a VBScript that fill a table in Oracle and displays the following error:


Script Error in [114]
Error # -2147467259: [Oracle] [ODBC] [Ora] ORA-12542: TNS: address already in use
Line: 36
Source: Microsoft OLE DB Provider for ODBC Drivers


The line mentioned is as follows (in green):

Set ado = CreateObject ("ADODB.Connection")
Connect = "DSN = observer; UID = ****; **** PWD =;"
Call ado.Open (Connect)

It is an intermittent error which we have found no cause and is happening for more than 6 months.

Thank in advance for any help.

1 ACCEPTED ANSWER

Ansley_Ingram
Elite Collaborator
Elite Collaborator

Hi Andres,

I have a few suggestions for you to check regarding this error. First, verify that you are closing any connections that are established in the script. It may be that a connection was left open in a previous execution and thus it is already still open.

Depending on the volume of connections being used in the script and against your TNS Listener, you may also want to work with your Oracle DBA to look into increasing the queuesize or free port range (depending on the OS platform of your Oracle database). Your Oracle DBA may also want to review the TNS Listener's log to determine if there are any errors occuring there at the time you encounter the error in the script.

Hope that helps.

Ansley

View answer in original post

1 REPLY 1

Ansley_Ingram
Elite Collaborator
Elite Collaborator

Hi Andres,

I have a few suggestions for you to check regarding this error. First, verify that you are closing any connections that are established in the script. It may be that a connection was left open in a previous execution and thus it is already still open.

Depending on the volume of connections being used in the script and against your TNS Listener, you may also want to work with your Oracle DBA to look into increasing the queuesize or free port range (depending on the OS platform of your Oracle database). Your Oracle DBA may also want to review the TNS Listener's log to determine if there are any errors occuring there at the time you encounter the error in the script.

Hope that helps.

Ansley