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 email@example.com for further assistance. Reference the community FAQ to learn more about the community.
I just encountered this error for the first time on a regularly scheduled report. If this happens again, I'd like to automatically re-attempt running the fex a few times as described above, but I can't find "Number of attempts" and "Restart from" in the list of fex properties. Are these properties still configurable, and if so, where?
Edit: added signatureThis message has been edited. Last edited by: sarahe,
This is with WebFOCUS - rereading the original post I see that the previous discussion was specific to DataMigrator. Is there similar setting in ReportCaster or WebFOCUS that I could use?
Setup is that I have a WebFOCUS report that is scheduled to run hourly with ReportCaster, and for the first time ever it failed with this error. It ran perfectly the next hour with no modifications. If possible, I'd like to try setting the report to re-attempt one or two times on error.
I believe this tells WebFOCUS to open the file as Read Only an you can avoid these locks.
We've been reporting off Oracle using the FOCUS language for almost 25 years, long before there was WebFOCUS, and we have never had locks and we have jobs that run every 10 minutes, 24/7, in Report Caster.
In FOCUS since 1985. Prod WF 8.0.08 (z90/Suse Linux) DB (Oracle 11g), Self Serv, Report Caster, WebServer Intel/Linux.
Posts: 975 | Location: Oklahoma City | Registered: October 27, 2006
ReportCaster does not have the ability to restart if there is an error. On the reporting server console if your fex resides in an application folder there is a separate scheduler but I don't see any flags to re-run if it encounters an error. I think it may be worth opening a case with techsupport to see if there is a way with the reporting server scheduler.
PS. I agree with John's suggestion on WRITE=NO.This message has been edited. Last edited by: FP Mod Chuck,
Thank you for using Focal Point!
Chuck Wolff - Focal Point Moderator WebFOCUS 7x and 8x, Windows, Linux All output Formats
Posts: 2127 | Location: Customer Support | Registered: April 12, 2005
Thank you both! I opened a ticket with tech support and they confirmed that in ReportCaster there is no option to have the schedule execute again on error. I'll give John's suggestion of the WRITE parameter in the .acx a go in our dev environment.