Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Satish Annam (SatishAnnam)
Standard Chartered Bank
AVP/Lead SRE - PEGA
Standard Chartered Bank
IN
SatishAnnam Member since 2017 3 posts
Standard Chartered Bank
Posted: Feb 21, 2018
Last activity: Feb 26, 2018
Posted: 21 Feb 2018 11:41 EST
Last activity: 26 Feb 2018 5:35 EST
Closed
Solved

Maximum elapsed time in seconds for export

In one of our report definition we have below parameter values under data access

Maximum elapsed time in seconds: 60

Maximum elapsed time in seconds for export: 30

We happened to see below exception while exporting the retrieved data to excel through report.

SQLState 72000, Error code 1013: java.sql.SQLTimeoutException: ORA-01013: user requested cancel of current operation

In few threads it says, configure the value in Maximum elapsed time in seconds for export parameter to be greater than or equal to the value in Maximum elapsed time in seconds parameter. Is it mandatory/advised to have Maximum elapsed time in seconds for export >= Maximum elapsed time in seconds.

Will there be any DB sessions or performance issue by increasing Maximum elapsed time in seconds for export from 30 seconds to 60 seconds.

Please guide with your valuable suggestions.

To see attachments, please log in.
System Administration

Accepted Solution

Posted: 6 years ago
Posted: 21 Feb 2018 12:30 EST
Mohammad Asif Hasan (Mohammad_Asif_Hasan)
EPAM Systems, Inc.
Mohammad Asif Hasan
EPAM Systems, Inc.
ES

Hi Satish,

Thanks for posting on PSC.

As per definition,

Show More

Hi Satish,

Thanks for posting on PSC.

As per definition,

Maximum elapsed time in seconds:
 
Optional. Specify the maximum elapsed time in seconds that the report execution is allowed to run before being interrupted. If you leave this field blank, the system enforces a default limit of 30 seconds.
 
If the report exceeds the maximum elapsed time, a dialog opens explaining that the report took too long to run and that the filter conditions must be more specific. A report typically runs faster by adding additional filter conditions, or by making the existing ones more constraining.
 
Maximum elapsed time in seconds for export:
Optional. Override the default of 30 seconds if your system generally requires more time to export a report.
 
So, it's not mentioned as per my research but will try to find more and share if found in this post.
 
Logically, maximum elapsed time in seconds for export should be greater than maximum elapsed time. Because later one is the timeout for retrieving the data from the database and mapping it into clipboard. So, in either case, whether you're trying to just retrieve the data to display in UI or export, data has to be populated on the clipboard so this elapsed time or query execution time will pass. 
 
Now, when export to excel operation is done on report definition the data will be again manipulated by OOTB activities to create a CSV or excel file in the format so this is additional time required.
 
By this, we can conclude that Maximum elapsed time in seconds for export >= Maximum elapsed time in seconds.
 
Now let's come to your second question,
 
Yes, there would database performance issue when your report definition is going to have millions of record as SQL query will take time and it would be irrespective of this configuration. These settings just allow the report definition rules to run till this threshold timing.
 
Hope it answers your questions, kindly notify if it does by marking this post as answered for tracking purpose.
 
Regards,
Asif
 

Show Less
To see attachments, please log in.
Posted: 6 years ago
Posted: 21 Feb 2018 12:42 EST
Satish Annam (SatishAnnam)
Standard Chartered Bank
AVP/Lead SRE - PEGA
Standard Chartered Bank
IN

Thanks Asif for clear explanation,

My concern here, is these approach advisable to update 60 seconds for export parameter as below and will these increase the DB sessions or reduce performance?

Maximum elapsed time in seconds: 60

Maximum elapsed time in seconds for export: 30 60

Thanks and regards,

Satish Annam

 

 

To see attachments, please log in.
Posted: 6 years ago
Posted: 22 Feb 2018 4:57 EST
Mahesh Midthuru (Mahesh Midthuru)
PEGA
Senior Principal Application Engineer, Customer Service Digital
Pegasystems Inc.
US

Hi Satish,

The settings Maximum elapsed time in seconds and Maximum elapsed time in seconds for export are used to control the timeout of the transaction during the execution of the report definition and export to excel of the report definition respectively.

Note: Here if you set Maximum elapsed time in seconds=30 -> if the database is not giving the result in 30 seconds then it stop the transaction(by throwing the error). This is done from the Pega side and not the Database side, so nothing to do with the DB sessions. With these settings we are controlling the timeout of the query result by throwing exception after the specified time to stop the transaction.

Hope this answers your query.

Regards

Mahesh

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice