Salesforce

Error, Transact, “Unable to read data from database server” if “Max Wait Time” not suitable for Transact.

« Go Back

Information

 
TitleError, Transact, “Unable to read data from database server” if “Max Wait Time” not suitable for Transact.
SummarySymptom: Seeding paf script run via EPBatch.exe failing intermittently in different user-plans.
URL NameError-Transact-Unable-to-read-data-from-database-server-if-Max-Wait-Time-not-suitable-for-Transact
Resolution
  • Increase “Max Wait Time” in EPC:  EP-Button > Database Connection > Connect Option
(Increase by a "substantial amount, to confirm that "Max Wait Time" is the contributing factor in the particular scenario)
 
  • Decrease Transact execution time by e.g.:
- Upgrade to EPClient 8.2.1.9 (If executing transact via, EPBatch)
- Split the single transact into multiple ones to split data retrieval in several batches
 
  • Investigate and address environmental causes e.g.:
-- Mid-Tier performance/configuration
-- Network performance
-- Database performance
 
(See also article 39982 Transact failing with "Unable to read data from database server" and Message-log showing "Authentication failed on the remote side")
ProductsEnterprise Planning Client Edition; Enterprise Planning Server Edition
Module
Version8.2.1.8
Error Message Code
"Unable to read data from database server"
Cause
This problem may occur if any of the following conditions are true:
  • “Max Wait Time” setting to small for transact volume.
Influenced by:
- Performance Issue in EPBatch.exe 8.2.1.8 or below, prolonging the execution time.
(See issue details below)

 
  • Mid-Tier performance/configuration
  • Network issues
  • Database issues

 
Additional Information
  • Batch.log error in context:
"I,42:0,Transact,09/15/2017,01:42:37,PLANNING_USER,Importing into \\machine\Toolkit\PROD\UserPlans\MOPP\CAT_0060\Roll3Year\CAT_0060\mod00001\mod00001. E,42:0,Transact,09/15/2017,01:57:37,PLANNING_USER,Unable to read data from database server."

Note that the time difference of Importing into (01:42:37) and Transact error (01:57:37) is here 15 minutes (900 sec) as set in "Max Wait Time". (Constant time span for all occurrences of reported issue)
 
  • The error "Unable to read data from database server” is a generic message and may not always represent a "Max Wait Time" condition.
 
  • 8.2.1.9 release notes:
Issue: EPBatch.exe performs very slow when compared to Planning.exe while running the same script.
Solution: Modified EP Batch such that few user interface related functionalities like Drawing cells, creating and removing temporary styles which are not necessary when running scripts via EPBatch.


(Redundant user interface related functionality been executed in the memory, when running scripts via EPBatch.)
 
  • Steps to Reproduce
 
- Running transact interactive using EPC:
EPC:  Home >  Transact
transact button

Source ServerDB
AppDB
OK
 
Import from ServerDB
BOP_RtlLY = BOP_RtlWP from ServerDB


transact
 
GUI error:
"Error retrieving data from the EP Mid-Tier server, the error returned is:
Unable to read data from database server"
transact GUI timeout

Planning.log:
"Unable to read data from database server."


 
 
- Running transact in batch mode using EPBatch.exe
Command window message: (log-file if command redirection operators > or >> are used)
"E,42:0,Transact,09/25/2017,08:02:05,PLANNING_USER,Unable to read data from database server."
transact error batch

Note, the time in-between “Importing into … \mod00001” and error “Unable to read data from database server” is the “Max Wait Time” choose in EPC > Connect Option. (In this sample 2 seconds)
Publication StatusPublished

Powered by