search cancel

QUERYHISTORYFAILED

book

Article ID: 230107

calendar_today

Updated On:

Products

XCOM Data Transport - Windows

Issue/Introduction

Although the files arrive at their destination, we continue to receive QUERYHISTORYFAILED message errors for several of those transfers in the Global Control Server log. The DB2 database for the XCOMHIST file is on a different server from the Gateway and XCOM server.

Submission Handle : 3412

TRANSFER ITEM NUMBER : 1

TRANSFER FILE NAME : file_name

TRANSFER FILE GUID : 

TRANSFER FILE SIZE : 0

TRANSFER FILE IMPORTATION TIME : Sat Nov 20  2021

TRANSFER MICR : 

TRANSFER STATUS : QUERYHISTORYFAILED

TRANSFER REQUEST NUMBER : 4061

TRANSFER LAST MESSAGE : Read timed out

TRANSFER REMOTE DESTINATION : null

 

Submission Handle : 3410

TRANSFER ITEM NUMBER : 1

TRANSFER FILE NAME : file_name

TRANSFER FILE GUID : 

TRANSFER FILE SIZE : 3255612

TRANSFER FILE IMPORTATION TIME : Sat Nov 20  2021

TRANSFER MICR : 

TRANSFER STATUS : QUERYHISTORYFAILED

TRANSFER REQUEST NUMBER : 4057

TRANSFER LAST MESSAGE : Read timed out

TRANSFER REMOTE DESTINATION : "ipaddr"

 

Environment

Release : 12.0

Component : XCOM DATA TRANSPORT GATEWAY FOR WINDOWS

Cause

After reviewing the GCS log for the Gateway and xcom.log it was determined that the history query for a transfer was taking minutes instead of seconds. Such history queries will take 3-5 seconds maximum, hence the "read timeout" message in the GCS log. 

Resolution

The problem was caused because tablespace "TS_DATA16KED" was full on their DB2 database. Once that was addressed the errors stopped.