Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

What pitfalls and exceptions are associated with the mechanisms for specifying the tablespace and storage parameters?

April 26, 2017associated exceptions mechanisms parameters pitfalls specifying storage tablespace

0

Posted

What pitfalls and exceptions are associated with the mechanisms for specifying the tablespace and storage parameters?

1 Answer

0

Posted

Even though it seems as though you have set up user-specific values and technical settings correctly, a number of SAP and Oracle patterns of behavior may result in the wrong tablespace or storage parameters being used: Depending on the release and patch status, PSA tables in BW (naming convention: /BI*/B*) follow their own rules with regard to tablespace and storage parameters. For more information, see Notes 639930 and 639941. New partitions for locally partitioned indexes in BW are automatically created if the relevant table gets new partitions. The tablespace in which the new index partitions are created cannot be explicitly specified. Instead, the default tablespace specified when the index is created is always used. Alternatively, if a default tablespace was not specified, the table tablespace is used. This may cause problems after moving indexes to another tablespace, for example, if the default tablespace was not also adjusted (see the BRSPACE bug from Note 822936, for example).