EIS - OLAP Model - Dimension Joins

Hi,
I know the in EIS OLAP model we need to build a logical STAR schema between dimensions and fact tables with some join condition. Now, can you tell me how the join works while building the dimensions? Do EIS really bother about the joins between dimension and fact tables? My understanding is, EIS will load all the members present in the dimension table irrespctive of join clause.
Pls shed some light on this!
Thanks!

You can join tables together with a "bad" JOIN. Your outlines will still build and probably look fine, however, this is what I tend to think of as a "dirty" EIS model. You will run into issues if you try and load data through EIS but you can probably get the outline to build how you want it. I highly recommend that you try and do things the "right" way as it will pay off in the future, but if you have to get it done some other way.... well, I've seen worse. :)

Similar Messages

Inserting the Brio Query Data into EIS OLAP Model tables directly

Dear Experts,
Can someone please suggest how we can export data (result set records) from bqy files' queries into an EIS server's OLAP Model's tables?
Right now I have a cube on Essbase server getting the data from excel sheets which store the data from the execution of .bqy files.
Use of file system (excel sheets) has not been liked by my business users so now I need to avoid storing the data from brio queries into excel sheets for loading into the Essbase cube. This I am required to achieve using EIS/AIS so that the data from brio queries(.bqy files) can be directly inserted into Essbase cube with the help of (i.e. via) EIS/AIS.
Any quick help would boost the life of this project of mine.
Thank you,
Vikas Jain

user12072290 wrote:
Dear Experts,
Can someone please suggest how we can export data (result set records) from bqy files' queries into an EIS server's OLAP Model's tables?
Right now I have a cube on Essbase server getting the data from excel sheets which store the data from the execution of .bqy files.
Use of <A class=bodylinkwhite href="http://www.software-to-convert.com/h264-conversion-software/h264-to-quicktime-software.html"><FONT face=tahoma,verdana,sans-serif color=#000 size=1>file</FONT></A> system (excel sheets) has not been liked by my business users so now I need to avoid storing the data from brio queries into excel sheets for loading into the Essbase cube. This I am required to achieve using EIS/AIS so that the data from brio queries(.bqy files) can be directly inserted into Essbase cube with the help of (i.e. via) EIS/AIS.
Any quick help would boost the life of this project of mine.
Thank you,
Vikas JainHave you got the answer? Would you pls post it here?

EIS - Is there a way to filter entire OLAP Model or MetaOutline

Is there a way to apply a filter on an entire metaoutline or OLAP Model to look at only the data for a single period during the outline extract vs. scanning the entire table? Or do you have to specify this in the filter for every dimension member?

Glenn:
Thanks for the response. Was wondering if you can provide some more specific info on how to define the selection for the OLAP model or metaoutline.
I have looked at filters in the metaoutline but cannot see how I would put a criteria in the edit filter mode. I know about filters at the member level but was hoping that I would not to have to define the time dim criteria in a filter for every member in my metaoutline.

Migrating OLAP Models and Metaoutlines from EIS to Studio.

Hi All,
I'm trying to migrate metaoutlines and olap models from EIS to Essbase Studio.
I am able to fetch all the models and metaoutlines but after that when i click on the Migrate button, it throws me this error:
Reading results from query for reading view attr failed. java.lang.NullPointerException
Any idea whats going wrong?
Kindly help.
Thanks in Advance.
Regards,
-Avishek

It just means that in the dropdown you need to pick the name that maps to the schema where your meta/data tables are stored for the EIS model/metaoutline you are migrating.
Cheers
John
http://john-goodwin.blogspot.com/

Need Suggestion on OLAP model

HI All,
We do have a reqirement to design a OLAP model for consolidating the issues identified on ASSETS from various sources\system.
Let us take one sample record;
Issue | Asset | Status |Priority |St_DT |End_Dt
ISS1 | ASS1,ASS2 |Open |High |1-Jan-13 |NULL
We have designed the below model for this scenario:
Dimension_Asset: Conformed dimesion for assets.
Dimension_Asset_Group: Since each issue can have multiple assets we have designed a group table.
Dimension_Date: Conformed and role playing dimension for start and end date
Fact_Issue: Issue_ID,Asset_Group_ID,Status,Priority,St_DT,End_DT
Please clarify the below doubts ( if at all the above model is good to go)
1. As of now client is not intersted in the history of the issue, if at all in future it requires then is it good to go with this model, by have multiple entries in the fact_issue table for same issue. Also on top of it can we build a accumulating snapshot fact table.
2. Actually issues will be associated with many deatiled text and lattributes. Do we need to capture this information in the FACT_ISSUE table as per this model. As of now we planned to move those information to another table called Dimension_Issue (though we cannot call it as dimension since its not repitative data in the fact table).

pinay39 wrote:
There's no model number i can find at the bottom, just the type and serial number.
Welcome to the forum!
It kind of looks like one of the 500s. What's the type number you found on the bottom?
Message Edited by nonny on 10-29-2008 09:36 PM
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество
Jane
2015 X1 Carbon, ThinkPad Slate, T410s, X301, X200 Tablet, T60p, HP TouchPad, iPad Air 2, iPhone 5S, IdeaTab A2107A, Yoga Tablet, Yoga 3 Pro
I am not a Lenovo Employee.
I AM one of those crazy ThinkPad zealots!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!

XML Export/Import OLAP Model or Metaoutline

Hi, I am using DB2 OLAP Server 7.1 and Fixpack 7. I had created and Validated OLAP Model. I am trying to export this model to a XML file. But "Error-1" is being raised and export is failing. Can any one know the details of the error?Thanks,Thangam

We had same problem on Windows NT server when running EIS as a service. Had to stop service and run in task manager on both servers in order to Export/Import. Did not encounter this issue with Windows 2000.

OLAP time dimension - how are the weeks allocated

Could someone please help me understand what logic Oracle uses when one makes use of Oracles OLAP time dimension based on weeks.
I am use Oracle OLAP 11.2
I have a Time dimension that has the following hierarchy:-
YEAR
QUARTER
MONTH
WEEK
For calculating the weeks ID I make use ISO week and year i.e. IYYYIW
For calculating the end date I use the following:- NEXT_DAY( l_date, 'MON' ) -1
i.e. the weeks end date is the Sunday.
According to me this is the required result.
Problem is that for some months there are 3 weeks allocated which makes no sense to me.
I cannot understand the logic used in allocating the weeks.
The following is an example:-
the following weeks were allocated to the month February
201306 (end date= 10-2-2013)
201307 (end date= 17-2-2013)
201308 (end date= 24-2-2013)
but the following week was allocated to January which makes no sence to me,
I would have expected it to be found in February
201305 (end date= 3-2-2013)
Week 201309 (end date= 3-3-2013) was allocated to March which according to me is correct..
Another example is week *201030 (end date= 1-8-2010)* that is allocated to July while I would have expected that it should be August.
I would have thought that it uses the end date that is placed in the mapping to determine the month to place it in.
Could some one please explain what the reason for this could be.

Oracle OLAP model/design (in this case, at least) cannot compensate to coverup existing flaws in the relational model/design.
I dont think this is a valid hierarchy even considering relational model/design.
Weeks do not fit in below Months (calendar months).
You can force fit them by making Weeks the source of truth and making all Months logical Months like "Business Month", "Business Quarter", "Business Year" etc. which will be composed of whole weeks but differ significantly from the calendar definition of Month, Quarter, Year etc.
You are better off modeling time as composed of two hierarchies:
H1: DAY -> MONTH -> QUARTER -> YEAR and
H2: DAY -> WEEK
Alternately if you dont want to introduce DAY level (lower granularity), you can split up the Time dimension into 2 different dimensions. And also modify your star schema to add an additional time dimension key to fact table - one key pointing to WEEK and another pointing to MONTH (independently).
TIME_MO: MONTH -> QUARTER -> YEAR
TIME_WK: WEEK
The fact data will need to be split up to correctly identify the coirrect MONTH-WEEK combination for the relational record.
E.g:
Fact table should have 2 dimension Fks for WK_KEY as well as MO_KEY so that a fact figure of 1000 evaluated over 7 days is split up into 300 from 29-31st of previous month and attached to MO_KEY of previous month and another record of 700 covering days from 1-4 and recorded/tied to same WK_KEY but next month (next month's MO_KEY).
HTH
Shankar

Create repository from database model- snowflake facts and dimension joins

I am working on a project that has a database model similar to the image in the link below.
There are other few tables around it, but this generally represent the spine or major database model. This is not exactly a snowflake schema as there are no intrinsic hierarchy in the dimension tables. As you can see dim2 and dim4 has one to many relationship with dim3. there are joins between the fact tables as well.
From some blogs and forum threads, I found out that I can create one fact/dimension table by joining many fact/dimension tables. Is this a right approach? Any thoughts on this model please?
Thanks,
Rakesh
ps: I am using Windows XP Pro and OBIEE 10.1.4.3.1 and right now analyzing the data to create a repository.

Hi Rakesh,
As above post says you combine all fact tables into single fact table with other dimension tables so it would become a simple start schema .Go throught these blogs for further information .
http://forums.oracle.com/forums/thread.jspa?threadID=2124061&tstart=0
http://www.obinotes.com/2010/08/joins-within-logical-table-sources-in.html#comment-form
Hope it helps you.Seems your new to forum you sud follow these rules http://forums.oracle.com/forums/ann.jspa?annID=939
By,
KK

Hyperion OLAP model vs. Oracle OLAP

Hi, I have a question re: how to properly model stuff in Hyperion OLAP. I know the basics of Essbase, but I've never found out how to do this...
In Oracle OLAP, I can define a set of dimensions, and then create cubes that use any subset of those dimensions.
In Essbase, if I define a set of dimensions, there is only one cube - and it is forced to share ALL of the dimensions.
So I'm always at a loss how to model something that would be pretty simple in Oracle OLAP, like:
Sales cube - dimensioned by time, store, product, customer
Local tax rate cube - dimensioned by time, store (but not product or customer)
Sales goal cube - dimensioned by time, store, product (but not customer)
etc.
What's the best way to handle this in Essbase?
p.s. after these cubes are done, I'll also want to do some formulas like local taxes = sales cube * local tax rate, etc.
Thx,
Scott

Essbase basically has two different design approaches. One you build a cube via Admin services and or load rules, the other is via Integration Services. When using Integration Services, it fits the more traditional build methodology you are familiar with. Via Integration Services you would define a star schema with a fact table and dimensions. You would then build a meta-outline layer where you would define how you want the cube to be built. You could "publish" a cube with all dimensions, or you can have multiple versions of your meta-outline, some that use certain dimensions and others that do not. Within that model you could go one step further and apply filters so you could build two cubes with the same dimensions but filter groups of members out of the dimension in one cube that you allows to flow through in the other cube, or maybe only allow it to build down to a certain level. The options get pretty broad. I think EIS will will get you to what you are familiar with and make a lot more sense. Go to the download site and you can download the docs on EIS to start to get a better idea.

Hybrid OLAP model in Oracle 9i OLAP

Please, does anybody know if with Oracle 9i OLAP Technology is possible to create an hybrid model? In Express I've used the RAM for mapping dimensions and fact tables with Express multidimensional cubes, so when I ran queries (i.e. OSA queries) the RAM/Express engine knew dynamically what data to retrieve from the fact tables (i.e. detail data) and what data to retrieve from the Express cubes (i.e. aggregated data) in a hidden way for the end user.
So, in Oracle 9i OLAP which is in charge of accomplishing the RAM function? and if this functionality exists, could the Analytic Workspace Manager create the metadata of this hybrid model?
Secondly, OWB 9.0.4 is capable of creating the OLAP metadata from the result of a fact load mapping; do you think that the OWB future releases would allow to create the hybrid metadata?, for later to be exploited from BI Beans?
Thanks a lot in advance,
Pablo Ibarra.

Support for a hybrid model will be implemented in a future release.
Warehouse Builder, as a design and implementation platform, will continue to evolve as OLAP evolves.

MS SQL Server Analysis Services (SSAS) OLAP Connection - Dimension descriptions

Hello,
We are trying to create some reports on BO 4.0 on top of BPC 10 MS information.
In order to overcome some issues related to standard connector between BO and BPC (XMLA Planning and consolidation 10 for Microsoft platform), we created a new connection based on discussion MS SQL Server Analysis Services (SSAS) OLAP Connection - Business Intelligence (BusinessObjects) - SCN Wiki
However we have a major issue with this approach. We cannot see on BO dimension member descriptions.
Is there anything that we missed?
Could you help?
Regards,
Vitor Ramalho

Bill,
So, what you need is a model like SQL Server failover cluster instances. (before sql server 2012)
In SQL Server 2012, AlwaysOn replaces SQL Server failover cluster, and it has been seperated to
AlwaysOn Failover Cluster Instances (SQL Server) and
AlwaysOn Availability Groups (SQL Server).
Since your requirement is not in database level, I think the best option is to use AlwaysOn Failover Cluster Instances (SQL Server).
As part of the SQL Server AlwaysOn offering, AlwaysOn Failover Cluster Instances leverages Windows Server Failover Clustering (WSFC) functionality to provide local high availability through redundancy at the server-instance level—a
failover cluster instance (FCI). An FCI is a single instance of SQL Server that is installed across Windows Server Failover Clustering (WSFC) nodes and, possibly, across multiple subnets. On the network, an FCI appears to be an instance of SQL
Server running on a single computer, but the FCI provides failover from one WSFC node to another if the current node becomes unavailable.
It is similar to SQL Server failover cluster in SQL 2008 R2 and before.
Please refer to these references:
Failover Clustering in Analysis Services
Installing a SQL Server 2008 R2 Failover Cluster
Iric Wen
TechNet Community Support

Integration Services OLAP Model Upgrade

Hi,
We have installed EIS 716 on new server and needs to upgrade it. i have followed this approach until now..
Suppose i have catalog as "catalog1" getting connected with "A" on old box 7.1.2.
Now we got this "A" schema copied into new server from backend and am trying to upgrade the catalog from IS console with name as "catalog2" and getting connected with "B". so we will be able to see all the Models and MOTL's..
Here is my question, like when we upgrade the OLAP Metadata Catalog it upgrades the Models and MOTL's in it or we need to do a separate upgrade for these.I assume the Models and MOTL's reside in the catalog itself.
Further what i have noticed is that, when we get connected into new catalog on new server with "catalog2" and export one model or MOTL using XML import/export option..it is showing with old schema names like "A" and version 7.1.2.
Will it show the old version only and not with 7.1.6 and upgrade schema "B"?
Is this the correct way to upgrade EIS or do we need to export each and every model & MOTL and upgrade with the schema name like "B".?
Can anyone help me on this issue elaborately as i was into issues here..
Your help is very much appreciated
Thanks

EIS will automatically upgrade you new catalog the first time you connect to it. Don't worry about the version indicated in the XML files. The important thing is that the binaries have been updated.
Gee

Facts and dimensions joins

Hi,
Can we use three fact tables in rpd and not join them? We have three facts and four dimensions. All the four are common dimensions to the three fact tables. So in the physical joins can we just join the facts to the dimensions? will it be accepatble if we do not have a join between fact tables. Is it necessary that all the tables (fact and dimensions) need to be joined to some tabler? Can we leave the joins between the facts which are not necessary? Please advice.

We do not do joins between fact tables, the joins between facts will be happened through dimensions (conformed dimensions).
In your case the 4 dimension will act as an conformed one.
Is it necessary that all the tables (fact and dimensions) need to be joined to some tabler? You cannot have a table in BMM which is not joined to any other table.
Can we leave the joins between the facts which are not necessary?Yes, Dim1 - fact1 -Dim 2 in this fact 1 is connected with Dim1, Dim2 and there is no relationship for fact1 with Dim3 so we don't join it.
Dim1,Dim2,Dim3 is joined with fact2 in this case Dim 1 and Dim2 will act as conformed dimesion between fact1 and fact2, where as dim3 will be a non conformed dimesion.
Thanks,
Vino

Querying Levels in Dimensions joined to the Facts

I created a location dimension using the standard levels, i.e., region > subregion > country > state > location_id. I then attached it to a sales fact that had the location_id as the key, but when I tried to query the cube by it's levels the only level I see is the location_id level which is at the state. None of the other levels appear or are queryable when I do something like:
SELECT * FROM vw_SALES_CUBE A, vw_LOCATION_DIM B
WHERE A.LOCATION_DIM = B.DIM_KEY
AND A.LEVEL = 'COUNTRY'
Only one level comes up although in the location_dim all the other levels exist the join does not carry them over. The data for the levels appears in the COUNTRY_LONG_DESCRIP column and not in the LEVEL column.
What am I doing wrong. Are there other objects I need to create like an MV.
jrod

I was thinking that is if I created a cube such as the one described in the thread and that I did a query along the LEVEL_NAME that the cube would fetch the data without the need for me to create say MV's aggregateing the data. For example,
/* The following is a basic query against a fact table */
SELECT T.CALENDAR_YEAR_DSC TIME, SUM(F.SALES) SALES
FROM TIME_DIM T, UNITS_FACT F
WHERE T.CALENDAR_YEAR_DSC IN ('2005', '2006')
AND T.MONTH_ID = F.MONTH_ID
GROUP BY T.CALENDAR_YEAR_DSC;
/* The next query fetches the exact same results from a cube using filters: */
SELECT T.LONG_DESCRIPTION TIME, F.SALES SALES
FROM TIME_CALENDAR_VIEW T,
PRODUCT_PRIMARY_VIEW P,
CUSTOMER_SHIPMENTS_VIEW CU,
CHANNEL_PRIMARY_VIEW CH,
UNITS_CUBE_VIEW F
/* Apply filters to every dimension */
WHERE T.LONG_DESCRIPTION IN ('2005', '2006')
AND P.LEVEL_NAME = 'TOTAL'
AND CU.LEVEL_NAME = 'TOTAL'
AND CH.LEVEL_NAME = 'TOTAL'
/* Join dimension views to cube view */
AND T.DIM_KEY = F.TIME
AND P.DIM_KEY = F.PRODUCT
AND CU.DIM_KEY = F.CUSTOMER
AND CH.DIM_KEY = F.CHANNEL
ORDER BY TIME;
In these two queries I fetch the same grain. So why is it that the cube has not precomputed these factors. What do I need to do this?

Issue with Fact and Dimension join

Hello,
I have two Facts F1 & F2 and two Dimensions D1 & D2.
in my schema, D1 is the common dimension between F1 & F2 and D2 is joined to F2 only.
so when I am trying to get one record from each of D1, D2, F1 & F2 the query is not getting generated for D2 & F2. It is only creating a query like " select a1,a2, a3 from F1,D1,F2 where D1.a2=F1.a1 and D1.a2=F2.a3".
Need some suggestion where i am wrong that OBIEE is not creating query for D2 & F2 join.
Thanks,
-Shub

Discussed multiple times Business Intelligence Suite Enterprise Edition .

EIS - OLAP Model - Dimension Joins

Similar Messages

Maybe you are looking for