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     Memory Issues - Desktop/Server

Read-Only Read-Only Topic
Go
Search
Notify
Tools
Memory Issues - Desktop/Server
 Login/Join
 
gw2006
Member
posted
We have an 81 line compound report generated by 81 focexecs. Sometimes the report runs all the way through, and sometimes it stops halfway. If we wait long enough we get a message that says, " No Query Data to Decode" and the part of the report that was displayed goes away. A view source of one of the partial report results usually shows only part of the &ECHO... (ie. the report goes to line 75 but the ECHO stops at fex 64..etc.)

In addition we have a report that runs fine when the reclimit is set to 10k, but when the reclimit is set to 50k the report gets a page not displayed error when running EXL2K, and when running HTML it never returns but uses over 2GB of virtual memory on the desktop paging file.

Are there any server settings or client side settings that can be changed to help solve this issue? It almost appears as if there is not enough memory on the client side to process.
 
Posts: 6 | Registered: June 07, 2006Report This Post
Kerry
Expert
posted Hide Post
Hi gw2006,

Has this issue been resolved on your side?

I ran some search on Information Builders' online documents and came to the understanding that this issue should be reported to Information Builders' Customer Support Services for further debugging. The phone number is 1-800-736-6130, or you may access the online system InfoResponse at http://techsupport.ibi.com. Here is a list of information to be ready when you call: http://techsupport.ibi.com/before_you_call.jsp.

Hope this helps. Big Grin

Cheers,

Kerry


Kerry Zhan
Focal Point Moderator
Information Builders, Inc.
 
Posts: 1948 | Location: New York | Registered: November 16, 2004Report This Post
gw2006
Member
posted Hide Post
We actually are using a workaround. We are going to chunk out the reports into smaller groups. Not what we wanted to do but unfortunately we currently didn't have the time to continue to research.

Thanks for the assistance.
 
Posts: 6 | Registered: June 07, 2006Report 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     Memory Issues - Desktop/Server

Copyright © 1996-2020 Information Builders