Generic Database Extractor ETL failing with "FAILED BCO_DB_FAIL103: Availability/Connectivity: the DB instance seems to be DOWN or not reachable." but DB is up and accessible

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    TrueSight Capacity Optimization


    COMPONENT:

    Capacity Optimization


    APPLIES TO:

    BMC TrueSight Capacity Optimization 10.5, 10.3, 10.0



    PROBLEM:

    Problem symptoms include:

    (1) The General Database Extractor ETL is failing with the following errors:

    [2016-06-22 16:10:23] FAILED BCO_DB_FAIL103: Availability/Connectivity: the DB instance seems to be DOWN or not reachable. Reason: java.sql.SQLException: Listener refused the connection with the following error:
    ORA-12505, TNS:listener does not currently know of SID given in connect descriptor

            at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:458)
            at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:546)
            at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:236)
            at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
            at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521)
            at java.sql.DriverManager.getConnection(DriverManager.java:664)
            at java.sql.DriverManager.getConnection(DriverManager.java:247)
            at com.neptuny.cpit.etl.DBInterface.connect(DBInterface.java:212)
            at com.neptuny.cpit.etl.extractor.DMSQLE.connect(DMSQLE.java:90)
            at com.neptuny.cpit.etl.Engine.start(Engine.java:129)
            at com.neptuny.cpit.etl.ETLrun.main(ETLrun.java:159)
    Caused by: oracle.net.ns.NetException: Listener refused the connection with the following error:
    ORA-12505, TNS:listener does not currently know of SID given in connect descriptor


    (2) The ETL is configured to use an Administration -> ETL & System Tasks -> External DB Connections database configuration which is working properly with another ETL
    (3) The extract.database.url reported in the ETL log does not match the expected connection string for the defined External DB Connection


    SOLUTION:

     

    First, validate that the Administration -> ETL & System Tasks -> External DB connections -> [Database definition for this ETL] is correctly defined.  If the ETL is configured to access a database via the 'External DB connections' the properties associated with the External DB Connection will be applied when the ETL runs and only the SID being used will be visible in the ETL output error message (the hostname and port will not be reported).

    Also, note that if you correct the 'External DB connections' properties for a database definition it is necessary to restart the TSCO ETL Engine Scheduler to apply those changes to the next ETL execution.  This is definitely necessary for the update to be picked up if the ETL is to be tested immediately after the External database properties definition is changed.

    The problem may be that some parameters related to a database connection defined within the ETL itself may be "stuck" in the ETL configuration.

    So, when an ETL is configured to use an external database connection the "extract.connection.id" parameter should be set in the ETL -- but the extract.database.driver and extract.datbase.url parameters should not be defined.

    Workaround

    Edit the ETL configuration and:
     (1) Validate that the extact.connection.id parameter is set
     (2) Click the red circle delete button next to the extract.database.driver and extract.database.url fields

     


    Article Number:

    000122239


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles