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 wanted to create a report based on a stored procedure at a Sybase Database
Creating the synonym gives me this error:
(FOC1400) SQLCODE IS 7713 (HEX: 00001E21)
: Stored procedure 'fmc_pages.dbo.p_brokers' may be run only in unchained transaction mode.
The 'SET CHAINED OFF' command will cause the current session to use unchained transaction mode.
(FOC1405) SQL PREPARE ERROR.
I wonder if anybody knows what this is and how I can solve the problem.This message has been edited. Last edited by: FrankDutch,
Frank
prod: WF 7.6.10 platform Windows, databases: msSQL2000, msSQL2005, RMS, Oracle, Sybase,IE7 test: WF 7.6.10 on the same platform and databases,IE7
Posts: 2387 | Location: Amsterdam, the Netherlands | Registered: December 03, 2006
If your login has the proper roll you could execute SET CHAINED OFF
just prior to executing your stored procedure. My guess is that you don't. Altering the procedure can be a way around.
You are left with only one alternative. You MUST execute the stored procedure from within a transaction. That is what the error message is so poorly trying to tell you. You can do one of two things. 1) Set auto Commit to true. This will allow the stored proc to execute without this error message. 2) start a transaction prior to executing the stored proc and commit when complete.
WebFocus 7.6.5 AND WebLogic server as web server sql2005 as database server
Posts: 273 | Location: Europe | Registered: May 31, 2007