Anyone ever see this error

[robert fuschetto]

 

 

I run a fex and it pops up.  There are several prompts and a bunch of chaining.  It seems to occur when I select certain periods and run for ALL data...later periods in particular. It could be hashing through over a million rows of data..but never an issue before. This is a new fex though.  We have been having issues not only with WF but SSMS and MsAcess with data being returned timely and timing out...just curious if this error might be indicating something similar. I am going to rebuild the fex and try again in the mean time.

 

[David Briars]

Can you do a 'View Page Source' on your HTML report, in the browser, under the condition when it does run (smaller number of records read/processed)?

Go to the bottom and check to see if you see any system messages. 

I once had a focexec that created a system warning message for every record read/processed.  At very high volumes the agent would crash because of too many messages filling a buffer.  

  

 

  

[David Beagan]

I don't recall seeing that specific error before. But it is probably functionally equivalent to a message like "Something Went Wrong."

Perhaps a good starting point in trying to diagnose this is to do some SQL tracing.  Put these at the top of the fex:

 SET XRETRIEVAL=OFF,EMPTYREPORT=OFF
 SET TRACEOFF=ALL,TRACEON=STMTRACE//CLIENT,TRACEUSER=ON,TRACESTAMP=OFF

Then when you run with the criteria that had produced the error. Hopefully with the XRETRIEVAL=OFF (to suppress WebFOCUS actually pulling data), you might see other errors or clues in the SQL generated. 

In the SQL statement(s) start by looking at the number of select statements. If more than one select, or more that should be expected, need to find out why. 

Edited November 14 by David Beagan

[Patrick Huebgen]

Check Event.log for ERRORS and Share what you see.

if you have auto drill enabled -lease disable and retry.

[robert fuschetto]

Well, I narrowed it down to a fex which when run outside of the HTML page yielded the same error.  I had a dozen BY LOWEST lines...it seems eliminating one (no one in particular as I recall) resolved the issue.  No idea why that would cause an error....can only process so many...?

[David Beagan]

Good debug work. I've seen 20 or more BYs. There is probably more than just that BY that is the issue.

[robert fuschetto]

suggestions?

 

[David Beagan]

You can concatenate BY fields to reduce the total number of BY fields: 

SET BYDISPLAY=ON,PAGE=NOLEAD

TABLE FILE GGSALES
"Three BY fields"
SUM 
    UNITS 
    DOLLARS
 BY REGION
 BY ST
 BY CITY
END

DEFINE FILE GGSALES
STCITY/A30 = ST | CITY;
END

TABLE FILE GGSALES
"Two BY fields"
SUM ST
    CITY
    UNITS 
    DOLLARS
 BY REGION
 BY STCITY NOPRINT
END

 

[Patrick Huebgen]

@robert fuschetto did you tried to test with

WHERE REORDLIMIT EQ 1000  

just to see if the volume of data is causing a problem - I need to check but the limitation of number of BY fields is higher then 20 could be an issues with volume of data