Cumulative and levels

Hi,
I am a bit confused about cumulative and levels. When I backup using RMAN, and specify incremental cumulative with level = 2 every day, am I not backing everything that has changed since level 0 (or a full backup done over weekend) every day?.
Why should I concern my self with level at all ?. I just want to backup all incremental changes that happened every single day during the week so that I can recover the instance with using two backups. Incremental cumulative means just that right ? Why should I specify level?
Pls clarify my confusion.
Thanks
Vissu

Hi,
Cumulative values are those key figures that are cumulated using all characteristics, thus also using time.
Non-cumulative values are those key figures that are measured in relation to a period in time; Non-cumulative values are summarized over time using so-called exception aggregation.
In Inventory, When you initialize the stock by using BX Data source. It will bring the current status of the stock by calculating the past transactions happens in all the storage locations.
After loading the Data into Cube you compress the cube with Marker update, then system will take a reference point for the marker. Next when you load BF for the historical data, you compress with "No marker update". This may not be necessary in all the cases. If the client requires reporting on the past data you need to extract this. This time you run the info package with init Delta. If historical data is not required you can run the info pack INIT t without Data transfer.
In the above case you use No marker update, because you have initialized the stock by calculating all the historical data and then you are loading historical data, there would be data mismatch happen to avoid that use no marker so that it will not add to the reference point. Later you can run the delta loads by using BF data source. This time you need to use "Marker update" because all the delta movements are new they should be updated to reference point. Similarly UM also With marker updated for Price revaluations. Why Reference point: When you use Non Cumulative KF in the Cube, During query execution the data will come from Reference point which is set by marker update
Regards,

Similar Messages

RMAN Cumulative and differential level 1taking too much time

hi,
I am attempting to HOT backup my 600 GB database to backup into Tape using NMO 5 EMC Networker 7.6.
My networker server is on Win Serv 2003.
My oracle database is on RHEL 4.5 Architecture ia64
Oracle DB Version 10.2.0.4.0
Using ASM
Using EMC Storage as Databse storage
Using tape backup media type LTO-Ultrium-5
No of chaneels used same for bothLevel 0 & 1 is 4
there are 60 Datafiles fior the database
i am atttempting incremental backup[Hot] backup
for Incrementa Level 0 is taking 90 Minutes to complete.
BUT leve1 backup [Both differential and cumulative] are taking almost the same time as taken for Level 0 backup
almost 80Mins.
but the backup Set size for Level 0 is almost 500 GB and Sizes for any Level 1 backup not more than 200MB.
i am confused if both LEVEL 0 AND LEVEL 1 BACKUP should take the same span of time.
please help to reduce the time to complete the Level 1 backups..
thanks in advance

RMAN incremental level 1 and up will have to verify every block in the data files to identify if any modifications have occurred. The time it takes to complete the incremental backup will depend on how much changed. Are you using the latest patches? There are known bugs that can affect performance problems with RMAN backup and recovery. Otherwise, check the Oracle documentation to troubleshoot RMAN.
Block change tracking as already mantioned, introduced in 10g, can greatly speed up your incremental level 1 and up backups.
From what I understand:
SQL> ALTER DATABASE ENABLE BLOCK CHANGE TRACKING USING FILE '/mydir/rman_change_track.f';
As soon as block change tracking is enabled, Oracle starts to record every block that updates. The information is stored in a bitmap inside the BCT file. Every incremental backup causes a bitmap swtich in the BCT file.
If there exists a previous bitmap beside the current bitmap, then an incremental level 1 backup will only backup the blocks according to the current bitmap. Incremental level 1 backups are differential backups by default. If there is no previous bitmap, the RMAN backup will perform a conventional scan of the database as usual.
The bitmap logic applies also to cumulative level 1 incremental backups, which will use all the bitmaps recorded since the last bitmap switch from a level 0 incremental backup. Due to the limit of 8 bitmaps, a cumulative incremental level 1 backup will have to perform a conventional scan of the database, if you make a level 0 database backup followed by 7 differential incremental backups.

Adding Cumulative and Non Cumulative Key Figure

Hi All,
Can we add Cumulative and Non Cumulative KF in a query and display the resuly.
regards,
Jeet

Yes, you can.
Cumulative KF at query level are same as non cumulative.
Hope it helps.
regards

Cumulative and Non-cumulative KFs

Guys,
so I am confused about cumulative/Non-cumulative keyfigures. I read what it says about them on help.sap.com
Flow/non-cumulative value
You can select the key figure as a cumulative value. Values for this key figure have to be posted in each time unit, for which values for this key figure are to be reported.
Non-cumulative with non-cumulative change
The key figure is a non-cumulative. You have to enter a key figure that represents the non-cumulative change of the non-cumulative value. There do not have to be values for this key figure in every time unit. For the non-cumulative key figure, values are only stored for selected times (markers). The values for the remaining times are calculated from the value in a marker and the intermediary non-cumulative changes.
Non-Cumulative with inflow and outflow
The key figure is a non-cumulative. You have to specify two key figures that represent the inflow and outflow of a non-cumulative value.
For non-cumulatives with non-cumulative change, or inflow and outflow, the two key figures themselves are not allowed to be non-cumulative values, but must represent cumulative values. They must be the same type (for example, amount, and quantity) as the non-cumulative value."
and also checked a few threads on sdn but still a little confused about their purpose.
Can someone tell me when do we use which one?
Thanks,
RG.

Hi Ram,
Cummulative & Non Cummulative Key Figures :
Basically the key figures are of two types cumulative and non cumulative.
Cumulative are the normal one which you use always and they always bring the new values of the key figures in the delta that is if suppose A has value 10 and after change the new value is 20 then you will use cumulative key figures there, and your delta( new value) will bring 20.
but suppose your key figures field only the change in the prior value that is in this case the delta in the key figure value will bring 10 (20-10- change of 10 )as new value in the key figure A then you will have to model it through the non cumulaitve key figures.
Now
1) Cumulative is for the first case that is if the key figure alwyas brings the new values of the key figure and not the change sin the key fiures value.
2)NCum. value with NCUM value change:
In this case ther is only one field which brings the changes for a particualr key figure and you ahve to define that key figure as non cumulative.
Ex: In case of stock only one filed brings both ingoing value and outgoing value so 10 ,-4,100,-34.....
In this case you will this option and use the key figure here in the space provided.
3) In this case you haev two separate key figures one for the inflow of stocks and one for the outflow of the stocks.
you use one key figure for the inflow and one key figure for the outflow.
The main key figure autiomatically takes care of the logic and gives the correct output upon the summation
net value of stocks( inflow- outflow).
Also do remember in this case the key figure for inflow and out flow are the basic key figures that is cumulative key figures.
A non-cumulative is a non-aggregating key figure on the level of one or more objects that is always displayed in relation to time. Examples of non-cumulatives include headcount, account balance and material inventory. here the aggregation of key figure is based on the another info object
There are two different ways to define non-cumulative key figures:
u2022 Non-cumulative key figure with non-cumulative changes:
Before you can define the non-cumulative key figure, an additional cumulative key figure containing the non-cumulative change must exist as an InfoObject.
u2022 Non-cumulative key figure with inflows and outflows
There has to be two additional cumulative key figures as InfoObjects for non-cumulative key figures - one for inflows and one for outflows. The cumulative key figures have to have the same technical properties as the non-cumulative key figure, and the aggregation and exception aggregation have to be SUM.
Features of non-cummulative key figures
A non-aggregating key Figure.
Records are not summarized for Reporting
Exception Aggregation is being applied on these key figures on the level of one or more info objects usually with time .
Examples: Head Count, Account balance, Material stock
consider simple senario
Date Net Stock Quantity Sales Revenue
01.02.2005 40 1000
02.02.2005 50 2000
03.02.2005 25 3000
this is the query output if stock quantity has treated as cummulative and non-cummulative key figures
if stock quantity taken as a cummulative key figure
Date NET STOCK QUANTITY SALES REVENUE
01.02.2005 30 1000
02.02.2005 50 2000
03.02.2005 20 3000
RESULT 100 6000
in the above result the key figure has aggregated to the total value that wont give sense to the net stock quantity
if stock quantity taken as non-cummulative key figure
Date Net Stock Quantity (LAST) Sales Revenue
01.02.2005 30 1000
02.02.2005 50 2000
03.02.2005 20 3000
RESULT 20 6000
Hope it helps you.
Thanks & Regards,
SD

Larger backups for cumulative incremental level 1 backups

I am noticing some strange behaviour for backup of data files in the RMAN cumulative incremental level 1 backup for certain days. I would explain that with an elaboration- the cumulative backup sizes are around 2GB, 19GB, 19GB, 1GB for the dates of 10th Dec, 5th Dec, 3rd Dec and 28th Nov respectively.
Can there be so much difference between the values of backup size for the RMAN cumulative incremental level 1 backup as they are fluctuating from 19GB->1GB?
I hope, my question is clear.
Please revert with the reply to my query.
Regards

975148 wrote:
Thanks for your reply. Level 0 backup happened twice between 5th Dec and 10th Dec. I guess, a block which has changed multiple times would be backed up once with all the changes done in a backup on a particular day. The same changes should get reflected in the subsequent level 0 backup.
Regards
Yes, obviously any backup (of any kind, of any product) is only capable of backing up the state of things as they exist at the time of the backup.
The recoverability of "intermediate" states (say a given block was modified 5 times between backups, the next backup only gets the 5th state of the block) is done by applying redo - archived or online, as is needed.
So to make an example to replicate what you report
Day 1 - backup level 0
- block # 1 modified
Day 2 - backup level 1 - backs up Block #1 - backup size 8k
- block # 1 modified
- block # 2 modified
- block # 1 modified
- block # 3 modified
- block # 1 modified
- block # 4 modified
Day 3 - backup level 1 - backs up Blocks 1,2,3,4 - backup size 32k
- block # 5 modified
- block # 2 modified
- block # 7 modified
- block # 3 modified
- block # 6 modified
- block # 4 modified
Day 4 - backup level 1 - backs up Blocks 1,2,3,4,5,6,7 - backup size 56k
- block # 5 modified
Day 4 - backup level 1 - backs up Blocks 1,2,3,4,5,6,7 - backup size 56k
Day 6 - backup level 0 - all blocks - size ???
- block # 3 modified
Day 7 - backup level 1 - backs up block 3 - backup size 8 k

Difference between cumulative and non-cumulative key figures

Hi,
What is the difference between cumulative and non-cumulative key figures and under what conditions they are used. What is snapshort and where it is used.

Hi.............
Basically the key figures are of two types cumulative and non cumulative.
Cumulative are the normal one which you use always and they always bring the new values of the key figures in the delta that is if suppose A has value 10 and after change the new value is 20 then you will use cumulative key figures there, and your delta( new value) will bring 20.
but suppose your key figures field only the change in the prior value that is in this case the delta in the key figure value will bring 10 (20-10- change of 10 )as new value in the key figure A then you will have to model it through the non cumulaitve key figures.
Now
1) Cumulative is for the first case that is if the key figure alwyas brings the new values of the key figure and not the change sin the key fiures value.
2)NCum. value with NCUM value change:
In this case ther is only one field which brings the changes for a particualr key figure and you ahve to define that key figure as non cumulative.
Ex: In case of stock only one filed brings both ingoing value and outgoing value so 10 ,-4,100,-34.....
In this case you will this option and use the key figure here in the space provided.
3) In this case you haev two separate key figures one for the inflow of stocks and one for the outflow of the stocks.
you use one key figure for the inflow and one key figure for the outflow.
The main key figure autiomatically takes care of the logic and gives the correct output upon the summation
net value of stocks( inflow- outflow).
Also do remember in this case the key figure for inflow and out flow are the basic key figures that is cumulative key figures.
A non-cumulative is a non-aggregating key figure on the level of one or more objects that is always displayed in relation to time. Examples of non-cumulatives include headcount, account balance and material inventory. here the aggregation of key figure is based on the another info object
There are two different ways to define non-cumulative key figures:
Non-cumulative key figure with non-cumulative changes:
Before you can define the non-cumulative key figure, an additional cumulative key figure containing the non-cumulative change must exist as an InfoObject.
Non-cumulative key figure with inflows and outflows
There has to be two additional cumulative key figures as InfoObjects for non-cumulative key figures - one for inflows and one for outflows. The cumulative key figures have to have the same technical properties as the non-cumulative key figure, and the aggregation and exception aggregation have to be SUM.
Features of non-cummulative key figures
A non-aggregating key Figure.
Records are not summarized for Reporting
Exception Aggregation is being applied on these key figures on the level of one or more info objects usually with time .
Examples: Head Count, Account balance, Material stock
consider simple senario
Date Net Stock Quantity Sales Revenue
01.02.2005 40 1000
02.02.2005 50 2000
03.02.2005 25 3000
this is the query output if stock quantity has treated as cummulative and non-cummulative key figures
if stock quantity taken as a cummulative key figure
Date NET STOCK QUANTITY SALES REVENUE
01.02.2005 30 1000
02.02.2005 50 2000
03.02.2005 20 3000
RESULT 100 6000
in the above result the key figure has aggregated to the total value that wont give sense to the net stock quantity
if stock quantity taken as non-cummulative key figure
Date Net Stock Quantity (LAST) Sales Revenue
01.02.2005 30 1000
02.02.2005 50 2000
03.02.2005 20 3000
RESULT 20 6000
Hope this helps you..............
Regards,
Debjani................
Edited by: Debjani Mukherjee on Sep 15, 2008 7:22 AM

What are the "Profile" and "Level" Settings in AME?

One thing I never understood is the option for the Profile and Level when I'm exporting a clip in AME. Not sure if those are options for most codecs but it is for the MainConcept H.264 Video Codec. For Profile, there is an option of "Baseline", "Main", and "High". For Level, starting from 3.1 and up, it's 3.1, 3.2, 4.0, 4.1, 4.2, 5.0, 5.1. I don't know what these are and therefore don't know which to choose. I know that the level has something to do with resolution so if I'm exporting in 720p, which level should I choose?
**While on the video encoding topic, in terms of quality, best to worst, what would the order be for the types of bitrates? Is it VBR 2-pass, CBR, then VBR 1-Pass?
-Sorry if this is a bit off-topic for Premiere CS4. There just wasn't any specific location for AME or Video-encoding..

Profiles outline/suggest certain encoding/decoding capabilities of a given video compression standard, like H.264. For example, the High profile enables B-frames and CABAC encoding. Levels are a means of ensuring that a hardware decoder can properly decode a stream. For example, an iPod can play back Baseline profile, Level 3.0 encoded video, but nothing higher. Higher profiles and levels enable other hardware, like Blu-Ray players. For the most part, you can ignore levels when encoding for computer playback, and only concern yourself with profile. I pretty much stick with [email protected]
The link Eddie posted has a ton of information, but here's a good article from Jan Ozer that puts it in more accessible terms.

Default Pay scale group and Level in infotype-0008

Hi,
While hiring should display the default Pay scale group and Level in infotype-0008 or the pay scale group and level can default from the Job or position. Itu2019s possible? Thanks in advance.
Regards

No there is no standard Feature to default PSG and PSL. TARIFF is for PSA and PST.
Wait for some body may have some information.
Afrasyab

Defaulting PayScale Group and Level in IT0008.

The System is configured as that the Payscale Group and Level will get defaulted in IT0008 from the Planned Compensation maintained for the Job.
This is working fine for all personnel areas except one.
Can anyone pls explain what all tables/SPRO nodes I have to check for the same?

Hi,
Check the Indirect valuation A, B, C & D config in the Reiumbursement Allownace & Perqusities( RAP's )config for the combination of PSArea, PSType, PSGroup, PSlevel
Regards,
Hemant V. Mahale

Cumulative and Non Cumulative Keyfigures

Hi,
What are Cumulative and Non Cumulative Keyfigures..? and
what is the lik betwqeen these keyfigures and the option " NO MARKER UPDATE " in the manage tab of infocube?
Can you please tell eloborately?
Regards
Naresh.

Hi,
Cumulative values are those key figures that are cumulated using all characteristics, thus also using time.
Non-cumulative values are those key figures that are measured in relation to a period in time; Non-cumulative values are summarized over time using so-called exception aggregation.
In Inventory, When you initialize the stock by using BX Data source. It will bring the current status of the stock by calculating the past transactions happens in all the storage locations.
After loading the Data into Cube you compress the cube with Marker update, then system will take a reference point for the marker. Next when you load BF for the historical data, you compress with "No marker update". This may not be necessary in all the cases. If the client requires reporting on the past data you need to extract this. This time you run the info package with init Delta. If historical data is not required you can run the info pack INIT t without Data transfer.
In the above case you use No marker update, because you have initialized the stock by calculating all the historical data and then you are loading historical data, there would be data mismatch happen to avoid that use no marker so that it will not add to the reference point. Later you can run the delta loads by using BF data source. This time you need to use "Marker update" because all the delta movements are new they should be updated to reference point. Similarly UM also With marker updated for Price revaluations. Why Reference point: When you use Non Cumulative KF in the Cube, During query execution the data will come from Reference point which is set by marker update
Regards,

Cumulative and Non Cumulative KF

Hi all,
 What are Cumulative and Non Cumulative KFs. How do we create it and where do we use them?
Thanks in advance,
Sekhar

Hai Sekhar...
Some of the Information Given Below......
Key figures:
1. Cumulative Vaules
2. Non Cumulative Values
Cumulative Values:
 Cumulative Values are Keyfigures for which Keyfigure Values are must posted in every time unit that reported on (= time period specific Values).
Example:
 Revenue
Non Cumulative Values:
 Non Cumulative Values are Keyfigures for which KeyFigures are only evaluated for selected time Periods.
Cumulative Keyfigures With Exception Aggregation:
 It's a 'normal' KF (with summation, min or max as aggregation behaviour), but you set some exception in this behaviour...for example, you can say that a KF, normally aggregated by 'summation', have to show the max value (or the average, or '0' or something else), that is the 'exception aggregation' when you use it in combination with 0DOC_DATE (or other char), that is the 'exception aggregation char reference'...in this case OLAP processor give to you the possibility to see your KF with different behaviour depending from you use 0DOC_DATE (in our example, MAX) or something else (SUMMATION).
Non Cumulative keyfigure with Associated Single Delta:
 If you have a stock KF that is fed from only one (other) movement KF that can assume positive and negative sign.
KF1 (initial) STOCK (non-***.) = 100
KF2 flow = -30
KF2 flow = 70
KF1 (final) STOCK (non-***.) = 140
Non-cumulative key figure with associated in and outflow:
 This is the case of 2LIS_03_BF KF stocks fields.
Here, we have the same situation in point 2, but you will have not only ONE flow KF, but TWO, one dedicated to in and another one dedicated to out !
You have to use this scenario if you have no KF that have positive and negative sign, but two KFs each one representing positive (in) and negative (out) logical sign!
KF1 (initial) STOCK (non-***.) = 100
KF2 (out))flow = 30
KF3 (in)flow = 70
KF1 (final) STOCK (non-***.) = 140
Website Addresses For Non Cumulative KeyFigures:
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html
http://help.sap.com/saphelp_nw04/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.html
http://help.sap.com/saphelp_bw31/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/content.html
http://help.sap.com/saphelp_erp2004/helpdata/en/d2/e0173f5ff48443e10000000a114084/content.html
Re: Non-Cumulative keyfigure example
Re: Types of non-cumulative keyfigures
/community [original link is broken]
http://help.sap.com/saphelp_bw32/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.html
/community [original link is broken]?forumID=131&threadID=29557&messageID=273049
/community [original link is broken]?forumID=131&threadID=111914&messageID=1248243
Assign Points If it Helps......
BalajeeKannan

Rman backup full then level 0 and level 1 Weekly

Please share your thoughts of backups.
Friday -> Take a full rman backup
Saturday -> Take a level 0 rman backup -> If recovery needed restore full and apply level 0 ?
Sunday -> Take a level 1 rman backup -> If recovery needed restore full and apply incremental 1 ?
Monday -> Take a level 2 rman backup -> If recover needed restore full and apply incremental 1 ?
Tuesday -> Take a level 1 rman backup -> If recover needed restore full and apply incremental 2 ?
Wednesday -> Take a level 2 rman backup -> If recovery needed restore full and apply incremental 1 ?
Thursday -> Take a level 1 rman backup -> If recovery need restore full and apply incremental 2 ?
Thanks

Please note that Full and level 0 backs are same...
Sunday -> Take a level 0 rman backup
Monday -> Take a level 1 rman backup
Tuesday -> Take a level 1 rman backup
Wednesday -> Take a level 2 rman backup
Thursday -> Take a level 1 rman backup
Friday-> Take a level 1 rman backup
Saturday -> Take a level 1 rman backup
Taking level 2 in the middle of the week, so that in case of any recovery you need ao apply changes since the last level 0, 1 or 2

Rman Level 0 and Level 1

Hi Everybody
I have to schedule my rman backup in the following manner.
1. Weekly once level 0 backup has to run
2. Rest of the other days level 1 backup has to run to disk
3. In between the week if we moved all backup to some other destination, the backup schedule has to run the level 0 instead of incremental backup automatically.
Then level 1 backup follows the level 0 backup.
Can anyone help me out how to schedule this task that satisfies the above three condition.

Thanks Aman
My manager he needs like windows backup that level 0 run at once in a week and level 1 follows till end of the week if we remove the backup or moved within the week then backup folder will be empty that time level 0 has to run instead of next incremental backup.
For example: I am schedule the rman by following manner by windows schedule task with script.
1. Level 0 is scheduled at saturday only
2. level 1 is scheduled from sunday to thursday.
My manager he don't want like this. level 0 should not run by day like saturday. he wants script will check the disk if level 0 is existing or not
if existing it will replace the level 0 with new one.
if not existing it will create the new one.
Is there possible to run level 0 and level 1 in the same script.

Defaulting Pay Scale Group and Level

Dear All,
Is there any way of defaulting Pay Scale Group and Level as they are fixed for Employee Sub-Groups?
Regards,
Ahsan Zaidi

TARIF: Default Pay Scale Type and Area in the Basic Pay
Object
Feature
Task
With this feature you control whether the default value is determined
     from the T001P from the personnel area and personnel subarea, or whether
     the default value is determined direct from the feature.
The return value must have the form xx/yy, when xx is the pay scale
     type, and yy the pay scale area.
If the feature returns SPACE as a value, then the value pay scale type
     or pay scale area is determined by table T001P. If the value does not
     equal SPACE, then this value will be taken as the pay scale type or pay
     scale area.
You can either enter return both values or only one of the two values.
     The missing value is determined from table T001P.

CAT2 - Payscale group and level

Does anyone know how to get project systems / finance to read the payscale group and levels from HR (instead of reading the rate from Project Systems - CP26).
Thanks.
(we have too many rates to store in Project systems and would prefer to store them in HR, any ideas?)

Hi Dianna,
Do you want to get payscale groups and level on CAT2 screen(time entry screen).
If thats your question,yes you can get that.For that you have change the settings of the CATS profile you are using.
The Display IMG path is
Cross-Application Components->Time Sheet->Time Recording--->Choose Fields
And in that click on DataEntry selection and uncheck the hide radio button for the Payscale area and group.
Hope this helps
Pl let me know if you have any questions

Cumulative and levels

Similar Messages

Maybe you are looking for