Essbase XTD Administration Services Release 6.5.3 |
Documentation Addendum |
Return to Readme |
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.
The following new features are added in this release:
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.
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.
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:
|
Data target group |
Repair the necessary information for the target database:
|
Repair button |
Click this button to repair the partition. |
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.
The following information updates the published Essbase Administration Services Release 6.5.1 documentation:
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. |
©2001-2003 Hyperion Solutions Corporation. All Rights Reserved. http://www.hyperion.com |