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.
Hi All, We are getting an issue often when running report from WF to Oracle 10g RAC server. Sometime it works and sometimes not. we checked the Data Adapter,but its fine. Anyone encountered a similar issue before? Please help.
If you have an explicit connection to Oracle, determine if the RDBM's allow for concurrent connections.
The other, which I would suspect you would've received a FOC1400, FOC15xx, FOC15xx for should give you an idea as to the type of message.
If security is on, i would have to believe that the user id that was running the request may not have access to the SQL*NET thus the driver never loaded for that agent.
if that's not the case, you may want to post the error that they get.
Thanks for the update. we found out why it was happening.
The issue was that since it was a RAC server and there were two instances defined in tnsnames file, at runtime it would pick any of the instance randomly. The second instance was down, so whenever the request was refering to the second instance it used to fail.