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.
What database are you writing reports for? Oracle, SQL, SFDC?
What version of everything?
More details about the type of reports you're trying to optimize would be very helpful. If you're using relational dbms, you might want to search for Optimization in the doc.
WebFOCUS 8206, Unix, Windows
Posts: 1853 | Location: New York City | Registered: December 30, 2015
My suggestion would be to start by looking at the SQL generated. Here is some code that can help you do that.
SET TRACEOFF=ALL
SET TRACEON=SQLDI
SET TRACEON=SQLCALL
SET TRACEON=SQLAGGR//CLIENT
SET TRACEON=STMTRACE//CLIENT
SET TRACEON=STMTRACE/2/CLIENT
SET TRACEUSER=ON
SET TRACESTAMP=OFF
-* XRETRIEVAL defines whether you want the SQL to be passed to the DBMS or not. Uncomment the below set command if you don't want the query to run
-* and only want to see what would be generated
-* SET XRETRIEVAL=OFF
If this isn't written efficiently you will need to look at the errors listed as to why and adjust accordingly. If the SQL looks correct, then you will want to look at the possibility of Indexes in your database or performance tuning your tables.
As Babak mentions, without more direction there isn't much more we can suggest.
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, 2013
After that it is tuning things within WebFocus. Simple things that deal with the internal matrix. For instance if you have 500 fields don't make 499 of them BY fields while printing one. That means it has to sort the Matrix 499 times. But again, more info is needed.
WebFOCUS 7.7.05 (Someday 8) Windows 7, All Outputs In Focus since 1983.