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.
We've got a serious problem. Our application urgently needs Xfocus and FDS together with Maintain. Unfortunately the agent crashes unless we SET COMMIT=OFF in the edasprof.prf. That will cause the FDS to quit setting the variables foccurrent,focerror and focerrnum. Is there a fix for this? We're currently on 7.6.4 on a W2003 Server.
Tia HåkanThis message has been edited. Last edited by: Håkan,
I know you are working with Customer Support, but please check out this discussion and make sure you have the FDS configured properly. The agent should not crash.
Mark, the thing about this is that the FDS have been running for some 8 years now, starting with 3.3.1 or a similar release and has been working all the time, and is still working with normal Focus db's. It's only with Xfocus it crashes. I made a search on COMMIT on Tech Support and there has been a problem with COMMIT and Xfocus in the SU environment that was supposed to be fixed in 7.6.2. Maybe a revision problem?
I just identified a project that is in 7.65 (Pno 85575). I asked the consultant working on your case to check into it. "XFC shadow/commit support needed for XFOCUS d/b" That could be the issue.
Mark
Posts: 663 | Location: New York | Registered: May 08, 2003
It seems that Resource Analyzer monitoring everything was the root of all evil. When we reduced monitoring to Query only it all seems to be working fine.