Oracle Hyperion: hyperion interview questions and answers.

hyperion interview questions and answers.

Showing posts with label hyperion interview questions and answers.. Show all posts

Can we have multiple metaoutlines based on one OLAP model in Integration services?
Ans: Yes

What are LRO's( Linked Reporting Objects)?
Ans: They are specific objects like files, cell notes or URL's associated with specific data cells of Essbase database. You can link multiple objects to a single data cell. These linked objects are stored in the server. These LRO's can be exported or imported with the database for backup and migration activities.

What are the three primary build methods for building dimensions?
Ans:1. Generation references
2. Level references
3. Parent-Child references

How does UDA's impact database size?
Ans: There will be no impact on the database as the UDA’s doesn’t store data in the database.

Can we have an metaoutline based on two different OLAp models.
Ans: No.

Can we create UDA’s and apply it to Dense as well as Sparse dimensions?
Ans: Yes

Types of Partitions available in Essbase?
Ans: Three types of partitions are there.
1. Transparent partition: A form of shared partition that provides the ability to access and manipulate remote data transparently as though it is part of your local database. The remote data is retrieved from the data source each time you request it. Any updates made to the data are written back to the data source and become immediately accessible to both local data target users and transparent data source users
2. Replicated Partition:
3. Linked Partition:

What is hybrid analysis?
Ans: Lower level members and associated data remains in relational database where as upper level members and associated data resides in Essbase database.

Why top-down calculation less efficient than a bottom-up calculation?Being less efficient, why do we use them.
Ans: In the process it calculates more blocks than is necessary. Sometimes it is necessary to perform top-down calculation to get the correct calculation results.

On what basis you will decide to invoke a serial or parellel calculation method.
Ans: If we have a single processor, we will use serial calculation but if we have multiple processors we can break the task into threads and make them run on different processors.

How can you display UDA’s in reports?
Ans: UDA's values are never displayed in the reports and hence do not impact report performance.

While loading the data, you have applied both the selection criteria as well as rejection criteria to a same record. What will be the outcome?
Ans: The record will be rejected.

What are the specified roles other than Aministrator to view sessions, disconnect sessions or kill users requests for a particular application?
Ans: You should have the role of Application manager for the specified application.

What is block locking system?
Ans: Analytic services(or Essbase Services) locks the block and all other blocks which contain the childs of that block while calculating this block is block locking system.

What are the three options specified in Username and Password management under security tab in Essbase server proprties.
Ans: 1. Login attempts allowed before username is disabled.
2. Number of inactive days before username is diabled.
3. Number of days before user must change password.

Can we have multiple databases in one single application?
Ans: Yes. But only one database per application is recommended.
Depend on which database that you are going to create. For Example: If you are creating ASO then we can’t create more that 1 db per application. If you are creating BSO then you can create more than 1 db per application

How is data stored in the Essbase database?
Ans: Essbase is an file based database where the data is stored in PAG files of 2 GB each and grows sequentially.

We have created an application as unicode mode. Can we change it later to non-unicode mode.
Ans: No

What are the types of partitioning options available in Essbase?
Ans: 1. Replicated partition. 2. Transparent partition 3. Linked partition.

Dynamic calc decreases the retreival time and increases batch database calculation time. How true is the statement?
Ans: The statement should be just opposite. As dynamic calc members are calculated when requested, the retreival time should increase.

What is the role of provider services.
Ans: To communicate between Essbase and Microsoft office tools.

A customer wants to run two instances of an Essbase server on a same machine to have both test environment and Development environment on the same server. Can he do that?
Ans: Yes. We can have multiple instances of an Essbase server on a single machine and there will be different sets of windows services for all these instances.

Why top-down calculation less efficient than a bottom-up calculation?Being less efficient, why do we use them.
Ans: In the process it calculates more blocks than is necessary. Sometimes it is necessary to perform top-down calculation to get the correct calculation results.

METHOD 1:
1. Make sure the application is stopped. (Stop app in Essbase Administration Services Console). Go into the OS system (for example: Explorer for Windows) and find the Essbase Application.

2. Within the database directory, please delete the following files:
Db_name.ind
Ess00001.pag
Ess00001.ind
Db_name.esm
Db_name.tct

3. After deleting these files, please reload data (via text file, spreadsheet or relational source) and calculate database.

METHOD 2:
Below is a step-by-step walk-through of an alternative method of recovering the database. The typical way of backing up the database is to delete the five files we recommend (ess00001.pag, ess00001.ind, db_name.ind, db_name.esm, db_name.tct) and reload the data back into the database to restore these files as stated above.

1. Copy the essbase.sec file to another location within the system while the application is closed/stopped. This file holds all the security information. However the reason to make a copy of it is because in later steps, it is recommended to delete the application. The security file will update itself once this is done. A copy of this file ensures the security information of the application is not lost.

2. Make sure you know all the Database settings for your application because you will be blowing away db_name.db. There are several ways to do this:
(a) Going through Database | Information and write down information
(b) In Esscmd, run commands: GETDBSTATS, GETDBSTATE. This will output the Database settings.

3. Delete the problematic application and database. This is done via the Essbase Administration Services Console. This will delete the db_name.db. To double-check this, look into Windows Explore to make sure the application is deleted. Note: Do NOT attempt to delete the application/database through Windows Explorer (if on Windows). This is unsupported and will not delete it properly.

4. Create a NEW application and database, name it the same name as the old application. This is because the security file points to the application with that particular name.

5. Copy the essbase.sec back into the bin directory over the previous essbase.sec. The reason is because the one existing in essbase\bin has been altered upon deletion of the database. It wiped out the database’s security settings.

6. Reload data into the database and calculate.

This recovery method will give a *fresh* new start of the database. This will provide a clean application and will hopefully decrease the crashes/corruption encountered. If it doesn't decrease the crashes, the next step would be to analyze disk space, memory and cache settings to find the root of the corruption problem.

The following procedure needs to be carried out in order to display data in Hyperion Planning webforms in format other than the standard numeric format:
In Classic Applications
- Login to the planning application
- Go to Administration -> Dimensions -> Select dimension that the member (format needs to be other than numeric) belongs to
- Select member and click on Edit
- Alter data type to desired format (Percentage in this example) and Save
- Click on the 'Evaluation Order' tab and move the account dimension to the 'Selected Dimensions' section and Save
Refresh to Essbase is not needed as these are planning features.
In EPMA applications- Login to Workspace
- Click on the Navigate Button -> Administer -> Application Library
- Right click on Application -> Edit -> Data Type Evaluation
- Move desired dimension to the 'Selected Dimensions' section -> click on OK
- Drill down on Dimension and select the member to be altered
- On the properties list section, alter the 'Data Type' to desired format and click on Save
- In the Application library Window, right click on the application -> Deploy -> Application.
Do not select the Essbase options as that is not needed.

The Data should now display in the correct format in the Hyperion Planning webforms

When are Implied Shares Created?

An Implied Share is a relationship between a parent member and its child member in the Application outline. Implied Shares are an Essbase feature that will also affect Planning users since Planning applications are built on top of Essbase.

The purpose of Implied Shares is to reduce the block size in Essbase by avoiding the unnecessary duplication of data. Implied Sharing is enabled by default.

There are three scenarios where an Implied Share relationship will be created between a parent and its child.

The parent has only one child

The parent has only one child that consolidates to the parent (the other children of that parent being non-aggregating)

The parent is of data type "Label Only", in which case the parent will inherit the value of the first child, no matter what the aggregation settings of the children

Examples:

Assume all members are set to data type "Store"
Scenario #1
              Parent A
           Child 1 (+)
Scenario #2
       Parent A
           Child 1 (+)
           Child 2 (~)
           Child 3 (~)

In both of these scenarios, Essbase will automatically create an Implied Share relationship between Parent A and Child 1. This is done because the values of the parent and child in the above scenarios are always going to be the same, so storing two separate values in Essbase only increases block size unnecessarily.

When an implied share relationship is created, each implied member will assume the other member value. If a data value is entered for the parent, the child will assume the same value after a save (Planning Data Form) or after a lock, send and refresh (Excel add-in for Essbase).

If a data value is entered for the child, the parent will usually assume the same value after a save (Planning Data Form) or after a lock, send and refresh (Excel add-in for Essbase). There is one exception to this, explained below.
Unintended Effects on Planning Data Forms
Usually, the parent and child can be treated interchangeably. For example, if a Calculation Script or Essbase Load Rule is used to populate a parent or child in an Implied Share relationship, the other member will always assume the value of the member populated by the Calculation Script or Load Rule. The last value calculated or imported will "win", and become the value for both members. It is possible to refer to either the parent or the child as a variable in a Calculation Script and the result will be the same.

However, this is one situation in which the behaviour described above can interact with the particular design of a web form to produce unexpected results. If both the parent and child members are displayed on the same Planning Data Form, data entered for the child may be discarded when the form is saved, leaving that cell in the form empty, or displaying the "#missing" null value. Alternatively, the cell may revert to an earlier value, discarding changes made since the last save.
This situation arises because of the way that a data form is saved. During a save operation, the form is read line by line from left to right, with the top line read first. Since most Planning applications are "bottom-up" applications, data is typically entered for the child member (as the parent member is read only). This typically leads to the following sequence of events:

The data form displays the child member above the parent, on the data form. This is the default layout for a data form: the parent is displayed on the row below its children, indented.

The user enters data for the child member, which was previously null

The data form is saved. The save operation reads the form left-to-right and top-to-bottom. Therefore the child is saved first and the newly entered data submitted to Essbase.

The save operation then reaches the parent, which is still null (an empty cell). Because of the Implied Share, this null value overwrites the value of the child member, effectively discarding the data entered in step 2.

How to Avoid the Side Effects of Implied Shares in Planning
There are several ways to work around the issue outline above.
I. Use the "Never Share" setting

Set the parent member to use the "Never Share" storage setting, rather than "Store". This disables the implied share, so that the parent and child store their values separately.
A "Never Share" member differs from a "Store" member in one respect: a parent member set to "Store" will display the aggregated value of its children after a save (Planning Data Form), after a lock, send, and refresh (Excel add-in for Essbase), or after running an aggregation (running a Business Rule to aggregate the members on the form). A parent member set to "Never Share" will only display the aggregated value of its children after an aggregation is run.

It is usually advantageous for parents with single children to use the default storage type of "Store" (thus keeping the Implied Share relationship) as it reduces the block size and overall database size in Essbase, and improves calculation and aggregation times. Only use "Never Share" when actually required.
II. Add a Dummy Member

Add a dummy member to the outline as a second aggregating child. A dummy member need not be used on forms, but exists in the outline. This will disable implied sharing, since the parent member now has more than one aggregating child (see Examples section above).

Note that this workaround will not help if the parent is a "Label Only" member. "Label Only" parents have an Implied Share with their first child, no matter how many other aggregating children are present. The only way to disable implied sharing in such a scenario is to change the "Label Only" storage type.
III. Change the Design of the Planning Data Form

Do not include both parent and child on the same data form.
IV. Disable Implied Sharing Completely

Prior to version 11.1.1.0 this could only be done on a server-wide basis, so that all applications on the Essbase server would be affected. Since disabling Implied Sharing will have a negative impact on performance and database size this should not be done lightly.
Disable Implied Sharing for the entire Essbase server (9.3.1 and earlier)

Back up all Essbase data as a precaution

Shut down Essbase (stop the service)

Edit the ESSBASE.CFG file and add the following line:
EVENT 29

Start Essbase. Upon startup, Essbase internally eliminates the implied share optimization.

Note: do not use EVENT 29 with later versions! See the section below instead
Disable Implied Sharing on a per-application basis (Essbase 11.1.1.0 and above)

Back up Essbase data as a precaution

Shut down Essbase (stop the service)

Edit the ESSBASE.CFG file and add the following line:
IMPLIED_SHARE [application name] FALSE
This will disable implied shares for this application. Omit the square brackets when entering the real application name.
If no application name is specified implied sharing will be disabled at the server level (the same effect as EVENT 29 in earlier versions)

Start Essbase. Upon startup, Essbase internally eliminates the implied share optimization.

SET AGGMISSG works with sparse dimensions, As given in the technical reference if it is set to OFF it will not aggregate #Missing values ,which makes big difference to our calculations. If we look at the below detailed .................example it can explain how it works.

For example find below outline

Account(Dense)

Department(Sparse)

And I want to load some data to Department level 0 and aggregate the dimension to get data at parent level as my cube is BSO I have to write some calculation to get it aggregated. Assume I have data like below.

Case 1:

A1->D1 =10

A1->D2 =20

A1->D3 =20

And I will use AGG function or CALC DIM to aggregate Department data .

SET AGGMISSG OFF

Fix(Account)

AGG(Department);

ENDFIX;

Now the data looks like

A1->Department = 50

Case 2 : Again run the calculation by sending # Missing to one of the intersections like below.

A1->D1=10

A1->D2 =#Missing

A1->D3 =20

SET AGGMISSG OFF

Fix(Account)

AGG(Department);

ENDFIX;

Now the data looks like

A1->Department = 30,which is correct .

Case 3 :

Now clear all the data and load like below, and run the calculation.

A1->D1=10

A1-> D2 =20

A1-> D3 =20

SET AGGMISSG OFF

Fix(Account)

AGG(Department);

ENDFIX;

Now the data looks like

A1-> Department = 50,which is correct.

Then send #Missing to all the intersections and run the calc like below

A1->D1=#Missing

A1-> D2 =#Missing

A1-> D3 =#Missing

SET AGGMISSG OFF

Fix(Account)

AGG(Department);

ENDFIX;

Now the data looks like

A1-> Department = 50,which is Not correct because we don’t have data for Department children but still it is showing 50 .We have explanation about how it will work but not in a elaborated way to show how exactly it make difference to a calculation results.

Now run the same calculation by keeping AGGMISSG ON

SET AGGMISSG ON

Fix(Account)

AGG(Department);

ENDFIX;

Now the data looks like below

A1-> Department = #Missing which is correct.

So it will not aggregate #Missing values when you set it to OFF only when you don’t have data for all the combinations. It will only make difference when you don’t have data for all its children of particular member ,it doesn't matter whether or not you set it to OFF or ON if we have data for
atleast one child .

So i will always keep it ON to get accurate data.

Hi Guys,

Please find the link for Hyperion business rules optimization. Hope it helps to solve your business rules run time.

http://camerons-blog-for-essbase-hackers.blogspot.in/2009/06/why-i-hate-and-love-business-rules-part.html

We must be thankful to MR.Cameron for helping us.

Regards,

Kotireddy

when I try to open my data form, I am getting below error.

“Unable to obtain a connection to Hyperion Essbase. If this problem persists, please contact your administrator”

Solution

Edit the datasource via the Configuration Utility.
- Test the Essbase connection and make sure that the user used to make the connection is valid and has admin rights to Essbase.
- Restart the Hyperion Planning service once the Essbase user has been given the correct access rights.
- Login to the Essbase Administration Services (EAS) console and right click on the Essbase server name node -> Refresh security from Shared Services
- Expand the applications node (under the Essbase server name node) and check that there is an application with exactly the same name as the Planning application.
Note: Go to section 'manually recreating a Planning application in Hyperion Essbase, if the Planning application is missing in the above step.
- Login to the application in Hyperion Planning web.

Manually recreating a Planning application in Essbase:
- Login to the EAS console as admin (the Essbase user used by admin must have Essbase administrator rights)
- Go to Essbase servers -> your Essbase server name -> right click on applications -> Create application -> Using Block Storage and enter the exact Hyperion Planning Application name then click on ok.
Note: The above step will only create the application shell without the databases.
- Login to the application in Hyperion Planning web as admin and go to Administration menu -> Manage Database -> select database and filters (to create filter access to Essbase) and Refresh (refresh will also recreate the databases if they don't exist)

Regards,

Hi to all

Please find Lifecycle Management migration screen shots.It is very very important document.

http://www.oracle.com/technetwork/middleware/performance-management/tutorials/pln-lcm-obe-095602.html

This document always helps you in migration.

Regards,

Hyperion Essbase errors

Some of Hyperion essbase errors, Hope it helps you.If you need all the errors look into oracle forums.

Essbase Error 1051084 - You do not have sufficient access to delete this substitution variable.
Essbase Error 1051085 - You do not have sufficient access to get this substitution variable.
Essbase Error 1051088 - Duplicate disk volume name [%s] encountered in the disk volume settings for database [%s].
Essbase Error 1051089 - User name and password can not be the same
Essbase Error 1051090 - User Password has expired
Essbase Error 1051091 - User has been locked out. Please contact your system administrator.
Essbase Error 1051092 - User has not login the system for more than %s days. Please contact your system administrator.
Essbase Error 1051093 - Please change the password now
Essbase Error 1051094 - The new password can not be the same as the old password
Essbase Error 1051096 - Failed to rename application [%s].
Essbase Error 1051097 - Creating Samppart application and Company database
Essbase Error 1051098 - Cannot rename the only supervisor
Essbase Error 1051099 - Creating Sampeast application and East database
Essbase Error 1051100 - Failed to add application %s. License restricted to one application.
Essbase Error 1051101 - Creating East database
Essbase Error 1051102 - Getting lock for Application %s failed
Essbase Error 1051103 - Failed to Initialize the Application Specific Concurrency Control Structure for application %s.
Essbase Error 1051105 - Failed to add application. License does not allow this data storage type. Please refer to the Essbase Documentation for valid settings.
Essbase Error 1051107 - \nCannot copy database %s between applications with different storage types
Essbase Error 1052001 - Error reading from server
Essbase Error 1052002 - Error writing to server
Essbase Error 1052003 - Timed out reading from server
Essbase Error 1052004 - Timed out writing to server
Essbase Error 1053001 - Cannot open object file: %s
Essbase Error 1053002 - Cannot create application directory: %s [%s]
Essbase Error 1053003 - Application directory does not exist: %s
Essbase Error 1053004 - Cannot create database directory: %s [%s]
Essbase Error 1053005 - Database directory does not exist: %s
Essbase Error 1053006 - Invalid object type
Essbase Error 1053007 - Cannot rename object %s to %s
Essbase Error 1053008 - Cannot create object %s
Essbase Error 1053009 - Cannot delete object %s
Essbase Error 1053010 - Object %s is already locked by user %s
Essbase Error 1053011 - Object %s is not locked by user %s
Essbase Error 1053012 - Object %s is locked by user %s
Essbase Error 1053013 - Object %s unlocked by user %s
Essbase Error 1053014 - Object %s does not exist
Essbase Error 1053015 - Object %s already exists
Essbase Error 1053016 - Cannot open temporary file
Essbase Error 1053017 - Cannot open log file for application %s
Essbase Error 1053018 - Operation not permitted on outline objects
Essbase Error 1053019 - Cannot rename directory: %s [%s]
Essbase Error 1053020 - Error writing file: %s
Essbase Error 1053021 - Cannot copy object %s to itself
Essbase Error 1053022 - Database [%s] is in read-only mode for backup
Essbase Error 1053023 - User's log message: %s
Essbase Error 1054001 - Cannot load application %s - see server log file
Essbase Error 1054002 - Loading application %s is not currently permitted
Essbase Error 1054003 - Error %s loading application: %s
Essbase Error 1054004 - Application %s is not loaded
Essbase Error 1054005 - Shutting down application %s
Essbase Error 1054006 - Cannot terminate application %s
Essbase Error 1054007 - Application %s not responding
Essbase Error 1054008 - Cannot load application %s - enable IOPL in CONFIG.SYS
Essbase Error 1054009 - Application %s is currently not accepting connections
Essbase Error 1054010 - Application %s is currently not accepting user commands
Essbase Error 1054011 - Loading database %s is not currently permitted
Essbase Error 1054012 - Invalid syntax in filter line %s
Essbase Error 1054013 - Syntax error loading filters - operation canceled
Essbase Error 1054014 - Database %s loaded
Essbase Error 1054016 - Invalid file name [%s]. [%s] aborted
Essbase Error 1054017 - Cannot read from file with handle [%s], [%s] failed
Essbase Error 1054018 - RECEIVED ABNORMAL SHUTDOWN COMMAND - ESSBASE TERMINATING
Essbase Error 1054019 - Cannot modify settings for application [%s] while application is loaded and user who has modified the settings is logged in
Essbase Error 1054020 - *** Missing command line password! [%s]
Essbase Error 1054021 - Cannot modify settings for application [%s]. See server log for more information
Essbase Error 1054022 - Cannot copy application [%s] while database [%s] is in archive or read only mode
Essbase Error 1054023 - Cannot modify settings for application [%s] while database [%s] is in archive or read only mode
Essbase Error 1054024 - Agent on [%s] could be deadlocked. Increase number of t
Essbase Error 1054025 - Cannot rename application [%s] while database [%s] is in archive or read only mode
Essbase Error 1054026 - Cannot create a new database in application [%s] while database [%s] is in archive or read only mode
Essbase Error 1054027 - Application [%s] started with process id [%s]
Essbase Error 1054029 - Invalid parameter values for database file information request.
Essbase Error 1055001 - \n%s login system\n
Essbase Error 1055002 - \n Welcome to the Hyperion Essbase OLAP Server.\n\n Before using this product, you will need to register your personal\n details, including the name of your company or organization, your own\n name (which will be used to create your user id), and a secret system\n password which you will need to use each time you run the product.\n\n Be sure to choose a password which is easy to remember, but difficult\n to guess (you may wish to write it down and keep it in a safe place).\n
Essbase Error 1055003 - \n The password must be at least %s charaters long, and it can consist\n of any number of letters or spaces.\n\n
Essbase Error 1055004 - \nUser name and password can not be the same.\n\n
Essbase Error 1055005 - \n\nYou have entered the following details:\n
Essbase Error 1055006 - \n\tCompany name: %s
Essbase Error 1055007 - \n\tYour name: %s
Essbase Error 1055008 - \n\tSystem password: %s
Essbase Error 1055009 - \n\nThese will be used to create the initial system security information\nincluding the system supervisor.\n
Essbase Error 1055010 - \n\rAre these details correct? (y/n):
Essbase Error 1055011 - \n\nRe-enter your details\n\n
Essbase Error 1055012 - \n\nRegistering user information\n
Essbase Error 1055013 - \nCreating initial system security defaults...\n
Essbase Error 1055014 - \n\r%s [%s]:
Essbase Error 1055015 - \n\rPlease re-enter (must be between %s and %s characters)
Essbase Error 1055016 - \nUnlimited login system\n
Essbase Error 1055017 - \r\n*** Abnormal shutdown request entered ***\r\nShutting down all applications and exiting Essbase\r\n
Essbase Error 1055018 - \r\n*** A fatal error has happened, Essbase is trying to shutdown ***\r\n
Essbase Error 1055019 - \r\nShutdown request is aborted, Essbase will continue processing\r\n
Essbase Error 1055020 - \r\nCannot stop application %s
Essbase Error 1055021 - \nEssbase Default Storage type is Multidimensional\n
Essbase Error 1055022 - \nEssbase Default Storage type is DB2Relational\n
Essbase Error 1055023 - \nEssbase Default Storage type is Oracle Relational\n
Essbase Error 1055024 - \nEssbase Default Storage type is Undefined\n
Essbase Error 1055025 - \nHyperion Essbase OLAP Server - %s
Essbase Error 1055026 - \nCopyright 1991-2000 Hyperion Solutions Corporation.\nUS Patent Number 5,359,724\nAll Rights Reserved.\n
Essbase Error 1055027 - \nSerial number: %s\n
Essbase Error 1055028 - \r\nRegistered to: %s\r\n %s\r\n\n
Essbase Error 1055029 - Use essbase -b to start in background
Essbase Error 1055030 - Error:\t*** Incorrect password!\n
Essbase Error 1055031 - \r\nPlease type the system password:
Essbase Error 1055032 - \n\nStartup sequence completed\n
Essbase Error 1055033 - \nSecurity is enabled
Essbase Error 1055034 - \nSecurity is disabled
Essbase Error 1055035 - \nLogins are enabled
Essbase Error 1055036 - \nLogins are disabled
Essbase Error 1055037 - \nAgent Threads - %s
Essbase Error 1055038 - \nWaiting for Client Requests...\n
Essbase Error 1055039 - \nError: Cannot allocate memory.
Essbase Error 1055040 - \nError: Cannot create thread.
Essbase Error 1055041 - \nError: Cannot create daemon thread.
Essbase Error 1055042 - \n
Essbase Error 1055043 - \nExecuting command: %s\n
Essbase Error 1055044 - \n*** Usage: START application\n
Essbase Error 1055045 - \n*** Usage: STOP application\n
Essbase Error 1055046 - \nHyperion Essbase by courtesy of:\n%s
Essbase Error 1055047 - \n\n%s connection%s in use\n
Essbase Error 1055048 - \nNo users connected\n
Essbase Error 1055049 - %s port%s available\n
Essbase Error 1055050 - \nNo ports available\n
Essbase Error 1055051 - \n\n%s port%s in use\n
Essbase Error 1055052 - \nEnter system password:
Essbase Error 1055053 - \nUser [%s
Essbase Error 1055054 - ] is not logged in!\n
Essbase Error 1055055 - \n*** Usage: DUMP filename\n
Essbase Error 1055056 - \nEnter old system password:
Essbase Error 1055057 - Enter new system password:
Essbase Error 1055058 - Re-type new system password:
Essbase Error 1055059 - \n*** Passwords do not match!
Essbase Error 1055060 - \n*** Password must be less than 100 characters\n
Essbase Error 1055061 - \n*** Password must be at least %s characters\n
Essbase Error 1055062 - \nInvalid argument: %s\n
Essbase Error 1055063 - \nDebugging %sabled\n
Essbase Error 1055064 - \n*** Unknown user!\n
Essbase Error 1055065 - \n*** Usage: LOGOUTUSER user\n
Essbase Error 1055066 - \nCommands available are:\n\n
Essbase Error 1055067 - START application - start an application\n
Essbase Error 1055068 - STOP application - stop an application\n
Essbase Error 1055069 - USERS - list all connected users\n
Essbase Error 1055070 - PORTS - list port usage\n
Essbase Error 1055071 - LOGOUTUSER user - forcibly logout a user\n
Essbase Error 1055072 - PASSWORD - change the Essbase system password\n
Essbase Error 1055073 - DUMP filename - dump current state of security to a file\n
Essbase Error 1055074 - VERSION - display the Essbase version number\n
Essbase Error 1055075 - HELP - display this text\n
Essbase Error 1055076 - QUIT/EXIT - exit program (stop all applications)\n
Essbase Error 1055077 - \nERROR: Could Not Initialize Application specific Concurrency Control structure for application %s.\n
Essbase Error 1055078 - ERROR: Invalid application index %s for Substitution Variable %s\n
Essbase Error 1055079 - ERROR: Invalid database index %s for Substitution Variable %s\n
Essbase Error 1055080 - \nERROR: Substitution Variable(s) corrupted in security file\n
Essbase Error 1055081 - ACTION REQUIRED: Redefine the applications for all Substitution Variables\n
Essbase Error 1055082 - ACTION REQUIRED: Redefine the databases for all Substitution Variables\n
Essbase Error 1060000 - Invalid outline handle passed to ESSOTL function %s
Essbase Error 1060001 - NULL argument (%s) passed to ESSOTL function %s
Essbase Error 1060002 - Invalid outline type
Essbase Error 1060003 - Invalid sort type
Essbase Error 1060004 - Invalid sorting compare function
Essbase Error 1060005 - Too many members to sort
Essbase Error 1060006 - The outline is a currency outline
Essbase Error 1060007 - There is no accounts dimension
Essbase Error 1060008 - There is no time dimension
Essbase Error 1060009 - There is no country dimension
Essbase Error 1060010 - Invalid member name (%s)
Essbase Error 1060011 - Invalid consolidation type
Essbase Error 1060013 - Illegal move of member
Essbase Error 1060014 - Invalid input member name string
Essbase Error 1060015 - Illegal member name
Essbase Error 1060016 - Duplicate member name
Essbase Error 1060017 - Illegal currency member
Essbase Error 1060018 - Illegal default alias name
Essbase Error 1060019 - Illegal combinational alias name
Essbase Error 1060020 - Illegal member combinational for alias
Essbase Error 1060021 - Illegal dimension tag
Essbase Error 1060022 - No time dimension defined
Essbase Error 1060023 - Duplicate alias
Essbase Error 1060024 - Illegal member formula
Essbase Error 1060025 - Shared member not at level 0
Essbase Error 1060026 - Shared member with no actual member
Essbase Error 1060027 - Accounts dimension is dense and time dimension sparse
Essbase Error 1060028 - Leaf member defined as a label member
Essbase Error 1060030 - Illegal time balance value
Essbase Error 1060031 - Illegal time balance skip value
Essbase Error 1060032 - Illegal share value
Essbase Error 1060033 - Illegal dimension storage value
Essbase Error 1060034 - Illegal storage category
Essbase Error 1060035 - Illegal alias table
Essbase Error 1060036 - Invalid user attribute
Essbase Error 1060037 - Cannot find user attribute %s
Essbase Error 1060038 - The maximum number of alias tables has been reached
Essbase Error 1060039 - Illegal alias table name
Essbase Error 1060040 - Alias table %s already exists
Essbase Error 1060041 - Cannot rename the default alias table
Essbase Error 1060042 - Cannot delete the default alias table
Essbase Error 1060043 - Invalid object type
Essbase Error 1060044 - Cannot create temporary file name
Essbase Error 1060045 - Invalid transaction type
Essbase Error 1060046 - Could not open file
Essbase Error 1060047 - Could not read from or Write to file
Essbase Error 1060048 - Invalid restructure type passed to ESSAPI function %s
Essbase Error 1060049 - Too many dimensions in a currency outline
Essbase Error 1060050 - Member name already used
Essbase Error 1060051 - Member name already used
Essbase Error 1060052 - Too many dimensions to configure
Essbase Error 1060053 - Outline has errors
Essbase Error 1060054 - Cannot find gen or level name
Essbase Error 1060055 - Invalid gen or level name passed to ESSAPI function %s
Essbase Error 1060056 - Gen or level name already exists
Essbase Error 1060057 - Dimension name expected
Essbase Error 1060058 - Shared member cannot have a formula
Essbase Error 1060059 - There is no alias combination
Essbase Error 1060060 - Gen or level already has a name
Essbase Error 1060061 - Illegal gen or level value
Essbase Error 1060062 - There is no alias for this member
Essbase Error 1060063 - There is no formula for this member
Essbase Error 1060064 - A shared member cannot have user-defined attributes
Essbase Error 1060065 - The generation or level name is the same as a member or alias
Essbase Error 1060066 - There is a generation or level name with the same name as the member or one of its aliases
Essbase Error 1060067 - The source and destination alias tables are the same
Essbase Error 1060068 - The file was opened in the wrong mode to make this call
Essbase Error 1060069 - Illegal option
Essbase Error 1060070 - Level 0 virtual members must have a formula associated with them
Essbase Error 1060072 - Parent of an only child virtual member must also be virtual
Essbase Error 1060073 - Virtual member has more than 100 children
Essbase Error 1060074 - Dimension without children cannot be virtual
Essbase Error 1060075 - Unknown DTS member
Essbase Error 1060076 - Member in which to store data is type Dynamic Calc
Essbase Error 1060077 - DTS member is not enabled for this generation
Essbase Error 1060079 - Extended member comment exceeds maximum length
Essbase Error 1060080 - Invalid Structure ID
Essbase Error 1060081 - Attribute Dimension is not associated to the base dimension
Essbase Error 1060082 - Base member's level is not matching with the association level
Essbase Error 1060083 - Not an Attribute member
Essbase Error 1060084 - Base member is invalid. It Might be Attribute or Aggregate type
Essbase Error 1060085 - Attribute is not level zero
Essbase Error 1060086 - Attribute dimension is already associated
Essbase Error 1060087 - Not a sparse dimension(s)
Essbase Error 1060088 - Attribute is not associated with the base member
Essbase Error 1060089 - Non attribute dimension(s) exist(s) after attribute dimension
Essbase Error 1060090 - Attribute association and disassociation is not allowed for shared/label only members.
Essbase Error 1060091 - Attribute longname for member %s is longer than ESS_MBRNAMELEN
Essbase Error 1060092 - NULL value for member name string
Essbase Error 1060093 - Invalid setting for usGenNameBy in attribute specifications
Essbase Error 1060094 - Invalid setting for usUseNameOf in attribute specifications
Essbase Error 1060095 - Invalid setting for delimiter in attribute specifications
Essbase Error 1060096 - Invalid setting for Date Format in attribute specifications
Essbase Error 1060097 - Invalid setting for usBucketingType in attribute specifications
Essbase Error 1060098 - Illegal numeric attribute value
Essbase Error 1060099 - Illegal boolan attribute value
Essbase Error 1060100 - Illegal date value.
Essbase Error 1060101 - Attribute dimension can not be followed by Standard/base dimensions
Essbase Error 1060102 - Illegal datatype for attribute
Essbase Error 1060103 - Attribute members datatype is not matching with Attribute dimensions datatype.
Essbase Error 1060104 - Attribute parent-child category illegal
Essbase Error 1060105 - Attributes can not have associated UDAs
Essbase Error 1060106 - Refer to Error2 in ESS_OUTERROR_T
Essbase Error 1060107 - Illegal operation for the member
Essbase Error 1060108 - Illegal attribute value for level 0 attribute member
Essbase Error 1060109 - Boolean/AttrCalc dimensions have invalid children count
Essbase Error 1060110 - Illegal Attrcalc dimension/member name
Essbase Error 1060111 - More than one AttrCalc dimension
Essbase Error 1060112 - Invalid value being set for attribute memberinfo
Essbase Error 1060113 - Invalid value being set for attrcalc dimension/member memberinfo
Essbase Error 1060114 - Attribute Calculations dimension can not be created
Essbase Error 1060115 - Attribute Calculations dimension/member name already used.
Essbase Error 1060116 - Not a member
Essbase Error 1060118 - The error in operation has resulted in unrecoverable outline. Please abort! do not save.
Essbase Error 1060119 - In the tree/subtree being traversed, Level 0 Attribute Member's long name %s already used.
Essbase Error 1060120 - The member is not fetched as part of the query
Essbase Error 1070000 - Index cache is full. Please increase the index cache size for database [%s].
Essbase Error 1070013 - Index cache size ==> [%s] bytes, [%s] index pages.
Essbase Error 1070014 - Index page size ==> [%s] bytes.
Essbase Error 1070016 - Invalid index Context. [%s] aborted
Essbase Error 1070017 - Invalid file id [%s]. [%s] aborted
Essbase Error 1070018 - Invalid file handle [%s]. [%s] aborted
Essbase Error 1070019 - Invalid file name [%s]. [%s] aborted
Essbase Error 1070020 - Out of disk space. Cannot create a new [%s] file. [%s] aborted

Essbase Error 1070088 - Index migration to an index page size of [%s] completed successfully
Essbase Error 1070089 - Index migration to an index page size of [%s] failed
Essbase Error 1070090 - Unable to unlock physical memory allocated for the index of database [%s].
Essbase Error 1070091 - Not enough memory to allocate the index buffer cache. Using the minimum size.
Essbase Error 1070092 - Waiting to swap an index cache page for database [%s]. Performance could potentially be improved by increasing the index cache size.
Essbase Error 1070093 - Error [%s] encountered while waiting for completion of an index flush for database [%s].
Essbase Error 1070094 - Premature end of a file descriptor page chain for database [%s] was encountered.
Essbase Error 1070095 - Migrating the database index from V6 Beta I format to V6 format ...
Essbase Error 1070096 - Index migration from V6 Beta I format to V6 format completed successfully
Essbase Error 1070097 - Index migration from V6 Beta I format to V6 format failed
Essbase Error 1070098 - Error [%s] encountered while waiting to traverse the index for database [%s].
Essbase Error 1080001 - Block in the transaction list has an invalid status. [%s] aborted
Essbase Error 1080004 - Unable to set the transaction flag in the .ESM file. [%s] aborted.
Essbase Error 1080007 - Transaction Commit: [%s] blocks will be processed
Essbase Error 1080009 - Fatal error [%s] encountered during transaction commit.
Essbase Error 1080010 - The Transaction Manager component of the Essbase Kernel must already have been initialized in order to begin a transaction.
Essbase Error 1080011 - The Transaction Manager component of the Essbase Kernel must already have been initialized in order to commit a transaction.
Essbase Error 1080012 - The Transaction Manager component of the Essbase Kernel must already have been initialized in order to abort a transaction.
Essbase Error 1080013 - Fatal error [%s] encountered during transaction abort.
Essbase Error 1080014 - Transaction [%s] aborted due to status [%s].
Essbase Error 1080015 - Unable to create Transaction Cleanup Daemon thread.
Essbase Error 1080016 - Error [%s] upon creating the event to stop the Transaction Cleanup Daemon.
Essbase Error 1080017 - Error [%s] upon setting the event to stop the Transaction Cleanup Daemon.
Essbase Error 1080018 - Error [%s] upon waiting for the Transaction Cleanup Daemon to stop.
Essbase Error 1080019 - Error [%s] upon deleting the Transaction Cleanup Daemon's Thread Context resources.
Essbase Error 1080020 - Transaction Cleanup Daemon terminating due to error [%s].
Essbase Error 1080021 - Invalid transaction handle [%s] passed to the Essbase Kernel for database [%s].
Essbase Error 1080022 - Reinitializing the Essbase Kernel for database [%s] due to a fatal error ...
Essbase Error 1080023 - Reinitializing the Essbase Kernel for currency database [%s] due to a fatal error ...
Essbase Error 1080024 - Reinitializing the Essbase Kernel for currency database [%s] due to a fatal error ...
Essbase Error 1080026 - Unable to recover database [%s] while the database is in read-only mode.
Essbase Error 1080027 - Performing transaction recovery for database [%s] following an abnormal termination of the server.
Essbase Error 1080028 - Performing transaction recovery for database [%s] during fatal error processing.
Essbase Error 1080029 - Transactions for database [%s] have temporarily been disabled. Please retry your operation later.
Essbase Error 1080030 - The Transaction Manager component of the Essbase Kernel must already have been initialized in order to disable transactions.
Essbase Error 1080032 - Forcibly aborting transaction [%s] while quiescing update activity on database [%s].
Essbase Error 1080033 - TCT File opened (fd = %s)
Essbase Error 1080034 - TCT File closed (fd = %s)
Essbase Error 1080035 - TCT File read error (%s, %s)
Essbase Error 1080036 - TCT File write error (%s, %s)
Essbase Error 1080037 - Transaction [%s] aborted due to invalid transaction status [%s].
Essbase Error 1080038 - Terminating the Essbase Application Server process due to a fatal error encountered by the Essbase Kernel for database [%s].
Essbase Error 1080039 - Unable to create the Database Writer's thread.
Essbase Error 1080040 - Error [%s] upon setting the event to stop the Database Writer.
Essbase Error 1080041 - Error [%s] upon waiting for the Database Writer to stop.
Essbase Error 1080042 - Database Writer terminating due to error [%s].
Essbase Error 1080043 - Error [%s] upon creating the event to start the Database Writer.
Essbase Error 1080044 - Error [%s] upon setting the event to start the Database Writer.
Essbase Error 1080045 - Error [%s] upon waiting for the Database Writer to start.
Essbase Error 1090000 - Cannot create temporary file name
Essbase Error 1090001 - Column Ordering is Incorrect (Column %s)
Essbase Error 1090002 - Member Missing For Add As Of Child Dimension Setting For Dimension [%s]
Essbase Error 1090003 - Dimension Invalid For Column [%s]
Essbase Error 1090004 - Unable To Open File [%s]
Essbase Error 1090005 - Unable To Read From File [%s]
Essbase Error 1090006 - Revision Invalid For From File [%s]
Essbase Error 1090007 - Member [%s] For Add As Of Child Dimension Is From Wrong Dimension
Essbase Error 1090008 - Field Label (Column %s) does not match build method
Essbase Error 1090009 - File [%s] Can Not Be Read, The File is Password Protected
Essbase Error 1090010 - Error in File [%s] Which is a [%s] Spreadsheet
Essbase Error 1090011 - Unable to Open Error File (%s)
Essbase Error 1090012 - Unable to Process Rules File (%s)
Essbase Error 1090013 - Cannot Open Data Source
Essbase Error 1090014 - Initialization failed - Memory Error
Essbase Error 1090015 - Error processing data file
Essbase Error 1090016 - Illegal DUPLEVEL (Column %s)
Essbase Error 1090017 - Column Contains Invalid Generation (Column %s)
Essbase Error 1090018 - Error Initializing Outline Information
Essbase Error 1090019 - Error Modifying Outline Information
Essbase Error 1090020 - Dynamic Reference Initialization failed
Essbase Error 1090021 - Error Initializing Dimension Field Name Information
Essbase Error 1090022 - Processing Terminated - No Valid Build Fields
Essbase Error 1090023 - Bad string length [%s] found reading outline
Essbase Error 1090024 - Bad region type found reading region defn file
Essbase Error 1090025 - Invalid slice map count found reading region defn file
Essbase Error 1090026 - Bad data direction found in region defn file
Essbase Error 1090027 - Unable to open file %s
Essbase Error 1090028 - File %s has bad type
Essbase Error 1090029 - Unable To Create File [%s]
Essbase Error 1090030 - Advanced numeric method (Column %s) does not match attribute dimension type
Essbase Error 1090031 - Range size must be greater than 0
Essbase Error 1090032 - Base dimension (%s) not sorted for ranges
Essbase Error 1090033 - Dimension in column %s is not a base dimension for (%s)
Essbase Error 1090034 - ATTRPARENT column %s must precede a numeric or date/time attribute association column
Essbase Error 1090035 - ATTRPARENT column %s gen value %s must match next column gen value
Essbase Error 1090036 - There were errors validating the outline. Please check the error file.
Essbase Error 1120000 - Unable to lock file [%s].
Essbase Error 1120001 - Unable to unlock physical memory allocated by the Essbase Kernel for database [%s].
Essbase Error 1140000 - Invalid LRO Context. [%s] aborted
Essbase Error 1140002 - Invalid member name entered - %s.
Essbase Error 1140003 - index entry for Linked Object not found. [%s]
Essbase Error 1140004 - mismatch linked object handle. [%s] aborted
Essbase Error 1140005 - Missing member name.
Essbase Error 1140007 - Corrupted Node Page in the LRO B+tree. [%s] aborted
Essbase Error 1140008 - Object type can not be updated. [%s]
Essbase Error 1140009 - You do not have sufficient access to perform a %s on this database
Essbase Error 1140011 - This server is not licensed with the Linked Object option
Essbase Error 1140012 - Unable to [%s] linked object; database is in readonly mode for archive
Essbase Error 1140013 - Invalid cell address entered.
Essbase Error 1140014 - Unable to delete LRO file - [%s]
Essbase Error 1140015 - Invalid member count [%s], expected [%s] members
Essbase Error 1140017 - Unable to add a linked object in [%s] due to object handle overflow.
Essbase Error 1140018 - Attribute members not allowed in LRO operations.
Essbase Error 1150000 - Cannot apply file [%s], error [%s] returned
Essbase Error 1150001 - Cannot read from file handle [%s]
Essbase Error 1150003 - Cannot create alias table [%s], error [%s] encountered
Essbase Error 1150004 - Cannot delete alias table [%s], error [%s] encountered
Essbase Error 1150005 - OUTLINE SYNC: Cannot add dimension [%s], error [%s] encountered
Essbase Error 1150006 - OUTLINE SYNC: Cannot delete dimension [%s], error [%s] encountered
Essbase Error 1150007 - OUTLINE SYNC: Cannot update dimension [%s], error [%s] encountered
Essbase Error 1150008 - OUTLINE SYNC: Cannot move dimension [%s], error [%s] encountered
Essbase Error 1150009 - OUTLINE SYNC: Cannot rename dimension [%s], error [%s] encountered
Essbase Error 1150010 - OUTLINE SYNC: Cannot add member [%s], error [%s] encountered
Essbase Error 1150011 - OUTLINE SYNC: Cannot delete member [%s], error [%s] encountered
Essbase Error 1150012 - OUTLINE SYNC: Cannot move member [%s], error [%s] encountered
Essbase Error 1150013 - OUTLINE SYNC: Cannot update member [%s], error [%s] encountered
Essbase Error 1150014 - OUTLINE SYNC: Cannot rename member [%s], error [%s] encountered
Essbase Error 1150019 - There is 1 message in the application log identifying a change that was not applied during outline synchronization.
Essbase Error 1150020 - There are %s messages in the application log identifying changes that were not applied during outline synchronization.
Essbase Error 1150021 - OUTLINE SYNC: Cannot find location for adding member [%s]
Essbase Error 1150022 - OUTLINE SYNC: Cannot find member [%s] to rename
Essbase Error 1150023 - OUTLINE SYNC: Cannot find member [%s] to move
Essbase Error 1150024 - OUTLINE SYNC: Cannot find destination for moving member [%s] with parent [%s]
Essbase Error 1150025 - OUTLINE SYNC: Cannot find member [%s] to update
Essbase Error 1150026 - OUTLINE SYNC: Cannot find dimension [%s] to rename
Essbase Error 1150027 - OUTLINE SYNC: Cannot find dimension [%s] to move
Essbase Error 1150028 - OUTLINE SYNC: Cannot find destination for moving dimension [%s]
Essbase Error 1150029 - OUTLINE SYNC: Cannot find dimension [%s] to update
Essbase Error 1150030 - OUTLINE SYNC: Cannot find location for adding dimension [%s]
Essbase Error 1150031 - OUTLINE SYNC: Cannot find attribute dimension [%s] to associate with dimension [%s]
Essbase Error 1150032 - OUTLINE SYNC: Cannot find attribute [%s] to associate with member [%s]
Essbase Error 1150033 - OUTLINE SYNC: Attribute dimension [%s] deleted due to missing base dimension
Essbase Error 1150034 - OUTLINE SYNC VERIFY: Global Error -- Too many dimensions in currency outline
Essbase Error 1150035 - OUTLINE SYNC VERIFY: Global Error -- Attribute calculations dimension is absent
Essbase Error 1150036 - OUTLINE SYNC VERIFY: No Global Error
Essbase Error 1150037 - OUTLINE SYNC VERIFY: Unknown Global Error
Essbase Error 1150038 - OUTLINE SYNC VERIFY: Member errors follow
Essbase Error 1150039 - OUTLINE SYNC VERIFY: No errors
Essbase Error 1150040 - OUTLINE SYNC VERIFY: Member %s verification fails
Essbase Error 1150041 - OUTLINE SYNC VERIFY: Illegal member name %s
Essbase Error 1150042 - OUTLINE SYNC VERIFY: Duplicate member name %s
Essbase Error 1150043 - OUTLINE SYNC VERIFY: Illegal currency member %s
Essbase Error 1150044 - OUTLINE SYNC VERIFY: Illegal default alias for member %s
Essbase Error 1150045 - OUTLINE SYNC VERIFY: Illegal alias combination for member %s
Essbase Error 1150046 - OUTLINE SYNC VERIFY: Illegal alias string for member %s
Essbase Error 1150047 - OUTLINE SYNC VERIFY: Illegal tag for member %s
Essbase Error 1150048 - OUTLINE SYNC VERIFY: No time dimension for member %s
Essbase Error 1150049 - OUTLINE SYNC VERIFY: Duplicate alias for member %s
Essbase Error 1150050 - OUTLINE SYNC VERIFY: Illegal member formula for member %s
Essbase Error 1150051 - OUTLINE SYNC VERIFY: Shared member %s not at level 0
Essbase Error 1150052 - OUTLINE SYNC VERIFY: Shared member %s with no actual member
Essbase Error 1150053 - OUTLINE SYNC VERIFY: Accounts dimension is dense and time dimension sparse
Essbase Error 1150054 - OUTLINE SYNC VERIFY: Leaf member %s defined as a label member
Essbase Error 1150055 - OUTLINE SYNC VERIFY: Alias shared for member %s
Essbase Error 1150056 - OUTLINE SYNC VERIFY: Illegal time balance value for member %s
Essbase Error 1150057 - OUTLINE SYNC VERIFY: Illegal time balance skip value for member %s
Essbase Error 1150058 - OUTLINE SYNC VERIFY: Illegal share value for member %s
Essbase Error 1150059 - OUTLINE SYNC VERIFY: Illegal dimension storage value for member %s
Essbase Error 1150060 - OUTLINE SYNC VERIFY: Illegal category for member %s
Essbase Error 1150061 - OUTLINE SYNC VERIFY: Illegal storage category for member %s
Essbase Error 1150062 - OUTLINE SYNC VERIFY: Base member (%s) association level does not match base dimension association level
Essbase Error 1150063 - OUTLINE SYNC VERIFY: Attribute dimension can not be followed by Standard/base dimensions
Essbase Error 1150064 - OUTLINE SYNC VERIFY: Attribute member (%s) datatype is not matching with Attribute dimensions datatype.
Essbase Error 1150065 - OUTLINE SYNC VERIFY: Attribute parent-child category illegal for member %s
Essbase Error 1150066 - OUTLINE SYNC VERIFY: Attribute Dimension %s is not associated to the base dimension
Essbase Error 1150067 - OUTLINE SYNC VERIFY: Attribute member %s can not have associated UDAs
Essbase Error 1150068 - OUTLINE SYNC VERIFY: Boolean/AttrCalc dimension %s has invalid children count
Essbase Error 1150069 - OUTLINE SYNC VERIFY: Illegal Attrcalc dimension/member name %s
Essbase Error 1150070 - OUTLINE SYNC VERIFY: Invalid value being set for attribute memberinfo of member %s
Essbase Error 1150071 - OUTLINE SYNC VERIFY: Invalid value being set for attrcalc dimension/member memberinfo
Essbase Error 1150072 - OUTLINE SYNC VERIFY: Illegal datatype for attribute member %s
Essbase Error 1150073 - OUTLINE SYNC VERIFY: Illegal attribute value for level 0 attribute member %s
Essbase Error 1160000 - The size of outline change records exceeds [%s], changes are not logged. Please increase OutlineChangeLogFileSize setting to [%s]
Essbase Error 1170000 - AttrTest Info [%s] [%s]
Essbase Error 1170010 - Number of base members with the Attribute association is [%s]
Essbase Error 1200000 - Framework initialization failed, error code [%s]
Essbase Error 1200001 - Error [%s] preprocessing macro [%s]
Essbase Error 1200002 - Compilation failed
Essbase Error 1200003 - Optimization stage error [%s]
Essbase Error 1200004 - Program tree rebuild error [%s]
Essbase Error 1200005 - Dependency checking error [%s]
Essbase Error 1200006 - Unable to create execution control data structure
Essbase Error 1200008 - Error [%s] executing function [%s] during optimization
Essbase Error 1200314 - Invalid array length specified
Essbase Error 1200315 - Invalid object type
Essbase Error 1200316 - Internal calculator framework error
Essbase Error 1200317 - Error : index out of range
Essbase Error 1200318 - Calculator framework error: stack full
Essbase Error 1200319 - Error: memory buffer full
Essbase Error 1200320 - Error getting function signature. Invalid function code: [%s]
Essbase Error 1200321 - Error: name redefinition
Essbase Error 1200322 - Error: bracket mismatch
Essbase Error 1200323 - Syntax error: expression expected after [%s]
Essbase Error 1200324 - Syntax error: operator expected after [%s]
Essbase Error 1200325 - Error: nothing to do
Essbase Error 1200326 - Error: semicolon missing
Essbase Error 1200327 - Error: identifier expected after [%s]
Essbase Error 1200328 - Invalid declaration
Essbase Error 1200329 - Invalid assignment
Essbase Error 1200330 - Invalid variable name
Essbase Error 1200331 - Invalid initializer
Essbase Error 1200332 - Invalid number format
Essbase Error 1200333 - Error: no matching quote found
Essbase Error 1200334 - Error: invalid argument number
Essbase Error 1200335 - Error: invalid argument
Essbase Error 1200336 - Error: [%s] without [%s]
Essbase Error 1200337 - Error: [%s] without [%s]
Essbase Error 1200338 - Error: [%s] without [%s]
Essbase Error 1200339 - Error: [%s] without [%s]
Essbase Error 1200340 - Error: [%s] without [%s]
Essbase Error 1200341 - Error: [%s] without [%s]
Essbase Error 1200342 - Error: procedure without [%s]
Essbase Error 1200343 - Error: [%s] without procedure
Essbase Error 1200344 - Error: [%s] without [%s]
Essbase Error 1200345 - Error: [%s] without [%s]
Essbase Error 1200346 - Error: [%s] without [%s]
Essbase Error 1200347 - Error: [%s] must be function
Essbase Error 1200348 - Error: name is reserved
Essbase Error 1200349 - Expression is constant
Essbase Error 1200350 - Error: construction requires more points
Essbase Error 1200351 - Error: spline data invalid (may be repeated points)
Essbase Error 1200352 - Error: invalid weight
Essbase Error 1200353 - Error: invalid data
Essbase Error 1200354 - Type mismatch: argument [%s] cannot be [%s]
Essbase Error 1200355 - Error: name redefinition
Essbase Error 1200356 - Error: invalid type
Essbase Error 1200357 - Error: invalid dimension
Essbase Error 1200358 - Unexpected end of expression: [%s]
Essbase Error 1200359 - Error: illegal procedure variable name
Essbase Error 1200360 - Error: illegal syntax
Essbase Error 1200361 - Error: unknown function: [%s]
Essbase Error 1200362 - Error: [%s] withour [%s]
Essbase Error 1200363 - Invalid array dimension
Essbase Error 1200364 - Arguments have different dimensions ([%s] and [%s])
Essbase Error 1200365 - Infinite loop suspected. Execution cancelled
Essbase Error 1200366 - Invalid macro argument number
Essbase Error 1200367 - Error: invalid moving window width
Essbase Error 1200368 - Error: delimiter mismatch Error 1200369 - Error: cannot cross members from the same dimension
Essbase Error 1200370 - Error: attempt to cross a null member
Essbase Error 1200371 - [%s] dimension undefined. No default parameter allowed
Essbase Error 1200372 - Error: range not from the [%s] dimension
Essbase Error 1200373 - Error: argument must be a valid generation or level name or number
Essbase Error 1200374 - Invalid expression return type
Essbase Error 1200375 - Invalid procedure syntax
Essbase Error 1200376 - Fatal error: core function [%s] undefined
Essbase Error 1200377 - Invalid [%s] syntax
Essbase Error 1200378 - Empty [%s] block
Essbase Error 1200379 - Error: arrays have different sizes
Essbase Error 1200380 - Invalid tag
Essbase Error 1200381 - Invalid range
Essbase Error 1200382 - Invalid dimension number in projection
Essbase Error 1200383 - Invalid SKIP instruction
Essbase Error 1200384 - Invalid execution mode
Essbase Error 1200385 - Invalid macro syntax
Essbase Error 1200386 - Number of arguments in a macro must be an integer
Essbase Error 1200387 - Invalid member name
Essbase Error 1200390 - Basis member for allocation not supplied
Essbase Error 1200391 - Invalid method specified to allocate function
Essbase Error 1200392 - Allocation amount must include a member from every allocation range dimension. Calculation results may be unpredictable
Essbase Error 1200393 - Round member must include a member from every allocation range. Calculation results may be unpredictable
Essbase Error 1200394 - Allocation range is empty. Calculation results may be unpredictable
Essbase Error 1200395 - Xref connection to data source [%s] timed out. Restoring connection...
Essbase Error 1200396 - Invalid argument number in argument request
Essbase Error 1200397 - Invalid argument type (double expected)
Essbase Error 1200398 - Invalid argument type (member range expected)
Essbase Error 1200399 - Invalid argument type (external variable or array expected)
Essbase Error 1200400 - Scalar double argument expected
Essbase Error 1200401 - Single member argument expected
Essbase Error 1200402 - Single string argument expected
Essbase Error 1200403 - Single range argument expected
Essbase Error 1200404 - Single numerical argument expected
Essbase Error 1200405 - Operands of a binary operator have different dimensions
Essbase Error 1200406 - Error: attempt to redefine constant [%s]
Essbase Error 1200407 - Error: attempt to redefine function [%s]
Essbase Error 1200408 - Error: attempt to redefine macro [%s]
Essbase Error 1200409 - Internal error: calculator stack contains a null object
Essbase Error 1200410 - Error [%s] getting parameters for function [%s]
Essbase Error 1200411 - Error [%s] executing function [%s]
Essbase Error 1200412 - Argument type mismatch in function [%s]
Essbase Error 1200413 - Argument dimension mismatch in function [%s]
Essbase Error 1200414 - Argument [%s] may not have length [%s]
Essbase Error 1200415 - Internal error: unexpected end of program code
Essbase Error 1200416 - Cannot assign [%s] objects of different length
Essbase Error 1200417 - Cannot assign objects of different types ([%s] and [%s])
Essbase Error 1200418 - Cannot assign objects of different length ([%s] and [%s])
Essbase Error 1200419 - Attempt to assign an object of type [%s] where [%s] was expected
Essbase Error 1200420 - Error encountered on line [%s]
Essbase Error 1200421 - Error encountered on or after line [%s]
Essbase Error 1200422 - Expected type [%s] found [%s]
Essbase Error 1200423 - Exceeded [%s] iterations in [%s]. The result may be meaningless
Essbase Error 1200426 - Argument missing in function [%s]
Essbase Error 1200427 - Invalid date format string in function [%s]
Essbase Error 1200428 - Arguments out of range when compiling a formula involving @POWER and constants. Returned value may be different from versions < 6.0
Essbase Error 1200429 - Argument [%s] is out of range when compiling a formula involving @FACTORIAL and constants. Returned value may be different from versions < 6.0
Essbase Error 1200430 - Division by zero occured when compiling a formula involving constants. Returned value may be different from versions < 6.0
Essbase Error 1200431 - Formula for member [%s] altered internally
Essbase Error 1200432 - Original formula [%s] Modified formula [%s]
Essbase Error 1200434 - Invalid operator specified in function [%s]
Essbase Error 1200436 - Error: procedure should return a value. [%s] operator missing
Essbase Error 1200437 - Error: invalid mode [%s] in function [%s]
Essbase Error 1200438 - Compiling formula for member [%s]
Essbase Error 1200439 - Reserved token [%s] encountered on line [%s] currently not supported
Essbase Error 1120110 - Could not open the DB2 OLAP Server configuration file.
Essbase Error 1120111 - No relational database name was supplied in the DB2 OLAP Server configuration file.
Essbase Error 1120113 - DB2 OLAP Server has encountered an error. %s
Essbase Error 1120200 - The cube could not be located in the Cube Catalog table.
Essbase Error 1120201 - The number of start-up connections is greater than the maximum pool size.
Essbase Error 1120202 - A database with the name [%s] already exists in the relational database for this application.
Essbase Error 1120300 - Anchor dimension definition cannot be changed with data loaded. Outline changes rejected. Remove all data from the database and try again.
Essbase Error 1120301 - No anchor dimension specified. Outline changes rejected. Specify an anchor dimension and try again.
Essbase Error 1120302 - More than one anchor dimension specified. Outline changes rejected.
Essbase Error 1120303 - Anchor dimension specified is SPARSE. The anchor dimension must be DENSE. Outline changes rejected.
Essbase Error 1120304 - Not enough columns remain in the fact table to store the added dimensions. Outline changes rejected.
Essbase Error 1120305 - Not enough columns remain in the fact table to store the anchor dimension members added. Outline changes rejected.
Essbase Error 1120306 - A short name for the dimension could not be created. Rename the dimension and try again.
Essbase Error 1120307 - A relational name for a fact column could not be created.
Essbase Error 1120308 - DB2 OLAP Server could not select a suitable anchor dimension from those in the outline. Outline changes rejected.
Essbase Error 1120309 - The system selected anchor dimension [%s] cannot be replaced by a user-specified anchor dimension with data loaded. Outline changes rejected.
Essbase Error 1120310 - The system selected anchor dimension [%s] has been deleted with data loaded. Outline changes rejected.
Essbase Error 1120311 - The system selected anchor dimension [%s] has been made SPARSE with data loaded. Outline changes rejected.
Essbase Error 1120312 - The system selected anchor dimension [%s] has been made SPARSE but no suitable replacement anchor dimension could be found. Outline changes rejected.
Essbase Error 1120313 - The system selected anchor dimension [%s] has been deleted but no suitable replacement anchor dimension can be found. Outline changes rejected.
Essbase Error 1120314 - The migration of database [%s] has begun.
Essbase Error 1120315 - The migration of database [%s] has ended successfully.
Essbase Error 1120316 - The addition of alias table [%s] has failed because its name is the same as a current relational attribute column name on dimension [%s]. Outline changes were rejected.
Essbase Error 1120323 - Database [%s] in application [%s] was not started because the outline file does not match the outline stored in the relational database.
Essbase Error 1120501 - Some relational database commits worked and some failed. Database [%s] in application [%s] may not be valid.
Essbase Error 1120801 - The outline restructure used up all the available [%s] bytes of memory. Increase the data or index cache by [%s] bytes to improve outline restructure performance.
Essbase Error 1120900 - The relational database environment could not be initialized.
Essbase Error 1120901 - An error was encountered when closing the relational database environment.
Essbase Error 1120902 - Using default isolation level of cursor stability. The value specified in the configuration file is not valid.

Essbase Error 1120926 - The relational database returned information following an extended read.
Essbase Error 1120927 - The relational database returned an error when processing an extended read.
Essbase Error 1120928 - The relational database returned an error when preparing an extended read.
Essbase Error 1120929 - The relational database returned information when the DB2 OLAP Server requested a named data cursor.
Essbase Error 1120930 - The relational database returned an error when the DB2 OLAP Server requested a named data cursor.
Essbase Error 1120931 - DB2 OLAP Server encountered a column with an unsupported data type while copying a table.
Essbase Error 1120932 - DB2 OLAP Server encountered a column with an unknown data type while copying a table.
Essbase Error 1120937 - Database error information: %s.
Essbase Error 1120938 - The relational database returned an error when the DB2 OLAP Server requested a result column count.
Essbase Error 1120939 - The relational database returned information when the DB2 OLAP Server requested a result set description.
Essbase Error 1120940 - The relational database returned an error when the DB2 OLAP Server requested a result set description.
Essbase Error 1120941 - DB2 OLAP Server encountered an internal error while preparing an SQL string.
Essbase Error 1120942 - The relational database returned information when the DB2 OLAP Server prepared an SQL SELECT statement.
Essbase Error 1120943 - The relational database returned information when the DB2 OLAP Server read internal ID data.
Essbase Error 1120944 - The relational database returned an error when the DB2 OLAP Server read internal ID data.
Essbase Error 1120945 - DB2 OLAP Server encountered an internal error when attempting to allocate a new internal ID.
Essbase Error 1120946 - DB2 OLAP Server encountered an error when attempting to query configuration information for the relational database.
Essbase Error 1120947 - DB2 OLAP Server encountered an error because DB2 is not enabled for multiple concurrent connections.
Essbase Error 1120952 - The relational database has encountered an error: %s
Essbase Error 1121000 - DB2 OLAP Server failed to open the storage manager. %s (%s) Report this error to your system administrator.
Essbase Error 1121001 - DB2 OLAP Server failed to close the storage manager. %s (%s) Report this error to your system administrator.
Essbase Error 1121002 - DB2 OLAP Server failed to open an application. %s (%s) Report this error to your system administrator.
Essbase Error 1121003 - DB2 OLAP Server failed to close an application. %s (%s) Report this error to your system administrator.
Essbase Error 1121004 - DB2 OLAP Server failed to open a database. %s (%s) Report this error to your system administrator.
Essbase Error 1121005 - DB2 OLAP Server failed to close a database. %s (%s) Report this error to your system administrator.
Essbase Error 1121006 - DB2 OLAP Server failed to open a thread. %s (%s) Report this error to your system administrator.
Essbase Error 1121007 - DB2 OLAP Server failed to close a thread. %s (%s) Report this error to your system administrator.
Essbase Error 1121008 - DB2 OLAP Server failed to open a transaction. %s (%s) Report this error to your system administrator.
Essbase Error 1121009 - DB2 OLAP Server failed to close a transaction. %s (%s) Report this error to your system administrator.
Essbase Error 1121010 - DB2 OLAP Server failed to commit a transaction. %s (%s) Report this error to your system administrator.
Essbase Error 1121011 - DB2 OLAP Server failed to abort a transaction. %s (%s) Report this error to your system administrator.
Essbase Error 1121012 - DB2 OLAP Server failed to fix a block. %s (%s) Report this error to your system administrator.
Essbase Error 1121013 - DB2 OLAP Server failed to fix the next block. %s (%s) Report this error to your system administrator.
Essbase Error 1121014 - DB2 OLAP Server failed to read a block. %s (%s) Report this error to your system administrator.
Essbase Error 1121015 - DB2 OLAP Server failed to unfix a block. %s (%s) Report this error to your system administrator.
Essbase Error 1121016 - DB2 OLAP Server failed to set the database to a read-only state. %s (%s) Report this error to your system administrator.
Essbase Error 1121017 - DB2 OLAP Server failed to set the database to a read-write state. %s (%s) Report this error to your system administrator.
Essbase Error 1121018 - DB2 OLAP Server failed to clear data from the database. %s (%s) Report this error to your system administrator.
Essbase Error 1121019 - DB2 OLAP Server failed to retrieve database information. %s (%s) Report this error to your system administrator.
Essbase Error 1121020 - DB2 OLAP Server failed to retrieve database runtime information. %s (%s) Report this error to your system administrator.
Essbase Error 1121021 - DB2 OLAP Server failed to free database information. %s (%s) Report this error to your system administrator.
Essbase Error 1121022 - DB2 OLAP Server failed to restructure a database. %s (%s) Report this error to your system administrator.
Essbase Error 1121023 - DB2 OLAP Server failed to create a new database. %s (%s) Report this error to your system administrator.
Essbase Error 1121024 - DB2 OLAP Server failed to delete a database. %s (%s) Report this error to your system administrator.
Essbase Error 1121025 - DB2 OLAP Server failed to rename a database. %s (%s) Report this error to your system administrator.
Essbase Error 1121026 - DB2 OLAP Server failed to copy a database. %s (%s) Report this error to your system administrator.
Essbase Error 1121027 - DB2 OLAP Server failed to archive a database. %s (%s) Report this error to your system administrator.
Essbase Error 1121028 - DB2 OLAP Server failed to validate a database. %s (%s) Report this error to your system administrator.
Essbase Error 1121029 - DB2 OLAP Server failed to create a new application. %s (%s) Report this error to your system administrator.
Essbase Error 1121030 - DB2 OLAP Server failed to delete an application. %s (%s) Report this error to your system administrator.
Essbase Error 1121031 - DB2 OLAP Server failed to rename an application. %s (%s) Report this error to your system administrator.
Essbase Error 1121032 - DB2 OLAP Server failed to copy an application. %s (%s) Report this error to your system administrator.
Essbase Error 1121033 - DB2 OLAP Server failed to link an object. %s (%s) Report this error to your system administrator.
Essbase Error 1121034 - DB2 OLAP Server failed to delete a linked object. %s (%s) Report this error to your system administrator.
Essbase Error 1121035 - DB2 OLAP Server failed to update a linked object. %s (%s) Report this error to your system administrator.
Essbase Error 1121036 - DB2 OLAP Server failed to get a linked object. %s (%s) Report this error to your system administrator.
Essbase Error 1121037 - DB2 OLAP Server failed to get the catalog of linked objects. %s (%s) Report this error to your system administrator.
Essbase Error 1121038 - DB2 OLAP Server failed to list the linked objects. %s (%s) Report this error to your system administrator.
Essbase Error 1121039 - DB2 OLAP Server failed to purge the linked objects. %s (%s) Report this error to your system administrator.
Essbase Error 1121040 - IBM DB2 OLAP Server 5679-OLP (C) Copyright IBM Corp., 1998. All rights reserved. Licensed Materials - Property of IBM. US Government Users Restricted Rights. Use, duplication or disclosure restricted by GSA ADP Schedule contract with IBM Corp.
Essbase Error 1121041 - DB2 OLAP Server failed to create a list of LRO flags. %s (%s) Report this error to your system administrator.
Essbase Error 1121042 - DB2 OLAP Server failed to free LRO memory. %s (%s) Report this error to your system administrator.
Essbase Error 1121043 - DB2 OLAP Server failed to retrieve the current database settings. %s (%s) Report this error to your system administrator.
Essbase Error 1121044 - DB2 OLAP Server internal error.
Essbase Error 1121102 - DB2 OLAP Server could not continue because the [%s] entry in the rsm.cfg file is not a supported parameter. Report this error to your system administrator.
Essbase Error 1121103 - DB2 OLAP Server could not continue because the [%s] parameter in the rsm.cfg file is not supported in the section for application [%s]. Report this error to your system administrator.
Essbase Error 1121104 - DB2 OLAP Server could not continue because the [%s] parameter in the rsm.cfg file is not supported in the section for database [%s]. Report this error to your system administrator.
Essbase Error 1121105 - DB2 OLAP Server could not continue because the value [%s] specified in the rsm.cfg file for parameter [%s] is incorrect. Report this error to your system administrator.
Essbase Error 1121200 - The LRO object was not updated because the provided status did not match the status in the LRO table.
Essbase Error 1121201 - The LRO object was not updated because the provided object type did not match the object type in the LRO table.
Essbase Error 1121202 - The update or get LRO operation failed because the LRO object was not found in the LRO table.
Essbase Error 1121302 - The removal of the relational attribute column [%s] failed because relational attributes exist in the column. The column must be empty before being removed. Outline changes were rejected.
Essbase Error 1121303 - No relational attribute column name was found after the RELCOL keyword for dimension [%s]. Outline changes were rejected.
Essbase Error 1121304 - No data type was found after the RELCOL keyword and relational attribute column name [%s] for dimension [%s]. Outline changes were rejected.
Essbase Error 1121305 - The relational attribute column name [%s] specified after the RELCOL keyword for dimension [%s] is too long. Outline changes were rejected.
Essbase Error 1121306 - No recognized data type was found after the RELCOL keyword and relational attribute column name [%s] for dimension [%s]. Outline changes were rejected.
Essbase Error 1121307 - No size was found following a character data type after the RELCOL keyword and relational attribute column name [%s] for dimension [%s]. Outline changes were rejected.
Essbase Error 1121308 - No matching single quote was found at the end of a column name after the RELCOL keyword for dimension [%s]. Outline changes were rejected.
Essbase Error 1121309 - The column name [%s] after the RELCOL keyword for dimension [%s] does not conform to the naming convention for columns in the relational database. Outline changes were rejected.
Essbase Error 1121310 - The column name [%s] after the RELCOL keyword for dimension [%s] is the same as the name of a current relational attribute column or an attribute column being deleted. Outline changes were rejected.
Essbase Error 1121311 - The column name [%s] after the RELCOL keyword for dimension [%s] is the same as the name of a current alias table. Outline changes were rejected.
Essbase Error 1121312 - No relational attribute column name was found after the RELVAL keyword for member [%s] in dimension [%s]. Outline changes were rejected.
Essbase Error 1121313 - No data value was found after the relational attribute column name and RELVAL keyword for member [%s] in dimension [%s]. Outline changes were rejected.
Essbase Error 1121314 - The relational attribute column name specified after the RELVAL keyword for member [%s] in dimension [%s] is too long. Outline changes were rejected.
Essbase Error 1121315 - The column name specified after the RELVAL keyword for member [%s] is not recognized as an existing relational attribute column for dimension [%s]. Outline changes were rejected.
Essbase Error 1121316 - No quotes were found surrounding the character data after the RELVAL keyword and relational attribute column name for member [%s] in dimension [%s]. Outline changes were rejected.
Essbase Error 1121317 - No matching single quote was found at the end of a column name after the RELVAL keyword for member [%s] in dimension [%s]. Outline changes were rejected.
Essbase Error 1121318 - Character data following the RELVAL keyword is larger than the size specified for the relational attribute column for member [%s] in dimension [%s]. Outline changes were rejected.
Essbase Error 1121500 - Current anchor dimension [%s] is dimension number
Essbase Error 1121501 - Number of blocks currently fixed
Essbase Error 1121502 - High water number of blocks fixed
Essbase Error 1121503 - Number of blocks currently cached
Essbase Error 1121504 - High water number of blocks cached
Essbase Error 1121505 - Maximum number of cache blocks
Essbase Error 1121506 - Block cache hit rate
Essbase Error 1121507 - Number of keys currently cached
Essbase Error 1121508 - High water number of keys cached
Essbase Error 1121509 - Maximum number of cached keys
Essbase Error 1121510 - Key cache hit rate
Essbase Error 1121511 - Percent waste fact table space in unused columns
Essbase Error 1121512 - Number of values per row in the fact table
Essbase Error 1121513 - Maximum number of rows per block in the fact table
Essbase Error 1121514 - Current number of connections
Essbase Error 1121515 - High water number of connections
Essbase Error 1121516 - Connection pool size
Essbase Error 1121517 - Maximum connection pool size
Essbase Error 1121518 - High water block cache size
Essbase Error 1121519 - High water key cache size
Essbase Error 1180000 - Autodelete group (%s) is not an Essbase/400 group. Autodelete disabled.
Essbase Error 1180001 - Cannot autodelete only supervisor!
Essbase Error 1180002 - OS400UsersGroup (%s) is not an OS/400 Group User Profile, OS400UsersGroup disabled
Essbase Error 1180003 - OS400UsersGroup (%s) is not an Essbase/400 group, OS400UsersGroup disabled
Essbase Error 1180004 - OS400CommonGroup (%s) ignored. It is not an OS/400 Group User Profile
Essbase Error 1180005 - OS400CommonGroup (%s) ignored. It is not an Essbase/400 group
Essbase Error 1180006 - Autodelete group (%s) has been deleted, Autodelete disabled
Essbase Error 1180007 - User (%s) holds lock on object (%s). Autodelete skipped
Essbase Error 1180008 - OS400UsersGroup group (%s) has been deleted, OS400UsersGroup disabled
Essbase Error 1180009 - Attempt to rename OS400UsersGroup [%s] group disallowed
Essbase Error 1180010 - Attempt to rename OS400AutoDelete [%s] group disallowed
Essbase Error 1180011 - Attempt to rename OS400CommonGroup [%s] group disallowed
Essbase Error 1180012 - Attempt to rename OS400 integrated user [%s] disallowed
Essbase Error 1180013 - OS/400 Change Password validation error: [%s]
Essbase Error 1180018 - Received Get NLS Info request
Essbase Error 1180019 - NLS Configuration differs between client and server
Essbase Error 1180020 - NLS Configuration cannot be verified with non-OS/400 Essbase server
Essbase Error 1180021 - Total Calc CPU Time : [%s] seconds
Essbase Error 1180022 - Calc Percent CPU: [%s]
Essbase Error 1180023 - Free space management overflow. Sorting input data based on sparse columns before loading or using SQL ORDER BY clause to order on sparse columns in data load rule file may alleviate this problem

Essbase Error 1017015 - The tagged CCATEGORY member [%s] does not exist
Essbase Error 1017016 - The tagged CCATEGORY member [%s] is not in Currency ACCOUNTS dimension
Essbase Error 1017018 - Removed [%s] data blocks
Essbase Error 1017019 - Unknown Member [%s] in Currency Database [%s] for SETCRTYPE Command
Essbase Error 1017020 - Member [%s] is not of TYPE dimension in Currency Database [%s] for SETCRTYPE Command
Essbase Error 1017021 - Currency Database Not Set to Database [%s]
Essbase Error 1019001 - Unable to Init Res Stack, Stack Ptr Not NULL
Essbase Error 1019002 - Unable To Open [%s]
Essbase Error 1019003 - Unable To Read Information From [%s]
Essbase Error 1019004 - Unable to write information to file [%s], errno is [%s].
Essbase Error 1019005 - Unable to Read [%s], Not a Recognized Format
Essbase Error 1019006 - Unable to Read [%s], Created Using A Previous Version
Essbase Error 1019007 - Unable To Read [%s], Type Does Not Match Name
Essbase Error 1019008 - Reading Application Definition For [%s]
Essbase Error 1019009 - Reading Database Definition For [%s]
Essbase Error 1019010 - Writing Application Definition For [%s]
Essbase Error 1019011 - Writing Database Definition For [%s]
Essbase Error 1019012 - Reading Outline For Database [%s]
Essbase Error 1019013 - Writing Outline For Database [%s]
Essbase Error 1019014 - Unable To Write Information For Database [%s]
Essbase Error 1019015 - Database Outline Already Loaded For Database [%s]
Essbase Error 1019017 - Reading Parameters For Database [%s]
Essbase Error 1019018 - Writing Parameters For Database [%s]
Essbase Error 1019019 - Reading Data File Free Space Information For Database [%s]...
Essbase Error 1019020 - Writing Free Space Information For Database [%s]
Essbase Error 1019021 - Reading Database Mapping For [%s]
Essbase Error 1019022 - Writing Database Mapping For [%s]
Essbase Error 1019024 - Reading Outline Transaction For Database [%s]
Essbase Error 1019025 - Reading Rules From Rule Object For Database [%s]
Essbase Error 1019026 - Unknown member [%s] found while processing string [%s]
Essbase Error 1019028 - Out of disk space, Unable to write information to file [%s]
Essbase Error 1019029 - Can not read data. Page file volume [%s] from the index section differs from the volume defined by ARBORPATH [%s]
Essbase Error 1019030 - Checking Data Indexes For Database [%s]
Essbase Error 1019031 - Unable to write [%s]; database is in readonly mode for backup
Essbase Error 1019032 - Unable to write to [%s]; database is in readonly mode for archive
Essbase Error 1019034 - Reading Outline Change Log For Database [%s]
Essbase Error 1019035 - Writing Outline Change Log For Database [%s]
Essbase Error 1019036 - Dimension number [%s] for Database [%s] is invalid
Essbase Error 1019037 - Member number [%s] for Database [%s] is invalid
Essbase Error 1019038 - DB file is missing.
Essbase Error 1019039 - Cannot write to file [%s] because object type [%s] is invalid. Make sure Essbase is properly installed and configured.
Essbase Error 1019040 - Unable to write to file [%s] because the application is shutting down
Essbase Error 1019041 - Unable to write information to file [%s], adWriteObject returns [%s]. See server logfile for details.
Essbase Error 1019042 - Unable to move the file pointer to the location specified for file [%s], errno is [%s].
Essbase Error 1019043 - Error Creating Outline Pool For Database [%s]
Essbase Error 1180024 - %s error(s) logged during data load operation
Essbase Error 1180025 - ESSCMD/400 exiting
Essbase Error 1180026 - Too few arguments for %s command. Each missing argument will be substituted with . This may cause the command to fail. See subsequent messages (if any) to determine if this command was successful.
Essbase Error 1180027 - You must login before using the %s command
Essbase Error 1180028 - You must select a Database before using the %s command
Essbase Error 1180029 - Error(s) logged during dimension build operation
Essbase Error 1180030 - User (%s) is managed via Integrated Security. This change must be made via OS/400 User Profile management interfaces

Subscribe to: Posts ( Atom )

Oracle Hyperion

Hyperion Essbase Interview Questions and answers part2

Hyperion Essbase Interview Questions and answers part2

Restore Essbase application from Backup

Restore Essbase application from Backup

How to display data in Hyperion planning webforms in format other than standard numeric format

How to display data in Hyperion planning webforms in format other than standard numeric format

Understanding Essbase Implied sharesproperty

Understanding Essbase Implied sharesproperty

When are Implied Shares Created?

Unintended Effects on Planning Data Forms

How to Avoid the Side Effects of Implied Shares in Planning

SET AGGMISSG ON/OFF in Hyperion Essbase

SET AGGMISSG ON/OFF in Hyperion Essbase

Hyperion Planning business rule optimization

Hyperion Planning business rule optimization

Unable to Obtain a Connection to Hyperion Essbase from Planning Application

Unable to Obtain a Connection to Hyperion Essbase from Planning Application

Lifecycle Management Migration(Hyperion planning)

Lifecycle Management Migration(Hyperion planning)

Hyperion Essbase Errors

Hyperion Essbase Errors

Facebook Fan Page

Contact Us