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.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     FEX returns : "Invalid Root Page" for each record

Read-Only Read-Only Topic
Go
Search
Notify
Tools
FEX returns : "Invalid Root Page" for each record
 Login/Join
 
<NorthNone>
posted
Thanks for taking time to read this.
I'm getting an "Invalid Root Page" for each record when I run the related FEX. There are 1111 records, so "Invalid Root Page" prints on each of 1111 rows on the screen each time I run this FEX.
Is it the '/' in the literals?
Is it the WHERE statement?
I am about to pull my last hair out of what's left of my head. Help GRATEFULLY acknowledged.
NorthNone

--partial code where this happens - converting from old FOCUS to WebFOCUS--
-----------------------
TABLE FILE FRISEXPI
IF FUND2 NE 94
WHERE GRCN_TOTAL GE 1 OR GRCN_TOTAL LE -1
SUM
GRCN_DIRECT AS 'Grants/Con,Direct Exp'
GRCN_INDIRECT AS 'Grants/Con,Indirect Exp'
GRCN_TOTAL AS 'Grants/Con,Total'
BY SHORT_NAME SUBTOTAL MULTILINES AS 'TOTAL'
BY SPURPOSE AS 'PURPOSE' SUBTOTAL MULTILINES AS 'TOTAL'
BY ACTV_CODE AS 'ACTV,CODE'
BY Y2K_FY_A4 AS 'FY'
BY DEPT
BY FUND
BY Y2K_PFNDTO
...............etc., etc., etc...
 
Report This Post
Leah
Virtuoso
posted Hide Post
Must be something else related to the file definition, as

TABLE FILE CAR
PRINT COUNTRY AS 'A/COUNTRY'
MODEL
END

works just fine.
 
Posts: 1317 | Location: Council Bluffs, IA | Registered: May 24, 2004Report This Post
susannah
Expert
posted Hide Post
I have experienced invalid root page errors when i have joins that are insane. Once i clear up my joins and get them corrected, the irp errors go away.
I find it best with an error like this to start small and rebuild my fex bit by bit until it breaks.
 
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003Report This Post
<NorthNone>
posted
Thanks for the troubleshooting idea - this is a fex called by another fex, so instead of rebuilding it, I am commenting portions out until it works, then putting them back in. I thought I had it nailed, but the )(#$&#$ slipped out of my grasp at the last minute by working when I expected it to break.
If I ever figure it out, I will be SURE to post it here.
 
Report This Post
<WFUser>
posted
Is this a FOCUS database? Could be corrupted. try ? FILE.
 
Report This Post
<NorthNone>
posted
Smiler THANKS TO ALL! Here's the bottom line: Turns out the problem was with two fields that should have been a result of the join, but were not there. If I commented out references to those two fields, I would not get the Invalid Root Page error. But if they were referenced in some way, the IRP error would return.
The solution was to make all the files involved in the join into FOCUS files. Some had been FOCTEMP (FTM) files. That fixed the join, resulting in the two problem fields "SPURPOSE AS 'PURPOSE'" and "ACTV_CODE AS 'ACTV,CODE'" then being present in the join. Once they were present, references to those fields no longer gave an IRP error.
Apparently there can be a problem(?) with FOCTEMP (FTM) files not having reliable end of record or end of file markers??? and that FOCUS files are more reliable.
WHEW!! Appreciate the help MUCHLY!!!
 
Report This Post
Bethany
Platinum Member
posted Hide Post
I'm coming up with an INVALID ROOT PAGE error. I don't have any old FOCUS files involved. And when I copied the fex file from one domain to a new one, the report ran with NO IRP errors. Any idea what gives?

-Bethany
DevStudio 7.1.4


Server Environment: Win2K3 Server WebFOCUS 7.13 Apache Tomcat standalone application server
 
Posts: 188 | Registered: April 14, 2005Report This Post
OPALTOSH
Platinum Member
posted Hide Post
Betahny,
Do you have any JOINS in the request? If so please check that all your JOIN fields have matching formats and lengths.
 
Posts: 140 | Location: Adelaide South Australia | Registered: October 27, 2006Report This Post
Bethany
Platinum Member
posted Hide Post
I don't have any joins, but I was using an SQL statement with the where clause "WHERE ITEM_EMPLID IN (SELECT CTERM_EMPLID FROM HFILE)". I checked that the format of ITEM_EMPLID and CTERM_EMPLID were the same, both A11. And that code worked perfectly in a different domain.


Server Environment: Win2K3 Server WebFOCUS 7.13 Apache Tomcat standalone application server
 
Posts: 188 | Registered: April 14, 2005Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     FEX returns : &quot;Invalid Root Page&quot; for each record

Copyright © 1996-2020 Information Builders