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.
I am new to WebFOCUS, so please let me know if I am not using the proper jargon.
My boss wants to replace permanent hold files with database views in Oracle. I have been asked to research the pros and cons of this approach. Our hold files contain anywhere from a few hundred records to a few million records. So, I would appreciate any feedback that I can get.
Thanks. RajThis message has been edited. Last edited by: <Emily McAllister>,
So, the data is stored in .foc files on disk not in a DBMS like Oracle. You can back them up just like any disk file. No need to go through the DBMS backup and restore procedure. They are also much easier to transport from one directory to another. The advantage of putting these extracts in a DBMS is that they'll be a part of back up process and you won't need to deal with them separately. FOCUS hold files may also have a little less overhead in processing because you don't have the DBMS involved. That might not necessarily be noticeable. The main question is why does your boss wants this done? Does your boss think there's a specific benefit?
WebFOCUS 8206, Unix, Windows
Posts: 1853 | Location: New York City | Registered: December 30, 2015
One of the reasons is that we have had numerous issues in the past few months where the permanent hold files would not get refreshed and we would end up with old/no data.
But I think the main reason is that we are trying to refactor our datamart and properly stage the data we need at he database level. So, if we are doing all this work at the database level, my boss wants to know why we need to maintain datasets both in our datamart (as views) and as permanent hold files.
That's a very good reason. Usually, these hold files are used for quick caching of data or transformation of data that's hard to report from. I've also seen very complex code that almost functions like ETL which ends up putting the answer set in a hold file for reporting. If you are creating a dimensional model and going through the process of creating a DM, then it makes sense to eliminate the hold files so you only have a single source of the truth but still utilize hold files when they make reporting convenient.
WebFOCUS 8206, Unix, Windows
Posts: 1853 | Location: New York City | Registered: December 30, 2015