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

Similar Messages

  • 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 create a working day/holiday attribute in Time Dimension with OWB ?

    Hello everybody,
    I am trying with no success to create a Time Dimension (with the wizard it would be easier...) with a working day or holiday attribute (0 or 1) to be able to calculate measures only on working time !!! I am totally sure it's possible, obviously, but I found nothing on forums... Could you help me ??
    I use OWB 11g, I need all fiscal year/quarter/month/week and all calendar year/quarter/month/week attributes so without any wizard it would be quite impossible... thank you for your help !
    NB: of course I know how to define if a day is a working one or not, but I currently can't add any columns in Time dim created with wizard...
    Francois
    Edited by: [email protected] on Jun 15, 2009 8:24 AM

    Hi,
    First of all, thanks everyone for your help.
    I did several tests this morning.
    First of all, i've tried with time_from = 000000 and time_to = 235959 (23:59:59 CET) and the activity has been created with Time From = 04:00:00 and Time To = 03:59:59
    Strange no ??
    I've also tried with 230000 for time from and time to but the activity has been created with Time From = 03:00:00 and Time to = 03:00:00
    I cannot understand the logic behind....
    Thanks,
    Johnny Baillargeaux

  • Modelling Time Dimension with Fact Table containing Start Date and End Date

    Hi Gurus,
    I have a time dimension with Year till Date. I have a fact table which consists of Start Date, End Date, Person ID, Department ID.
    How do i design Time dimension with fact table the below scenario
    In the dashboard i have start Month and End month as prompts.
    In the report i need to display Count(Person ID) > Start Date and < End Date along the trend.
    For instance, i have selected Jan-2009 as start date and Apr-2009 as End Date, then i need to display Count(Person ID) of Jan-2009, Feb2009, Mar-2009 andApr-2009.
    I Can not connect Time dimension with only Start Date or only with End Date to get the trend along the months.
    Please advice on the issue which i am having.

    Hi,
    Thanks for the response, Infact i tried using Complex join in physical layer. I have considered Time table joined with Fact table, and used >= and took and alias of the Time table and joined fact table using <=. When coming to BMM, i am not knowing how do i design this as if i merge the both the time dimensiona and its alias into single table, values will not be correct and if i make them as seperate columns. i can not show the trend as both are different columns.
    Can you please let know where i am going wrong.
    Thanks

  • Advice needed: join fact to time dimension with between clause

    Hi All,
    I've got 1 dimension and two fact tables. The 1 dimension could serve as a time dimension.(not specifically marked as this is a time dimension)
    My Tables look like this (simplified)
    Dim1:
    date_pk (unique identifier)
    date
    month
    year
    fact1:
    iid_date (foreign key to date_pk)
    fact1_amount
    Fact2:
    begin_date
    end_date
    fact2_amount
    In the physical layer i have a complex join between fact 1 and dim1 (date_pk = idd_date) and a complex join between fact2 and dim1 (dim1.date between fact2.begin_date and fact2.end_date and dim1.date <= CURRENT_DATE). In the business model i have complex joins between fact1 and dim1 and a complex join between fact2 and dim1 without further specification.
    What I would like to achieve in Answers is that I select a Year and a Month from dim1 and add fact1_amount and fact2_amount to the same report and that the report shows both amounts. I would like some advice on how to set this up. Further more how to add a drill from year to month to date and what should I do when I'm willing to add more facts joined to the same Dim1
    Any Advice is greatly appreciated
    Gilles

    Hello MMA1709,
    You're right, this setup works!
    But...
    When you add an hierarchy and mark it as a time dimension it doesn't work anymore. It gives the following error in the consistency checker:
    [38086] Physical table Dim1 in the time dimenison table source Dim1 is part of a complex join condition
    And that means you cannot use any timebased calculations (AGO and TODATE). When I just create an hierarchy and do not mark it as a time dimension the hierarchy works well.
    Any suggestions?

  • All Event times change with Daylight Savings time

    With the time change associated with daylight savings time (March 8 2008) all my event times were changed by one hour. EG: events that were 8:45 am are now 7:45 am. I have tried using Time machine to restore to pre March 8 status,but an adjustment takes place and the events remain 1 hour ahead. I have looked through the discussions pages and don't even see the issue identified. I have looked through the menu and preference items and find nothing to help.
    I am surprised not to find this a front page topic today, March 9 2008.
    Can anyone offer some help ?
    Bill Mullen

    Michael,
    I never have changed time zones. Are you suggesting I should have time zone support enabled ?
    I just tried turning on Time Zone Support, then restoring my calendar using Time machine. No change here.
    As I mentioned earlier, this same problem occurred in the fall (although I don't remember which way the event times moved), this time they moved forward. At the Fall change I was using a Mac G4, which I used as a target to build this machine. The only thing I can think of that makes me unique (although I'm not in that small of a group) is that I have altered one of the files in iSync to allow iSync to sync calendar events with iCal. The syncing has always worked OK.
    Right now I'm leary of attempting to do anything with iSync. I'm also finding it difficult to believe I'm not one of 10,000 people experiencing the same problem, but I don't see any other posts.
    I found a time zone in south america which returns my times to the correct figure, with time zone support enabled, but that looks like a deeper hole to dig out of.
    Still stuck,
    Bill

  • Backing up a 1TB Time Capsule with a 2TB Time Capsule

    I have a 1TB Time Capsule and a 2TB Time Capsule.
    Can I use the 1TB TC as a network disk (to store my iTunes files and my iPhoto file) and have it automatically backed up on the 2TB TC through Time Machine?

    No you cannot do that.. TM cannot backup a network drive.
    You can do it using a 3rd party backup software.. CCC, superduper.. anything really just not TM.

  • Handling Time Dimensions with Monthly and Weekly analysis

    I'm charged to build a cube that can handle both monthly and weekly analysis. They want to be view projections on a weekly grain, but looking back at history they want to be able to tie back to the general ledger at a monthly level.
    Is it overkill to load data down to the daily level in order to support multiple roll ups to the month and week? What is the best way to handle this kind of situation?

    Having the data come as two different formats (one for months, one for weeks) versus having it come in daily buckets and constructing the months/weeks within Essbase is a call I wouldn't make without understanding the needs first.
    Assuming there is no need for data at the daily level, I would weigh the selection based on performace. If the performance is not too outragious, taking the data in at a daily basis would make it easier to reconstruct later. If performance is an issue (or becomes an issue), I would still be tempted to load a daily cube at level 0, summarize the Months and Weeks, and then feed the main cube from there.
    So many ways to do this... and for every way there is a reason you might want to try something else. I'd start with the easy approach, and only go "grand" if you have to (meaning: load it daily, summarize in Essbase, and revisit the detail/summary cube split idea if the performance tanks out).

  • SCEP scheduled scan time problem with daylight-saving time?

    Since the daylight-saving time change from last weekend (1 hour earlier) we see that a large group of SCEP clients start their scheduled scan at 11:00 where we have it set in the policy in SCCM2012 at 12:00.
    Most workstations still begin their scan at 12:00.
    Any idea?
    Regards, Bob

    I’m cleaning up old post, did you figure this out yet, if so what was the solution?
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • Reminder times change with daylight savings time

    How can I prevent my reminders from changing with daylight savings? I want the times to remain static throughout the year.

    Michael,
    I never have changed time zones. Are you suggesting I should have time zone support enabled ?
    I just tried turning on Time Zone Support, then restoring my calendar using Time machine. No change here.
    As I mentioned earlier, this same problem occurred in the fall (although I don't remember which way the event times moved), this time they moved forward. At the Fall change I was using a Mac G4, which I used as a target to build this machine. The only thing I can think of that makes me unique (although I'm not in that small of a group) is that I have altered one of the files in iSync to allow iSync to sync calendar events with iCal. The syncing has always worked OK.
    Right now I'm leary of attempting to do anything with iSync. I'm also finding it difficult to believe I'm not one of 10,000 people experiencing the same problem, but I don't see any other posts.
    I found a time zone in south america which returns my times to the correct figure, with time zone support enabled, but that looks like a deeper hole to dig out of.
    Still stuck,
    Bill

  • TIME Dimension - TIME_SPAN parameter value (constant or decrementing?)

    Hi all
    For the the 'TIME_SPAN' parameter value in dimension of type 'TIME', should the value be constant for all members in a particular level or should the value decrement over time as the period progresses.
    For example, for a TIME dimension having levels DAY > MONTH should the values for TIME_SPAN be:
    DAY, DAY_END_DATE, DAY_TIME_SPAN, MONTH, MONTH_END_DATE, MONTH_TIME_SPAN
    D01JAN2010, 01-01-2010, 1, M01_Y2010, 31-01-2010, 31
    D02JAN2010, 02-01-2010, 1, M02_Y2010, 31-01-2010, 31
    D03JAN2010, 03-01-2010, 1, M03_Y2010, 31-01-2010, 31
    and so on...
    or like below:
    D01JAN2010, 01-01-2010, 1, M01_Y2010, 31-01-2010, 31
    D02JAN2010, 02-01-2010, 1, M02_Y2010, 31-01-2010, 30
    D03JAN2010, 03-01-2010, 1, M03_Y2010, 31-01-2010, 29
    and so on...
    Any assistance will be appreciated.
    Cheers.

    Here's a script that might be helpful to you. It fills in aggregate values for date and times span when you have existing days with date data type. If you have time periods shorter than a day, you might check out this post.
    http://oracleolap.blogspot.com/2010/05/time-dimensions-with-hourly-time.html
    CREATE TABLE time_dim
    DAY_KEY DATE,
    DAY_TIME_SPAN NUMBER,
    MONTH_ID VARCHAR2(30),
    MONTH_END_DATE DATE,
    MONTH_TIME_SPAN NUMBER,
    QUARTER_ID VARCHAR2(30),
    QUARTER_END_DATE DATE,
    QUARTER_TIME_SPAN NUMBER,
    CALENDAR_YEAR_ID VARCHAR2(30),
    YEAR_END_DATE DATE,
    YEAR_TIME_SPAN NUMBER
    -- Add rows for days. E.g.,
    -- insert into time_dim (select distinct day_key from fact_view);
    --UPDATE time_dim
    --SET hour_time_span = round(1/24,5);
    -- Add month members.
    UPDATE time_dim SET month_id = TO_CHAR(day_key 'MON-YYYY');
    UPDATE time_dim a
    SET month_time_span =
    (SELECT ts
    FROM
    (SELECT DISTINCT month_id,
    SUM(day_time_span) AS ts
    FROM time_dim
    GROUP BY month_id
    ) b
    WHERE a.month_id = b.month_id
    UPDATE time_dim a
    SET month_end_date =
    (SELECT ed
    FROM
    (SELECT DISTINCT month_id,
    MAX(day_key) AS ed
    FROM time_dim
    GROUP BY month_id
    ) b
    WHERE a.month_id = b.month_id
    -- Add Quarter members.
    UPDATE time_dim SET quarter_id = TO_CHAR(day_key 'Q-YYYY');
    UPDATE time_dim a
    SET quarter_time_span =
    (SELECT ts
    FROM
    (SELECT DISTINCT quarter_id,
    SUM(day_time_span) AS ts
    FROM time_dim
    GROUP BY quarter_id
    ) b
    WHERE a.quarter_id = b.quarter_id
    UPDATE time_dim a
    SET quarter_end_date =
    (SELECT ed
    FROM
    (SELECT DISTINCT quarter_id,
    MAX(day_key) AS ed
    FROM time_dim
    GROUP BY quarter_id
    ) b
    WHERE a.quarter_id = b.quarter_id
    -- Add Year members.
    UPDATE time_dim SET month_id = TO_CHAR(day_key 'YYYY');
    UPDATE time_dim a
    SET year_time_span =
    (SELECT ts
    FROM
    (SELECT DISTINCT year_id,
    SUM(day_time_span) AS ts
    FROM time_dim
    GROUP BY year_id
    ) b
    WHERE a.year_id = b.year_id
    UPDATE time_dim a
    SET year_end_date =
    (SELECT ed
    FROM
    (SELECT DISTINCT year_id,
    MAX(day_key) AS ed
    FROM time_dim
    GROUP BY year_id
    ) b
    WHERE a.year_id = b.year_id
    ;

  • 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

  • Disaggregate Periodic Data to Weekly Data (Modeling Time Dimension)

    Hi,
         We are using BPC MS Version 7.0. Our users plan at period level and I need to disaggregate periodic data to weekly data by looking up weeks from Time Dimension.
    Suppose if 2009.Jan  has 4 weeks I need the following result
    Periodic Data
    2009.Jan Acct1 1000$
    Weekly Data
    2009.Jan Wk1 Acct1 250$
    2009.Jan Wk2 Acct1 250$
    2009.Jan Wk3 Acct1 250$
    2009.Jan Wk4 Acct1 250$
    Can we model Time Dimension with two hiearchies to achieves this?
    Which is best way to dissaggrate? (Stored Proc or SSIS Pacakge or Script Logic) ?
    Thanks
    Raj

    An easy way to achieve this feature is to have the time dimension be weekly and do the spread on the input schedules before sending. 
    There would be two EVDREs (one refresh only of monthly data and the other send only of weekly data).  The data range of the monthly EVDRE would be input and where the user enters data.  The data range of the weekly EVDRE would be formulas (pointing to the monthly data and doing the correct division based on number of weeks in a month).  The user is inputting monthly data, but the schedule is sending the weekly values.
    The allocation will work as well, but I would suggest to create a weekly input node under each month to capture the monthly value and then spread to the weekly members.
    JAN
    |---WK Input
    |--- WK1
    |--- WK2
    |--- WK3
    |--- WK4

  • Optimizing order by query with multiple time dimensions

    Hello all,
    I have two time dimensions, one a standard date dimension (Year,Qtr, Month, Week, Day) the other a user defined Time dimension (All, Hour, Minute, Second).
    I am joining my cube with my time dimension using only the 'All' level, so that I can get a single record for the Day level in my Date dimension. Under these circumanstances there aren't many records in my sample data. Less than 100 dates, although at the lowest level(seconds) there are approx 2 million records.
    In order to get my results back in order I am ordering by the date dimension day_end_date. The query is taking longer than I would expect given that there aren't many records at the Day Level. How can I ensure that my query is ordering based only on the values in the current day_level and not all day_end_dates values in the underlying cube.

    Changed order, speed improved significantly.

  • Problem with time dimension aggregation

    I have a time dimension with 2 columns:Year and week
    I've created a hierarchy in it to drill down from the year to the week.
    when I report the sales in week level I have the right values but when I report the sales value in year level I don't have the right aggregation.Even if the year Level is a grand Total in the hierarchy.
    The problem is that for all the years I have the same value but when I add the week level to the report Then I have the right values.
    What could be the problem

    Hi,
    1.Actually the drill down Route path is not properly generated with your given key columns in herarchies.
    need to give correct key columns
    like year(YYYY)-->Week(wee should be the unique column for each and evry year)
    suppose:
    2000-sunday
    2001-sunday should be different
    so mostly the problem at your week column make the unique yearweek column as the key identifier at that level
    Every Week is unique cause the logical key is a combination of the year and the weeknumber
    2.if not you need to set individual levels for measures in content tab...
    you mean by the content tab the level tab when you doubleclick into the measure???
    Thanks

Maybe you are looking for