Essbase XTD Administration Services Release 6.5.3

Documentation Addendum

This addendum provides documentation for new features added in Essbase XTD Administration Services Release 6.5.3 and lists other updates to the documentation set from Release 6.5.1. Only the Readme file, Installation Guide, and Installation Checklist have been updated for Release 6.5.3.

Documentation for New Features
Documentation Updates

Documentation for New Features

The following new features are added in this release:

Exporting Databases
Repairing Partitions
Support for New MaxL Statements

Exporting Databases

If you have Read permission for a database, you can back up data in a database by exporting it. Exporting data copies it to an ASCII text file that you specify; it does not compress data. The export file contains data only and does not include control, outline, or security information.

If the database you are exporting is not started, Administration Services starts it for you. During a data export, users can connect to and perform read-only operations on the database. For more information about exporting data, see the Database Administrator's Guide.

To export a database:

From Enterprise View or a custom view, select the database to export.
Right-click and select Export from the pop-up menu.
In the Export Database dialog box, specify the name for the export file.
Select the amount of data to export.
If you want to export data in a columnar format, select Export in column format.
Click OK.

Export Database Dialog Box

Export to file text box	Enter the name of the export file. By default, the export file is not given a file extension and is stored in the /app directory. If you want to store the export file in a different location, specify the full path for the location. The directory that you want to contain the export file must already exist.
Export options option group	All data option: Exports all data from the database to the specified file, including the consolidation and calculation results. Level 0 data blocks option: Exports data from level 0 data blocks only (blocks containing only level 0 sparse member combinations). Input level data blocks option: Exports data from input blocks only (blocks containing data from a previous data load or spreadsheet Lock & Send). This option excludes the consolidation and calculation results.
Export in column format check box	Exports the data in columns, which facilitates loading the exported data into a relational database. In each row, the columnar format displays a member name from every dimension. Names can be repeated from row to row. The columnar format provides a structure to the exported data, so that it can be used for further data processing by applications other than Essbase tools. In non-columnar format, sparse members identifying a data block are included only once for the block. Because the export file in non-columnar format is smaller than in columnar format, reloading a file in non-columnar format is faster.

Repairing Partitions

When you create a partition definition, the information for the partition is stored in two separate .ddb files—one in the database directory of the source and the other in the database directory of the target. If the connection information stored in one of these .ddb files is invalid, the partition needs to be repaired before you can open and edit it from Enterprise View. A partition cannot be restored if one of the .ddb files for the source or target is physically missing (for example, if the application or database is deleted using a tool other than Essbase Administration Services).

In general, if you rename, copy, or delete applications and databases that contain partitions using Essbase Administration Services, the corresponding partition definitions are updated or removed automatically to reflect the change.

A partition may need repair in the following cases:

The application or database referenced in a .ddb file has been renamed or copied to a different location using a tool other than Essbase Administration Services (for example, MaxL).
The host name referenced in a .ddb file is different from the actual host name.
User information (username and password) in a .ddb file is invalid.

If applications or databases are renamed or copied using a different tool (such as MaxL), Essbase Administration Services may not be able to find the corresponding .ddb file for the second half of the partition. If for any reason Essbase Administration Services cannot determine both the source and target for the partition, the partition is displayed under the Orphan Partitions node in Enterprise View so that you can repair or delete it. If both .ddb files exist in their expected locations but are still invalid, you can select the source or target partition under the Source Database or Target Database node in Enterprise View and repair the invalid information.

Note: This new functionality is available only if you are connecting to a Release 6.5.3 OLAP Server. You cannot repair partitions if you are connecting to OLAP Server Release 6.2, 6.5.1, or 6.5.2.

To repair a partition:

From Enterprise View or a custom view, find the database that contains the partition you want to repair.
Under the Partitions node, find the source or target partition definition that you want to repair, or find the partition definition under the Orphan Partitions node.
Right-click the partition and select Repair partition from the pop-up menu.

The Repair Partition dialog box is displayed. Only fields that need repair are editable.
Edit the invalid fields, and click Repair.

Essbase saves the corrected information to the .ddb partition definition file.
If you want to edit the partition after the repair is complete, right-click the partition in Enterprise View and select Edit partition.
If an invalid partition cannot be repaired and you want to delete the available half of the partition, right-click the partition in Enterprise View and select Delete partition.

Repair Partition Dialog Box

Use this dialog box to repair partitions that include invalid application, database, or user information. Only fields that need repair are editable.

Data source group

Repair the necessary information for the source database:

OLAP Server: Select the name of the OLAP Server on which the source database resides.
Application: Select the name of the application that contains the source database.
Database: Select the name of the source database.
User: Specify the username that you want the partition to use to connect to the OLAP Server on which the source database resides.
Password: Specify the password that you want the partition to use to connect to the OLAP Server on which the source database resides.

Data target group

Repair the necessary information for the target database:

OLAP Server: Select the name of the OLAP Server on which the target database resides.
Application: Select the name of the application that contains the target database.
Database: Select the name of the target database.
User: Specify the username that you want the partition to use to connect to the OLAP Server on which the target database resides.
Password: Specify the password that you want the partition to use to connect to the OLAP Server on which the target database resides.

Repair button

Click this button to repair the partition.

Support for New MaxL Statements

Two new MaxL partitioning statements are supported in the MaxL Script Editor (only when you are connecting to OLAP Server Release 6.5.3): alter partition and drop partition with force. For more information about these statements, see the Readme file for Essbase XTD Analytic Services Release 6.5.3.

Top

Documentation Updates

The following information updates the published Essbase Administration Services Release 6.5.1 documentation:

The Migrate Users to OLAP Server dialog box now has an additional check box: "Replace existing users on target". Select this check box if you want the selected users to overwrite existing users with the same name on the target OLAP Server.

Also, the Available list box no longer lists Supervisors, since Supervisors cannot be migrated across servers.

These same changes apply to the Migrate Groups to OLAP Server dialog box.

The documentation for the Print Outline dialog box is incorrect. The "all expanded items" option prints the members that are showing or have been showing at one time since you opened the outline. The "Only visible items" option prints only the members that are currently showing in the outline. (56252)

Custom-defined functions (CDFs) and custom-defined macros (CDMs) are now displayed in the function/command tree in Calculation Script Editor. CDFs and CDMs are displayed only after an outline is associated with the editor. (27984)

You cannot open partitions in EAS that were saved locally using Application Manager. (43067)

In the Area Mapping Member Selection dialog box, the Member Information dialog box now displays alias, generation, or level information for the selected member. (56975, 56976))

In order to view e-mail attachments sent by Administration Services that contain OLAP Server, application, or database properties information, you must have Microsoft Internet Explorer version 6.0 or higher installed on your computer.

A new Data Storage tab has been added to the Essbase Administration Server window. The items on this tab are properties for the embedded database that is used to store Essbase Administration Services user information. These properties should not be changed, with the possible exception of JDBC pool size. The items on this tab are documented below:

JDBC RDBMS	The name of the embedded database.
JDBC archive text box	Name of the .jar file that contains the JDBC driver. This item is blank since the JDBC driver is installed with Essbase Administration Services.
JDBC driver text box	Name of the JDBC driver.
JDBC URL text box	Path to the Essbase Administration Services repository.
JDBC username text box	Username for the database.
JDBC password text box	Password for the database.
JDBC pool size text box	Initial size of the connection pool for the database.

Top