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 had a problem where reports was scheduled in reportcaster. It did show up in the admin and schedule tool but they just did not want to run. I did do a check file on all the focus db's of reportcaster as well as a reorg and table file print *. Non of these reported errors.
After I created new reportcaster db's it was fine again. (lost al schedules jobs, again).
Is there a better way to check the focus db's?
Thank you Phillip du PlooyThis message has been edited. Last edited by: Kerry,
The next time this happens, turn the RC traces on to see what is going on and/or open a case with IBI before you remove everything.
It may be that you are out of space or the data bases need rebuilding.
Don't use a sledge hammer to resolve the problem when a fly swatter might do. I feel very badly that you lost all of your work. Does this happen often?
It's very unlikey that anything other than the log files are the issue.
Except as Ginny suggests space (but they may be the cause of that issue).
I would first backup the log databases and recreate just them and see if that resolves the problem.
As an ideal if you can switch from Focus DBs to SQL based that may well resolve the issue, seeing your profile you have both Oracle and MSSQL available.