Averify Connects to DB Host Which Is Not Set to averify.properties
(Doc ID 2240658.1)
Last updated on NOVEMBER 26, 2024
Applies to:
Oracle Agile PLM Framework - Version 9.3.2.0 and laterInformation in this document applies to any platform.
Symptoms
Actual Behavior
Averify connects to different DB host which is not set in averify.properties file
Steps
- Modify the tnsnames.ora. Set only 1 DB host name.
AGILE9 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = XXXXX.com)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = agile9)
)
) - Set averify.properties file. averify.dest.jdbc.url is set to different existing DB host other then the one set in step 1.
averify.dest.jdbc.url = jdbc:oracle:thin:@YYYYY.com:1521:agile9
averify.dest.jdbc.driver = oracle.jdbc.driver.OracleDriver
averify.dest.tns.name = agile9
averify.dest.oracle.home = /u01/app/oracle/product/12.1.0/dbhome_1 - Run averify and review Averify.log
check-tns:
[exec]
[exec] TNS Ping Utility for Linux: Version 12.1.0.2.0 - Production on 03-MAR-2017 16:00:46
[exec]
[exec] Copyright (c) 1997, 2014, Oracle. All rights reserved.
[exec]
[exec] Used parameter files:
[exec] /u01/app/oracle/product/12.1.0/dbhome_1/network/admin/sqlnet.ora
[exec]
[exec]
[exec] Used TNSNAMES adapter to resolve the alias
[exec] Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS =
(PROTOCOL = TCP)(HOST = XXXXX.com)(PORT = 1521))) (CONNECT_DATA =
(SERVICE_NAME = agile9)))
[exec] OK (70 msec)
check-tns-failed:
[AverifyAll] File Deleted
[AverifyAll] File ../scripts/run.sql created
.... - Review the averify output
Cause
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
Symptoms |
Cause |
Solution |
References |