Oracle 9i OLAP Time Dimension

I have got a problem with my cube in Oracle 9i R2 OLAP Services.
I would like to create time dimension with hour level. But, time type have
only day level.How I can create dimension with hour level ?
user cwm2 or OWB

Hi Jiaxu,
Are u a Chinese?
I find that you are learning OracleR2 OLAP.
I just take a project about OracleR2 OLAP.
Could we talk about the technology?
My mail is [email protected]
Best Regards
Chen Qizhuan

Similar Messages

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

Essbase/OLAP Time Dimension in OBIEE

I am on OBIEE 11g release. After exported the below essbase time dimension with dynamic time series thru the Administration tool
Time
|_ Spring
|_ Q1
     |_Feb
          |_FebW1
     |_FebW1D1
          |_ .....
          |_FebW1D7
|_FebW2
     |_Mar
     |_...
     |_ Q2
     |_....
|_Fall
Of course OBIEE converted, OB converted the time into
Time
Year
Season
Quarter
Month
Week
Gen6
Drag the Time hierarchy from physical layer to Logical layer and to presentation layer.
However, when try to see the time hierarchy in Answer by drill down on the hierarchy from Year, it only shows spring but not fall, and drill from spring
I can only see Q1 etc .....
Is there a setup I need to done ?
Thanks

Answer not display hierarch when there is no data assoicated.

Time dimension - not ordered

Hello,
I'm new on OLAP Cubes,
I've made one that works well instead of the fact that my time dimension is not sorted : dates are not in order.
I've tried to sort dates before the cube, in the views. but even if when i see time attribute sorted in my view my cube time dimension stays unsorted.
I'm working with AWM 10g
please help !

You can always use the time_end_date attribute to sort the results of the query. When you say that the time dimension values are not sorted? what do you mean .... is the hierarchy correct ... all nn-JAN-yyyy records under JAN-YYYY or is it also mixed up due to the improper sorting? If the hierarchy is alright.. you may need to
Can you provide more details... perhaps all details relating to db view/table - structure (table/view, columns, datatype, size etc) and sample data (few rows) as well as how the data appears in the olap time dimension when viewed through AWM results. Whats loaded (all of the records but sorted improperly or if only some of them => what're the records which dont get loaded?)
Also noticed that you used the term olap cube time dimension.. the time dimension is not exactly an independent component of the cube, its used by the cube. Its defined in the AW and exists only as a dimension (independent of any/all cubes). The cube only references it.
Another reason for mismatch (not very likely though) could be that you have time end date data in your view as a varchar field instead of a date and is interpreted wrongly while its being loaded as a date datatype attribute by the AW dimension load program. Depending on your NLS settings (and thereby the default date format), the date string is interpreted as a inappropriate date. You usually encounter errors during such a load ... day #13 interpreted as month #13 (invalid) as a result of a mismatch of date format settings.
HTH

Oracle 11gR2 use the time dimension wizard---the cube didn't show any information!

I created a Time Dimension with the Time dimension wizard , a category dimension, and a rel_expense cube in OWB 。what I do is following the oracle 11g r1's turtoial
The rel_expense cube has two forigen keys, one is refrence the category dimension's dimension_key(primary key in the category dimension), and the other one refrence the time dimension's start_day_date(bussniess key in the time dimension).
The result I get is the rel_expense_tab had datas, but the rel_expense cube had nothing.
.I delete the category dimension , it is the same result(cube rel_expense had nothing).
But if I only delete the time dimension, it is ok(both of them had datas)!!!
So I think is the time dimension's problem ,because the 11g r2's time dimension wizard didnt' generate the dimension_key for time. Is the forigen key(time dimension) i refrenced in the cube is error,so if it is, what should I do?
SEEK FOR YOU HELP!!!!!
ps:my mother language isn't English ,so it has many erros in the passage

can anybody help me? the measures in my cube were round to integer, i doubt it came from time dimension. did anyone encounts such a senario

Oracle Warehouse Builder 11GR2 -no time dimension wizard?

Hi,
I am running OWB 11GR2 on top of a 11GR2 database (OEL 5.4 64 bit).
I don't have a time dimension wizard, just a normal wizard. What I do is right-click, new dimension....but no time wizard. How can I activate it?
I have installed everything several times, but no luck...
Can anyone help, please?

Hi
Right Johnny. This happened when we moved to the new UI, all objects can be created using the New 'gallery' style approach, not exactly intuitive for how you remember time dimensions being created but it's still all there.
Cheers
David

How to build the time dimension in Essbase with Fiscal Year (July thru Jun)

Hi,
In a recent project i have a situation where i need the time dimension to have some thing like this Fiscal Year (July - June) using BSO need to achieve DTS (YTD and QTD) functionality also.
And also my reports should also be able to drill through and needs comparison years(Prev Year Vs Current Year), months(Prev Year Vs Current Year) and Qtrs(Prev Year Vs Current Year).
How can i achieve this using BSO?.

Hi there,
This forum is for Oracle OLAP. The Essbase forum can be found here:- Essbase
Thanks,
Stuart Bunby
OLAP Blog: http://oracleOLAP.blogspot.com
OLAP Wiki: http://wiki.oracle.com/page/Oracle+OLAP+Option
OLAP on OTN: http://www.oracle.com/technology/products/bi/olap/index.html
DW on OTN : http://www.oracle.com/technology/products/bi/db/11g/index.html

Time Dimension not loaded correctly when imported to 10.2.0.3 database

Dear All,
I created a Time dimension using the wizard that contian both Normal and Fiscal hierarchies on a repository created on 10.2.0.1 DBMS
I exported the poject in mdl and imported it in repository on 10.2.0.3 DBMS ... the Time dimension in the new poject wasn't loaded correctly
the Rows of the Day level contain information about the upper fiscal levels' columns while the columns of the normal hierarchy containd null
Can you help me to solve this problem ???? !!!!!...
Best of regards,
Shaimaa

Your quote comes from the OBIEE Plug-in user guide (http://www.oracle.com/technetwork/database/options/olap/awm-plugin-user-guide-for-obiee10g-303148.pdf)
So, yes, you can only use this if you are using database 11.1.0.7 or later and if you are creating an 11g style AW.
You can map 10g style AWs to OBIEE, but it is a manual and complex task. You would need to start by generating views using (for example) the OLAP View Generator (10.2.0.3) available on http://www.oracle.com/technetwork/database/options/olap/olap-downloads-098860.html . After this you would need to manually create the mapping metadata in OBIEE.

Setting up a TIME dimension in OBIEE

Hi,
We have an Oracle OLAP Cube built using AWM v10.2.0.3A. We have also created a relational view for this cube (using the OLAP view generator) and are now using this view as a data source in OBIEE v.10.1.3.3.2.
As part of defining the Time dimension in the Business Model Layer of OBIEE repository, we have done all the relevant mappings to the TIME dimension as in the AWM Cube and have marked the dimension as type 'TIME'. Also, for the TIME logical table, we have defined each level (All Years, Year, Month, Quarter, and Day) to have its own chronological key with unique values at all levels. The primary key for our TIME table in the business layer is 'Day'. This level 'Day' is mapped to TIME_DAY_LVLDSC column of the relational view created over the AWM cube. The data type for this column is "VARCHAR". (We basically picked up all the 'Description' columns while creating the view over the cube!)
With this background of the TIME dimension structure, here is the problem scenario:
When we try to create a report with one AGO and one TODATE function defined over the "Day" level (both are defined as logical columns), then the report takes forever to run and never comes back with any data/error even for a handful of rows. We are seeking the forum's help on the following:
1. Is it necessary for the primary key 'Day' of the TIME logical table to be of type DATE? If yes, does this mean that we have to change the column data type in our cube (or select a 'date' type column to be a part of the view and then redo the mapping in the repository) or do we just make a change to the column data type in the physical layer of OBIEE repository?
2. Going by the description above, is there something missing (other than point 1. above) in the setup of the TIME dimension in OBIEE so as to make it usable for Time Series type of calculations/functions?
Any help is much appreciated.
Thanks and Regards,
Piyush

Hi Wildmight,
Thanks a lot for your kind inputs.
1. No, VARCHAR is fine. You should have also defined unique time keys in your time dimension (Quarter Year, Month Year) and check box 'time dimension' in the properties of your time dimension.
-->> The Time dimension that we have defined in the Business layer of the repository is mapped to the respective level columns in the AWM cube and has already got unique members at each level. We are using the "Description (LVLDSC)" columns for each level and have defined the "Description" column to have unique values at each level. A sample data set looks like :
Year:
2007
2008
Quarter:
QUARTER1 2007
QUARTER2 2007
QUARTER1 2008
QUARTER2 2008
Month:
JANUARY 2007
FEBRUARY 2007
JANUARY 2008
FEBRUARY 2008
Day:
Monday, January 1st 2007
Tuesday, January 2nd 2007
So in the above case, do we still need to define a unique key for each level like Quarter Year, Month Quarter, etc.? (Please note that the check box for 'TIME' dimension is checked !)
2. Is your AGO based on TODATE? or your TODATE based on AGO?
-->> I am not sure what this really means - however I can tell you that we have created two new logical columns (in the fact table in Business Layer) : one to show the measure as TODATE for Day level, and the other to show the measure as Day Ago.
So it means that we are trying to create two reports with three columns as below:
- Day Measure on Day Measure Todate (Day)
- Day Measure on Day Measure Day Ago (Day, 1)
I hope I have been able to clarify the problem scenario with this. Does this setup seem correct to you?
Many thanks for your help.
Best Regards,
Piyush

Time dimension with Hourly base time periods

Hi all
I need to analyze data at Hour, Day, Month, and Year levels. The data in the fact and dimension tables are at the 'Hour' level with DATE datatype, such as:
02-SEP-10 10:00:00 AM
02-SEP-10 11:00:00 AM
To use Time-Series type calculations, I understand that I have to create an OLAP dimension of type 'TIME' (and not 'USER') and map it to the populated relational time dimension table.
1) Can I have the primary key for 'Hour' level as the actual base level value of datatype DATE (eg. 02-SEP-10 10:00:00 AM) ?
2) For the END_DATE and TIME_SPAN attributes at the 'Hour' level, what should I use?
The documentation is only available for minimum 'Day' level hierarchies, which allows setting END_DATE and TIME_SPAN to the actual 'Day' value and 1, respectively.
3) For the END_DATE and TIME_SPAN attributes at the 'Month' level, do I need to supply the last-date-of-each-month and number-of-days-in-that-month, respectively?
Please bear in mind that I am relatively new to Oracle OLAP. Any assistance will be appreciated.
Cheers.

Thank you Szilard and Adnan for the very prompt and informative responses.
I managed to follow the advice on the oracleolap.blogspot link and created a time dimension with members at Hour level loaded into the dimension in character format: TO_CHAR(hour_id, 'DD-MON-YYYY HH24')
The problem now is the maintenance (loading) of the dimension is taking an abnormally large amount of time (over 1 hour) as opposed to when the members were being loaded in DATE format (5 minutes). The mapping table only as 10,000 entries.
Why is these such a big difference? Is it normal? Is there a way to speed up the maintenance time?
FYI, I have not created any indexes on any of the attributes.
My platform is:
11.1.0.7.0 DB
11.1.0.7.0B Client

Time Dimension with Hourly base level

Hi all
I need to analyze data at Hour, Day, Month, and Year levels. The data in the fact and dimension tables are at the 'Hour' level with DATE datatype, such as:
02-SEP-10 10:00:00 AM
02-SEP-10 11:00:00 AM
To use Time-Series type calculations, I understand that I have to create an OLAP dimension of type 'TIME' (and not 'USER') and map it to the populated relational time dimension table. My questions are:
1) Can I have the primary key for 'Hour' level as the actual base level value of datatype DATE (eg. 02-SEP-10 10:00:00 AM) ?
2) For the END_DATE and TIME_SPAN attributes at the 'Hour' level, what should I use?
The documentation is only available for minimum 'Day' level hierarchies, which allows setting END_DATE and TIME_SPAN to the actual 'Day' value and 1, respectively.
3) For the END_DATE and TIME_SPAN attributes at the 'Month' level, do I need to supply the last-date-of-each-month and number-of-days-in-that-month, respectively?
Please bear in mind that I am relatively new to Oracle OLAP. Any assistance will be appreciated.
Cheers.

Thank you Szilard and Adnan for the very prompt and informative responses.
I managed to follow the advice on the oracleolap.blogspot link and created a time dimension with members at Hour level loaded into the dimension in character format: TO_CHAR(hour_id, 'DD-MON-YYYY HH24')
The problem now is the maintenance (loading) of the dimension is taking an abnormally large amount of time (over 1 hour) as opposed to when the members were being loaded in DATE format (5 minutes). The mapping table only as 10,000 entries.
Why is these such a big difference? Is it normal? Is there a way to speed up the maintenance time?
FYI, I have not created any indexes on any of the attributes.
My platform is:
11.1.0.7.0 DB
11.1.0.7.0B Client

How to load time dimension informatica...

Hi, im new to datawarehouse... Can anybody tell me,how to load time dimension informatica...
Thanks and Regards,
jagadish.

Do you mean Informatica, the ETL tool? If you do then I would post your question on the Informatica website as we typically use Oracle Warehouse Builder and Analytic Workspace Manager here at Oracle.
If you want to know hoe to generate a time dimension table, then I would recommend using the Time Dimension Wizard in Warehouse Builder as this will automatically create the target dimension table and populate all the required levels with the correct data values. There is more information on the OWB OTN Home Page
Keith Laker
Oracle EMEA Consulting
OLAP Blog: http://oracleOLAP.blogspot.com/
OLAP Wiki: http://wiki.oracle.com/page/Oracle+OLAP+Option
DM Blog: http://oracledmt.blogspot.com/
OWB Blog : http://blogs.oracle.com/warehousebuilder/
OWB Wiki : http://wiki.oracle.com/page/Oracle+Warehouse+Builder
DW on OTN : http://www.oracle.com/technology/products/bi/db/11g/index.html

Additional custom level on Time dimension ?

Hi,
I´m very new to OWB, so I don't know if what I want to do is even possible at all.
I created a time dimension using the "Time Dimension Wizard", selecting all possible levels (year, quarter, month, day), but I also need to have one extra level: semester. You see, we need that level for our reports.
I tried to open the mappings that were generated automatically but Oh, boy! does that look complicated!!! Some operators call time functions but when looking them up, they're in packages that come wrapped, so basically I have no clue as to how the data is being generated by Oracle.
Do you know of any way to accomplish this? Basically have a time dimension with the levels:
Year -> Semester -> Quarter -> Month -> Day
Any help would be very much appreciated.
Rgds,
--Oswaldo Santos
[osantos]

Hi JP,
Thanks for the tip.
I created a new "time" dimension manually. I basically made a copy of the attributes and levels of a normal time dimension, plus the new fields for "semester". I also defined the corresponding fields for "END DATE" and "TIME SPAN".
Now, I can populate this dimension, based on a script that someone else posted in this forum. I'm not sure, though, that Oracle OLAP will recognize this as a "time" dimension, will it? I mean, OWB adds some extra fields for a time dimension created with the wizard (like "level type"). Will this affect the performance or behavior of my cubes? Or, can I say that this is as real a time dimension as one created with the wizard in OWB?
Again, thanks a lot for your support.
Regards,
--osvaldo santos.
[osantos]

Selection objects and Time Dimension

I have instantiated QueryClient object using the query manager. I have 5 dimension in my MOLAP cube where one of the dimension is TIME dimension. I create a selection object for each dimension and apply the selection array to the queryClient object. I create selection objects by using its constructor which takes dimension unique id as argument. I get OLAP Source not found error when I take this approach. When I do create a selection object by queryClient.createQueryAccess.getSelection("DimUniqID") for time dimension only, everything works fine and I see results. What is special about selections and time dimension ? Can anybody throw some light on this or there is some flaw in my understanding ?
Thanks
Swapan.

Did you review the topic "Defining a Query Programmatically" that is part of the BI Beans Help documentation. This has some good examples.
Hope this helps
Business Intelligence Beans Product Management Team
Oracle Corporation.

Time Dimension: Naming requirement?

I am trying to create a YTD calculation in a cube using BI beans/Jdeveloper. This used to work fine in a previous version of the cube. In the new cube, the 'next' button remains grayed out if I select the 'YTD calculation (or any other time related calculation)
One of the changes between the cubes seems to be that we renamed the time dimension to t_time_month. I am wondering if BI beans has a requirement that the time dimension ends in 'Time', similar to the requirement that the dimension name needs to end with 'Name'. I can't find a way to tell BI beans which is the time dimension, so maybe the name is the only way it could know?
Is there a document that describes this type of requirements for BI Beans?
Thank you in advance for your help.
Cor Wooning

Hi,
There are certain requirements for a dimension to be of type time. Each level in the dimension must have two attributes: End Date and Timespan.
If your DW environment is purely relational you can use OEM to check the status of your time dimension. There is a radio button to indicate if the dimension is of type time. You can try setting this, when you apply the change OEM will validate the dimension to see if it complies with the requirements for a time dimension.
If you are using Oracle Warehouse Builder to construct your DW environment, it provides a default mapping and dimension within a best practice MDL file. (it is located in the OWB_HOME/owb/misc/time directory).
There should me information in the OLAP Developer and user manuals relating Analytic Workspace dimensions
Hope this helps,

Oracle 9i OLAP Time Dimension

Similar Messages

Maybe you are looking for