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.
This may be more of a database management question than a WebFOCUS question but since I'm trying to see if I can solve the issue with a WebFOCUS Managed Join I thought I'd post it here. This message has been edited. Last edited by: Dan Pinault,
7.7.05M/7.7.03 HF6 on Windows Server 2003 SP2 output to whatever is required.
Posts: 393 | Location: St. Paul, MN | Registered: November 06, 2007
seems odd, Dan Does your OEM_INFO dimtable have more than 1 row for each OEM_ID? (double check this) You say that only join to the OEM INFO table causes the multiple records, yes? Do you have JOIN ... TO UNIQUE OEM_ID IN OEM_INFO
you're doing the joins inside the master, yes? What about taking them out of the master, and doing them in join statements until you can nail this sucker down...
ps..really nice problem layout technique, by the way.
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003
Thanks Susannah. Yes, it is possible that a BaseModel is built by more than one OEM. I thought about that after I created the example but I didn't want to go back and change it (lazy). I guess a better example would have been to say that as soon as there are multiple instances of BASE_MOD_ID I get the Multiplicative Effect. So, just doing...
SUM R_QTY
BY R_COUNTRY
BY PROD_YEAR
would cause the problem.
Yes, the joins are being created in the synonym. I added the segments via metadata import so the PK/FK relationship would be recognized. I'll try doing the joins in a procedure and see what happens.
Finally, I tried creating a bridge table between the Base Model Table and Registration Table that consists of existing distinct combinations of BASE_MOD_ID and REG_ID. I guess that isn't doing anything for me that I didn't have set up in the original structure.
Stay tuned...
7.7.05M/7.7.03 HF6 on Windows Server 2003 SP2 output to whatever is required.
Posts: 393 | Location: St. Paul, MN | Registered: November 06, 2007
Well, I need to move on. It's either that or pull my hair out!
I've got to give a demo of this particular application in 2 days and there is a lot of work to do on the launch pages and such.
For the time being I just created a SQL View that basically functions like a big flat file. We're talking about less than 100,000 rows so I'm not too worried about performance.
However, I DO need to figure out this many-to-many relationship thing pretty soon! I guess that's what I get for being monogamous for so long -
Cheers,
Dan
7.7.05M/7.7.03 HF6 on Windows Server 2003 SP2 output to whatever is required.
Posts: 393 | Location: St. Paul, MN | Registered: November 06, 2007
Just for a test, have you tried doing a simple join of 2 tables, holding the output and then joining the output to the other table? This may give you a better idea of where the multiplicity comes from.
WF 7.6.11 Oracle WebSphere Windows NT-5.2 x86 32bit
Francis - I like doing the joins in the WebFOCUS synonym because, if they are set up right, WebFOCUS will pass a SQL join command only for those tables required for the specific request. This makes queries more efficient. With large tables this can be very tangible. My understanding of SQL Views is that all the joins are issued every time you make a request from the view regardless of which columns are included in the request. I could be wrong about that.
RSquared - When I have a chance to test this I will try your idea.
Thanks all!
Dan
7.7.05M/7.7.03 HF6 on Windows Server 2003 SP2 output to whatever is required.
Posts: 393 | Location: St. Paul, MN | Registered: November 06, 2007