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 have some reports which are based on a new SQL reporting DB that updates at the top of every hour. We notice that our reports and dashboards seem to lock up and freeze during this time.
How could we fix this performance issue? Should we be using the SQL set command that enables "read uncommitted" in all our procedures in order to always read the database in a timely manner, regardless if it is in the process of updating?
Thank you,This message has been edited. Last edited by: Joey Sandoval,
Prod/Dev: WebFOCUS 8.0.08 on Windows Server 2008/Tomcat , WebFOCUS DevStudio 8.0.08 on Windows 7 Pro
Yes they are being locked. I received this message earlier today.
Microsoft SQL Native Client: [40001] Transaction (Process ID 75) was dea : dlocked on lock resources with another process and has been chosen as th : e deadlock victim. Rerun the transaction.
Waz, do you think this is solvable from the WF side? Or do you think our IT group would have to access the update schedule?
Prod/Dev: WebFOCUS 8.0.08 on Windows Server 2008/Tomcat , WebFOCUS DevStudio 8.0.08 on Windows 7 Pro
A deadlock error should really only occur if two transactions are trying to modify the same interdependent set of records in different orders. There's absolutely no reason to get a deadlock when you're only reading from a database (MS-SQL is a database based on the MVCC principle, so it should be able to deal with that situation gracefully).
Apparently your reports or dashboards are writing to the database and, apparently, to the same tables that the replication software is trying to update (is that master-slave replication, or master-master?).
Whether that's the intended scenario or whether that's desirable is up to you. I have to say though that I find it highly unusual that reporting software would attempt to modify data in a replicated DB.
That is how it should be according to theory. However, we're talking about a Microsoft product, so none of the above is necessarily true. It's also possible that the MSSQL adapter in WF is doing something it shouldn't.
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :
Oh, updating a table can lock it for read. No doubt about that.
Presumably you have a real need for data that is updated that frequently?
If that is the case you may want to put a table in the middle that you have more control over. Depending on size copying the table to an XFocus table (scheduled task running on the half-mark of each hour) that strictly supports your reports could be an option.
J.
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007