Partitioning InfoCubes on BW 3.5

Hi all,
we are currently starting the process of partitioning two infocubes on our system.
FYI DB is Oracle 9.2 and it is BW 3.5.
The two Infocubes have been emptied of data and have been logically partitioned by CALMONTH over a year with a total of 14 partitions.
We are also going to physically partition these cubes, is this required, i.e. does physical and logical partitioning go together???
Does anyone know the work involved physically partitioning the cubes as I can't find any OSS notes???
Thanks for your help in advance,
Shane.

Physical Vs Logical Partitioning

Similar Messages

Partition InfoCubes for non-cumulatives

Hi,
I would like to partition inventory cube 0IC_C03 that consists of non-cummulatives. The partition was executed from 12.2007 to 12.2010. I would like to add partition to 12.2012 via option "Adding Partitions". There was error prompt that infocube for non-cummulative has to carry out by using option "complete repartitioning".
Can expert please share with me what would be the recoomendation in order to enter the correct value for complete repartitioning?
Thanks and regards,
Kang Ring

Hi,
Not able to select by Year, the only active option is 0CALMONTH.
Regards,
Kang Ring

Unable partitioning InfoCube

Hello, friends!
Can you help me.
I create InfoCube with 3 times characteristics:
0CALDAY
0CALMONTH
0CALYEAR.
I have activated this InfoCube, no data have been loading.
But I cant use option partitionng in extras menu in InfoCube maintening.
What should I do to acess this option?
I use NW2004S. Database Oracle 10.2.0.2.0.
Thanks.

Unfortunately, it does'nt help
In Edit mode in Standard InfoCube ( Not Real-time)? I can't use partioning.
May be it is because some system profile parameters ?

Delete InfoCube Index Question

Hi,
Before my data loads I have always dropped InfoCube Indexes. I recently Partitioned our largest InfoCube and now it seems that dropping the indexes takes forever so now I can't really drop the indexes during our daytime loads because it would take too long to delete and rebuild the indexes on this InfoCube.
Does anyone know if this is normal behavior for a partitioned InfoCube to take so long to drop and rebuild indexes?
Thanks for any ideas or thoughts!

Hey Kenneth,
Since you stated that this infocube was large, and you recently partitioned it, make sure you compress your requests . Also consider compressing with zero elimination as much as possible - this will reduce data size for indexing.
How big is the DB server this is running on? Are the DBAs looking at DB settings regarding this which could impact index creation time, e.g. ora init settings, temp space, index tablespaces, etc.
You might also need to delete unused indexes which are still existing on your cube.
Also, these index rebuilds should be running with No logging specified - which is default. But it might help to check and confirm once.
Other than this, OSS note 323090 might be worth checking for you.
Hope this helps!
Thanks,
Sheen

Design of infocube

Hi Experts
Good Day!
when i try to execute the query it taking lot of time and this query there no complex query also .i followed these are steps to improve the performance still not good . but my cube is contain almost 6 crore records
1, i created aggregats
2,every day we are deleting the indexes and creating the indexes .
3.when i try to partioing its giving error message the properties 0FISCVARNT should be constant .when i try change the properties it is disabled.can you please tell me how to enable this properties
actually the data is coming from the ODS . i plan split diffent years of data like 2006,2007,2008.after that i plan create infocubes each year and finally execute the queries on multicueb for underlying each year of infocube data.is it good design or i need change design parameter.can you please guide me on this issues
regards
RK

Hi Rama,
Check if u are using the proper steps in the paritioning based on Fiscal Period:
http://help.sap.com/saphelp_erp2005/helpdata/en/0a/cd6e3a30aac013e10000000a114084/frameset.htm
Partitioning infocube with multiple fiscal variants
To partition the cube double click the cube this will take you to the definition of the cube. Click on the extras button at the top of the screen. you will get a dropdown, there you can see Partition option, click on that you will get another window there you all time chars select on which you want to partition and continue.
you will get another popup window there you have to give Range.
When you activate the cube fact tble will be created in DB with number of partitions corresponding to your Range.
While you do this there should be no data in the cube.
Thanks
Assign points if this helps

Index Problem in Infocube

Hi BW lovers
I am having problem with the index in one of our cubes. This is the story:
1. I did a lot of compress on a cube with 41 000 000 records in. After that run DB statistics (ended up green).
2. After that I checked index in the performance tab and it was yellow.
3. I tried to repair index, and it did not help (still yellow)
4. Delete and created index again (still yellow)
5. I run a check in RSRV and there was one yellow saying "Index /BIC/FZHISTORY~900 type is BITMAP. Type NORMAL was expected". I tried to repair it but still the same problem.
6. I tried to run ABAP program SAP_INFOCUBE_INDEXES_REPAIR (still yellow)
7. Did all things in note 401242 (check DB02 etc)
Still yellow.... Anyone have a clue what to do?
Best Regards
/Pontus

I'm assuming this is an Oracle DB because of refrence to bitmap index.
The 900 index is an index that is added to the F fact table for InfoCubes wher you have specified they are to be partition (from the Extras menu option). This is an index on characteristic that was specified for partitioning (0CALMONTH or 0FISCPER). According to Note 217397, the index is supposed to be a bitmap index.
Partitioned Infocubes
There is an additional index for F facttables of partitioned infocubes in BW 3.x systems. Thereby it does not matter whether the infocube is standard or transactional. There is an additional bitmap index on the column of the F facttable that corresponds to the partitioning column of the E facttable This index's name is "900", i.e. "/BIC/F...~900" on the database.
So how do we reconcile your error msg and this Note? Msg saying it expected a Normal index and this Note saying it is supposed ot be bitmap?
This isn't a transactional cube is it?
Note 1024018 makes reference an earlier Note that indicates the 900 index was not included as part to of the rebuild index process at some previosu point, but the note it referenced didn't see, to clarify when the change was made. I would check and see if the 900 index actually gets rebuilt when you perform the repair.
Maybe you could have your DBA rebuild it if the Repair function is not doing it. Seems like some more OSS Note digging is in your future. Note 401242 - Problems with InfoCube or aggregate indexes - runs thru some diagnostic efforts you can pursue.
Note 1003360 - BW fact tables: Deleting index from process chain terminates - talks about a failure in PCs because the 900 index gets deleted twice.
Note sure what SP you're on - but since it looks like the 900 index has been a problem off and on, you'll have to see what Notes might be applicalable to your SP.

Logical Partition.

Hello All,
I have a lil knowledge about logical partition. Could you please send me some document related to logical partition?
Where and how it can be used in BW?
Thanks.

Hi ,
1.Partitioning the cube in both physical and logical way helps you to increase its performance on Queriying.
Partitioning InfoCubes Using the Characteristic 0FISCPER (At Infocube maintainance)
Prerequisites
When partitioning using 0FISCPER values, values are calculated within the partitioning interval that you specified in the InfoCube maintenance. To do this, the value for 0FISCVARNT must be known at the time of partitioning; it must be set to constant.
Procedure
1. The InfoCube maintenance is displayed. Set the value for the 0FISCVARNT characteristic to constant. Carry out the following steps:
a. Choose the Time Characteristics tab page.
b. In the context menu of the dimension folder, choose Object specific InfoObject properties.
c. Specify a constant for the characteristic 0FISCVARNT. Choose Continue.
2. Choose Extras -->DB Performance --> Partitioning. The Determine Partitioning Conditions dialog box appears. You can now select the 0FISCPER characteristic under Slctn. Choose Continue.
3. The Value Range (Partitioning Condition) dialog box appears. Enter the required data.
Pls chk the below link for partioning..
http://help.sap.com/saphelp_bw33/helpdata/en/33/dc2038aa3bcd23e10000009b38f8cf/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/0a/cd6e3a30aac013e10000000a114084/frameset.htm
Re: logical Vs physical partitions ?
Regarding Partitioning
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ce7fb368-0601-0010-64ba-fadc985a1f94
/message/4204952#4204952 [original link is broken]
How i can partioning the BW?
Partioning and ETable
What is the use of cube partition?
Re: logical Vs physical partitions ?
*Hope this helps*
Regards
CSM reddy

Logical Partition of Cube

Hi BW experts,
Can anyone explain the steps to create logical partitioning of Cube data?
I want to do it per fiscal year. If we create 05 cubes(Same structure) each for say fiscal year 04' 05'...08'
now how will the data flow into respective cubes.
Kindly explain the steps.
thanks,
Nipun Sharma
P.S. points will be rewarded.

Hi Nipun,
1.Partitioning the cube in both physical and logical way helps you to increase its performance on Queriying.
Partitioning InfoCubes Using the Characteristic 0FISCPER (At Infocube maintainance)
Prerequisites
When partitioning using 0FISCPER values, values are calculated within the partitioning interval that you specified in the InfoCube maintenance. To do this, the value for 0FISCVARNT must be known at the time of partitioning; it must be set to constant.
Procedure
1. The InfoCube maintenance is displayed. Set the value for the 0FISCVARNT characteristic to constant. Carry out the following steps:
a. Choose the Time Characteristics tab page.
b. In the context menu of the dimension folder, choose Object specific InfoObject properties.
c. Specify a constant for the characteristic 0FISCVARNT. Choose Continue.
2. Choose Extras -->DB Performance --> Partitioning. The Determine Partitioning Conditions dialog box appears. You can now select the 0FISCPER characteristic under Slctn. Choose Continue.
3. The Value Range (Partitioning Condition) dialog box appears. Enter the required data.
Pls chk the below link for partioning..
http://help.sap.com/saphelp_bw33/helpdata/en/33/dc2038aa3bcd23e10000009b38f8cf/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/0a/cd6e3a30aac013e10000000a114084/frameset.htm
Re: logical Vs physical partitions ?
Regarding Partitioning
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ce7fb368-0601-0010-64ba-fadc985a1f94
/message/4204952#4204952 [original link is broken]
How i can partioning the BW?
Partioning and ETable
What is the use of cube partition?
*pls assign points,if info is useful*
Regards
CSM reddy

Partitioning an active but uncompressed cube

Hello Community,
There are many posts on partitioning InfoCubes. I promise I have read all of them before asking this question -->
Partitioning for a fact table must be defined before you activate the InfoCube. It cannot be done afterwards.
But what if the cube has not been compressed yet ?
My hope is that the ability to partition any time up until the 1st fact-table compression has come with newer BW releases ?
The reason I have this hope is because partitioning affects only the E-fact tables. And, of course, the E-Fact remains empty until the 1st compression. (F-fact tables are automatically partitioned by the request-ID).
So why should it be impossible to define the partitioning if the E-Fact table is still empty ?
Another question : when working with the BW GUI, if it is indeed true that I must unload, partition, and reload the unpartitioned cubes before compressing them, what is lost or gained by skipping that process and simply compressing the unpartitioned cube followed by partitioning with database tools ?
Thanks!
Keith

Hi Keith,
Sorry, but you have to implement partitioning before the first data load - when the InfoCube is initially activated.
With regard to you second question, you could indeed do this but you will run into major issues if you need to activate the InfoCube again or do any maintenance on the InfoCube. The activation from BI could result in the activation of the E and F fact tables with differing definitions to the modified DB tables (effectively loosing the partition tables underneath). I have not tested this but it is a big possibility so I would advise care).
I hope this helps,
Mike.

Shadow tables that have been created via the new partitioning schema

Hi,
 Complete Partitioning :
 In a complete partitioning, the fact table of the infocube are fully converted using shadow
tables that have been created via the new partitioning schema.
 in the above Explanation what is the meaning of shadow tables which perform the
 partitioning of an info cube.

Hi
Shadow tables have the namespace /BIC/4F<Name of InfoCube> or /BIC/4E<Name of InfoCube>.
Complete Partitioning
Complete Partitioning fully converts the fact tables of the InfoCube. The system creates shadow tables with the new partitioning schema and copies all of the data from the original tables into the shadow tables. As soon as the data is copied, the system creates indexes and the original table replaces the shadow table. After the system has successfully completed the partitioning request, both fact tables exist in the original state (shadow table), as well as in the modified state with the new partitioning schema (original table). You can manually delete the shadow tables after repartitioning has been successfully completed to free up the memory. Shadow tables have the namespace /BIC/4F<Name of InfoCube> or /BIC/4E<Name of InfoCube>.
You can only use complete repartitioning for InfoCubes. A heterogeneous state is possible. For example, it is possible to have a partitioned InfoCube with non partitioned aggregates. This does not have an adverse effect on functionality. You can automatically modify all of the active aggregates by reactivating them.
Hope it helps and clear

Partitioning

Hi,
Can anyone tell me how you go about partitioning a fact table in 3.5?
Andy

You can partion the data based on the time characteristic available in your info-provider. If you have 0CALMONTH, 0FISCPER, 0CALWEEK in your info-provider then you can also partition based on these time characteristics.
From a perform,ance point of view partitioning by 0CALDAY is not recommended as it is going to create a huge number of partitions. If you have a date range over 2 months in the report then you are literally going to access 60 partitions to get that data which is not good. However if you partion by year it will be in one / two partion depending on the year and in 2 partitions if based on 0CALMONTH / 0FISCPER.
It is always recommended to partition by 0CALMONTH / 0FISCPER. You need to have these 2 chars in your cube if you want to partition your data based on these 2 characteristic.
To partition cube
Just right click on Infocube -> Change or doble click on the infocube to go to infocube maintenace. From the menu choose Extras ->Partitioning.
Partitioning:
http://help.sap.com/saphelp_nw04/helpdata/en/33/dc2038aa3bcd23e10000009b38f8cf/content.htm
Partitioning InfoCubes using the Characteristic 0FISCPER:
http://help.sap.com/saphelp_nw04/helpdata/en/0a/cd6e3a30aac013e10000000a114084/content.htm
infocube partitioning
Older versions of SQL database (prior to MS SQL Server 2005) does not support "Partition" this feature.
Oracle and Informix does support.. refer oss note: 869407 for more details.

Partition in production

Hi guys,
is it advisable to partition in production or do we need to transport the partitioning too...
if so how any help
your help will be greatly appreciated

Hi
Partitions in BW are of 2 types Logical Partitioning & Table (DB) Partitioning.
Following are the pros n cons of both
Logical Partitioning
1.     Pros
i.      Requires Multi-cube for an enterprise wide view
ii.      Multi-cubes facilitate parallel processing
iii.      Can be used in conjunction with database partitioning
iv.      Reduces the size of InfoCubes
1.     Cons
i.      Requires additional development (multi-cube, transitioning queries to multi-cubes)
ii.      Requires a change in existing documentation
iii.      Data model changes have to be implemented on each base data target
iv.      Challenging to keep all base target in sync
Database Partitioning
1.     Pros
i.      Partitioning Pruning for Query run-time
ii.      Improvement on query performance
iii.      InfoCube Compression by combining all requests into 1 request
1.     Cons
i.      The performance gain is only achieved for the partitioned InfoCube if the time dimension of the InfoCube is consistent. This means that with a partition using 0CALMONTH, all values of the 0CAL x characteristics of a data record have to match in the time dimension.
ii.      Limited ways to delete data since compression has occurred (Selective deletion or DBA manual deletion)
so u have to choose depending on ur requirement
And u have to do the Partition in production it cannot b transported
-Transaction SPRO (IMG)
-Business Information Warehouse > Links to Other Systems > Maintain Control Parameters for the Data Transfer
- OR Transaction RSCUSTV6
Hope this helps to solve ur question
Sonal...

Cube Partition

Hi,
Can anbody please explain as to what criteria is used to specify the MAX. NO OF PARTITIONS when partitioning a Cube.

Hi
By using partitioning you can split up the whole dataset for an InfoCube into several, smaller, physically independent and redundancy-free units. Thanks to this separation, performance is increased when reporting, or also when deleting data from the InfoCube.
Only certain database providers support this function (for example, ORACLE, INFORMIX). If you use a database that does not support this function, then this function is not provided by the BW system.
Integration
Prerequisites
You can only partition a dataset using one of the two partitioning criteria u2018calendar monthu2019 (0CALMONTH) or u2018fiscal year/period (0FISCPER). At least one of the two InfoObjects must be contained in the InfoCube.
If you want to partition an InfoCube using the fiscal year/period (0FISCPER) characteristic, you have to set the fiscal year variant characteristic to constant.
See Partitioning InfoCubes using the Characteristic 0FISCPER
Functions
When activating the InfoCube, the fact table is created on the database with one of the number of partitions corresponding to the value range. You can set the value range yourself.
You choose the partitioning criterion 0CALMONTH and determine the value range
from 01.1998
to 12.2003
6 years * 12 months + 2 = 74 partitions are created (2 partitions for values that lay outside of the range, meaning < 01.1998 or >12.2003).
You can also determine how many partitions are created as a maximum on the database for the fact table of the InfoCube.
You choose the partitioning criterion 0CALMONTH and determine the value range
from 01.1998
to 12.2003
You choose 30 as the maximum number of partitions.
Resulting from the value range: 6 years * 12 calendar months + 2 marginal partitions (up to 01.1998, from 12.2003) = 74 single values.
The system groups three months at a time together in a partition (meaning that a partition corresponds to exactly one quarter); In this way, 6 years * 4 partitions/year + 2 marginal partitions = 26 partitions are created on the database.
The performance gain is only gained for the partitioned InfoCube if the time dimension of the InfoCube is consistent. This means that all values of the 0CAL* characteristics of a data record in the time dimension must fit each other with a partitioning via 0CALMONTH.
In the following example, only record 1 is consistent. Records 2 and 3 are not:
Activities
In the InfoCube maintenance choose Extras ® Partitioning, and specify the value range. Where necessary, limit the maximum number of partitions. Note: You can only change the value range when the InfoCube does not contain any data.

Logical Vs physical partitions ?

Hello BW Experts,
What is the diff between the logical and physical partitions. The partitions that we do on a cube based on 0calmonth / 0fiscyear is that logical or physical.
Suggestions appreciated.
Thanks,
Kalyan

hi,
in bw, physical partitioning done on database level and logical partitioning done with multiprovider. cube partitioning with 0calmonth is physical partitioning.
take a look
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ce7fb368-0601-0010-64ba-fadc985a1f94
Database (or Physical) Partitioning
-Database tables are cut into smaller chunks (partitions)
-One logical database table
-Transparent for user
-Available for the following database management systems
Range Partitioning: ORACLE, Informix, IBM DB2/390
Hash Partitioning: IBM DB2/UDB
Database (or Physical) Partitioning
*Benefits
-Parallel accesses to partitions
-Read smaller sets of data Fast
-Deletion of partitions (DROP PARTITION instead DELETE FROM WHERE)
*Automatically Partitioned Database Tables (for Range Partitioning)
-InfoCube F-Fact table: partitioned by request
-PSA table: partitioned by request ODS
-Change Log: similar to PSA table
*User Defined Partitioning Criteria (for Range Partitioning)
-InfoCube E-Fact table
-Partition Criteria:
Time characteristics like month or fiscal period
-Note: Both fact tables are extended by the SID of the chosen time characteristic
MultiProvider (or Logical)
-Partitioning Possible partitioning criteria: year, plan/actual, regions, business area
-Parallel sub-queries are started automatically to basic InfoCubes

Steps for Repartitioning Infocube in BI7

Hi all,
Plaese give me detailed steps for Repartitioning Infocube which is having Data & not having partitions ( Before ) in BI 7.
2. Please provide significance of a) Adding Partitions
b) Merging Partitions
c) Complete Repartitioning Processing Options in the Repartitioning of Infoproviders Screen.
Points will assign.
Thanks & Regards,
Ram.

Hi Ram,
Repartitioning can be useful if you have already loaded data to your InfoCube, and:
1.You did not partition the InfoCube when you created it.
2. You loaded more data into your InfoCube than you had planned when you partitioned it.
3.You did not choose a long enough period of time for partitioning.
4.Some partitions contain no data or little data due to data archiving over a period of time.
Integration
All database providers support this function except DB2 for Linux, UNIX, Windows and MAXDB. For DB2 for Linux, UNIX and Windows, you can use clustering or reclustering instead. For more information, see Clustering .
Features
Merging and Adding Partitions
When you merge and add partitions, InfoCube partitions are either merged at the bottom end of the partitioning schema (merge), or added at the top (split).
Ideally, this operation is only executed for the database catalog. This is the case if all the partitions that you want to merge are empty and no data has been loaded outside of the time period you initially defined. The runtime of the action is only a few minutes.
If there is still data in the partitions you want to merge, or if data has been loaded beyond the time period you initially defined, the system saves the data in a shadow table and then copies it back to the original table. The runtime depends on the amount of data to be copied.
With InfoCubes for non-cumulatives, all markers are either in the bottom partition or top partition of the E fact table. Whether mass data also has to be copied depends on the editing options. For this reason, the partitions of non-cumulative InfoCubes cannot be merged if all of the markers are in the bottom partition. If all of the markers are in the top partition, adding partitions is not permitted. If this is the case, use the Complete Repartitioning editing option.
You can merge and add partitions for aggregates as well as for InfoCubes. Alternatively, you can reactivate all of the aggregates after you have changed the InfoCube. Since this function only changes the DB memory parameters of fact tables, you can continue to use the available aggregates without having to modify them.
SAP recommends that you completely back up the database before you execute this function. This ensures that if an error occurs (for example, during a DB catalog operation), the can restore the system to its previous status.
Complete Partitioning
Complete Partitioning fully converts the fact tables of the InfoCube. The system creates shadow tables with the new partitioning schema and copies all of the data from the original tables into the shadow tables. As soon as the data is copied, the system creates indexes and the original table replaces the shadow table. After the system has successfully completed the partitioning request, both fact tables exist in the original state (shadow table), as well as in the modified state with the new partitioning schema (original table). You can manually delete the shadow tables after repartitioning has been successfully completed to free up the memory. Shadow tables have the namespace /BIC/4F<Name of InfoCube> or /BIC/4E<Name of InfoCube>.
You can only use complete repartitioning for InfoCubes. A heterogeneous state is possible. For example, it is possible to have a partitioned InfoCube with non partitioned aggregates. This does not have an adverse effect on functionality. You can automatically modify all of the active aggregates by reactivating them.
Monitor
You can monitor the repartitioning requests using a monitor. The monitor shows you the current status of the processing steps. When you double-click, the relevant logs appear. The following functions are available in the context menu of the request or editing step:
Delete: You delete the repartitioning request; it no longer appears in the monitor, and you cannot restart. All tables remain in their current state. The InfoCube may be inconsistent.
Reset Request: You reset the repartitioning request. This deletes all the locks for the InfoCube and all its shadow tables.
Reset Step: You reset the canceled editing steps so that they are reset to their original state.
Restart: You restart the repartitioning request in the background. You cannot restart a repartitioning request if it still has status Active (yellow) in the monitor. Check whether the request is still active (transaction SM37) and, if necessary, reset the current editing step before you restart.
Background Information About Copying Data
By default, the system copies a maximum of six processes in parallel. The main process splits dialog processes in the background. These dialog processes each copy small data packages and finish with a COMMIT. If a timeout causes one of these dialog processes to terminate, you can restart the affected copy operations, after you have altered the timeout time. To do this, choose Restart Repartitioning Request.
Background Information About Error Handling
Even if you can restart the individual editing steps, you should not reset the repartitioning request or the individual editing steps without first performing an error analysis.
During repartitioning, the relevant InfoCube and its aggregates are locked against modifying operations (loading data, aggregation, rollup and so on) to avoid inconsistent data. In the initial dialog, you can manually unlock objects. This option is only intended for cases where errors have occurred and should only be used after the logs and datasets have been analyzed.
Transport
Since the metadata in the target system is adjusted without the DB tables being converted when you transport InfoCubes, repartitioned InfoCubes may only be transported when the repartitioning has already taken place in the target system. Otherwise inconsistencies that can only be corrected manually occur in the target system.
Activities
You can access repartitioning in the Data Warehousing Workbench using Administration, or in the context menu of your InfoCube.
You can schedule repartitioning in the background by choosing Initialize. You can monitor the repartitioning requests by choosing Monitor.
Hope this helps
Regards
Karthik

Partitioning InfoCubes on BW 3.5

Similar Messages

Maybe you are looking for