Oracle Essbase Database Administrators Guide RELEASE 11.1.2.

content
1. Introduction to Essbase 2. Essbase Architecture 3. Essbase Product Components 4. Understanding Mutidimensional Databases 5. Running Essbase server, Application and databases 1. Essbase Executable Files 2. Understanding the Agent 3. Starting Essbase Server in foreground 4. Starting Essbase server as background Process 5. Changing the Essbase server system password 6. stopping Essbase server 7. Starting and Application 8. Stoping and Application 9. Stopping an Application Improperly 10. Staring a Database 11. Stopping a Database 12. Essbase Logs 6. Managing Applications and Databases 1. Copying or Migrating an Application 2. Reanaming an Application 3. Deleting an Application 4. Copying Databases 5. Reanming Databases 6. Deleting Databases 7. Starting and Stopping Essbase Products 8. Launching client

Introducing Essbase
Essbase is a multidimensional database management system (MDBMS) that provides a multidimensional database platform upon which to build analytic applications. With Essbase, companies quickly leverage and integrate data from multiple existing data sources and distribute filtered information to end-user communities in the format that best meets the users needs. Essbase is the business analysis server technology that provides an environment for rapid development of custom analytic and enterprise performance management applications. For example, Essbase enables line-of-business personnel to develop and manage analytic applications that model complex scenarios, forecast business trends, and perform what-if analyses. Essbase supports extremely fast query response times for vast numbers of users, for large data sets, and for complex business models. It is hot-pluggable across any data source.

Essbase Architecture
Essbase products incorporate powerful architectural features to handle a wide range of analytic applications across large multiuser environments. Figure 1 provides a high-level view of the information flow between the three tiers of the Essbase architecture. The client tier (on the left) includes Essbase Server clients, such as Oracle Hyperion Smart View for Office, Fusion Edition and Administration Services Console. The middle tier (in the center) includes services, such as Oracle Hyperion Provider Services and Oracle Essbase Administration Services. The database tier (on the right) is made up of Essbase Servers. Communication between the client and middle tiers, and the middle and database tiers, is through HTTP. Communication between the client and database tiers is through TCP/IP or HTTP. Communication between data sources and the metadata catalog with the middle and database tiers is through ODBC and JDBC drivers.

Figure 1 High-level Information Flow Between Product Components

Essbase Product Components

Administration Services
Administration Servicesthe database and system administrators interface to Essbase provides a single-point-of-access console to multiple Essbase Servers. Using Administration Services, you can design, develop, maintain, and manage multiple Essbase Servers, applications, and databases. You can preview data from within the console without having to open a client application, such as Spreadsheet Add-in. You can also use custom Java plug-ins to leverage and

extend key functionality.

Essbase Studio
Oracle Essbase Studio simplifies cube construction by delivering a single environment for performing tasks related to data modeling, cube designing, and analytic application construction. With a wizard-driven user interface, Essbase Studio supports modeling of the various data source types from which Essbase applications are typically built. A single common metadata repository, or catalog, captures all metadata related to all Essbase applications built in the enterprise and allows the reuse of metadata at the lowest level of granularity. The catalog makes Essbase Studio inherently aware of the common metadata that is shared across the various applications enterprise wide. Essbase Studio supports several drill-through options: relational databases, custom SQL, URLs (including Oracle Business Intelligence Enterprise Edition and Oracle Hyperion Financial Data Quality Management, Fusion Edition URLs), and Java methods. Essbase Studio also supports lineage tracking through a rich graphical view of metadata relationships, allowing users to follow application lineages to their metadata components and through to the data sources from which they were sourced.

Spreadsheet Add-in
Spreadsheet Add-in integrates Essbase with Microsoft Excel. Spreadsheet Add-in adds the Essbase menu to Excel, which provides enhanced commands such as Connect, Pivot, Drilldown, and Calculate. Users can access and analyze data on Essbase Server with mouse clicks and dragging operations. Spreadsheet Add-in enables multiple users to access and update data on an Essbase Server simultaneously.

Visual Explorer
Oracle Essbase Visual Explorer provides a query and analysis interface for creating interactive summaries and reports about the data in an Essbase database. You can choose to visualize data in various graphical formats, including bars, lines, Gantt bars, shapes, colors, and tables. Visual Explorer is installed with and accessed from Spreadsheet Add-in.

Data Mining
Data Mining reveals hidden relationships and patterns in your data, enabling you to make better business decisions. Using Data Mining, you can plug in various data mining algorithms, build models, and apply them to existing Essbase applications and databases.

Integration Services
Oracle Essbase Integration Servicesan optional product componentprovides a metadatadriven environment to bridge the gap between data stored in Essbase databases and detailed data stored in relational databases. The Hybrid Analysis feature gives business users more detail for decision-making and IT managers more modularity in designing and maintaining large-scale analytic applications. Hybrid Analysis allows portions of Essbase databases to be stored in a relational database. This relational-stored data is mapped to the appropriate Essbase hierarchies.

Provider Services
Provider Services is a middle-tier data-source provider to Essbase for Java API, Smart View, and XMLA clients. Provider Services supports highly concurrent analytical scenarios and provides scalability and reliability in a distributed Web-enabled enterprise environment.

Smart View
Smart View provides a common Microsoft Office interface for Essbase, Oracle Hyperion Financial Management, Fusion Edition, Oracle Hyperion Planning, Fusion Edition, and Oracle Enterprise Performance Management Workspace, Fusion Edition data. Using Smart View, you can view, import, manipulate, distribute, and share data in Microsoft Excel, Word, and PowerPoint interfaces.

Application Programming Interface (API)

Essbase APIthe developers interface to Essbaseenables you to create customized applications. The Oracle Essbase API Reference provides a complete listing of API functions.

Developer Products
Essbase developer products enable the rapid creation, management, and deployment of tailored enterprise analytic applications, whether or not users have programming knowledge. The products (for example, Application Builder and Oracle's Hyperion Application Builder for .NET) provide a comprehensive set of application programming interfaces, drag-and-drop components, and services.

Smart Search Command Line Utility

Oracle Hyperion Smart Search Command Line Utility integrates with leading enterprise search solutions such as Google Search Appliance and Oracle Secure Enterprise Search to provide a familiar search interface. Using simple business terminology, users can obtain structured information from Essbase applications and databases. Information that has been filtered according to user privileges is delivered in data grids and live links in Smart View. Oracle Hyperion Smart Search Command Line Utility greatly enhances the way in which users can quickly get to information contained within Oracle applications.

Lifecycle Management
Oracle Hyperion Enterprise Performance Management System Lifecycle Management provides a consistent way for Oracle Hyperion Enterprise Performance Management System products to migrate an application, a repository, or individual artifacts across product environments and operating systems. Generally, the Lifecycle Management interface in Oracle's Hyperion Shared Services Console is consistent for all EPM System products that support Lifecycle Management. However, EPM System products display different artifact listings and export and import options in the Lifecycle Management interface. Lifecycle Management features: Viewing applications and folders Searching for artifacts Migrating directly from one application to another Migrating to and from the file system Saving and loading migration definition files Viewing selected artifacts Auditing migrations Viewing the status of migrations Importing and exporting individual artifacts for quick changes on the file system

Understanding Multidimensional Databases

OLAP and Multidimensional Databases
Online analytical processing (OLAP) is a multidimensional, multiuser, client-server computing environment for users who need to analyze enterprise data. It has the ability to provide managers the information that they need to make effective decisions about an organization's strategic directions. A successful OLAP application provides information as needed; that is, it provides just-in-time information for effective decision-making. Key to OLAP systems are multidimensional databases, which not only consolidate and calculate data; but also provide retrieval and calculation of a variety of data subsets. A multidimensional database supports multiple views of data sets for users who need to analyze the relationships between data categories. In multidimensional databases, the number of data views is limited only by the database outline, the structure that defines all elements of the database. Users can pivot the data to see information from a different viewpoint, drill down to find more detailed information, or drill up to see an overview.

Dimensions and Members

A dimension represents the highest consolidation level in the database outline. The database outline presents dimensions and members in a tree structure to indicate a consolidation relationship. For example, in figure 2,Year is a dimension (of type Time) and Qtr1 is a member.
Figure 2 Hierarchical Structure

Essbase has standard dimensions and attribute dimensions. Standard dimensions represent the core components of a business plan and often relate to departmental functions. Typical standard dimensions: Time, Accounts, Product Line, Market, and Division. Dimensions change less frequently than members. Attribute dimensions are associated with standard dimensions. Through attribute dimensions, you group and analyze members of standard dimensions based on the member attributes

(characteristics). For example, you can compare the profitability of noncaffeinated products that are packaged in glass to the profitability of noncaffeinated products packaged in cans. Members are the individual components of a dimension. For example, Product A, Product B, and Product C might be members of the Product dimension. Each member has a unique name. Essbase can store the data associated with a member (referred to as a stored member in this chapter), or it can dynamically calculate the data when a user retrieves it.

Outline Hierarchies
All Essbase database development begins with creating a database outline, which accomplishes the following: Defines the structural relationships between members in an Essbase database Organizes data in the database Defines the consolidations and mathematical relationships between items

Essbase uses the concept of members to represent data hierarchies. Each dimension consists of one or more members. The members, in turn, may consist of other members. When you create a dimension, you tell Essbase how to consolidate the values of its individual members. Within the tree structure of the database outline, a consolidation is a group of members in a branch of the tree. For example, many businesses summarize their data monthly, rolling up monthly data to obtain quarterly figures and rolling up quarterly data to obtain annual figures. Businesses may also summarize data by zip code, city, state, and country. Any dimension can be used to consolidate data for reporting purposes. In the Sample.Basic database included with Essbase Server, for example, the Year dimension comprises five members: Qtr1, Qtr2, Qtr3, and Qtr4, each storing data for an individual quarter, plus Year, storing summary data for the year. Qtr1 comprises four members: Jan, Feb, and Mar, each storing data for a month, plus Qtr1, storing summary data for the quarter. Similarly, Qtr2, Qtr3, and Qtr4 comprise the members that represent the individual months plus the member that stores the quarterly totals. The database outline in Figure 2 uses a hierarchical structure to represent the data consolidations and relationships in Qtr, as described in the previous paragraph. Some dimensions consist of relatively few members, while others may have hundreds or even thousands of members. Essbase does not limit the number of members within a dimension and enables the addition of new members as needed.

Dimension and Member Relationships

Essbase uses hierarchical (generations and level; and roots and leaves) and family history (parents, children, and siblings; and descendants and ancestors) terms to describe the roles and relationships of the members in a database outline. The subtopics in this section reference the outline show in Figure 3 in describing the position of the members. Figure 3 Member Generation and Level Numbers

Parents, Children, and Siblings

Figure 3 illustrates the following parent, child, and sibling relationships: A parent is a member that has a branch below it. For example, Margin is a parent member for Sales and Cost of Goods Sold. A child is a member that has a parent above it. For example, Sales and Cost of Goods Sold are children of the parent Margin. Siblings are child members of the same immediate parent, at the same generation. For example, Sales and Cost of Goods Sold are siblings (they both have the parent Margin), but Marketing (at the same branch level) is not a sibling, because its parent is Total Expenses.

Descendants and Ancestors

Figure 3 on page 60 illustrates the following descendant and ancestral relationships: Descendants are members in branches below a parent. For example, Profit, Inventory, and Ratios are descendants of Measures. The children of Profit, Inventory, and Ratios are also

descendants of Measures. Ancestors are members in branches above a member. For example, Margin, Profit, and Measures are ancestors of Sales.

Roots and Leaves

Figure 3 on page 60 illustrates the following root and leaf member relationships: The root is the top member in a branch. Measures is the root for Profit, Inventory, Ratios, and the children of Profit, Inventory, and Ratios. Leaf members have no children. They are also referred to as level 0 members. For example, Opening Inventory, Additions, and Ending Inventory are leaf members.

Generations and Levels

Figure 3 on page 60 illustrates the following generations levels: Generation refers to a consolidation level within a dimension. A root branch of the tree is generation 1. Generation numbers increase as you count from the root toward the leaf member. In Figure 3, Measures is generation 1, Profit is generation 2, and Margin is generation 3. All siblings of each level belong to the same generation; for example, both Inventory and Ratios are generation 2. Figure 4 shows part of the Product dimension with its generations numbered. Product is generation 1, 100 is generation 2, 100-10 is generation 3, and 100-10-12 and 100-10-16 are generation 4. Figure 4 Generations

Level also refers to a branch within a dimension; levels reverse the numerical ordering used for generations. Levels count up from the leaf member toward the root. The root level number varies depending on the depth of the branch. In Figure 3, Sales and Cost of Goods Sold are level 0. All other leaf members are also level 0. Margin is level 1, and Profit is level 2. Notice that the level number of Measures varies depending on the branch. For the Ratios branch, Measures is level 2. For the Total Expenses branch, Measures is level 3. Figure 5 shows part of the Product dimension with its levels numbered. 100 is level 2, 100-10 is level 1, and 100-10-12 and 100-10-16 are level 0.

Figure 5 Levels

Generation and Level Names

To ease report maintenance, you can assign a name to a generation or level and then use the name as a shorthand for all members in that generation or level. Because changes to an outline are automatically reflected in a report, when you use generation and level names, you do not need to change the report if a member name is changed or deleted from the database outline.

Standard Dimensions and Attribute Dimensions

Essbase has standard dimensions and attribute dimensions. This chapter focuses on standard dimensions, because Essbase does not allocate storage for attribute dimension members. Instead, it dynamically calculates the members when the user requests data associated with them. An attribute dimension is a special type of dimension that is associated with a standard dimension. Sparse and Dense Dimensions Most data sets of multidimensional databases have two characteristics: Data is not smoothly and uniformly distributed. Data does not exist for the majority of member combinations. For example, all products may not be sold in all areas of the country. Essbase maximizes performance by dividing the standard dimensions of an application into two types: dense dimensions and sparse dimensions. This division allows Essbase to cope with data that is not smoothly distributed, without losing the advantages of matrix-style access to the data. Essbase speeds data retrieval while minimizing memory and disk requirements. Most multidimensional databases are inherently sparse; they lack data values for the majority of member combinations. A sparse dimension is one with a low percentage of available data positions filled. For example, the outline of the Sample.Basic database in Figure 6 includes the Year, Product, Market, Measures, and Scenario dimensions. Product represents the product units, Market

represents the geographical regions in which the products are sold, and Measures represents the accounts data. Because not every product is sold in every market, Market and Product are chosen as sparse dimensions. Most multidimensional databases also contain dense dimensions. A dense dimension has a high probability that one or more cells is occupied in every combination of dimensions. For example, in the Sample.Basic database, accounts data exists for almost all products in all markets, so Measures is chosen as a dense dimension. Year and Scenario are also chosen as dense dimensions. Year represents time in months, and Scenario represents whether the accounts values are budget or actual values.
Figure 6 Sample.Basic Database Outline

Data Storage
Each data value in a multidimensional database is stored in one cell. A particular data value is referenced by specifying its coordinates along each standard dimension. Consider the simplified database shown in Figure 4. This database has three dimensions: Accounts, Time, and Scenario: The Accounts dimension has four members: Sales, COGS, Margin, and Margin%. The Time dimension has four quarter members, and Qtr1 has three month members The Scenario dimension has two child members: Budget for budget values and Actual for actual values. Figure 4 A Multidimensional Database Outline

Data Values
The intersection of one member from one dimension with one member from each of the other dimensions represents a data value. The example in Figure 16 has three dimensions (Accounts, Time, and Scenario); therefore, the dimensions and data values in the database can be represented as a cube. Figure 5 Three-Dimensional Database

As illustrated in Figure 6, when you specify Sales, you are specifying the slice of the database that contains eight Sales values, where Sales intersect with Actual and Budget. Figure 6 Sales Slice of the Database

Slicing a database amounts to fixing one or more dimensions at a constant value while allowing the other dimensions to vary. As illustrated in Figure 7, when you specify Actual Sales, you are specifying the slice of the database that contains four Sales values, where Actual and Sales intersect. Figure 7 Actual, Sales Slice of the Database

A data value is stored in one cell in the database. To refer to a specific data value in a multidimensional database, you specify its member on each dimension. In Figure 8, the cell containing the data value for Sales, Jan, Actual is shaded. The data value can also be expressed using the cross-dimensional operator (->) as Sales -> Actual -> Jan. Figure 8 Sales->Jan->Actual Slice of the Database

Data Blocks and the Index System

Essbase uses two types of internal structures to store and access data: data blocks and the index system. Essbase creates a data block for each unique combination of sparse standard dimension members (providing that at least one data value exists for the sparse dimension member combination). The data block represents all the dense dimension members for its combination of sparse dimension members. Essbase creates an index entry for each data block. The index represents the combinations of sparse standard dimension members. It contains an entry for each unique combination of sparse standard dimension members for which at least one data value exists. Each unique data value can be considered to exist in a cell in a data block. When Essbase searches for a data value, it uses the index to locate the appropriate data block. Then, within the data block, it locates the cell containing the data value. The index entry provides a pointer to the data block. The index handles sparse data efficiently because it includes only pointers to existing data blocks. By carefully selecting dense and sparse standard dimensions, you can ensure that data blocks do not contain many empty cells, minimizing disk storage requirements and improving performance. In Essbase, empty cells are known as #MISSING data.

Multiple Data Views

A multidimensional database supports multiple views of data sets for users who need to analyze the relationships between data categories. Slicing the database in different ways gives you different perspectives of the data. For example, in Figure 9, the slice for Jan examines all data values for which the Year dimension is fixed at Jan. Figure 9 Data for January

The slice in Figure 10 shows data for the month of Feb:

Figure 10 Data for February

The slice in Figure 11 shows data for profit margin

Figure 11 Data for Profit Margin

Running Essbase Server, Applications and databases

Essbase Executable Files
Executable File essbase.exe esssvr.exe essmsh.exe esscmd.exe adminsvr.exe or startEAS.exe admincon.exe Describtion Essbase Server Agent process Application server process MaxL Shell ESSCMD command-line client interface Essbase Administration Server executable Administration Services Console application EPM_ORACLE_HOME/ products/Essbase/eas/ server/bin EPM_ORACLE_HOME/ products/Essbase/eas/ server/bin ESSBASEPATH/bin ESSBASEPATH/bin ESSBASEPATH/bin Location ESSBASEPATH/bin

Understanding the Agent

Launching the Agent executable file, essbase.exe, starts the Essbase Server Agent process. The Agent process starts and stops all applications and acts as the traffic coordinator for Essbase Server. On the computer where Essbase Server is installed, the Agent is accessible only from the server console, which is the primary terminal, or monitor, connected to the server computer. When you start Essbase Server in the foreground, the Agent becomes active in an operating system window. In the Agent window, you can view release and license information, enter login and administrative commands, and monitor the behavior of Essbase Server. On Windows, Essbase can be accessed only from the server console. On UNIX, a telnet session is used to access Essbase remotely. When you start Essbase Server in the background, the terminal becomes free for other input, and the Agent activities are not visible in the terminal. The agent log is called the Essbase Server log.

Starting Essbase Server in the Foreground

Starting Essbase Server in the foreground starts the Agent in an operating system window, in which you can enter commands and monitor Essbase Server activities. When starting an Essbase Server for the first time (for example, after installing Essbase), the administrator enters a company name, Essbase Server system administrator user ID, and a system password. This information is saved in the Essbase security file (essbase.sec). As long as essbase.sec is present in your Essbase installation, you are not prompted to provide this information when subsequently starting Essbase Server. To start Essbase Server in the foreground, For Windows, choose a method: On the Start menu, select Programs, then Oracle EPM System, then Essbase, then Essbase Server, and then Essbase. In the file system, launch the startEssbase.bat file.

Starting Essbase Server as a Background Process

If you start Essbase Server in the background, these conditions apply:

You do not have access to Agent commands. You cannot shut down Essbase Server from the Agent. You must use MaxL or ESSCMD. You cannot access the application server window to monitor a running application. You must access this information from the application log (ARBORPATH/app/appname/ appname.log). You cannot monitor Essbase Server activity using the Agent. You must access this information from the Essbase Server log (EPM_ORACLE_HOME/logs/essbase/ essbase.log).

To start Essbase Server in the background on UNIX or on Windows systems utilizing a UNIXl ike shell such as MKS, enter the following command at a command prompt: startEssbase.sh -b & Using the ampersand (&) at the end of the command is optional; however, if you do not use &, the command prompt is not returned after Essbase Server is started. Note: On Windows, unless you are using a UNIX-like shell such as MKS, the ampersand (&)

has no effect. Essbase Server starts in the background, but control of the command prompt is not returned. You may need to press the Enter key twice before the command prompt returns.

Changing the Essbase Server System Password

You can change the password that is required to start Essbase Server. Note: Changing the system password does not change the connection password for the Essbase system Administrator. To change the Essbase Server system password, use a tool:

Tool Agent MaxL ESSCMD

Topic password alter user system_administrator set password password SETPASSWORD

Essbase verifies that the system password has been updated.

Stopping Essbase Server

You need Administrator permissions to stop or shut down Essbase Server. To stop Essbase Server and all running applications, use a tool: Tool Agent MaxL ESSCMD Topic quit exit Alter system shutdown SHUTDOWNSERVER

If you stop the Agent by closing the Agent window or by pressing Ctrl + C, the next time you start the database, Essbase rolls back any transactions that were in progress.

Starting an Application
When you start an application, the following actions can happen: Users can connect to the application. The application can respond to commands from the Agent. Users can change the settings of the application.

Data and user security are enabled. Each database in the application can start.

To start an application, use a tool: Tool Agent MaxL ESSCMD Administration Services Topic START appname alter system load application LOADAPP or SELECT Starting Applications

The application starts and, if you are running on Windows, opens the application server window on the Essbase Server computer. You can also start an application by completing any of these actions: Starting a database within an application. Saving an outline to Essbase Server. (Opening an outline does not start an application.). You can set options that control how applications start: startup (Allow user to start application): If an application is stopped, and a user attempts to retrieve data from any databases within that application, the application starts on the Essbase Server computer automatically. autostartup (Start application when Essbase starts): Users may experience better initial performance when they make requests of databases in that application, because the application and databases are already loaded into memory on the Essbase Server computer.

Stopping an Application
Stop applications properly to prevent the databases within them from becoming corrupt. When you stop an application, transactions may be running. If you stop an application using any of the proper methods (see the following table), the application does not stop if a calculation or data load is in progress. Instead, Essbase displays a message in the Agent console. If you stop the Agent by closing the server console window or by pressing Ctrl+C, the application stops, and the next time you start the application, Essbase rolls back any transactions that were in progress.

To properly stop applications, use a tool:

Tool Agent MaxL ESSCMD Administration Services

Topic stop appname alter system unload application UNLOADAPP Stopping Applications

Stopping an Application Improperly

Sometimes, stopping the application server process improperly, by closing the application server window, is necessary; for example, if the application server is corrupted and is not processing client requests. To stop the application improperly, use a method for the operating system on which Essbase Server runs: For UNIX platforms, kill the ESSSVR process. You can use the ps output to identify individual applications. If an application freezes, you can stop the application by using this command: kill -9 <pid> For Windows, choose a method: Perform a Windows operating system End Task. Windows does not display process IDs for individual Essbase applicationsall of the running Essbase applications are displayed as undifferentiated ESSSVR processes, preventing you from stopping a single application in the event that the application freezes. Click the Close button in the application server window. Taskkill the process ID.

You can find the process ID for individual application servers in the EPM_ORACLE_HOME/logs/essbase/essbase.log file. When the server starts, a line like the following is displayed in the Essbase Server log: Application [Sample] started with process id [225]

Starting a Database
When Essbase starts a database and loads it to memory, the entire index cache for that database is allocated in memory automatically. The data cache and data file cache are allocated as blocks requested from Essbase clients. When you start an application, Essbase loads the application and its databases into memory on the Essbase Server computer. When you start a database from an application that is not started, the application is loaded into memory along with all its related databases. To start a database, use a tool: Tool Agent MaxL ESSCMD Administration Services Topic START appname alter application load database UNLOADAPP LOADDB or SELECT

To configure a database to start automatically when its parent application starts, use a tool:

Tool MaxL Administration Services

Topic alter database enable autostartup Configuring Databases to Start Automatically

Stopping a Database
Stopping a database unloads all data from memory and commits any updated data to disk. If a database is stopped and a user attempts to retrieve data from it, the database starts on Essbase Server automatically, without any explicit commands issued. When you stop a database, transactions may be currently running. If you stop a database using any of the proper methods (see the following table), the database does not stop if a calculation or data load is in progress. Instead, Essbase displays a message in the server console window. If you stop the Agent by closing the server console window or by pressing Ctrl+C, the database stops, and the next time you start the database, Essbase rolls back any transactions that were in progress.

To stop a database, use a tool:

Tool Agent MaxL ESSCMD Administration Services

Topic STOP appname alter application unload database UNLOADDB Stopping Databases

Essbase Logs
This topic describes the logs that Essbase Server creates to record information about server, application, and database activities.. Note: Log files (except for Essbase Server log files) may be located under ARBORPATH/app/appname, depending on the value of the DEFAULTLOGLOCATION configuration parameter.
Summary of Logs

Type of Log

Location of Log

Information Included

HYPERION_HOME/logs/essbase/ESSBASE.LOG Note: If your installation contains multiple instances of Essbase Essbase Server Server activities Server, each instance has its own log file directory, as log and errors controlled by the InstanceID configuration setting. For example: if InstanceID is set to inst1, the logging directory for that instance is HYPERION_HOME/logs/essbase_inst1. Application log Query log HYPERION_HOME/logs/essbase/app/appname/appname.L Application OG activities and errors Query patterns of HYPERION_HOME/logs/essbase/app/appname/dbname/dbn Essbase database ame00001.qlg retrievals

Outline change HYPERION_HOME/logs/essbase/app/appname/dbname/dbn Changes to the log ame.olg outline One of these locations: ARBORPATH/log00001.xcp HYPERION_HOME/logs/essbase/app/log00001.xcp HYPERION_HOME/logs/essbase/app/appname/log00001.xc p HYPERION_HOME/logs/essbase/app/appname/dbname/log 00001.xcp Errors that result when Essbase Server stops abnormally

Exception log

Dimension One of these locations Errors from a build and data ARBORPATH/client/dataload.err dimension build or load error logs HYPERION_HOME/logs/essbase/app/appname/appname.log a data load

EPM System Configurator and System Log Files

Log Type EPM System Configurator logs Log Location EPM_ORACLE_INST ANCE/ diagnostics/log s/ config Name and Contents cmconfig.logTrace info generated during Reporting and Analysis configuration from Reporting and Analysis (CMC) APIs called q configtool.logConfiguration task output and warning messages q configtool-http-ant.logTrace from ant code executed during Web server setup q ConfigTool-stdout.logConsole output q Configtool-appdeployment.logTrace of deployment steps q configtool_summary.logSummary status about pass/fail tasks q EssbaseExternalizationTask.log Trace information for the Essbase externalization process executed during Essbase custom configuration q SharedServices_CMSClient.log Shared Services CMS client trace, generated during configuration when CMS calls are made q ocm-config.logOracle Configuration Manager configuration log q registry.logTrace of Oracle Hyperion Shared Services Registry calls made during configuration q SharedServices_Security.logShared Services Registry registration log validation.logTrace information generated during diagnostic utility execution Note: A file name validation-n.log indicates that the log has rolled over because of size limits q validationTool-stderr.logError information generated during diagnostic utility execution q validationTool-stdout.logTrace information generated during diagnostic utility execution q velocity.logDiagnostic utility trace generated by velocity component calls

EPM System Diagnostics logs

EPM_ORACLE_INST ANCE/ diagnostics/log s/ validation/

EPM System Diagnostics reports Application Server logs For Oracle WebLogic Server installed with EPM System Installer. For WebLogic Server installed outside EPM System Installer, see the WebLogic Server documentation for information about logs Web server logsFor Oracle HTTP Server installed with EPM System Installer. For Web servers installed outside EPM System Installer, see vendor documentation for information about logs. Start and stop logs

EPM_ORACLE_INST ANCE/ diagnostics/rep orts WebLogic Server service, error, and console logs: EPM_ ORACLE_INSTANCE / diagnostics/log s/ PRODUCT

instance_report_20110305_121855.htmlValidation tool report

See the product folders for the specific logs.

EPM_ORACLE_INST ANCE/ httpConfig/ohs/ diagnostics/log s/ OHS/ohs_compone nt

q access_log and access_log.number WebLogic-generated log file for a managed server q console~OHS~1.logOracle HTTP Servergenerated log file, console output q ohs_component.logOracle HTTP Servergenerated log file PRODUCT.logStart and stop logs for each EPM System product

EPM_ORACLE_INST ANCE/ diagnostics/log s/ starter (UNIX) EPM_ORACLE_INST ANCE/ diagnostics/log s/ services (Windows)

Services startup logs

PRODUCT-syserr.log and PRODUCTout.logWindows service startup logs; trace of messages through startup

Shared Services Registry logs

MIDDLEWARE_HOME registry.logRegistry activity /user_ projects/domain s/ domain name/servers/ managed server name/ logs CSS and Shared SharedServices_SecurityClient.log Services Native Directory Registry product initialization, CSS initialization activity: MIDDLEWARE_HOME /user_ projects/domain s/ domain

Security logs

name/servers/ managed server name/ logs WebLogic logs MIDDLEWARE_HOME access.logWebLogic activity needed when /user_ contacting Oracle Support projects/domain Services. s/ domain name/servers/ managed server name/ logs

Foundation Services Logs

Log Location Foundation Services: MIDDLEWARE_HOME/user_ projects/domains/domain name/servers/managed server name/logs Shared Services: MIDDLEWARE_HOME/user_ projects/domains/domain name/servers/ Log Name and Description FoundationServices0.logServer and security activity

q SharedServices_Admin.logApplications Groups management activity q SharedServices_Audit.logAudit server errors while reading/writing audit information to the database or while configuring auditing q SharedServices_Audit_Client.log Information about the audit client q SharedServices_CMSClient.logMetadata Service client activity q SharedServices_Hub.logShared Services context listener and initialization activity q SharedServices_LCM.logLifecycle Management activity q SharedServices_Registry.logShared Services Registry activity q SharedServices_Security.logUser management, provisioning, authentication, and single sign-on activity q SharedServices_TaskFlow.logInformation about Taskflows q Workspace.logEPM Workspace error and informational messages q Framework.log: r EPM System common user interface framework error and informational messages r Miscellaneous messages; for example, locale detection

EPM Workspace: MIDDLEWARE_HOME/user_ projects/domains/domain name/servers/managed server name/logs

r Messages regarding BPMUI configuration files or registry settings r Any errors due to invalid configuration files; for example: corrupt BpmServer. properties or registry. r BPMUI security messages, including CSS initialization, logon/logout logs from the Web application, and CSS authentication error messages Smart View Smart View is a client-side application. The name and location of the file where it logs events, errors, and other information are specified as options in Smart View. For more information about Smart View logging options, see the Oracle Hyperion Smart View for Office User's Guide. q DimensionServer.logActivities from Performance Management Architect Dimension Server; for example, all export activities and dimension manipulation q datasync.logLogging information from Data synchronization activities; for example, validation and execution errors from connectors q EpmaDataSync0.logPerformance Management Architect Web- tier activities; for example, deployment activities, LCM activities, and product interaction activities q epma.logLogging information from Web reports q EpmaWebReports0.logPerformance Management Architect Web-tier activities

Performance Management Architect Dimension Server logs: EPM_ORACLE_INSTANCE/ diagnostics/logs/epma Performance Management Architect: Data Sync Web application server logs: MIDDLEWARE_HOME/user_ projects/domains/domain name/servers/managed server name/logs Performance Management Architect: Web application server logs: MIDDLEWARE_HOME/user_ projects/domains/domain name/servers/managed server name/logs Calculation Manager: MIDDLEWARE_HOME/user_ projects/domains/domain name/servers/managed server name/logs

q apsserver.logGenerates communication logs between Calculation Manager and Essbase servers q CalcManager.logGenerates all Calculation Manager Web tier activities q CalcMgr0.logGenerates all Calculation Manager activities

Essbase Logs
The following table contains information about Essbase product family logs that use ODL format: Essbase Administration Services Essbase Studio

Provider Services

Log Location Essbase: EPM_ORACLE_ INSTANCE/ diagnostics/ logs/essbase/ essbase_0

Log Name and Description q Essbase Server log: ESSBASE_ODL.log Essbase Server activities and errors q Essbase application log: /app/APPLICATION_NAME_ODL.log Essbase application activities and errors q Data load log: dataload_ODL.err Data load and dimension build errors q SSAUDIT log files: dbname_ODL.atx and dbname_ODL.alg Successfully completed spreadsheet update transactions. These are SSAUDIT log files; file name and location are specified through an essbase.cfg setting. See Monitoring Data, Applications, and Databases in the Oracle Essbase Database Administrator's Guide and the Essbase Technical Reference. q Exception log: log0000x.xcp Errors that result when Essbase Server stops abnormally q Essbase Server Lease Manager log: leasemanager_server_HOSTNAME.log Essbase Server Lease Manager information q Essbase Agent Lease Manager log: leasemanager_essbase_HOSTNAME.log Agent Lease Manager information EssbaseStudioServer.log Essbase Studio upgrade activity

Essbase Studio upgrade log: EPM_ ORACLE_ INSTANCE/ diagnostics/ logs/upgrades Essbase staging tool: The working directory

essStaging.logErrors that result when the staging tool (essStage.bat | sh prepares configuration and security information, data, and applications for file transfer during an upgrade. For more information about the stating tool, see Preparing Essbase Data for Upgrading in Chapter 5, Upgrading EPM System Products, in the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide. EssbaseRehost.logErrors recorded by the Essbase rehosting tool when it rehosts Essbase connections during an upgrade. For more information about Essbase Server rehosting, see Rehosting Essbase Server in Appendix B, Rehosting Foundation Services Web Application and Essbase Server, of

Essbase Server rehosting log: EPM_ORACLE_ INSTANCE/ diagnostics/ logs/essbase

the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide. Essbase Security Client log:EPM_ ORACLE_ INSTANCE/ diagnostics/ logs/essbase Oracle Process Manager and Notification Server logs: EPM_ORACLE_ INSTANCE/ diagnostics/ logs Security_client.logTracking of EPM System component and CSS communications with native provider. Also records the JDBC configuration from registry in this log file for any binds with native providers.

q OPMN server log: /OPMN/opmn/opmn.log Diagnostic information that the OPMN server prints for various operations performed against a managed component (Essbase). This log contains information about when Essbase starts, stops, and how many retry attempts are made to start and stop. q Essbase console log: /OPMN/opmn/ console~ESSBASE_CLUSTER_NAME~ESSBASE_PROCESS_T YPE~AGENT~1.LOG All console messages are directed to a file that is called the "console" output file for a managed process, in this case, Essbase. Essbase often writes the same log file entries to Essbase.log and stdout; therefore there might be duplicate entries in Essbase.log and this console log file. q OPMN Forward Ping log: /OPMN/opmn/EssbasePing.log OPMN Forward Ping information essbaseplugin_ODL.logLog statements related to the LCM artifact listing

Essbase Plugin logs: MIDDLEWARE_ HOME/user_ projects/ domains/domain name/servers/ managed server name/logs/ essbase/lcm Administration Services: MIDDLEWARE_ HOME/user_ projects/ domains/domain name/servers/ managed server name/logs Note: To enable console logging, in admincon.lax, set the Java option parameter DEAS_ CONSOLE_LOG. to True. Essbase Studio:

q easserver.logAdministration Services Server activity q EssbaseAdminServices0.logWeb application activity

server.logEssbase Studio server activity

EPM_ORACLE_ INSTANCE/ diagnostics/ logs/esbstudio Provider Services: MIDDLEWARE_ HOME/user_ projects/ domains/domain name/servers/ managed server name/logs q AnalyticProviderServices0.logWeb application activity q apsserver.logProvider Services activity

Essbase Failover Logs

OPMN manages Essbase; therefore, the first set of logs to consult are the OPMN log files for Essbase. However, a failure reported in these log files may point to activity in the back-end Essbase log files that will help diagnose the problem. To properly diagnose error conditions, use the Essbase and OPMN log files listed in above Table and chain the log entries, known as log chaining, across the various processes according to the time line in which they occurred. There are many possible scenarios of issues involving runtime failures that affect failover.

The following files are key log files when Essbase runs in failover mode. See above Table for the location and description of these logs. Essbase Server log Essbase Server Lease Manager log Essbase Agent Lease Manager log OPMN server log Essbase console log OPMN Forward Ping log

Managing Applications, Databases, and Database Artifacts

Copying or Migrating Applications
You can copy an application to any Essbase Server to which you have appropriate access. You can copy (migrate) an entire application to another Essbase Server, or you can copy an application on the same Essbase Server. For example, you may need to migrate an entire application from a development server to a production server. Or, you may want to copy an application on the same server for testing or for backup purposes. Essbase copies applications differently, depending on whether you are copying to the same Essbase Server or to a different Essbase Server. When you migrate applications, you can select the artifacts to migrate, such as calculation scripts, report scripts, rules files, custom-defined macros and functions, substitution variables, and filters. You can also specify how user and group security is migrated. To copy an application, use a tool:

Tool MaxL ESSCMD Administration Services

Topic create application as COPYAPP Copying Applications

Renaming Applications
When you rename an application, the application and its associated directory (ARBORPATH/ app/appname) are renamed. All artifacts within the application (for example, databases or calculation scripts) with the same name as the application are not renamed Tool MaxL ESSCMD Administration Services Topic alter application RENAMEAPP Renaming Applications

Deleting Applications
When you delete an application, all artifacts within the application also are deleted. The ARBORPATH/app/appname directory and all files in the directory are deleted. Tool MaxL ESSCMD Administration Services Topic drop application DELETEAPP Deleting Applications

Copying Databases
You can copy a database in an application to any Essbase Server and application to which you have appropriate access. You can copy (migrate) an entire database to another Essbase Server, or you can copy a database on the same Essbase Server. For example, you may need to migrate an entire database from a development server to a production server. Or, you may want to copy a database on the same server for testing or for backup purposes. Essbase copies databases differently depending on whether you are copying to the same Essbase Server or to a different Essbase Server. See Copying Databases in Oracle Essbase Administration Services Online Help. Administration Services provides a Migration Wizard that helps you migrate applications and databases. See Migration Wizard in Oracle Essbase Administration Services Online Help. When you copy a database, all files associated with the database, except data files (.pag and .ind), are copied to the destination application. Before copying, make sure you have enough disk space to contain a full copy of the database and its related files. Tool MaxL ESSCMD Administration Services Topic create database as Copying Databases Copying Databases

Renaming Databases
When you rename a database, the database and its associated directory (ARBORPATH/app/ appname/dbname), and the outline file (.otl) are renamed. All other artifacts in the database (for example, calculation scripts) with the same name as the database are not renamed.

Tool MaxL ESSCMD Administration Services

Topic alter database

RENAMEDB

Renaming Databases

Deleting Databases
When you delete a database, all artifacts within it are also deleted. The ARBORPATH/app/ appname/dbname directory and all files located in the directory are deleted.

Tool MaxL ESSCMD Administration Services

Topic drop database DELETEDB Deleting Databases

Starting and stopping Essbase Products

Foundation Services Managed Server Application Server
The following table describes the services and processes for the Foundation Services Managed Server application server, which includes Shared Services, and EPM Workspace Web applications.

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel Description

Details Select Start, then Programs, then Oracle EPM System, then Foundation Services, and then Start Foundation Services HyS9Foundation Services Hyperion Foundation Services - Managed Server Hyperion Foundation Services support Hyperion applications, including authentication, user provisioning, task flow management, data and metadata synchronization

Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

EPM_ORACLE_INSTANCE/bin/startFoundationServices.bat EPM_ORACLE_INSTANCE/bin/startFoundationServices.sh EPM_ORACLE_INSTANCE/bin/stopFoundationServices.bat EPM_ORACLE_INSTANCE/bin/stopFoundationServices.sh

Web Server
The following table describes the services and processes for the Web server. EPM System Installer installs Oracle HTTP Server. The Oracle HTTP Server service is managed with OPMN.

Information type Display Name in Windows Services Control Panel

Details Oracle Process Manager (ohsInstanceInstanceNumber) Note that this menu command directs to the start script, which redirects Oracle HTTP Server to start using OPMN. The OPMN start script opmnctl.bat is located in EPM_ORACLE_INSTANCE/httpConfig/ohs/bin. IIS: IIS Admin Service

Description

IIS: Enables this server to administer Web and FTP services. If this service is stopped, the server will be unable to run Web, FTP, NNTP, or SMTP sites or configure IIS. If this service is disabled, any services that explicitly depend on it will fail to start.

Windows Startup Script (For Oracle Installer only)

EPM_ORACLE_INSTANCE/bin/startOHS.bat start using OPMN. The OPMN start script opmnctl.bat is located in EPM_ORACLE_INSTANCE/httpConfig/ohs/bin.

HTTP Server installed by EPM System Note that this start script redirects Oracle HTTP Server to

Unix Startup Script (For Oracle Installer only)

EPM_ORACLE_INSTANCE/bin/startOHS.sh start using OPMN. The OPMN start script opmnctl is located in EPM_ORACLE_INSTANCE/httpConfig/ohs/bin

HTTP Server installed by EPM System Note that this start script redirects Oracle HTTP Server to

Windows Stop Script (For Oracle HTTP Server installed by EPM System Installer only) Unix Stop Script (For Oracle HTTP Server installed by EPM System Installer only)

EPM_ORACLE_INSTANCE/bin/stopOHS.bat

EPM_ORACLE_INSTANCE/bin/stopOHS.sh

Essbase Server
During installation, EPM System Installer installs OPMN and registers Essbase Server for OPMN. OPMN manages the Essbase Agent, which manages the Essbase Server.

In a Windows environment, before you launch Essbase, change the OPMN service (Oracle Process Manager (instanceName)) to start as a named user so that the shared network files are accessible. Navigate to EPM_ORACLE_INSTANCE/bin and use the following commands to start and stop Essbase Server: opmnctl startproc ias-component=EssbaseInstanceName or ./opmnctl startall opmnctl restartproc ias-component=EssbaseInstanceName opmnctl stopproc ias-component=EssbaseInstanceName opmnctl status If you have not implemented clustering, EssbaseInstanceName is the name of the Essbase instance that you entered on the Essbase Server Configuration page during configuration with EPM System Configurator. If you have implemented clustering, EssbaseInstanceName is the name of the Essbase cluster that you entered on the Set up Essbase Clusters page during configuration with EPM System Configurator. If you are using Essbase in a clustered environment, there are additional steps required to set up Essbase failover on both nodes of the cluster. The following table describes additional methods for starting and stopping Essbase Server. Note that the Essbase Server start and stop scripts redirect to OPMN.

where EssbaseInstanceName is one of the following:

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel Windows Startup Script

Details Select Start, then Programs, then Oracle EPM System, then Essbase, then Essbase Server, and then Start Essbase This command launches startEssbase.bat (and redirects to OPMN) Oracle Process Manager (instanceName) Oracle Process Manager (instanceName) Essbase Server EPM_ORACLE_INSTANCE/bin/startEssbase.bat (redirects to OPMN) Each instance of Essbase Server has its own startup script. If you configured an additional instance of Essbase, startEssbase.bat|sh is located in additionalInstanceLocation/bin. Launch the start script from this

location to launch this instance of Essbase. ESSCMD EPM_ORACLE_INSTANCE/EssbaseServer/EssbaseServerInstance Name/bin/startEsscmd.bat (also available in the /EssbaseClient directory) essmsh EPM_ORACLE_INSTANCE/EssbaseServer/EssbaseServerInstance Name/bin/startMaxl.bat (also available in the /EssbaseClient directory) All the scripts call setEssbaseEnv.bat to set up ESSBASEPATH, ARBORPATH, and PATH before starting UNIX Startup Script Essbase Server EPM_ORACLE_INSTANCE/bin/startEssbase.sh (redirects to OPMN) Each instance of Essbase Server has its own startup script. If you configured an additional instance of Essbase, startEssbase.bat|sh is located in additionalInstanceLocation/bin. Launch the start script from this location to launch this instance of Essbase. ESSCMD EPM_ORACLE_INSTANCE/EssbaseServer/EssbaseServerInstance Name/bin/startEsscmd.sh (also available in the /EssbaseClient directory) essmsh EPM_ORACLE_INSTANCE/EssbaseServer/EssbaseServerInstance Name/bin/startMaxl.sh (also available in the /EssbaseClient directory) All the scripts call hyperionenv.doc to set up ESSBASEPATH, ARBORPATH, and PATH before starting. When running Essbase manually from a console, the console cannot be set to UTF-8 encoding. Windows Stop Script UNIX Stop Script Essbase Server EPM_ORACLE_INSTANCE/bin/stopEssbase.bat (redirects to OPMN) Essbase Server EPM_ORACLE_INSTANCE/bin/stopEssbase.sh (redirects to OPMN)

Stopping Essbase Server can take some time, depending on how many Essbase applications are running on the server. To stop Essbase Server, you need Administrator permissions.

Administration Services Server

The following table describes the services and processes for the Administration Services server.

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel Description Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

Details Select Start, then Programs, then Oracle EPM System, then Essbase, then Essbase Administration Services, and then Start Administration Services Hys9eas Hyperion Administration Services - Web Application HyS9eas - Controls the running of an Applications Server EPM_ORACLE_INSTANCE/bin/startEssbaseAdminServices.bat EPM_ORACLE_INSTANCE/bin/startEssbaseAdminServices.sh EPM_ORACLE_INSTANCE/bin/stopEssbaseAdminServices.bat EPM_ORACLE_INSTANCE/bin/startEssbaseAdminServices.sh

Integration Services Server

The following table describes the services and processes for the Integration Services server.

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel Windows Startup Script UNIX Startup Script Windows Stop Script

Details Select Start, then Programs, then Oracle EPM System, then Essbase, then Integration Services, and then Server Hyperion Integration Services Hyperion Integration Services EPM_ORACLE_INSTANCE/bin/startEisServer.bat EPM_ORACLE_INSTANCE/bin/startEisServer.sh EPM_ORACLE_INSTANCE/bin/stopEisServer.bat Note that you must manually stop the Integration Services service manually using the Task Manager

UNIX Stop Script

EPM_ORACLE_INSTANCE/bin/stopEisServer.sh Note that you must manually stop the Integration Services service by stopping the process.

Essbase Studio Server

The following table describes the services and processes for the Essbase Studio server.

Information Type Windows Start Menu Command Registered Service Name Display Name in Windows Services Control Panel Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

Details Select Start, then Programs, then Oracle EPM System, then Essbase, then Essbase Studio, and then Start Server Hyperion Studio Service BPMS bpms1 Hyperion Studio Service BPMS bpms1 EPM_ORACLE_INSTANCE/bin/startBPMS_bpms1_Server.bat EPM_ORACLE_INSTANCE/bin/startBPMS_bpms1_Server.sh EPM_ORACLE_INSTANCE/bin/stopBPMS_bpms1_Server.bat EPM_ORACLE_INSTANCE/bin/stopBPMS_bpms1_Server.sh

Provider Services Application Server

The following table describes the services and processes for the Provider Services application server.

Information Type Windows Start Menu Command Registered Service Name Services Control Panel Description Windows Startup Script UNIX Startup Script Windows Stop Script UNIX Stop Script

Details Select Start, then Programs, then Oracle EPM System, then Essbase, then Provider Services, and then Start Analytic Provider Services HyS9aps

Display Name in Windows Hyperion Provider Services - Web Application Provide access service to Hyperion Provider Services EPM_ORACLE_INSTANCE/bin/startAnalyticProviderServices.bat EPM_ORACLE_INSTANCE/bin/startAnalyticProviderServices.sh EPM_ORACLE_INSTANCE/bin/stopAnalyticProviderServices.bat EPM_ORACLE_INSTANCE/bin/stopAnalyticProviderServices.sh

Launching Clients
This section describes how to launch EPM System clients. It lists default URLs and script names as appropriate. Most clients can also be started using the Windows Start menu. The following table describes the URLs and scripts for launching EPM System clients.

Client Services Console

URL 000/interop/

Script or Other Launch Method then Oracle EPM System, then Foundation Services, and then Shared Services URL. Note: The Start menu item is available only on the machine on which you installed the Web server.

Oracle Hyperion Shared http://dba1.appsahyd.com:19 From the Start menu, select Programs,

EPM Workspace

http://dba1.appsahyd.com:19 From the Start menu, select Programs, 000/workspace/ then Oracle EPM System, then Workspace, and then Workspace URL. Note: The Start menu item is available only on the machine on which you installed the Web server.

Smart View

NA

Use the Smart View menu or Smart View ribbon in Microsoft Excel, Microsoft Word, or Microsoft PowerPoint

Administration Services Console

http://dba1.appsahyd.com:19 From the Start menu, select Programs, 000/easconsole/console.html then Oracle EPM System, then Essbase, then Essbase Administration Services, and then Start Administration Services Console.

Oracle Essbase Integration Services Console

NA

From the Start menu, select Programs, then Oracle EPM System, then Essbase, then Integration Services, and then Console. Or EPM_ORACLE_HOME/products/Essbas e/eis/console/bin/startOlapbldr.bat

Essbase Studio Console NA

From the Start menu, select Programs, then Oracle EPM System, then Essbase, then Essbase Studio, and then Essbase Studio Console. Or EPM_ORACLE_HOME/products/Essbas

e/EssbaseStudio/Console/startStudio.bat Oracle Essbase Spreadsheet Add-in From the Excel menu bar, select Essbase to display the Essbase menu.