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.
Has anyone using a 'read only' data warehouse bound their Focus 7.2 plan with an isolation level of UR or uncommitted read? If so, did you see any negative impacts to this? We certain that there would be fewer locks being taken if we make the switch.
We are currently using CS.
Posts: 6 | Location: Grand Rapids, MI | Registered: April 25, 2003
Spoke to a product manager and here was the response: An Isolation Level of UR is the equivalent of a "dirty read". There are no locks taken on the object and this is ideal for read only applications that operate in an environment where the data is not volatile (not changed often), or in applications that can tolerate the possibility of data being changed even while it is being read. Reading data that may not be accurate is the down side.