Naming Restrictions for Essbase Applications, Databases, Dimensions, Members, and Aliases

In This Section:

Naming Restrictions for Applications and Databases

Naming Restrictions for Dimensions, Members, and Aliases

Naming Restrictions in Calculation Scripts, Report Scripts, Formulas, Filters, and Substitution and Environment Variable Values

List of Essbase System-Defined Dimension and Member Names

List of MaxL DDL Reserved Words

Naming Restrictions for Applications and Databases

When naming applications and databases, follow these rules:

  • Use no more than 8 bytes when naming non-Unicode-mode applications and databases.

  • Use no more than 30 characters when naming Unicode-mode applications and databases.

  • Do not use spaces in the name.

  • Do not use the characters listed in Table 254 in the name:

    Table 254. List of Restricted Characters in Application and Database Names

    CharacterDescription

    *

    asterisk

    []

    brackets

    :

    colon

    ;

    semicolon

    ,

    comma

    =

    equal sign

    >

    greater-than sign

    <

    less-than sign

    .

    period

    +

    plus sign

    ?

    question mark

    "

    double quotation mark

    single quotation mark

    /

    forward slash

    \

    backslash

    |

    vertical bars

     

    tabs

  • For database names, do not use the:

    • String drxxxxxx (not case-sensitive)

    • Reserved word Replay

  • For aggregate storage databases, do not use the following words as application or database names:

    DEFAULT
    LOG
    METADATA
    REPLAY
    TEMP

Application and database names are not case-sensitive. However, on case-sensitive file systems, the application or database name is created exactly as you enter it. Therefore, when creating, renaming, or copying applications and databases on case-sensitive file systems, Essbase ensures that the same application or database name but with different case usage cannot be used. For example, if you create an application name with all uppercase letters (NEWAPP), you cannot then create an application with the same name but with mixed-case letters (Newapp). Also, when manually copying application and database files from one computer to another and then creating an application or database, you must use the same case for the application and database directory names on both computers.

Naming Restrictions for Dimensions, Members, and Aliases

When naming dimensions, members, and aliases in the database outline, follow these rules:

  • Use no more than 80 bytes when naming non-Unicode-mode dimensions, members, or aliases.

  • Use no more than 80 characters when naming Unicode-mode dimensions, members, or aliases.

  • Names are not case-sensitive unless case-sensitivity is enabled.

    See “Setting Outline Properties” in the Oracle Essbase Administration Services Online Help.

  • Even when case-sensitivity is enabled, in an aggregate storage outline for which duplicate member names is enabled, do not use matching names with only case differences for a dimension name. For example, do not name two dimensions “Product” and “product.”

  • Do not use quotation marks (" "), brackets ([ ]), or tabs in dimension, member, or alias names.

  • At the beginning of dimension or member names, do not use the characters listed in Table 255:

    Table 255. Restricted Characters for Dimension, Member, and Alias Names

    CharacterDescription

    @

    at sign

    \

    backslash

    { }

    brace

    ,

    comma

    -

    dash, hyphen, or minus

    =

    equal sign

    <

    less than sign

    ()

    parentheses

    .

    period

    +

    plus sign

    '

    single quotation mark

    _

    underscore

    |

    vertical bar

  • Do not place spaces at the beginning or end of names. Essbase ignores such spaces.

  • Do not use these words as dimension, member, or alias names:

    • Calculation script commands, operators, and keywords

    • Report Writer commands

    • Function names and function arguments.

    • Names of other dimensions and members (unless the member is shared), and generation names, level names, and aliases in the database

    • Any of these words:

      ALL
      AND
      ASSIGN
      AVERAGE
      CALC
      CALCMBR
      COPYFORWARD
      CROSSDIM
      CURMBRNAME
      DIM
      DIMNAME
      DIV
      DYNAMIC
      EMPTYPARM
      EQ
      EQOP
      EXCEPT
      EXP
      EXPERROR
      FLOAT
      FUNCTION
      GE
      GEN
      GENRANGE
      GROUP
      GT
      ID
      IDERROR
      INTEGER
      LE
      LEVELRANGE
      LOOPBLOCK
      LOOPPARMS
      LT
      MBR
      MBRNAME
      MBRONLY
      MINUS
      MISSING
      MUL
      MULOP
      NE
      NON
      NONINPUT
      NOT
      OR
      PAREN
      PARENPARM
      PERCENT
      PLUS
      RELOP
      SET
      SKIPBOTH
      SKIPMISSING
      SKIPNONE
      SKIPZERO
      TO
      TOLOCALRATE
      TRAILMISSING
      TRAILSUM
      UMINUS
      UPPER
      VARORXMBR
      XMBRONLY
      $$$UNIVERSE$$$
      #MISSING
      #MI

Naming Restrictions for Dynamic Time Series Members

If you enable Dynamic Time Series members, do not use the following associated generation names:

  • History

  • Year

  • Season

  • Period

  • Quarter

  • Month

  • Week

  • Day

Naming Restrictions for Attribute Calculations Dimension Member Names

In unique member outlines that contain an attribute dimension (and, therefore, an Attribute Calculations dimension), do not use the following names unless you change the default names in the Attribute Calculations dimension:

  • Sum

  • Count

  • Min

  • Max

  • Avg

If the outline is tagged as a duplicate member outline, you can use the default names to name other base or attribute members.

See Changing the Member Names of the Attribute Calculations Dimension.

Naming Restrictions in Calculation Scripts, Report Scripts, Formulas, Filters, and Substitution and Environment Variable Values

In substitution variable values, environment variable values, calculation scripts, report scripts, filter definitions, partition definitions, or formulas, you must enclose member names in brackets ([ ]) when used within MDX statements, and otherwise in quotation marks (" "), in these situations:

  • Name starts with one or more numerals (for example, 100).

  • Name contains spaces or any characters listed in Table 256:

    Table 256. Characters that Require Member Name Enclosures

    CharacterDescription

    &

    ampersand

    *

    asterisk

    @

    at sign

    \

    backslash

    { }

    braces

    :

    colon

    ,

    comma

    -

    dash, hyphen, or minus

    !

    exclamation point

    =

    equal sign

    >

    greater than sign

    <

    less than sign

    ()

    parentheses

    %

    percent sign

    .

    period

    +

    plus sign

    ;

    semicolon

    /

    slash

    ~

    tilde

In calculation scripts and formulas, you must enclose these member names, which are also Essbase keywords, in quotation marks (" ") for block storage databases, and in brackets ([ ]) for aggregate storage databases:

BEGIN
DOUBLE 
ELSE
END
FUNCTION
GLOBAL
IF
MACRO
MEMBER
RANGE
RETURN
STRING
THEN

List of Essbase System-Defined Dimension and Member Names

When using attribute dimensions, Essbase creates the following dimension and members names:

Member names in attribute dimensions:

  • True

  • False

Dimension name: Attribute Calculations

Member names in the Attribute Calculations dimension:

  • Sum

  • Count

  • Min

  • Max

  • Avg

See Naming Restrictions for Attribute Calculations Dimension Member Names.

List of MaxL DDL Reserved Words

See “Reserved Words List” in the Oracle Essbase Technical Reference.