Table 239 lists limits related to block storage databases.
Table 239. Block Storage Database Limits
Artifact | Limits |
---|---|
Approximately 1,000,000 explicitly defined members in an Essbase outline. Hybrid Analysis and some uses of partitions enable access to many more members than those that are explicitly listed in an outline; the actual number of members accessible through the database is much greater. Longer member names, which can occur if using multibyte characters, decrease the number of members that are allowed. | |
Number of non-zero values in a dense data block in a block storage database | 32-bit and 64-bit: 228 -1 (268,435,455) |
Number of possible sparse blocks in a block storage database | The product of the stored member count of sparse dimensions cannot exceed the following values:
For instructions on how to calculate the number of possible sparse blocks in a block storage database, see Potential Number of Data Blocks. |
Number of possible cells per block in a block storage outline (cell limit when saving an outline) | 32-bit and 64-bit: 252 |
Number of Linked Reporting Objects in a block storage database | 32-bit and 64-bit: 2104 Note: When viewing or editing Linked Reporting Objects attached to cells, you may encounter a limitation prior to 2104, if the outline has non-stored members. If this occurs, the following error is displayed: "Error 1140013 Invalid Cell Address Entered" You can work around the limit by reordering the dimensions in the outline. |
Number of alias tables | 32 |
Number of parallel export threads | 1024 For information about how Essbase uses export threads, see the data export MaxL command for aggregate storage database and the EXPORTTHREADS configuration setting in the Oracle Essbase Technical Reference. |