AWA Using a tnsnames.ora reference in the Analytics Backend causes the backend to not start.

book

Article ID: 141234

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine AUTOMIC WORKLOAD AUTOMATION CA Automic One Automation CA Automic Operations Manager CA Automic Oracle

Issue/Introduction

When trying to utilize a connection for the Analytics that uses a tnsnames.ora, the Analytics agent does not start and gives an error similar to:

Error while generating chart.: Unrecognized token 'Connect': was expecting ('true', 'false' or 'null') at [Source: (String)"Connect to 10.96.137.137:8090 [/10.96.137.137] failed: Connection refused: connect"; line: 1, column: 8]

Cause

The use of the thin client requires both specific syntax and reference to the tnsnames.ora file directly at start.

Environment

Release : 12.3

Component : ANALYTICS

Resolution

1.) in the applications.properties, make sure the line reads like such (orclpdb in this case is my tnsnames entry)

datasource.ae.url=jdbc:oracle:thin:@orclpdb

2.) in the start command, you need to add a java flag pointing to your tnsadmin folder (-Doracle.net.tns_admin=/home/oracle/19c/network/admin)

So my full command to start looks like:

/opt/Java/jre1.8.0_231/bin/java -Xmx512M -jar -Doracle.net.tns_admin=/home/oracle/19c/network/admin analytics-backend.jar