Limits

In This Section:

Names and Related Artifacts

Data Load and Dimension Build Limits

Aggregate Storage Database Limits

Block Storage Database Limits

Drill-through to Oracle Applications Limits

Other Size or Quantity Limits

In this appendix, the term non-Unicode applications refers to non-Unicode-mode applications and applications on Essbase Servers that are not Unicode-enabled. See Understanding the Essbase Unicode Implementation.

Names and Related Artifacts

Table 237 lists limits for names and related artifacts.

Table 237. Names and Related Artifacts

Artifact

Limits

Alias name

  • Non-Unicode application limit: 80 bytes

  • Unicode-mode application limit: 80 characters

Alias table name

  • Non-Unicode application limit: 30 bytes

  • Unicode-mode application limit: 30 characters

Application name

  • Non-Unicode application limit: 8 bytes

  • Unicode-mode application limit: 30 characters

Application description

  • Non-Unicode application limit: 79 bytes

  • Unicode-mode application limit: 80 characters

  • Custom-defined function name

  • Custom-defined macro name

  • Custom-defined function specification

  • Custom-defined macro specification

  • Non-Unicode application limit: 127 bytes.

    MaxL and the API truncate characters after 127 bytes.

  • Unicode-mode application limit: 128 characters.

    MaxL and the API truncate characters after 128 characters.

In either case, no truncation on server. No error is displayed if truncation occurs.

Custom-defined function and macro comment

  • Non-Unicode application limit: 255 bytes.

    MaxL and the API truncate characters after 255 bytes.

  • Unicode-mode application limit: 256 characters.

    MaxL and the API truncate characters after 256 characters.

In either case, no truncation on server. No error is displayed if truncation occurs.

Database name

  • Non-Unicode application limit: 8 bytes

  • Unicode-mode application limit: 30 characters

Database description

  • Non-Unicode application limit: 79 bytes

  • Unicode-mode application limit: 80 characters

Directory path

For example: EPM_ORACLE_HOME/products/Essbase/EssbaseServer/bin

  • Non-Unicode application limit: 255 characters

  • Unicode-mode application limit: 1024 characters

Environment variable name

  • Non-Unicode application limit: 320 bytes

  • Unicode-mode application limit: 320 characters

Environment variable value

  • Non-Unicode application limit: 256 bytes

  • Unicode-mode application limit: 256 characters

Essbase Server name

  • Non-Unicode application limit: 1024 bytes

  • Unicode-mode application limit: 1024 characters

Filename for calculation scripts, report scripts, and rules files

  • Non-Unicode application limit: 8 bytes

  • Unicode-mode application limit:

    • If included within a path, the smaller of the following two values:

      • 1024 bytes

      • The limit established by the operating system

    • If not included within a path, as in some MaxL statements, 1024 bytes.

Filename for text and Excel files

Non-Unicode application limit: 8 bytes

Filter name

  • Non-Unicode application limit: 256 bytes

  • Unicode-mode application limit: 256 characters

Group name

  • Non-Unicode application limit: 256 bytes

  • Unicode-mode application limit: 256 characters

LRO cell note

  • Non-Unicode application limit: 600 bytes

  • Unicode-mode application limit: 600 characters

LRO URL

512 characters (always single-byte characters)

LRO description for URLs and files

  • Non-Unicode application limit: 80 bytes

  • Unicode-mode application limit: 80 characters

Member comment field

  • Non-Unicode application limit: 255 bytes

  • Unicode-mode application limit: 256 characters

Member name

  • Non-Unicode application limit: 80 bytes

  • Unicode-mode application limit: 80 characters

Qualified member name limit: the number of levels that can be specified in a qualified member name

  • 20 levels

Password

  • Non-Unicode application limit: 100 bytes

  • Unicode-mode application limit: 100 characters

Substitution variable name

320 bytes

Substitution variable value

256 bytes

Trigger name

  • Non-Unicode application limit: 30 bytes

  • Unicode-mode application limit: 30 characters

UDA

  • Non-Unicode application limit: 80 bytes

  • Unicode-mode application limit: 80 characters

User name

  • Non-Unicode application limit: 256 bytes

  • Unicode-mode application limit: 256 characters

Data Load and Dimension Build Limits

Table 238 lists limits related to data loading and dimension building.

Table 238. Data Load and Dimension Build Limits

Artifact

Limits

Selection and rejection criteria

Number of characters that describe selection and rejection criteria: combination of all criteria limited to 32 KB

Number of error messages written to a data load or dimension build error log (DATAERRORLIMIT in essbase.cfg)

Default 1000, minimum 1, maximum 65000

Maximum number of generations allowed when building a duplicate member dimension20

Aggregate Storage Database Limits

Table 239 lists limits related to aggregate storage databases.

Table 239. Aggregate Storage Limits

Artifact

Limits

Number of hierarchies in a single dimension of an aggregate storage database

65535 (including all stored hierarchies, dynamic hierarchies, and any attribute dimensions based on the dimension)

Number of members in an aggregate storage outline

10,000,000 to 20,000,000 members, depending on available memory and other memory requirements

Maximum file location size in an aggregate storage database

4,294,967,295 MB

Number of stored dimension level combinations in an aggregate storage outline

The product of dimension level factors across stored dimensions cannot exceed 252, which is equal to 4,503,599,627,370,496.

To calculate the number of stored dimension levels in an outline:

  1. Determine the stored-level factor for each dimension.

  2. Multiply the dimension factors together; for example, a * b * c * d, and so on.

To determine the factor for each dimension, use the following guidelines:

  • For dynamic dimensions, the factor is 1.

  • For stored dimensions, for an initial dimension factor, count the nonlabel-only levels.

    • If a stored dimension has attribute dimensions, count the levels in each attribute dimension, and add that number to the dimension factor. Then, if all level 0 members of the dimension have an attribute from a specific attribute dimension, subtract 1 for each attribute dimension in which this occurs.

    • If a stored dimension has additional stored hierarchies, count the number of nonlabel-only levels in each stored hierarchy, and add the count to the dimension factor. Do not count a level if it comprises only shared members.

    • Dynamic hierarchies in a stored dimension do not affect the dimension factor.

For example, multiplying the factors for the 11 dimensions in ASOsamp.Sample, 1 * 1 * 4 * 2 * 2 * 2 * 3 * 2 * 6 * 7 * 7 equals 56,448.

To view dimension level factors:

  • In Administration Services Console, right-click a database, select Edit, and then Properties. On the Statistics tab, under Aggregate storage statistics, each non-attribute dimension in the outline is listed, showing the number of stored levels (which is the dimension level factor) in each dimension. For example:

    Dimension [Products] has [6] levels, bits used 7
  • Use this MaxL command:

    query database appName.dbName list aggregate_storage runtime_info;

Maximum number of cells that can be queried in an aggregate storage database that has a very sparse data set

264

The limit is based on the number of cells that Essbase processes in the query, which is the product of the member count across all dimensions, not on the number of cells contained in the output report.

You might encounter this limit when using a client interface (such as Oracle Hyperion Financial Reporting, Fusion Edition) that suppresses missing data in order to generate a relatively small report compared to the size of the query.

Number of alias tables

32

Block Storage Database Limits

Table 240 lists limits related to block storage databases.

Table 240. Block Storage Database Limits

Artifact

Limits

Numbers of members in a block storage outline

Approximately 1,000,000 explicitly defined in an Essbase outline.

Hybrid Analysis and some uses of partitions enable access to many more members than are explicitly listed in an outline; the actual number of members accessible through the database is much greater.

Longer names, such as can occur if multibyte characters are used, decrease the number of members that are allowed.

Numbers of possible blocks in a block storage database

The product of the stored member count of sparse dimensions cannot exceed 2104.

For instructions on how to calculate the number of possible blocks in a block storage database, see Potential Number of Data Blocks.

Numbers of possible cells per block in a block storage database

252

Numbers of Linked Reporting Objects in a block storage database

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.

Numbers of alias tables

32

Drill-through to Oracle Applications Limits

Table 241 lists limits related to drill-through URLs.

Table 241. Drill-through to Oracle Applications Limits

Artifact

Limits

Number of drill-through URLs per database255
Number of drillable regions in a drill-through URL256
Number of characters per drillable region65536

Other Size or Quantity Limits

Table 242 lists other size and quantity limits.

Table 242. Other Size or Quantity Limits

Artifact

Limits

Caches: data, data file, and index

2 GB

Formula size

64 KB

Number of security filters

  • Per Essbase Server: 65535

  • Per Essbase database: 32290

Number of users and groups (combined)

30,000

Exceeding this limit results in an error.

Number of aggregate views within an aggregation

1023

Rules file maximum record size

64 KB

MDX maximum query limits and set sizes

See the “MDX Query Limits” topic in the Oracle Essbase Technical Reference.