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.
All developer gurus - we have WF 7.7.02 on Windows 2003 32bit OS. We have Oracle 11gR2 databases being queried by a mixture of WF self service and MRE/BID programs. Some queries are using SQL passthru, some are using FOCUS code with HOLD files, many queries are hitting Oracle views, we currently have no materialized views. We have recently added Indexes to several of the Oracle tables in the hopes to speed up some of the slower processing programs. We have been disappointed by this effort as the difference is barely noticeable.
We have heard the way Oracle 11g processes queries is very different from how the same query was processed in Oracle 9 and Oracle 10.
Do any of you have any tips or techniques we could try to better optimize our WF queries?
Tnx, PLThis message has been edited. Last edited by: Kerry,
You might try these commands to see if they help. If they do improve performance, they can be added to your system profile (edasprof.prf) so they are invoked for every user.
ENGINE SQLORA SET FETCHSIZE 5000
ENGINE SQLORA SET OPTIMIZATION ON
Also, IBI Tech Support does have some Oracle expertise, so it might be worthwhile to open a case and pose your question to them.
Finally, have you turned on SQL trace for your slow FOCUS queries in order to evaluate the SQL code being passed to Oracle? Sometimes the problem is in the FOCUS code and not the RDBMS.This message has been edited. Last edited by: Dan Satchell,
WebFOCUS 7.7.05
Posts: 1213 | Location: Seattle, Washington - USA | Registered: October 22, 2007
Hello Dan. Thanks for the suggestion; however these two settings did not appear to make any difference. I had another developer try the settings and he found the same. His comments follow. +++++++comments begin +++++++++++++ I added the 2 settings to a fex that was written in FOCUS code and it had no effect. Since our users primarily write FOCUS code against our reporting views, we are going to try and set this setting in Oracle to see if this helps:
Optimizer_secure_view_merging = FALSE
We are also going to get some EXPLAIN PLANS from Oracle 9i and Oracle 11g to see if we can find why certain queries are running so slow. ++++++Comments end +++++++++++++ I will update with the results in case anyone else has similar issues with Oracle 11g2
Francis thanks for the response. Some of the code is SQL passthru and is optimized for Oracle. We did capture the SQL code for the FOCUS code generated by MRE users and tested in both TOAD and SQL Developer. For some of the SQL we found code that ran efficiently in Oracle 9i does not run efficiently in Oracle 11g. It is my understanding the way the cursor is managed in Oracle 11g is different from Oracle 9i. I do not think the issue is with WF because we see the same decrease in efficiency when we run in TOAD and/or SQL Developer. I was just hoping someone in this forum would have seen a similar change after moving to Oracle 11g. Our Oracle DBA's continue to try to say the fault lies with WF, and I keep providing them with additional evidence it is differences in the Oracle RDBMS.