Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] Spurious FOC2591?

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[SOLVED] Spurious FOC2591?
 Login/Join
 
j.gross
Virtuoso
posted
I am getting
 FOC2590 - AGGREGATION NOT DONE FOR THE FOLLOWING REASON:
 FOC2591 - AVE ON ALPHA, DATE OR DATETIME CANNOT BE AGGREGATED

on a TABLE request against Oracle. There's no AVE. anywhere in the code.

Running on Release 7.6.10.

Has anyone else encountered this sitution? Any idea what may actually be the cause for the FOC2590/91 message pair?

This message has been edited. Last edited by: <Kathryn Henning>,


- Jack Gross
WF through 8.1.05
 
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005Report This Post
Francis Mariani
Expert
posted Hide Post
You might need to add a "MIN." on all alpha and date columns that are not in the BY statements...


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
 
Posts: 10577 | Location: Toronto, Ontario, Canada | Registered: April 27, 2005Report This Post
eric.woerle
Master
posted Hide Post
Just a thought... but is there an average applied to a field in the Metadata of which you are using in the report?


Eric Woerle
8.1.05M Gen 913- Reporting Server Unix
8.1.05 Client Unix
Oracle 11.2.0.2
 
Posts: 750 | Location: Warrenville, IL | Registered: January 08, 2013Report This Post
Waz
Expert
posted Hide Post
I agree with Francis.

Add a MAX or MIN to the alpha fields.

My assumption is that you have a SUM against several field and at least one of them is an alpha.

WebFOCUS is attempting to generate SQL to send to oracle and it doesn't know what to do with these fields.


Waz...

Prod:WebFOCUS 7.6.10/8.1.04Upgrade:WebFOCUS 8.2.07OS:LinuxOutputs:HTML, PDF, Excel, PPT
In Focus since 1984
Pity the lost knowledge of an old programmer!

 
Posts: 6347 | Location: 33°49'23.0"S, 151°11'41.0"E | Registered: October 31, 2006Report This Post
j.gross
Virtuoso
posted Hide Post
Imagine that. WF knows that the Last (LST.) operator runs counter to Mr Date's world, so it considers generating Average, and then issues a complaint against that attempt.

Actually, in principle dates can be averaged (in terms of the date-offset, just like any other integer variable). But why would one even consider doing so, if the implicit data-reduction operation in WF is to take the final (LST.) value?

I have to locate which report was generating that warning; will report back.
 
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005Report This Post
Doug
Expert
posted Hide Post
Jack, Consider adding the SQL Trace code to see if there really is an "AVE" in there someplace. Other then that, I think that FOC2591 is a generic message, making the Spurious message irrelevent.
SET XRETRIEVAL = ON
SET TRACEON = STMTRACE//CLIENT ;
SET TRACEUSER = CLIENT ;

"? 2591" Generates this:
(FOC2591) AVE ON ALPHA, DATE OR DATETIME CANNOT BE AGGREGATED
Aggregation was disabled due to the use of a AVE. operator
on an alpha, date or datetime field. These FOCUS operations do
not have counterparts in the RDBMS, therefore FOCUS must perform
this processing on the answer set.
 
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005Report This Post
j.gross
Virtuoso
posted Hide Post
It was SUM of an alpha field that triggered the message. It's a defined field, whose value is determined by the report's sort fields -- so MIN. would work; or switching from Define to Compute, which would avoid stuffing the (lengthy) Define logic into the generated SQL.
 
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] Spurious FOC2591?

Copyright © 1996-2020 Information Builders