Focal Point
Issue while Distributing from the ReportCaster.

This topic can be found at:
https://forums.informationbuilders.com/eve/forums/a/tpc/f/7971057331/m/8321002752

November 14, 2007, 09:03 AM
<Navin>
Issue while Distributing from the ReportCaster.
Hi

I am experiencing an issue like ,

************************************************

FATAL ERROR IN DATABASE I/O. FOCUS TERMINATING ERROR WRITING FOCSORT

************************************************

Any idea when will this happen ?? and what might be the reason ??
November 14, 2007, 09:17 AM
GinnyJakes
Not enough disk space to write the focsort file. This goes in edatemp. Make sure you have enough disk space in edatemp.

Also, look at your fex to make sure you are not bringing back too much data to be sorted by WebFOCUS.

Just a couple of ideas since you didn't give any detail on the program.


Ginny
---------------------------------
Prod: WF 7.7.01 Dev: WF 7.6.9-11
Admin, MRE,self-service; adapters: Teradata, DB2, Oracle, SQL Server, Essbase, ESRI, FlexEnable, Google
November 14, 2007, 09:17 AM
Leah
quote:
Originally posted by Navin:
Hi

I am experiencing an issue like ,

************************************************

FATAL ERROR IN DATABASE I/O. FOCUS TERMINATING ERROR WRITING FOCSORT

************************************************

Any idea when will this happen ?? and what might be the reason ??



From the looks of it, it appears you are retrieving more data than the sort space can handle on your application server.


Leah
November 14, 2007, 09:36 AM
<Navin>
FOCSORT . . .

Ok i have 6k Records as an output in the Qry Fex . .
But before it outputs 6k records, the query will be processing more than 500000 records. . .

Is that FOCSORT fie responsible for capturing all these intermediate records ??
November 14, 2007, 11:17 AM
Darin Lee
Only processes them if they meet selection criteria. But if you have code inefficiencies like WHERE test on a DEFINEd field, you could be processing all 500000+ records and yes, they would all be in the FOCSORT file.

But the real problem is that you have insufficient disk space allocated for server temporary files (edatemp)


Regards,

Darin



In FOCUS since 1991
WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex
Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex
WF Client: 77 on Linux w/Tomcat
November 14, 2007, 11:30 AM
Francis Mariani
If you're accessing DBMS tables, check that efficient SQL is being generated - turn SQL traces on. As previously mentioned, you may be bringing down too much data - you should let the DBMS take care of most of the work and then bring down only the 6k rows you're interested in.


Francis


Give me code, or give me retirement. In FOCUS since 1991

Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server