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

KB212182: "System call error. Error communicating with connection process" error occurs when running reports in MicroStrategy 9.3.x or earlier


Community Admin

• Strategy


"System call error. Error communicating with connection process" error occurs when running reports in MicroStrategy 9.3.x or earlier

SUMMARY
This document outlines a system error that is received when running reports against a database which supports parameterized queries. This issue has been identified as a defect with Strategy 9.3.x and earlier versions and has been fixed in Strategy 9.4.1 and later versions.
SYMPTOM
In Strategy 9.3.x or earlier, the following error is received when running reports against a database which supports parameterized queries. The following example error message is received when the warehouse is on an Oracle 11g database:

ka04W000000OhTbQAK_0EM4400000029KQ.jpeg

 
 


Error: SQL Generation Complete
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. SQL Statement: create table ZZTOWDE4Z6BOP000(
XXXXXX  VARCHAR2(508), 
XXXXXX VARCHAR2(255)).. 
QueryEngine encountered error: Report [New Report (3)]: Drop table error: DBInstance = Enterprise Manager WarehouseSQL Statement: drop table ZZTOWDE4Z6BOP000 purge. 
Error in Process method of Component: QueryEngineServer, Project Enterprise Manager_freshstart, Job 21843, Error Code= -2147212544.

Three conditions need to be met to expose this issue:

  1. Parameterized queries should be enabled on the database connection (advanced parameters of the database connection editor) corresponding to the warehouse database instance.
  2. The report should involve the creation of temporary table(s) during execution.
  3. Large volume of data transfer from Strategy to the temporary table, for example, over 300,000 rows of data write to the temporary table during report execution.

CAUSE
This is a known issue with Strategy 9.3.x and earlier in a case where parameterized inserts is enabled on the database connection and when a large volume of data is transferred to the database through this connection.
ACTION
This issue has been resolved in Strategy 9.4.1 and later versions.  Upgrade to the latest Strategy platform release or feature release version to take advantage of the fix.


Comment

0 comments

Details

Knowledge Article

Published:

May 18, 2017

Last Updated:

May 18, 2017