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.
A WebFOCUS TABLE request against some DB2 tables takes 20 minutes. I have traced the SQL and there are no inefficiencies and no error/warning messages. If I run the SQL generated by WebFOCUS in a DB2 client, it takes about 2.5 minutes. The result is 26 lines.
What could be the reason for the large discrepancy in execution time?
Thanks,
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
Do you have the ability to run a DB2EXPLAIN against the code? That should help identify the process to see if it's doing a tablespace scan or utilising indices.
TThis message has been edited. Last edited by: Tony A,
In FOCUS since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
WebFOCUS App Studio 8.2.06 standalone on Windows 10
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004
Tony, I've never run a DB2EXPLAIN - I'll check to see if we can here.
Meanwhile, I thought I would use SQL pass-through with the SQL that was generated by WebFOCUS and was run in the DB2 client - well it's taking 20 minutes instead of 2.
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
If you can not run it then your DB2 DBAs should be able to. They should also be able to help you interpret the output. It's been a while since I last ran the util although I seem to remember that I ran it using SQL passthru.
Good luck
T
In FOCUS since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
WebFOCUS App Studio 8.2.06 standalone on Windows 10
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004
Sometimes the DB2 prioritization can effect runtime. If WebFocus is setup with a very low priority in the DB2 system and the sql tool has higher authority, then WebFocus runs much slower. It's a matter of who's getting first shot at the DB2 resources and who's getting pushed down the line.
It sounds like you are taking the same query and running it from two different places. If this is correct, they should be hitting the same indexes and executing the same way. It seems like there's an issue with either how DB2 is handling the request or an issue with getting the request to DB2.
I am beginning to wonder about DB2 prioritization. I've sent an email to the DBA, but I'll probably be waiting a long while for a response, while three or five forms get filled and authorized before he can talk to me!
Thank you,
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
You can quickly check if its the connection priority eg wf vs spufi (assume you used this) by overriding the default db2 connection string with the string you're using to connect to db2 via spufi.
Assuming xyz is your connection in your .acx or access files
ENGINE DB2 SET CONNECTION_ATTRIBUTES xyz/spufiuserid,spufipassword
-* just to be safe ENGINE DB2 SET DEFAULT_CONNECTION xyz
Now try your fex.
John
John
Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2 Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo
Posts: 888 | Location: Airstrip One | Registered: October 06, 2006
One other thing to try in AQT could be running the job in batch (if option available) as this would give it a much lower MVS priority and thus might match the wf performance.
Always intrigued by these sorts of problem...
Regards
John
Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2 Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo
Posts: 888 | Location: Airstrip One | Registered: October 06, 2006