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.
[CLOSED] A column name in the select statement was longer than 64. Hello,
I am getting the error: "(FOC36395) TITLE IS TOO LONG - LIMIT IS 64 CHARACTERS BYPASSING TO END OF COMMAND"
when trying to invoke an Oracle stored procedure as follows: ENGINE SQLORA SET DEFAULT_CONNECTION fbctd4_c3dbo2 SQL SQLORA EX C3DBO2.PKG_WEBFOCUS_PROCESSES.PRC_C5A_WKLY_RANK_DATA '%','17-jul-09';
TABLE FILE SQLOUT PRINT * END -RUN
The issue is not the length of the procedure call itself, since I can execute a different Proc with a longer name in the same database. Any information will be appreciated. Thanks.This message has been edited. Last edited by: Kerry,
I don't think that the error you're getting has anything to do with the length of the procedure call itself but instead with the TITLE's length (in this case an Oracle column's name) in any of the columns being retrieved by your procedure.
Is your stored procedure returning a REF CURSOR? if so, do you have anything in the internal SQL query that is producing a column name longer than 64 characters? That usually happens if you have "virtual" columns in SQL as a result of function calls and WITHOUT an alias.
If you can post the internal SELECT statement that feeds the REF CURSOR inside of the PL/SQL procedure we might be able to spot something there.