07.02.2013 Views

Best Practices for SAP BI using DB2 9 for z/OS - IBM Redbooks

Best Practices for SAP BI using DB2 9 for z/OS - IBM Redbooks

Best Practices for SAP BI using DB2 9 for z/OS - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

In our example, our repartitioning process gave an error on step<br />

REORG_EFACT (highlighted with a red bullet in the example) where it tried to<br />

execute a reorganization. This type of error can be fixed by applying <strong>SAP</strong> note<br />

842792, which must be implemented by the database administrator. Once the<br />

<strong>SAP</strong> note is applied, you can restart that step and your repartitioning process<br />

then runs to completion.<br />

As in Figure 6-11, double-clicking any of the steps in the monitor allows you to<br />

retrieve more details on the step.<br />

Figure 6-11 InfoCube E- fact table (/<strong>BI</strong>C/EZ<strong>BI</strong>NFO1) be<strong>for</strong>e repartitioning<br />

Figure 6-11 also shows what the InfoCube E- fact table looked like be<strong>for</strong>e we did<br />

the complete repartitioning of the InfoCube. You see that the table has no<br />

partitions present. Executing transaction SE14 and entering the table name<br />

(which in our example is /<strong>BI</strong>C/EZ<strong>BI</strong>NFO1) will show this. Once you are on the<br />

window giving you the table in<strong>for</strong>mation, select Storage parameters and you will<br />

be presented with the window shown in the example.<br />

Chapter 6. <strong>Best</strong> practices <strong>for</strong> InfoCubes 85

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!