Receiving QUERYHISTORYFAILED messages with XCOM Gateway Sharing the Database

Products

• XCOM Data Transport - Windows
• XCOM Data Transport

Issue/Introduction

Intermittently transfers may receive a QUERYHISTORYFAILED message in the Gateway Control Center log. 

The system had both IPV4 and IPV6 enabled. IPV6 was using the hostname in the config files and when the hostname is used, it can resolve it to IPV4 or IPV6 causing the intermittent problem.

In this case you can resolve by:

1. Disable IPV6.

2. Make sure that the user identification for the history database is not specified in the xcom.glb with a Domain included:

3. Add the domain to the ODBC UID parameter:

[XCOMHIST]
CLISchema=svc_dbxc
Database=XCOMHIST
Port=60000
Hostname=xxxxxxx.cc.bbb.net
SchemaList='svc_dbxc','xcomhist'
UID=domain\svc_dbxc
DESCRIPTION=DB2XCOM

Environment

Release : 12.0

Component : CA XCOM DATA TRANSPORT GATEWAY FOR WINDOWS

Cause

The actual cause of the problem was due to sharing the same IBM DB2/MySQL database with multiple XCOM Gateway servers.

Resolution

It is not recommended that the XCOM Gateway database be shared with multiple Gateway servers. Sharing the database can cause multiple problems such as:

1. Message "XCOMN1301E SCHEDULE REQUEST FAILED: ERROR SETTING LOCAL USERID" and the transfer is not scheduled

2. QUERYHISTORYFAILED  messages in the Gateway Control Center log for the Transfer Status.

3. Policy File Watcher stopped when multiple Gateway Servers are sharing the database.

Each XCOM Gateway server requires its unique IBM DB2/MySQL database to prevent any type of contention when a file is received into the Gateway and needs to be onward transferred. 

Additional Information

This problem was encountered when a new more controlled network was created. There is a Windows server within this network that has XCOM and the Gateway. The REALM is local to this server. The XCOM XCOMHIST and Gateway databases are on a separate server outside this controlled network.