BugZero updated this defect 58 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
3/22/2024
Smart Assurance - Watch4net/M&R
No affected releases provided.
No fixed releases provided.
Watch4net 6.1 is unable to collect data from Oracle and receives "could not establish the connection" error The following error is seen in collecting-0-0.log of the sql-collector for the Watch4net Collector Manager: SEVERE -- [2013-04-11 15:11:59 YEKST] -- v::compute(): An exception occurs during the main collect!org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Io exception: The Network Adapter could not establish the connection) Watch4net Collector Manager receives "could not establish the connection" error even though the connection string is defined correctly in sql-collector-oracle.xml file and matches the entries in listener.ora and tnsnames.ora on the Oracle database host: <db-connection id="1" username="username" password="password" url="jdbc:oracle:thin:@(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = FQDN)(PORT = 1521)) (CONNECT_DATA=(SERVER = DEDICATED)(SERVICE_NAME = FQDN)))" The Oracle database host can be pinged successfully from the Watch4net Collector host, but telnet on port 1521 does not work.
There is a firewall in place that blocks communication on port 1521 between Watch4net collector host and Oracle database host.
Open required port 1521 and restart the SQL Collector Manager. Connection to the Oracle database should now be possible.