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
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
DSNU610I -<strong>DB2</strong>T 081 16:36:03.85 DSNUSUPD - SYSCOLDISTSTATS CATALOG UPDATE FOR <strong>BI</strong>9DB./<strong>BI</strong>C/EZGMA2 SUCCESSFUL<br />
DSNU604I -<strong>DB2</strong>T 081 16:36:03.85 DSNUSEOF - INDEXSPACE IS EMPTY<br />
DSNU610I -<strong>DB2</strong>T 081 16:36:03.85 DSNUSUCO - SYSCOLUMNS CATALOG UPDATE FOR <strong>BI</strong>9DB./<strong>BI</strong>C/EZGMA2~0 SUCCESSFUL<br />
DSNU610I -<strong>DB2</strong>T 081 16:36:03.85 DSNUSUIX - SYSINDEXES CATALOG UPDATE FOR <strong>BI</strong>9DB./<strong>BI</strong>C/EZGMA2~0 SUCCESSFUL<br />
DSNU604I -<strong>DB2</strong>T 081 16:36:03.87 DSNUSEOF - INDEXSPACE IS EMPTY<br />
DSNU610I -<strong>DB2</strong>T 081 16:36:03.87 DSNUSUCO - SYSCOLUMNS CATALOG UPDATE FOR <strong>BI</strong>9DB./<strong>BI</strong>C/EZGMA2~040 SUCCESSFUL<br />
DSNU610I -<strong>DB2</strong>T 081 16:36:03.87 DSNUSUIX - SYSINDEXES CATALOG UPDATE FOR <strong>BI</strong>9DB./<strong>BI</strong>C/EZGMA2~040 SUCCESSFUL<br />
DSNU604I -<strong>DB2</strong>T 081 16:36:03.87 DSNUSEOF - INDEXSPACE IS EMPTY<br />
DSNU610I -<strong>DB2</strong>T 081 16:36:03.87 DSNUSUCO - SYSCOLUMNS CATALOG UPDATE FOR <strong>BI</strong>9DB./<strong>BI</strong>C/EZGMA2~050 SUCCESSFUL<br />
DSNU610I -<strong>DB2</strong>T 081 16:36:03.87 DSNUSUIX - SYSINDEXES CATALOG UPDATE FOR <strong>BI</strong>9DB./<strong>BI</strong>C/EZGMA2~050 SUCCESSFUL<br />
DSNU604I -<strong>DB2</strong>T 081 16:36:03.87 DSNUSEOF - INDEXSPACE IS EMPTY<br />
DSNU610I -<strong>DB2</strong>T 081 16:36:03.87 DSNUSUCO - SYSCOLUMNS CATALOG UPDATE FOR <strong>BI</strong>9DB./<strong>BI</strong>C/EZGMA2~060 SUCCESSFUL<br />
DSNU610I -<strong>DB2</strong>T 081 16:36:03.88 DSNUSUIX - SYSINDEXES CATALOG UPDATE FOR <strong>BI</strong>9DB./<strong>BI</strong>C/EZGMA2~060 SUCCESSFUL<br />
DSNU604I -<strong>DB2</strong>T 081 16:36:03.88 DSNUSEOF - INDEXSPACE IS EMPTY<br />
DSNU610I -<strong>DB2</strong>T 081 16:36:03.88 DSNUSUCO - SYSCOLUMNS CATALOG UPDATE FOR <strong>BI</strong>9DB./<strong>BI</strong>C/EZGMA2~070 SUCCESSFUL<br />
DSNU610I -<strong>DB2</strong>T 081 16:36:03.88 DSNUSUIX - SYSINDEXES CATALOG UPDATE FOR <strong>BI</strong>9DB./<strong>BI</strong>C/EZGMA2~070 SUCCESSFUL<br />
DSNU604I -<strong>DB2</strong>T 081 16:36:03.88 DSNUSEOF - INDEXSPACE IS EMPTY<br />
DSNU610I -<strong>DB2</strong>T 081 16:36:03.88 DSNUSUCO - SYSCOLUMNS CATALOG UPDATE FOR <strong>BI</strong>9DB./<strong>BI</strong>C/EZGMA2~080 SUCCESSFUL<br />
DSNU610I -<strong>DB2</strong>T 081 16:36:03.88 DSNUSUIX - SYSINDEXES CATALOG UPDATE FOR <strong>BI</strong>9DB./<strong>BI</strong>C/EZGMA2~080 SUCCESSFUL<br />
DSNU620I -<strong>DB2</strong>T 081 16:36:03.89 DSNUSEOF - RUNSTATS CATALOG TIMESTAMP = 2007-03-22-16.36.00.422387<br />
DSNU010I 081 16:36:04.01 DSNUGBAC - UTILITY EXECUTION COMPLETE, HIGHEST RETURN CODE=0<br />
> connection: DEFAULT <strong>DB2</strong> User: <strong>SAP</strong>R3<br />
Since some specific RUNSTATS options are used <strong>for</strong> <strong>BI</strong> tables, statistics should<br />
not be created <strong>for</strong> <strong>SAP</strong> <strong>BI</strong> systems <strong>using</strong> external tools. Use the “RUNSTATS on<br />
objects needing new statistics” option in the planning calendar (DB13) to update<br />
the <strong>DB2</strong> statistics. We recommend that you schedule this to run daily or at least<br />
once a week, preferably at night. Since the <strong>DB2</strong> statistics <strong>for</strong> <strong>BI</strong> programs are<br />
already updated automatically <strong>for</strong> most <strong>BI</strong> tables, the DB13 statistics update<br />
should be very quick.<br />
Some additional comments:<br />
► RUNSTATS on the partition level. For per<strong>for</strong>mance reasons, <strong>SAP</strong> <strong>BI</strong> uses<br />
only the PART option of RUNSTATS if the partitioned table has more than<br />
one million rows.<br />
► Call RUNSTATS only if necessary means that RUNSTATS is only called if the<br />
old database statistics need to be refreshed. For this, the real time statistics<br />
(RTS) data are compared against the old statistics. If more than 10% of the<br />
data has been changed or if the table is small (fewer than 1000 rows),<br />
RUNSTATS is called again.<br />
More details are described in <strong>SAP</strong> note 915398. Additionally, this note describes<br />
the input parameter of the above-used function module<br />
RSDU_ANALYZE_TABLE_<strong>DB2</strong>.<br />
44 <strong>Best</strong> <strong>Practices</strong> <strong>for</strong> <strong>SAP</strong> <strong>BI</strong> <strong>using</strong> <strong>DB2</strong> 9 <strong>for</strong> z/<strong>OS</strong>