[Answered]Is there a way to catch ERROR: MR_UNKNOWN_ERROR -12: Pcb2.: java.io.EOFExcp
Hello everyone,
I got an error message saying ERROR: MR_UNKNOWN_ERROR -12: Pcb2.: java.io.EOFException.
It happened when when expected number of output records is too big.
My question is: is there a way I can catch this error in fex code and then display a more graceful message?
I did a throught search on this forum. I found some good error-handling technique, for example using IF &FOCERRNUM NE 0 GOTO FATAL. But seems like this can't catch this exception.
I also found a solution from this forum using IF &LINE > 60000 GOTO display something. But our BA prefer not to use a hard-coded number like 60000 or anything else.
we use dashboard to show this report. I personally think it is impossible to catch this error. But because my experience is very limited. I am not so comfident to tell them that firmly.
Can someone please give me some idea about this?
Thanks
aluThis message has been edited. Last edited by: alu,
Errors of these kind originate in the servlets, which is actually part of the webserver. This is completely out of control of anything that happens in the reporting server. It is not something you can catch - there is just no way. The cause of it may be that the number of output records is too big, but can also be something else entirely. If the problem is indeed caused by the number of records, then you may want to consider using the webviewer option. This will present the output of the request on a page-by-page basis, thus never overloading the browser or servlets. The remainder of the report stays on the server untill called by the user. Check it out.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
July 13, 2009, 09:06 AM
dlogan
Most errors in 7.1x can be controlled by editing the following file: \ibi\client71\wfc\etc\enib00e.html
In 76x this is: c:\ibi\webfocus76\client\wfc\etc\ENtemplate.xml c:\ibi\webfocus76\client\wfc\etc\ENwebfoc_strings.lng
In this particular case, I could not find a reference that seemed like it was a good match with a quick search.
when i have encountered this error, its in generating an extract file from a gigantic oracle file, and when i changed the output to hold a FOCUS file rather than a foctemp, bingo, the error went away. so, if that's your situation, try ON TABLE HOLD AS MYFILE FORMAT XFOCUS rather than ON TABLE HOLD AS MYFILE
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
July 15, 2009, 01:33 PM
jbmuir
I think we have seen this error in cases where there have been too many USEs.
Try reducing your USEs to the minimum.
WF 7.1.6 moving to WF 7.7, Solaris 10, HTML,PDF,XL
July 15, 2009, 04:24 PM
alu
Hi everybody,
Thank you all for taking time to reply my question.
I think I got my perfect answer from GamP. Also, I will remember dlogan, susannah and jbmuir's suggestion for future reference.
We are in the process of upgrade from version 5.3. to version 7.6. But right now we are still in version 5.3. I tried using "FORMAT XFOCUS". But seems it did not work in 5.3.
Thanks... This is stuff that I didn't consider at this dept till now.
BTW: the "IF &LINE GT 60000 GOTO" (I used 65535) is probably for the limits of Excel. I used that to alter my output form from Excel to a CSV format...