Fragmentation has a number of potential causes. Identify two.

Question

Options

• ADeleting member from a sparse dim
• BDeleting member from a dense dim
• CRenaming a member
• DRenaming an alias
• ESubmitting data/deleting data frequently (like in budget applications)

• A
  6% (2)
• B
  81% (25)
• C
  10% (3)
• D
  3% (1)

Explanation

Fragmentation is unused disk space. Fragmentation is created when Essbase writes a data block to a new location on disk and leaves unused space in the former location of the data block. Block size increases because data from a data load or calculation is appended to the blocks; the blocks must therefore be written to the end of a data file." Fragmentation is likely to occur with the following: Read/write databases that users are constantly updating with data (E) Databases that execute calculations around the clock Databases that frequently update and recalculate dense members (B) Data loads that are poorly designed Databases that contain a significant number of Dynamic Calc and Store members Databases that use an isolation level of uncommitted access with commit block set to zero You can prevent and remove fragmentation: To prevent fragmentation, optimize data loads by sorting load records based upon sparse dimension members Perform an export of the database, delete all data in the database with CLEARDATA, and reload Force a dense restructure of the database

No community discussion yet for this question.