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 receive the following error when executing a procedure that utilizes the SQL Wizard.
(FOC1400) SQLCODE IS 24373 (HEX: 00005F35) : ORA-24373: invalid length specified for statement L (FOC1405) SQL PREPARE ERROR. 0 ERROR AT OR NEAR LINE 290 IN PROCEDURE fdas5owvFOCEXEC * (FOC205) THE DESCRIPTION CANNOT BE FOUND FOR FILE NAMED: SQLOUT BYPASSING TO END OF COMMAND
When using SQL Navigator expected results are produced (i.e. I recieve no error). Does anyone know if there's a restriction on the size of a SQL query embedded into a procedue via the SQL Wizard? Or what exactly happens when WebFocus sends the code to the database?
My code does not include any case statements, the statements are mostly aggregation functions and datatype conversions.
Due to my company's security restrictions I cannot send the actual code however I could mock up the code with fictious tables and columns though. Would that yield something you could diagnose?
Also, after some additional research I was able to narrow down to a range of characters (space not included) in a query that produced results versus throwing the above error. I found this by replicating the same exact query using unions. This leads me to believe there is a character limit somewhere?
Check out this document that gives info on the SQL supported. However, bear in mind that it does not cover SQL passthru.
I am not sure how long you have been using WF, but most folks find that resorting to SQL passthru provides many benefits, the most important being that WF does not change your SQL and only the target (Oracle in your case) SQL interpreter has to be satisfied.
T
In FOCUS since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
WebFOCUS App Studio 8.2.06 standalone on Windows 10
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004
We use DB2 and dynamically build most of our SQL statements based on parameter values. There is a limit to the size of the SQL statement we can pass (about 64kb)through the SQL Engine in WF. Some of our longer queries, have had to be rewritten using 2 or 3 charater aliases, rather than the full table names. I don't know if this is what you are running into or not, but if the query is lengthy, try shortening it using aliases.
WF 7.6.10 / WIN-AIX
Posts: 141 | Location: Denver, CO | Registered: December 09, 2005