In This Section:
Some information in this chapter applies only to block storage databases and is not relevant to aggregate storage databases.
All examples in this chapter are based on the Sample.Basic database.
For basic information about outlines, see Understanding Multidimensional Databases.
When a database is created, Essbase creates an outline for that database automatically. The outline has the same name as the database (dbname.otl) and is stored in the database directory on Essbase Server. You can create content in the new outline in the following ways:
See “Opening and Editing Outlines” in the Oracle Essbase Administration Services Online Help.
If you open the same outline with two instances of the Administration Services Console using the same login ID, each save overwrites the changes of the other instance. Oracle does not recommend this practice, as it can be difficult to keep track of the changes that are saved or overwritten.
To create an outline or open an existing outline, use a tool:
In Outline Editor, an outline is always locked when it is opened in edit mode. Essbase unlocks the outline when the outline is closed. When an outline is locked, Essbase does not allow other users to save over, rename, delete, or edit the outline. When you attempt to edit a locked outline, you are given an option to view the outline in Outline Viewer.
Essbase uses a different process for locking and unlocking outlines than for other database artifacts. See Locking and Unlocking Artifacts.
Manually, using Outline Editor
With a data source and rules file, using Data Prep Editor
Before naming dimensions and members, see Naming Restrictions for Applications and Databases.
To add dimensions and members to an outline using Data Prep Editor, see “Creating Dimension Build Rules Files” in the Oracle Essbase Administration Services Online Help.
When you create dimensions and save an outline, Essbase automatically sets the new dimensions in the outline as sparse. You can change the dimension storage type according to the optimal configuration for the database.
Set as sparse any standard dimensions with which you plan to associate attribute dimensions. See Selection of Dense and Sparse Dimensions.
Dimensions are the highest level of organization in an outline. Dimensions contain members, which you can nest inside of other members in a hierarchy. See Dimensions and Members.
The relative locations of dimensions in an outline can affect calculation and retrieval performance times. See Designing an Outline to Optimize Performance.
You can have Essbase arrange dimensions within an outline or members within a dimension in alphabetical order (A–Z) or reverse alphabetical order (Z–A). For a list of consequences of sorting dimensions and members, see Moving Dimensions and Members.
When you sort level 0 members of numeric attribute dimensions in outlines, the members are sorted by their values. For example, Figure 37, Sorting Numeric Versus Text Attribute Dimension in Ascending Order shows text and numeric versions of the Sizes attribute dimension after sorting the members in ascending order. The members of the numeric attribute dimension (on the right) are sequenced by the numeric values of the members; the member 8 is before the other members. In the text attribute dimension (on the left), because the characters are sorted left to right, the member 8 is after the member 24.
You cannot sort Boolean attribute dimensions. See Understanding Attribute Types.
A descendant of a label only member is not tagged as Dynamic Calc.
The level 0 member name of a date attribute dimension must match the date format name setting (mm-dd-yyyy or dd-mm-yyyy). If the dimension has no members, because the dimension name is the level 0 member, the dimension name must match the setting.
The level 0 member name of a numeric attribute dimension is a numeric value. If the dimension has no members, because the dimension name is the level 0 member, the dimension name must be a numeric value.
You can save outlines to the Essbase Server or to a client computer or network. By default, Essbase saves outlines to the database directory on Essbase Server. If you are saving changes to an outline, Essbase may restructure the outline. For example, if you change a member name from Market to Region, Essbase moves data stored in reference to Market to Region. Each time that you save an outline, Essbase verifies the outline to ensure that it is correct.
If you add one or more new standard (nonattribute) dimensions, any data that existed previously in the database must be mapped to a member of each new dimension before the outline can be saved. For example, adding a dimension called Channel to the Sample.Basic outline implies that all previous data in Sample.Basic is associated with a particular channel or the sum of all channels.
If you delete one or more standard (nonattribute) dimensions, the data associated with only one member of each deleted dimension must be retained and associated with a member of one of the other dimensions. For example, removing a dimension called Market from the outline implies that all of the data that remains in the database after the restructure operation is associated with a single, specified member of the Market dimension.
If you delete an attribute dimension, Essbase deletes the associations to its base dimension. See Working with Attributes.
To create a sub-database:
Only one member can be kept when a dimension is deleted. See Saving an Outline with One or More Deleted Standard Dimensions.