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, I have database upgradation to UTF8. After the upgradation,I am getting below error in one focus file: (FOC098) LIMIT FOR TOTAL LENGTH OF ALL VERB OBJECTS EXCEEDED In the focus file we are reading some fields from one database table and holding it in some file. If I remove some of the columns from the list..it works. But I need to fetceh all the columns... Can you please help us here?This message has been edited. Last edited by: Kerry,
Found this statement from tech support's advanced search IB Tech Support:
quote:
Unfortunately this is a known problem with UTF8.
There is a limit on the length of all verb objects of 32k bytes.
With UTF8, the reporting server switches into character semantics mode, and every character is represented by 3 bytes, instead of one.
So, say you have an A4000VB field, and you do a CHECK FILE on it, you'll see that it actually has a total length of about 12000 bytes. This means that by even using two fields of this length, you're already at the 32k limit. 3*12000=36k and the FOC098 will occur.
This limit is to be lifted in release 7.7.0.
I'm now connecting your case with the original problem report, and you will be notified when the new release is available.
Instead of regular TABLE request. Try to pull the data using SQL Passthru. Don't know if this will work or not but its a different approach to pulling the data from the database.
Another thing you could try is to do multiple data pulls and join the data. If your table has a primary key I would use that to link the hold files. If not create your own key using a define or computed field.
TABLE FILE DATA
PRINT
FIELD1
FIELD2
FIELD3
FIELD4
BY PRIMARY_KEY
ON TABLE HOLD AS H1 FORMAT XFOCUS INDEX PRIMARY_KEY
END
-RUN
TABLE FILE DATA
PRINT
FIELD5
FIELD6
FIELD7
FIELD8
BY PRIMARY_KEY
ON TABLE HOLD AS H2 FORMAT XFOCUS INDEX PRIMARY_KEY
END
-RUN
TABLE FILE DATA
PRINT
FIELD9
FIELD10
FIELD11
FIELD12
BY PRIMARY_KEY
ON TABLE HOLD AS H3 FORMAT XFOCUS INDEX PRIMARY_KEY
END
-RUN
JOIN PRIMARY_KEY IN H1 TO PRIMARY_KEY IN H2 AS J1
JOIN PRIMARY_KEY IN H1 TO PRIMARY_KEY IN H3 AS J2
-RUN
TABLE FILE H1
PRINT
FIELD1
FIELD2
FIELD3
FIELD4
FIELD5
FIELD6
FIELD7
FIELD8
FIELD9
FIELD10
FIELD11
FIELD12
ON TABLE HOLD AS HRPTDATA
END