Solution : https://service.sap.com/sap/support/notes/722188 (SAP Service marketplace login required)
Summary :
This SAP Note explains partitioning in database management, focusing on how it separates data into logical subsets. The note details the partitioning of tables and indexes, with possible configurations like non-partitioned tables with partitioned relevant indexes, and allows for up to 64,000 partitions. It highlights how partitioning enhances administration, aids in performance optimization by facilitating operations on partitions directly, and how it impacts various types of queries. The note also discusses Oracle syntax for creating partitioned objects and handling common errors associated with partition operations, like ORA-014508 and ORA-14400. Different partitioning types, including range, list, and hash, are explained alongside methods to identify and manage partitions using Oracle views, such as DBA_TAB_PARTITIONS and DBA_IND_PARTITIONS. Additionally, it specifies that normal SAP R/3 systems do not have partitioned objects by default, though some InfoCube tables in BW are partitioned.
Key words :
logmnr_ts$logmnr_type$logmnr_user$logstdby$apply_progress, jan 01 2002 - dec 31 2002 -> partition 1column year, jan 01 2003 - dec 31 2003 -> partition 2column year, jan 01 2004 - dec 31 2004 -> partition 3 list partitioning, oracle9i database concepts-> 11 partitioned tables, avoid redo log data, generate redo log data, oracle store administrative information, oracle stores administrative information, relevant index partitioned table partitioned
Related Notes :
913862 | TDL: Partitioning transaction data tables |
859841 | Deinstallation of Oracle Partitioning software option |
832343 | FAQ: Clustering factor |
742243 | General table partitioning as of SAP_BASIS 46C |
666061 | FAQ: Database objects, segments and extents |
541538 | FAQ: Reorganization |
514178 | ORA-14508 when validating partitioned tables |
176754 | Problems with CBO and RBO |
105047 | Support for Oracle functions in the SAP environment |