partition on cube

[Former Member]

Hi friends,

I have 23 cubes i want to know which cube is partitioned.

is there any way to find partitioned cubes

Regards

mohan

[Former Member · Accepted solution]

Hi Mohan,

You can find this through Transaction Code RSRV,

Which cube is partitioned and which is not.

Regards,

PJR.

[former_member195940 · Accepted solution]

Hi Mohan:

this might help you from OSS note:

Symptom

• You want to distribute your fact, PSA or ODS tables across several partitions and must therefore repartition your data.

• You want to check and, if necessary, correct the partitioning keys for your fact, ODS and PSA tables after a heterogeneous system migration from another database platform, for example.

• You migrated from BW 2.0B or 2.1C to BW 3.0B or 3.1C and now want to distribute your ODS and PSA tables across several partitions.

Other terms

Node group, database partition group, partitioning key, hash partitioning, DB6CONV, repartitioning

Reason and Prerequisites

You have tablespaces that appear on several DB6 partitions or you want to extend your database to that effect.

Solution

Use the new function modules in the RSDU_PART_DB6 function group to check partitioning keys and correct them, if necessary. You can call the function modules directly from transaction SE37 or embed them into separate reports.

The following three function modules check the partitioning keys of InfoCube, ODS and PSA tables:

• RSDU_CHECK_PKEY_FACTTAB_DB6: This function module checks the partitioning key for the fact table of an InfoCube. The import parameters are the InfoCube name and the name of the fact table. The export parameters are two Boolean values IS_VALID and IS_MISSING.IS_VALID is true if the partitioning key for the table is correct. IS_MISSING is true if the table does not have a partitioning key. The function module generates the GET_PKEY_FIELDS_FAILED exception if the system is unable to determine the correct partitioning key.

• RSDU_CHECK_PKEY_ODSTAB_DB6: This function module checks the partitioning key for an ODS table. The import parameters are the name of the ODS table and the table type (4 = activation queue table, 0 = active table and 3 = change log table). The export parameters are two Boolean values IS_VALID and IS_MISSING. IS_VALID is true if the partitioning key for the table is correct. IS_MISSING is true if the table does not have a partitioning key. Note that BW 2.0B and 2.1C do not support hash partitioning for ODS objects. It is therefore okay if your ODS tables in BW 2.0B and 2.1C do not have a partitioning key. On the other hand, all ODS tables in BW 3.0B and 3.1C should have a partitioning key even if the ODS tablespace is only on a DB6 partition. The function module generates the GET_PKEY_FIELDS_FAILED exception if the system cannot determine the correct partitioning key.

• RSDU_CHECK_PKEY_PSATAB_DB6: This function module checks the partitioning key for a PSA table. The import parameter is the table name. The export parameters are two Boolean values IS_VALID and IS_MISSING. IS_VALID is true if the partitioning key for the table is correct. IS_MISSING is true if the table does not have a partitioning key. Note that BW 2.0B and 2.1C do not support hash partitioning for PSA tables. It is therefore okay if your PSA tables in BW 2.0B and 2.1C do not have a partitioning key. On the other hand, all PSA tables in BW 3.0B and 3.1C should have a partitioning key even if the PSA tablespace is only on a DB6 partition.

The following three function modules check the partitioning key of all InfoCube, ODS and PSA tables in your BW system. The modules can repair incorrect or missing partitioning keys (optional). There are two ways to do this:

• If the table to be repaired is in a tablespace that was not yet distributed across several partitions, the partitioning key is immediately corrected or created using simple database resources.

• If the table to be repaired is in a tablespace that was already distributed over several partitions, you must convert the table again. The function modules then generate a request for the DB6CONV table conversion report. To perform the conversion, you must call DB6CONV and schedule the request for the table.

The BW object name, the table name, the status of the partitioning keys and the return code of the process are returned for each table.The status of the partitioning key can accept the following values:

• 0 = correct (correct partitioning key)

• 1 = missing (missing partitioning key)

• 2 = incorrect (incorrect partitioning key)

• 99 = undefined (undefined status)

The return code of the processing can accept the following values:

• 0 = successfully_repaired (the partitoning key was successfully repaired or it was correct)

• 1 = db6conv_jobentry_created (a conversion request was generated for DB6CONV)

• 2 = db6conv_not_installed (DB6CONV is required, but it was not installed)

• 3 = wrong_db6conv_version (DB6CONV is required, but it was not installed in Version 3.00 or higher)

• 4 = object_not_found (the table was not found on the database)

• 5 = db6conv_jobentry_crea_failed (the attempt to generate a conversion request for DB6CONV failed)

• 99 = failed (failed for unknown reasons)

The following are the three function modules:

• RSDU_CHKREP_PKEY_ALL_CUBES_DB6: This function module checks the partitioning keys for the fact tables for all InfoCubes in your BW system as well as the aggregates (optional). The function module can perform repairs (optional) or, if necessary, create table conversion requests for DB6CONV. The import parameters are two Boolean valuesI_PROC_AGGREGATES and I_PREP_REPAIR. If I_PROC_AGGREGATES is true, all aggregates are checked in addition to the InfoCubes. If I_PREP_REPAIR is true, repairs are performed on tables whose partitioning key is incorrect or missing (direct repair or DB6CONV requests). After processing, the E_T_TABLE_OK and E_T_TABLE_ERR export parameters contain the return values for the individual tables. E_T_TABLE_OK contains all of the correct tables whereas E_T_TABLE_ERR contains all tables whose partitioning key is missing or incorrect.

• RSDU_CHKREP_PKEY_ALL_ODS_DB6: This function module checks the partitioning keys for all ODS tables in your BW system. The function module can perform repairs (optional) or, if necessary, create table conversion requests for DB6CONV. The import parameter is a Boolean value I_PREP_REPAIR. If I_PREP_REPAIR is true, repairs are performed on tables whose partitioning key is incorrect or missing (direct repair or DB6CONV request). After processing, the E_T_TABLE_OK and E_T_TABLE_ERR export parameters contain the return values for the individual tables. E_T_TABLE_OK contains all of the correct tables whereas E_T_TABLE_ERR contains all tables whose partitioning key is missing or incorrect. Since BW 2.0B and 2.1C do not support hash partitioning for ODS objects, conversion requests for DB6CONV (in the case of a missing partitioning key) are only created if the ODS tablespace is on several DB6 partitions. In the same way, tables without a partitioning key in BW 2.0B and 2.1C are only added to E_T_TABLE_ERR if their tablespace is on several partitions. Otherwise, these tables are classified as being correct. In BW 3.0B and 3.1C, conversion requests are always created (in the case of a missing partitioning key) if the I_PREP_REPAIR parameter is set to true and tables without a partitioning key are added to E_T_TABLE_ERR. In the case of transactional ODS objects, the activation queue table is not checked because it was not created for these objects.

• RSDU_CHKREP_PKEY_ALL_PSA_DB6:This function module checks the partitioning keys for all PSA tables in your BW system. The function module can perform repairs (optional) or, if necessary, create table conversion requests for DB6CONV. The import parameter is a Boolean value I_PREP_REPAIR. If I_PREP_REPAIR is true, repairs are performed on tables whose partitioning key is incorrect or missing (direct repair or DB6CONV request). After processing, the E_T_TABLE_OK and E_T_TABLE_ERR export parameters contain the return values for the individual tables. E_T_TABLE_OK contains all of the correct tables whereas E_T_TABLE_ERR contains all tables whose partitioning key ismissing or incorrect. Since BW 2.0B and 2.1C do not support hash partitioning for ODS objects, conversion requests for DB6CONV (in the case of a missing partitioning key) are only created if the ODS tablespace is on several DB6 partitions. In the same way, tables without a partitioning key in BW 2.0B and 2.1C are only added to E_T_TABLE_ERR if their tablespace is on several partitions. Otherwise, these tables are classified as being correct. In BW 3.0B and 3.1C, conversion requests are always created (in the case of a missing partitioning key) if the I_PREP_REPAIR parameter is set to true and tables without a partitioning key are added to E_T_TABLE_ERR.

You can use transaction RSRV to check the partitioning keys for the fact tables for an InfoCube and its aggregates.For this, select the database test "Database parameter for tables of the *schema for InfoCubes".To repair the partitioning key, however, you must proceed as follows.

Furthermore, the RSDU_PART_DB6 function group contains the following new function module to repartition tables if the tables are to be distributed across several partitions:

• RSDU_REPARTITION_PREPARE_DB6: This function module creates requests for table conversion using DB6CONV for all tables in a tablespace or in a list of tables that you can specify as import parameters (optional). You must either specify the tablespace or the table list or both. If you specify the tablespace without a table list, all tables are processed in the tablespace. If you specify the tablespace together with a table list, only the tables from the table list that exist in the specified tablespace are processed. As an import parameter, you must specify a target tablespace into which the tables are to be moved. The target tablespace must differ from the source tablespace. Conversion in the same tablespace is not possible. If you specify a table list, the system can only process those tables that are not already in the target tablespace. The export parameters are a general return code for the function module and a table that contains the table name and processing return code for each database table that was processed. The return codes for the database tables correspond to the return codes listed further above. If a conversion request for DB6CONV already exists for a database table, the system cannot create a new request. In this case, the return code is 5 = db6conv_jobentry_crea_failed. If you receive this error for a table, check DB6CONV to see whether a request already exists.

The return code for the function module can accept the following values:

o 0 = succeeded (function module successfully executed)

o 2 = db6conv_installed (DB6CONV was not installed)

o 3 = wrong_db6conv_version (DB6CONV was not installed in Version 3.00 or higher)

o 4 = object_not_found (the specified source or target tablespace was not found)

o 99 = failed (failed for unknown reasons)

You can use the RSDU_REPARTITION_PREPARE_DB6 function module if you have added one or more partitions to your database and you want to redistribute one or all of the tables from one or more tablespaces. For this, you must create new database partition groups (node groups) and new tablespaces.

The function module does not check whether the partitioning keys of the tables to be converted are correct. In the case of missing partitioning keys, the tables are not processed if the target tablespace is on more than one partition. In the return table, the partitioning key for these tables is flagged as 1 = 'missing'.To correct partitioning keys that are incorrect or missing, use the check and repair modules described above.

For all table conversion operations, you require DB6CONV in Version 3.00 or higher (for DB6CONV, see note 362325).Refer to the DB6CONV documentation for information on how to modify and schedule the conversion requests created by the function modules.

To obtain the current function modules version described in this note, you must also implement note 666291 'DB6: Short dump in RSDU_REPARTITION_PREPARE_DB6, RSDU_CHKREP*'.

• BW2.0B

Import Support Package 34 for Release 2.0B (BW2.0B Patch 34 or SAPKW20B34) into your BW system.The Support Package will be available when note 0523193 with the short text "SAPBWNews BW 2.0B Support Package 34", describing this Support Package in more detail, is released for customers.

To provide information in advance, note 0523193 may already be available before the Support Package is released.However, the short text will still contain the words "preliminary version" in this case.

• BW2.1C

Import Support Package 26 for Release 2.1C (BW2.1C Patch 26 or SAPKW21C26) into your BW system.The Support Package will be available when note 0523205 with the short text "SAPBWNews BW 2.1C Support Package 26" is released for customers.

• BW3.0B

Import Support Package 16 for Release 3.0B (BW3.0B Patch 16 or SAPKW30B16) into your BW system.The Support Package will be available when note 0571698 with the short text "SAPBWNews BW 3.0B Support Package 16", describing this Support Package in more detail, is released for customers.

• BW3.1C

Import Support Package 10 for Release 3.1C (BW3.1C Patch 10 or SAPKW31C10) into your BW system.The Support Package will be available when note 0571720 with the short text "SAPBWNews BW 3.1C Support Package 10", describing this Support Package in more detail, is released for customers.

Refer to note 110934, which contains further information on BW Support Packages.

assign points if helpful

kalyan

[Former Member]

HI,

Check it in RSRV T - Code.

Thanks,

Shashi.

[Former Member]

Please find the below function modules which can be usefull for you.

<b>RSDU_CHECK_PKEY_FACTTAB_DB6</b> -- This function module checks the partitioning key for the fact table of an InfoCube.

<b>RSDU_CHECK_PKEY_ODSTAB_DB6</b>: This function module checks the partitioning key for an ODS table.

<b>RSDU_CHECK_PKEY_PSATAB_DB6:</b> This function module checks the partitioning key for a PSA table

Regards

Murali

[Former Member]

Hi,

Check this OSS note:648432.

Hope this helps.

Assign points if useful.

Venkat

[Former Member]

hi kiran,

pls tell me how to check this oss note

iam able to logon to service.sap.com

could u tell me how can i see the oss notes regarding the topics of bw.

thanks in advance

mahesh

[former_member184494]

Mahesh,

Log on to Service.sap.com/notes

Here you will need an SID to log in , this you can get from the project , usually a SID comes with the product and that would be used across the project.

As for seeing notes for BW , you can use the search facility for the same.

Arun

Assign points if useful

[Former Member]

Hey Arun

thanks but iam in a project and i have id and password given by company. when iam going to search options it is showing bw3.1,bw3.5 version doc but iam unable to access that. if u could give me url where i can find all the oss notes it will be really fine.

awaiting for ur reply boss

thanks

mahesh