Note 892296 describes new functions in BRCONNECT 7.00, which are mainly aimed at supporting the new Oracle 10g functions.40. Can entries in DBSTATC be transported?
The table DBSTATC is not connected to the SAP transport system. If you want to transport the DBSTATC table, you can do so with an explicit transport using the Workbench Organizer. (Refer to Note 211105).41. How can I reduce the scope of the statistics history? As of Oracle 10g, Oracle keeps old statistics for 31 days by default to maintain the option of being able to activate such statistics again using DBMS_STATS.RESTORE_TABLE_STATS. In particular cases, the history statistics can lead to a massive memory requirement in the SYSAUX tablespace. Segments with statistical data and a potentially large memory requirement are, for example: WRI$_OPTSTAT_IND_HISTORY I_WRI$_OPTSTAT_HH_ST I_WRI$_OPTSTAT_HH_OBJ_ICOL_ST WRI$_OPTSTAT_HISTHEAD_HISTORY I_WRI$_OPTSTAT_H_ST WRI$_OPTSTAT_HISTGRM_HISTORY I_WRI$_OPTSTAT_H_OBJ#_ICOL#_ST The history statistics data can become particularly intense if histogram statistics are created on a large scale, as in the BW environment, for example.
Related Questions
- Note 892296 describes new functions in BRCONNECT 7.00, which are mainly aimed at supporting the new Oracle 10g functions.40. Can entries in DBSTATC be transported?
- Is there a reference manual that describes the operation details and available CAS functions?
- What are the supporting functions of Commercial Banks?
