Focal Point Banner


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.



Read-Only Read-Only Topic
Go
Search
Notify
Tools
FOC1426
 Login/Join
 
Håkan
Guru
posted
I'm trying to output 2 BLOBs in a report. I've succesfully made 1 to display, but when I'm trying with 2 WF returns the following message:

(FOC1426) DATA ELEMENT VALUE TOO BIG FOR SEGMENT/FIELD segname/fieldname
An error occurred when converting a data item for the field in the
segment with the names given in the message. Data could not be
converted without truncation from the USAGE to the ACTUAL format.
FOCERROR is posted to 1426.

Anyone has experincied this?

WF 7.6.10, SQL Server 2005, W2003


WebFOCUS DS 8.0.06/08 DS/AS
WebFOCUS RS 8.0.08 (Linux/IBM i)
WebFOCUS Client 8.0.06 (Linux)
 
Posts: 319 | Location: Stockholm, Sweden | Registered: February 04, 2004Report This Post
j.gross
Virtuoso
posted Hide Post
I believe this relates to the internal data structure (the "internal matrix") that TABLE defines and loads in order to build the report. That structure is (or at least used to be) none other than a Focus file. It follows that TABLE requests are subject to a segment size limit of 4096 bytes. (Perhaps Table now uses Xfocus for the internal matrix, but that still would impose a limit of 16k.)

There was a feature added not long ago, to place fields in a U segment where necessary to avoid overflowing the segment-size limit. That feature pertains to HOLD FORMAT FOCUS. But the same considerations apply to the internal matrix, and the same solution should be available.

I would open a case.


- Jack Gross
WF through 8.1.05
 
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005Report This Post
Tony A
Expert
posted Hide Post
Hakan,

Just a quick thought and completely out of the air -

If the problem might be what Jack is suggesting, could you use passthru ensuring that the data is in the sort order required for the report and then use TABLEF so that the internal matrix is not used?

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, 2004Report This Post
Håkan
Guru
posted Hide Post
Jack and Tony,
good ideas, but none of them helped. We had to stick to 1 BLOB. I suppose you could make something clever reading the SQL table once again and then create another url in the report, but imagine the performance........

Håkan

This message has been edited. Last edited by: Håkan,


WebFOCUS DS 8.0.06/08 DS/AS
WebFOCUS RS 8.0.08 (Linux/IBM i)
WebFOCUS Client 8.0.06 (Linux)
 
Posts: 319 | Location: Stockholm, Sweden | Registered: February 04, 2004Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic


Copyright © 1996-2020 Information Builders