My Oracle Support Banner

Averify Connects to DB Host Which Is Not Set to (Doc ID 2240658.1)

Last updated on FEBRUARY 21, 2019

Applies to:

Oracle Agile PLM Framework - Version and later
Information in this document applies to any platform.


Actual Behavior

Averify connects to different DB host which is not set in file


  1. Modify the tnsnames.ora. Set only 1 DB host name.

    AGILE9 =
       (ADDRESS_LIST =
         (ADDRESS = (PROTOCOL = TCP)(HOST = = 1521))
       (CONNECT_DATA =
         (SERVICE_NAME = agile9)

  2. Set file. averify.dest.jdbc.url is set to different existing DB host other then the one set in step 1.

    averify.dest.jdbc.url             =
    averify.dest.jdbc.driver          = oracle.jdbc.driver.OracleDriver             = agile9          = /u01/app/oracle/product/12.1.0/dbhome_1

  3. Run averify and review Averify.log

        [exec] TNS Ping Utility for Linux: Version - Production on 03-MAR-2017 16:00:46
        [exec] Copyright (c) 1997, 2014, Oracle.  All rights reserved.
        [exec] Used parameter files:
        [exec] /u01/app/oracle/product/12.1.0/dbhome_1/network/admin/sqlnet.ora
        [exec] Used TNSNAMES adapter to resolve the alias
        [exec] Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS =
    (PROTOCOL = TCP)(HOST = = 1521))) (CONNECT_DATA =
    (SERVICE_NAME = agile9)))
        [exec] OK (70 msec)

    [AverifyAll] File Deleted
    [AverifyAll] File ../scripts/run.sql created


  4. Review the averify output


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.