Oracle Express Server

When Jinitiator is installed, it appears as an item on the start menu.

Launching Express Instance Manager (EIM) From a Browser

To launch EIM, start the browser and enter the following URL:

http://<your-webserver-hostname.domainname.extension>/eim_webstage
/ExpressInstanceManager.html

If the server URL is oracle.olap.com, enter the following:

http://oracle.olap.com/eim_webstage/ExpressInstanceManager.html

Running Oracle Express Manager Console from a Browser

You can configure Oracle Enterprise Manager to run the Oracle Enterprise Manager Console from a browser.

Installing Instance Manager for Use with Oracle Enterprise Manager (Express Server Only)

To launch Express Instance Manager from the Oracle Enterprise Manager Console on a Windows system, install only Express Instance Manager into the Oracle Enterprise Manager Oracle home directory. Express Instance Manager is then installed into the program group representing the Oracle home directory of Oracle Enterprise Manager (for example, `Oracle-OEM Home').

Installing Express Server on a Machine with Existing Versions of Express Server

You may install Express Server 6.3.4 on a machine that has previous versions of Express Server (for example, versions 6.3.0 or 6.3.2.1). It is recommended that you install Express Server into a different Oracle home than previously installed versions in order to preserve oes.key information in the new environment.

Oracle Express Command-Line Service Manager (OESMGR)

To use Express Server's Service Manager utility, OESMGR, set the LD_LIBRARY_PATH environment variable to $ORACLE_HOME/lib. (In previous releases, LD_LIBRARY_PATH was set to $OLAP_HOME/lib.) For HP-UX, set SHLIB_PATH instead of LD_LIBRARY_PATH.

Migration Notes

Migration issues specific to Relational Access Manager include the following:

• When you log into the relational database using Relational Access Administrator 6.3.4 for the first time, Relational Access Administrator will automatically upgrade the Relational Access Manager repository if one already exists.
  • In order for Relational Access Administrator to upgrade the repository, the owner of the Relational Access Manager repository must have CREATE VIEW privileges. If you are using an Oracle database, you must also have CREATE SEQUENCE privileges.

  • Once the Relational Access Manager repository is upgraded to version 6.3.4, it cannot be used with older versions of Relational Access Manager. If you need to run multiple versions of Relational Access Manager, copy all objects in the current Relational Access Manager repository to a new schema (that is, a new user ID) and upgrade that version for use with Express Server 6.3.4. (If you are using the Oracle database, the most convenient method of copying the repository is to export the repository and then import it into the new schema.)

Migrations issues specific to Express Administrator include the following:

• Appendix C of the Oracle Express Database Administration Guide discusses issues related to upgrading from previous versions of Express Server and Express Administrator. It is recommended that you read this appendix before upgrading your databases if you use Express Administrator to administer your databases.

• If you will be upgrading your databases from a previous 6.x version of Express, you should open and then save each of them under Oracle Express Administrator, so that meta data can be upgraded. The upgrade will occur automatically when you open the database.

• If you will be upgrading your databases from a 5.x version of Express, you must follow the instructions outlined in Appendix C of the Oracle Express Database Administration Guide. If you do not follow those instructions, you will encounter problems using these databases with Oracle Express Objects version 2.2 and Oracle Express Analyzer version 2.2.

Migration issues specific to Express Batch Manger include the following:

• Jobs scheduled to run using Express Batch Manager are stored in the database file DSBTDATA.db. If you wish to use jobs defined using Express Batch Manager 6.2.x or Express Batch Manager 6.3 with Express Server 6.3.2, you must perform the following steps:
  1. Stop the instance of Express Server 6.3.2, if it is currently running.

  2. Overwrite the copy of DSBTDATA.db installed by Express Server 6.3 (in the ..OLAP\BTM631\SERVICE directory) with the copy of DSBTDATA.db used by Express Server 6.2 or 6.3 (from the ..OLAP\BTM6xx\SERVICE directory).

Migrating from Express Server 6.x

If you are upgrading from a pre-6.3 version of Express Server, you must export your current database and import it into a new database created with Express 6.3.4. If you are upgrading from 6.3.x, export/import is highly recommended, but not required. The export-import procedure will optimize your Express database by creating a new database with optimized data storage.

Express Server Notes

The following sections provide information on Express Server.

AGGREGATE Command vs. ROLLUP Command

The ROLLUP command is the primary method of aggregating data in Express Server 6.2 (and earlier versions). In Express Server 6.3, the new AGGREGATE command can be used to aggregate data. The AGGREGATE command is usually much more efficient than ROLLUP. In addition, the AGGREGATE command can be used to aggregate data at runtime. This eliminates the need to presummarize the entire database, as is required in Express Server 6.2 and earlier versions. See Express Language help for more information.

AGGREGATE and Conjoint Dimensions

As stated in the Express Language Reference, you cannot use conjoint dimensions in the definition of an aggregation map object. Use composite dimensions instead. If you include a conjoint dimension in the definition of an aggregation map object, compiling the aggregation map object fails and an error message which does not accurately describe the problem might be displayed (for example, the message might state that a relation is stated more than once in the definition of the aggregation map).

If the database contains conjoint dimensions and you wish to use AGGREGATE, change the definition of the conjoint dimension to a composite dimension before the aggregation map is defined. To do this, use the CHGDFN command. For example, enter:

CHGDFN <conjoint name> COMPOSITE

AGGREGATE and Relational Access Manager Databases

Databases built by Express Relational Access Manager use conjoint dimensions. If you use AGGREGATE with a Relational Access Manager database, redefine conjoint dimensions to composite dimensions before aggregating data. You must also redefine the composite dimensions back to conjoint dimensions after aggregating data. For example, enter:

CHGDFN <composite name> DIMENSION

AGGREGATE is Optimized for BTREE Index

The AGGREGATE command is optimized for composite dimensions that use the BTREE index method. If the composite dimension uses a HASH index, consider redefining it to use a BTREE index. To see what type of index a composite dimension uses the OBJ function. For example, enter:

SHOW OBJ(BTREE '<composite name>')

Use of WEIGHT and WEIGHTBY with AGGREGATE

The following information is an update to the AGGREGATE command and the RELATION command in the Express language Help System. Although you can use either the WEIGHT or the WEIGHTBY keyword, the WEIGHTBY keyword provides more flexibility. The WEIGHT keyword cannot follow the COUNTVAR keyword. Because the WEIGHT keyword has this restriction, Oracle Corporation recommends that you always use WEIGHTBY.

For example, suppose you want to use one AGGREGATE command to aggregate the data for three different variables: SALES, UNITS, and PROJECTED_SALES. Define an aggregation map named SALES.AGG, which has the following contents:

RELATION myt1.parent OPERATOR WSUM
RELATION myp1.parent OPERATOR WAVERAGE
RELATION myg1.parent OPERATOR AVERAGE

Both the WSum and the WAverage operators require that you define weight variables and use them with the WEIGHT or WEIGHTBY keyword in the AGGREGATE command. Because you want to use different weight values for each variable, define three different weight variables: SW (for SALES), UW (for UNITS) and PSW (for PROJECTED_SALES).

The Average operator requires that you define an integer variable for each variable and use them with the COUNTVAR keyword in the AGGREGATE command. Therefore, define three different integer variables: INTSALES (for SALES), INTUNITS (for UNITS), and INTPROJ (for PROJECTED_SALES).

If you prefer to use the WEIGHT keyword, then it must precede the COUNTVAR keyword and integer variables. For example, enter:

AGGREGATE sales units projected_sales USING sales.agg - 
WEIGHT sw uw psw COUNTVAR intsales intunits intproj

However, if you want the WEIGHT clause to follow the COUNTVAR clause, use WEIGHTBY instead. For example, enter:

AGGREGATE sales units projected_sales USING sales.agg -
COUNTVAR intsales intunits intproj WEIGHTBY sw uw psw

WNAFill Weight Variable Option

WNAFill is a weight variable option that you can use after the WEIGHT keyword in an AGGREGATE command. You can specify a number or NA after WNAFill. If you specify a number, then that number will replace every NA value in the weight variable or the weight formula. If you specify NA, then that NA weight causes the child value not to be aggregated into the parent value.

For example, suppose you define a SALES variable and an aggregation map named SALES.AGG. In the aggregation map, specify a RELATION command that uses a WAverage (weighted average) OPERATOR. Because WAverage requires that you define and use a weight variable, define a variable named SALESW that has identical dimensionality to SALES. You then add weight values to SALESW, but you do not have weights for every possible data value; therefore, some cells in SALESW are left as NA values. When the WAverage aggregation is performed you want to substitute a value of 0.7 for every NA value in SALESW. To do so, enter one of the following:

AGGREGATE sales USING sales.agg WEIGHT WNAFILL 0.7 salesw

or

AGGREGATE sales USING sales.agg WEIGHT WNAFILL NA salesw

Using WNAFill NA has the following effect:

• If the aggregation map contains a WAverage or a WSum OPERATOR, then any child cell in the weight variable that has a value of NA is treated as an NA cell.

• If the aggregation map contains an SSum OPERATOR, then the results depend on how the Express option NASKIP is set. If NASKIP is set to YES, then each NA value is treated as 0.0. However, if NASKIP is set to NO, then each NA value is treated as an NA value.

If you do not specify WNAFill in an AGGREGATE command, the following defaults apply:

• If you use a WAverage (weighted average) or a WSum (weighted sum) OPERATOR in a RELATION command in the aggregation map, then WNAFILL has a value of 1.0 by default.

• If you use an SSum (scaled sum) OPERATOR in a RELATION COMMAND in the aggregation map, then WNAFILL has a value of 1.0 by default.

WAgg Weight Variable Option

Oracle Express Server release 6.3.4 contains a new WAgg weight variable option. WSum and SSum use WNoAgg by default. This means that the weight values in the weight variable are not aggregated. If you want the weight values to be aggregated, use WAgg (weight aggregation) in the AGGREGATE command. If you use WAgg, then WVarPriority is also used by default, although you may change the default. If you want to use both WAgg and WAggPriority with WSum or SSum, then you must specify both WAgg and WAggPriority in the AGGREGATE command.

WAverage uses WAgg by default.

Accessing Event Logs

Express Server stores informational messages and error messages in event logs. You can view event logs using Express Instance Manager's Log sheet. Event logs are available for Express Server and Express Server Agent.

Accessing Files Across NFS

For Express Server to access files and databases on NFS mounts, you must enable root access across NFS.

New Restriction on INPLACE

You must open databases in exclusive mode if performing operations on INPLACE variables. If you use INPLACE variables in your Express applications, refer to the Using In-Place Variables note for a complete discussion.

Working with Oracle Reports

If you are using Oracle Reports to access data from Express Server, see the Oracle Reports installation notes for important NLS settings.

Large Address Space (Express Server NT Only)

When running on Windows NT 4.0 Enterprise Edition, Express Server can access up to 2GB of address space. To take advantage of the large address space, the boot parameter '/3GB' must be added to the operating systems section of the BOOT.INI file. For example:

multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows NT Server, Enterprise 
Edition Version 4.00 [3G address space]" /3GB

Known Problems

The following sections provide information on known problems in this release.

Sparse Looping in Models

When a solution variable for a model contains sparse dimensions (when the variable uses a composite) that are not listed in the model's DIMENSION statement, Express loops over the solution variable using the dimension-value combinations of the composite, rather than the values of the base dimensions. In this case, when Express Server solves the model, it assigns new values only to the dimension-value combination originally in the composite. It does not create or store new dimension-value combinations for the variable.

This default looping behavior might result in lost data if both the source and target variables of a model have sparse dimensions but use different composites to manage sparsity. Assume, for example, that the source composite contains dimension-value combinations that do not occur in the pre-solution target composite. In this case, the new values are ignored and are not propagated to the target.

To ensure that all values are propagated to the target, the model must loop over the values of the base dimensions of the solution variable rather than the dimension-value combinations of solution variable's composite.

Formerly, specifying ACROSS with the source expression's composite would have this effect; unfortunately, there were other undesirable side effects. Consequently the use of ACROSS in model equations was prohibited beginning in Express Server 6.2.

To cause a model that has a solution variable with sparse dimensions to loop over all the values of the base dimensions, specify all of the composite's base dimensions in the model's DIMENSION statement. In this way, you can ensure that all values are propagated to the target when the model is solved.

Using an RDBMS Data Source: Handling Non-default Decimal and Thousands Characters in Oracle RDBMS

When Express Server loads data from a relational database, it expects that both Express Server and the relational database use the same characters as thousands and decimal separators. If Express Server and the relational database do not use the same characters, it can misinterpret data values fetched from the relational database.

By default, Express Server, Oracle8i, and Oracle 9i expect a period (.) for the decimal character and a comma (,) for the thousands character. These values are often changed for localization and for some financial applications.

If you are using Express Relational Access Manager to fetch data from a relational database, Relational Access Manager will automatically set Express Server's thousands and decimal characters correctly. If you are not using Express Relational Access Manager, you must set thousands and decimal characters in your application.

For data to be copied from Express Server to an Oracle relational database correctly, both databases must use the default values for the decimal and thousands character. Be sure that the settings are correct for any Express session in which you use a decimal expression in the following commands:

SQL INSERT. . . VALUES expression
SQL UPDATE. . . SET expression WHERE expression
SQL SELECT. . . WHERE expression

The decimal and thousands characters must be set as follows:

To change the Express settings, enter the following:

DECIMALCHAR = '.'
THOUSANDSCHAR = ','

To change the Oracle8i or Oracle 9i setting, enter the following from Express Server:

sql alter session set nls_numeric_characters = '.,'

Sharing Sessions Between SNAPI and XCA Connections

Sharing sessions between SNAPI and XCA connections was designed to debug programs that run through SNAPI. The procedures for this method of debugging are described in Chapter 4 of the Express Language Programming Guide. Any other use of this feature may cause unpredictable results, including server crashes.

DATABASE VALIDATE Command

When you use the VALIDATE keyword with the DATABASE command, issue the command immediately after attaching the database. Otherwise, results are not reliable.

Express Instance Manager Notes (Express Server Only)

The following sections provide information on Express Instance Manager.

Session Management with Domain Level Security (Windows NT Only)

If you use Domain level security, you cannot access session management features in Express Instance Manager. If you require session management features (for example, to view and stop sessions), use Host level security.

Using CREATE and CREATE LIKE to Create New Express Server Instances

Express Instance Manager (EIM) can create additional Express Server instances using the CREATE and CREATE LIKE tools. When using these features, be aware of the following potential problems:

• When using CREATE LIKE on Windows NT, a new UUID is not generated. The UUID will be the same as the source instance. You must generate a new UUID before connecting to that instance of Express Server.

• When executing CREATE LIKE or COPY from one host machine to another, you must edit the ServerDBPath under the I/O Management Parameter manually.

• When executing a CREATE command, the ROLES are sometimes inaccurate. If the new instance of Oracle Express Server (OES) fails to start and the OES eventlog refers to a userid related error, retype the userids and passwords for all three ROLES.

• When executing CREATE, CREATE LIKE, or COPY, you do not have to log on to the target host; you will be asked for authentication at the end of completing the related dialog box. However, Oracle Corporation recommends that you log on to both the source and the target host first to reduce the possibility of intermittent agent and/or network problems. This also minimizes the possibility of user error.

• You can execute COPY from a Windows NT service to a UNIX service, or vice versa. However, Oracle Corporation recommends that you double check the configuration of the target instance.

• On Windows NT only, the EventLogPath under the I/O Management parameter is not configured for the default instance when OES is installed. The Express Server selection under Logs defaults to the Windows NT Event Viewer. If the main EventLogPath has not been changed, CREATE LIKE or COPY modeled on the main service will also have the EventLogPath display the Event Viewer. However, you can manually edit the new Windows NT services EventLogPaths independently of the default instance. Highlight EventLogPath, click on the Defaults button, answer YES to the dialog, and press Apply.

• If you have Batch Manager installed, and you execute CREATE LIKE using the default service as the model, the new instance might not start. The WakeUpSPLScript continuously runs a batch file that opens a database in the write mode. Two Express Services on the same host cannot run this script concurrently. Expand SessionManagement under Parameters and highlight InitialSessionManagement. Delete the path in the Value field of the WakeUpSPLScript.

Setting a UUID in Express Instance Manager

A UUID uniquely identifies an Express Server instance. You can generate a new UUID in the Parameters/Identifiers tab using Express Instance Manager. The standard procedure for generating a new UUID is to highlight

the current UUID in the ServerObjectID field and press the UUID button.

In Express Instance Manager 6.3.2.1, the UUID button is not automatically enabled when the ServerObjectID field is highlighted. To generate a new UUID, perform the following:

1. Highlight the ServerObjectID field.

2. Press the Set <NA> button.

3. Press the UUID button

Express Administrator Notes

The following sections provide information on Express Administrator.

Known Issues in Release 6.3

The following sections provide information on bugs in Oracle Express Server release 6.3.

Exiting Administrator

For Windows 95 and Windows 98 operating systems, exiting Express Administrator might result in an INVALID PAGE FAULT error. This is a known bug with MS Visual Basic v4 (Microsoft bug Q184332). At present, there is no user work-around.

Database ID

Express Administrator uses database identifiers to make meta data unique when multiple databases are attached in the same Express session. Database identifiers are defined when you define a new database. By default, the first two characters of a database name are used as the database identifier. For example, if a database is named BUDGET, its default database identifier is BU.

When Express Administrator generates meta data in the database, the name of the Express database object used to store the meta data might be prefixed with the database identifier. For example, if an ORGANIZATION dimension is created in the BUDGET database, which has a database identifier of BU, the relation used to store the parentage relation is named BUOR.PARENT (the prefix is a concatenation of the database identifier and the first two characters of the dimension).

If you create a different database, for example SALES, which also has an ORGANIZATION dimension, its meta data objects would have a prefix starting with SA (assuming you accept the default value for the database identifier). The parent relation for the ORGANIZATION dimension is then named SAOR.PARENT.

If two databases are named so that the first two characters are the same, and the existing database is not attached at the time you create the new database, Express Administrator reuses the same first two characters as the default value for the dimension identifier. If this default is accepted, and both databases are attached at a later time, object-naming conflicts can occur between the databases.

Express Administrator does not provide a method to change the database identifier of a database. Therefore, you should be very careful to avoid a situation where two databases share the same database identifier.

Hierarchy Editor

Changes made in the Hierarchy Editor are not be recognized in the Selector until the Hierarchy Editor before the Selector is opened. To avoid this, before bringing up the Selector, close the Hierarchy Editor after making changes to a dimension.

When using the Hierarchy Editor, you might encounter problems with dragging and dropping a large number of values from the Available pane to the Hierarchy pane. If you encounter problems, use cut and paste to move values between the panes.

In the Hierarchy Editor, you cannot scroll beyond the visible items in the Hierarchy pane while dragging values from the Available (left-hand) pane. To work around this problem, select the item under which you will be dropping values in the Hierarchy pane first, then select and drag the values from the Available pane.

Database Wizard

When loading a data file in the Database Wizard, you can set Advanced options for the data load. On the advanced options dialog, the 1-pass and 2-pass radio buttons are enabled, even though they should be disabled. If you select either of the buttons, the action is ignored.

The Database Wizard cannot generate a new database in a directory on a UNIX file system without write privileges. If you try to generate a new database, you receive a PERMISSION DENIED error, followed by a series of error messages. If you encounter this error, you must exit the Database Wizard, obtain write privileges to the directory and then re-run the Database Wizard.

Data Reader Interface

When using the Space Between Fields option in series data, the number you specify refers to the number of spaces before the first character in the first field of series data. (The Space Between Fields option is at the bottom of the Variable Properties (Numeric) dialog box that appears after you map a variable to a field in the text file you are reading). Therefore, when specifying the starting column and width of a field, you must make sure the starting column number precedes the start of the data by the number of spaces you specified, and that the width of the column includes the number of spaces you specified. If you do not account for these spaces, your data will be read incorrectly.

Spaces in Database Names

Oracle Express Administrator does not allow you to name a database that has a space in the name, such as My Database. If you do, you will receive an error when opening the Selector for a dimension or variable in the database.

Scheduler

The scheduler does not automatically update databases before running scheduled jobs. Be sure to use Express Administrator's File/Save command to update the database before submitting a job to the scheduler.

Missing Taskbar Icon

When some dialog boxes are open, you might not see the Oracle Express Administrator icon on the Windows Taskbar. To avoid this problem, close open dialogs before pressing ALT-Tab to go to another application.

File Formats

If you are using Oracle Express Server on the same Windows NT server as Express Administrator, specify path names in the 4GL using the DOS file format to reference files on the local system. For files that are remote to the Express Server system, you can use either DOS or UNC format, unless the documentation explicitly states otherwise. However, be consistent. All references to a given file must be in the same format.

DOS file name format is:

[d:] [\][path\] filename[.ext]

UNC file name format is:

\\host\share\[path\] filename[.ext]

Express Relational Access Manager Notes

The following sections provide information on Express Relational Access Manager.

Relational Access Administrator Performance

The performance of Express Relational Access Administrator in opening projects and saving changes to projects has been significantly improved for larger projects.

Relational Access Manager Meta Data

Express Relational Access Manager creates meta data in the Express database that describes mapping to source data in the relational database and Relational Access Manager's caching structures. Applications do not rely on or alter this meta data, as it can change without notice. These data structures have changed significantly in Express Relational Access Manager 6.3.

ODBC Requirements

If you use Oracle ODBC drivers to connect to an Oracle7 database using the Relational Access Administrator, version 2.5 (or later) of the Oracle ODBC driver is required. If you use Oracle ODBC drivers to connect to an Oracle8 database, version 8.0.4 (or later) of the Oracle ODBC driver is recommended.

Switch to Suppress Join Optimizations

If you use an Oracle RDBMS and if the top level of a dimension has only one value, by default the Relational Access Manager removes the JOIN for the level. This can result in slower performance. Set the SQ.SKIP.OPT.JOIN switch to YES to suppress removing the JOIN.

Support to Schemas with Data Partitioned Within a Level

The Relational Access Manager can support data within a level partitioned across hierarchies (belonging to the same dimension). Set the SQ.GOT.MULTIHIER switch in the READWH database to YES to support this type of schema. If you do not have this type of schema, leave the switch at its default setting of NO.

Known Problems with Express Relational Access Manager

The following sections provide information on common Express Relational Access Manager problems.

Multiple Users Opening Relational Access Manager Projects

Although Relational Access Administrator allows multiple users to open and edit the same Relational Access Manager project at the same time, Oracle Corporation recommends that you avoid doing this. If multiple users edit a Relational Access Manager project simultaneously, the project might be corrupted.

Truncated SQL Statements

SQL SELECT statements greater then 2,000 characters might be truncated to 2,000 characters when the SELECT statement is saved to the RDBMS. The Relational Access Manager Query Statistics application then displays only the first 2,000 characters of a SELECT statement.

Renaming Dimensions

The Relational Access Administrator allows you to rename a dimension. However, the new dimension name is not reflected in the Express database when an existing data file is updated. The new name is reflected in the Express database, only if the Express database is rebuilt as a new data file.

Printing Reports

Relational Access Administrator allows you to print reports that contain information about a Relational Access Administrator project. If changes have been made to the project before the project is saved, you might receive errors when you attempt to print a report. These problems are most common when changes have been made in the Data Model tab.

New Information for Express Relational Access Manager 6.3.4

The following section provides new information in connection with Relation Access Manager 6.3.4

Query Performance

If queries in 6.3x appear to be very slow only where the data model has a large number of levels for any number of dimensions and fact tables are partitioned (i.e., the data is partitioned) then the query time can be improved. This is particularly evident in upgrades from 6.2x to 6.3x. The switch SQ.FORCE.ETLOGIC can be set to YES to produce better SQL for the type of model described above.

Queries involving more than one custom measure (time-based) may be faster in some cases since less data is being retrieved at run time.

Embedded Total Tables

With embedded total tables, the hierarchy containing the lowest level needs to be defined first in RAA.

Attribute Mappings

If the same column is to be used for the key and the attribute description, the column should be mapped to the key column only and not mapped to the description column.

RAM Query Statistics

* Previously the only RDBMS user that would generate data for use in the RAM Query Statistics reports was the owner of the RAM meta data. All RDBMS users now generate RAM Query Statistics data. RAM Query Statistics for use with non Oracle RDBMS will be desupported in September 2002.

OLAP Worksheet

Oracle OLAP Worksheet 6.3.4 is a command-line access and debugging tool for use with Express Server. It is a Java-based application that is designed to work with any version of Express Server that supports the XCA protocol.

With the OLAP Worksheet you can edit and debug programs, and execute most Express SPL commands. The Worksheet has a Command Input window and an Edit window. The Input window contains a query (input) pane at the bottom, where you can enter Express commands, and a results (output) pane at the top, where the results of your commands appear.

The Edit window provides a means for editing Express programs. It appears when you type Edit (or Edt) and a program name in the input pane of the Command Input window.

The OLAP Worksheet is available with the OES 6.3.4 client package, on a separate CD with its own Installer. For instructions on how to use the Worksheet tool, consult OLAP Worksheet Help.