ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Alternative configuration of the DB Service

book

Article ID: 237854

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

In DB failover scenarios it may happen that the DB Service (VARA SQL / VARA SQLI) fails:

20211210/192709.996 - U02012045 The database returned an error for RunID '1771152447/1':
20211210/192709.997 -           No more data to read from socket
20211210/192709.997 - U02012037 Query with RunID '1771152447' ended abnormally

 

Environment

Release : 12.2

Component :

Resolution

The DB Service can also work in the following way:

1. Install the SQL Agent with the standard SQL Agent ini-file (ucxjsqlx.ini)

2. In the ini-file set type=GENERICJDBC

3. Start the Agent with the option -service:

java -jar -Xmx256M c:\uc4\ServiceManager\bin\..\..\Agents\sql_as_service\bin\ucxjsqlx.jar -service -ic:\uc4\ServiceManager\bin\..\..\Agents\sql_as_service\bin\ucxjsqlx.in

4. In the Connection Object choose: Generic JDBC

5. Set a string like this:

jdbc:oracle:oci:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=vviesup09.sbb01.spoc.global)(PORT=1521))(CONNECT_DATA=(SERVER = DEDICATED)(SERVICE_NAME = WO122)))

Note that the prefix is jdbc:oracle:oci instead of jdbc:oracle:thin

IMPORTANT: While testing with 'Connection Test' make sure that there are no other DB-Service Agents running because the test seems to fail if executed on a differently configured Service.