EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB19597: ‘Error communicating with connection process. Find target process dead while waiting for reply` error occurs when running reports against Teradata database


Community Admin

• Strategy


Error in report results Your request could not be processed due to a server error. Please try again. If the problem persists, contact the server Administrator.

SYMPTOM
Running a report in Strategy 10.x against a Teradata database generates the following error:
 
Error in report results
Your request could not be processed due to a server error.
Please try again. If the problem persists, contact the server
Administrator.
(Item not found in this collection.QueryEngine encountered error:
Unknown failed. Unable to connect. Error type: System call error.
Error communicating with connection process. Find target process dead
while waiting for reply..
Error in Process method of Component: QueryEngineServer, Project
AQUA, Job 16374, Error Code= -2147212544.)
DSSErrors logs show the following error messages:
 
2008-06-16 11:54:39.782+01:00 Failed to read from pipe.
System Error (ENXIO): No such device or address
2008-06-16 11:54:39.805+01:00 Find target process dead while waiting for reply
2008-06-16 11:54:39.821+01:00 Unknown failed. Unable to connect. Error type: System call error. Error communicating with connection process. Find target process dead while waiting for reply.
2008-06-16 11:54:39.855+01:00 QueryEngine encountered error: Unknown failed. Unable to connect. Error type: System call error. Error communicating with connection process. Find target process dead while waiting for reply.
CAUSE
The above error can occur in a situation where there is a hot standby node.
 
Note: A hot standby node is used to provide failover support in case one of the other nodes goes down. This hot node is always active and connected to the working system and as soon as one of the other nodes goes down, this hot node is switched into operation.
 
When Teradata ODBC Driver tries to connect to Teradata and if the node chosen (randomly) is the Hot Standby Node, the database immediately closes the TCP connection. This is a known issue with Teradata and is logged as Defect ID DR122548.
 
ACTION
To avoid running into this issue, the user should modify their .odbc.ini and remove the entry for Hot Standby Node. For instance in the following ODBC.ini file, the line "DBCName3=systerp3" should be removed (or commented out) because this entry relates to the Hot Standby Node.
 
========================================
Driver=/usr/lpp/tdodbc/odbc/drivers/tdata.so
Description=WAREHOUSE FOR TEST TERADATA
DBCName=systerp1
DBCName2=systerp2
DBCName3=systerp3 <=== comment this out.
SessionMode=Teradata
NoScan=Yes
RunInQuietMode=Yes
StCheckLevel=0
DateTimeFormat=AAA
LastUser=
Username=
Password=
Database=
DefaultDatabase=
CharacterSet=UTF8
Note: DBCName is the name of the Teradata system/node. In this case it is systerp3.
 
After making the above change, restart Strategy Intelligence Server.
 
19597


Comment

0 comments

Details

Knowledge Article

Published:

June 2, 2017

Last Updated:

June 8, 2018