essbase error message reference

O R A C L E E S S B A S E

R E L E A S E 1 1 . 1 . 1

E R R O R M E S S A G E R E F E R E N C E

Essbase Error Message Reference, 11.1.1

Copyright 1996, 2008, Oracle and/or its affiliates. All rights reserved.

Authors: EPM Information Development Team

This software and related documentation are provided under a license agreement containing restrictions on use anddisclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement orallowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit,perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilationof this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you findany errors, please report them to us in writing.

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S.Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS: Programs, software, databases, and relateddocumentation and technical data delivered to U.S. Government customers are "commercial computer software" or"commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplementalregulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions andlicense terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Governmentcontract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software is developed for general use in a variety of information management applications. It is not developed orintended for use in any inherently dangerous applications, including applications which may create a risk of personalinjury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe,backup, redundancy and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaimany liability for any damages caused by use of this software in dangerous applications.

This software and documentation may provide access to or information on content, products and services from thirdparties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind withrespect to third party content, products and services. Oracle Corporation and its affiliates will not be responsible for anyloss, costs, or damages incurred due to your access to or use of third party content, products or services.

Contents

Chapter 1. Understanding Essbase Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2. 1002122 to 1270527: Aggregate Storage Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 3. 1003000 to 1003048: Data Load Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 4. 1006002 to 1006057: Data Cache Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Chapter 5. 1008001 to 1008152: System Call Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Chapter 6. 1012000 to 1012750: Calculation Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Chapter 7. 1014004 to 1014043: Lock Manager Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Chapter 8. 1019002 to 1019056: Database Object Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Chapter 9. 1040002 to 1042025: Network Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Chapter 10. 1051002 to 1055041: Agent Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Chapter 11. 1120000 to 1120002: C Grid API Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Chapter 12. 1130203 to 1130613: Miscellaneous Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Appendix A. Referenced Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Setting Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Checking for Database Corruption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Fixing Database Corruption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Checking the User Limit Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Setting NETDELAY and NETRETRYCOUNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Ending the Server Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Unlocking Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Determining Operating System Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Contents iii

iv Contents

1Understanding Essbase Error

Messages

This document describes common Oracle Essbase error messages and informational messages,including possible causes and possible solutions for the errors. This reference does not documentevery error message that you may encounter.

See also theOracle Essbase Database Administrator's Guide and the Oracle Essbase TechnicalReference.

Table 1 provides error message categories for each error number range that is shown in the firstcolumn. When you receive an error message, use this table to identify the Essbase componentto which the error is related. .

Table 1 Error Message Categories

Error Message Number Range Component That Generated the Error

1001000-1001999 Report Writer

1002000-1002999 General server

1003000-1003999 Data load

1004000-1004999 General server

1005000-1005999 Backup, export, or validate

1006000-1006999 Data cache

1007000-1007999 Outline restructure

1008000-1008999 System calls, portable layer, ASD, or Agent

1009000-1009999 Restoring ASCII data

1010000-1010999 Internal (block numbering)

1011000-1011999 Internal (utilities)

1012000-1012999 Calculator

1013000-1013999 Requestor

1014000-1014999 Lock manager

1015000-1015999 Alias table

1016000-1016999 Report Writer

5


1017000-1017999 Currency

1018000-1018999 Not currently used

1019000-1019999 Database artifacts

1020000-102999 Spreadsheet extractor

1021000-1021999 SQL Interface

1022000-1022999 Security

1023000-1023999 Partitioning

1024000-1024999 Query Extractor

1030000-1030999 API

1040000-1040999 General network

1041000-1041999 NetworkNamed Pipes

1042000-1042999 NetworkTCP


1050000-1055999 Agent


1060000-1060999 Outline API


1070000-1070999 Index manager


1080000-1080099 Transaction manager


1090000-1099999 Rules file processing



1110000-1119999 Oracle's Hyperion Web Analysis

1120000-1129999 Grid API

1130000-1139999 Miscellaneous

1140000-1149999 Linked Reporting Objects (LRO)

6 Understanding Essbase Error Messages


1150000-1159999 Outline synchronization

1160000-1169999 Outline change records

1170000-1179999 Attributes

1180000-1189999 Showcase

1190000-1199999 Oracle Essbase Integration Services

1200000-1200999 Calculator framework

7

8 Understanding Essbase Error Messages

21002122 to 1270527: Aggregate

Storage Messages

Table 2 lists general server error and informational messages that are specific to aggregate storage.

Table 2 Aggregate Storage Messages 1002122 to 1270517

Message Number Message Possible Cause Possible Solution

1002122 Aggregate storageapplications ignore diskvolume settings inessbase.cfg

A DISKVOLUMES setting thatapplies to this database isspecified in essbase.cfg.Essbase ignores this settingas it does not use diskvolume settings to allocatestorage for aggregatestorage databases.

Essbase uses tablespaces tooptimize data storage andretrieval for aggregatestorage data files and workfiles. Tablespaces arelocation definitions that mapdata objects, such asaggregate views andaggregations to files.

Allocate storage by definingtablespace properties in theAdministration ServicesConsole or by using MaxL.

1003055 Aggregate storageapplications ignoreupdate to derived cells.[%s] cells skipped

The data source containsdata values for upper levelaggregate cells or formembers with formulas. Foraggregate storagedatabases, you cannot loaddata to upper level cells orcells whose values dependon formulas in the outline.

Load data only to level zerocells whose values do notdepend on formulas in theoutline.

1013101 Cannot restructure. Thereare other active users ondatabase [%s]

You cannot restructure adatabase if there are otherusers active on thedatabase.

Log off other users.

1013294, 1241164 A stopping size strictlygreater than 1.0 isrequired for aggregateselection

Essbase cannot selectaggregate views because thestorage stopping value,specified using MaxL, issmaller than 1.0.

Specify a storage stoppingvalue that is 1.0 or greater.

The stopping value is thedatabase size, expressed asa multiple of the size of theunaggregated level-0 data.For example, a stopping

9


value of 1.5 means that theaggregation should increasethe database size by nomore than 50%. It does notmake sense to specify avalue lower than 1.0,because that would meanthe aggregated databasesize is smaller than the sizeof the original unaggregatedlevel-0 data.

1060145, 1150091 It is not possible to havea formula on a labelmember

A label only member has aformula associated with it.No data is associated withlabel only members, so itdoes not make sense forthem to have formulas.

Remove the formula.

Convert the label onlymember to a non-label onlymember of a dynamichierarchy (storedhierarchies cannot haveformulas).

1060147 Aggregate storageoutlines require nonlevel-0 members inaccounts dimension anddynamic hierarchies tobe either non-storedmembers or haveinternal/external formula

A non level-0 member in theaccounts dimension or in adynamic hierarchy has thesetraits:

No label only tag.

No child that rolls up.

No member formula.

Ensure that all non level-0members in the accountsdimension and in dynamichierarchies are tagged aslabel only, have a child thatrolls up, or have a memberformula.

1060149 Label-only membersmust span all of theuppermost levels.

In a stored hierarchy, either:

The parent of a label onlymember is not tagged aslabel only.

A member at the samelevel as a label onlymember is not tagged aslabel only.

Ensure that the parents oflabel only members are alsolabel only.

Ensure that members at thesame level as label onlymembers are also labelonly.

1060172 Aggregate storageoutlines only allow anyshared member once in astored hierarchy,including prototype.

A stored hierarchy in adimension where multiplehierarchies are enabledcontains either:

A non-shared instance ofa member and a sharedinstance of thatmember.

Two shared instances ofone stored member.

Be sure that storedhierarchies in dimensionswith multiple hierarchiesenabled do not contain twoshared instances of onemember or one non-sharedand one shared instance ofone member.

1060175 Top member indimensions with multiplehierarchies must betagged as Label.

The label only tag wasremoved from the topmember in a dimension withmultiple hierarchiesenabled. When you tag the

Tag the top level member aslabel only.

10 1002122 to 1270527: Aggregate Storage Messages


top level member as multiplehierarchies enabled, it isautomatically tagged aslabel only, but it is possibleto remove the tag. If the labelonly tag is removed, theoutline fails verification.

1060180 The primary hierarchymust be tagged asStored.

The member representingthe first hierarchy (top levelmember of the hierarchy) ina dimension that hasmultiple hierarchies enabledis not tagged as a storedhierarchy. Essbase requiressuch a hierarchy to be astored hierarchy.

Tag as a stored hierarchy,the top-level member of thefirst hierarchy in thedimension.

1150085 OUTLINE SYNC VERIFY:Member %s has anincorrect label tag. Labelonly members must spanall of the uppermostlevels.

In a stored hierarchy, either:

The parent of a label onlymember is not tagged aslabel only.

A member at the samelevel as a label onlymember is not tagged aslabel only.

Ensure that the parents oflabel only members are alsolabel only.

Ensure that members at thesame level as label onlymembers are also labelonly.

1150086 OUTLINE SYNC VERIFY:Member %s has anincorrect aggregationoperator. Aggregatestorage outlines requireall members of non-accounts dimensions tohave ADD (+)aggregation, except forlabel-only members andtheir children

A non-accounts dimensionmember in a release 7.1outline does not have anaddition (+) consolidationoperator and it is not taggedas:

A label only member

The child of a label onlymember

Apply the addition (+)consolidation operator tothe member.

Note: When editingaggregate storage outlinesthat were created in release7.1, the restrictions onrelease 7.1 aggregatestorage outlines apply, evenif you are using a laterrelease of Essbase.

1150090 OUTLINE SYNC VERIFY:Aggregate storageoutlines require nonlevel-0 member %s inaccounts dimension tobe either non-storedmembers or haveinternal/external formula

A non-level 0 member in theaccounts dimension or in adynamic hierarchy is nottagged as label only, had nomember formula, and is notan aggregated value.

Ensure that all non-level 0members in the accountsdimension and in dynamichierarchies are tagged aslabel only, have at least onechild that rolls up, or have amember formula.

1150091

SeeChapter 2on page 10

1241164

See Chapter 2on page 9

11


1270001 Memory allocation failed Essbase cannot completethe requested operationbecause it ran out ofmemory.

Check the Essbase Servermemory requirements.

Configure the operatingsystem to handle morememory.

If necessary, increase thephysical memory.

1270004 Cannot completeoperation: insufficientaggregate storage cachesize

Essbase cannot perform therequested operationbecause the aggregatestorage cache size isinsufficient.

Use these guidelines toestimate the correctaggregate storage cachesize.

1270005 Fatal error: invalid pageencountered inaggregate storage file atlocation [%s]

The database is corrupt. Delete the application usingOracle EssbaseAdministration Services orMaxL and rebuild it frombackup files. Do not deletethe application from the filesystem.

If you cannot delete theapplication, delete alltablespace directories andfile locations, and reloaddata.

Tablespace directories:

ARBORPATH/app/defaultARBORPATH/app/logARBORPATH/app/metadataARBORPATH/app/temp

Call Oracle Support.

1270006 Failed to extendtablespace [%s]. Pleasesee application log fordetails

Essbase cannot extend files,nor can it create files in thetablespace file locations.Possible causes of thisproblem include:

Running out of diskspace

Reaching a userspecified limit

Essbase uses tablespaces tooptimize data storage and tooptimize retrieval for datafiles and work files.Tablespaces define one ormore location definitions

Look in the application logfor warning messages thatled up to this error.

Specify additional filelocations to accommodatethe application.




that map data objects, suchas aggregate views andaggregations, to files. Youcan specify the maximum filesize allowed within eachlocation in a tablespace.

As needed, Essbaseallocates disk space in fixedsize increments. WhenEssbase fails to extend atablespace, it prints awarning message to theapplication log, indicatingwhy it could not extend thetablespace. After eachfailure, Essbase makesanother attempt to extendthe tablespace. Afterrepeated failures, this errormessage is displayed.

1270009 Failed to removetablespace: operationnot allowed on thisspecial tablespace

You specified for removal atablespace that cannot beremoved.

Essbase sets up twotablespaces that cannot bealtered (log and metadata).You cannot remove thesystem defined tablespaces.In addition, you cannotdelete a file location within adefault or temp tablespace ifit contains data.

Check whether this is themetadata or log tablespace.Essbase cannot removemetadata and log and logtablespaces.

Check whether thetablespace contains data.Essbase cannot removetablespaces that containdata.

1270011 Failed to create filelocation [%s]: that filelocation is already usedby this tablespace

Essbase cannot create thelisted file location becausethe file location is used.

Specify another filelocation.

1270018 Failed to create filelocation: path too long

The path that you specifiedfor the tablespace filelocation is too long.

Specify a file location paththat is 460 bytes or less.

1270022 Failed to extend file: userlimit reached

Essbase cannot furtherincrease the size of the listedfile because it has reachedthe specified maximum filesize for that location in thetablespace.

Essbase uses tablespaces tooptimize data storage and tooptimize retrieval for datafiles and work files.Tablespaces define one ormore location definitionsthat map data objects, such

Increase the maximum filesize setting for thattablespace location.

13


as aggregate views andaggregations, to files. Youcan specify the maximum filesize allowed within eachlocation in a tablespace.

1270024 Fatal error at [%s], line[%s]; terminating theserver

The aggregate storageapplication is about to shutdown abnormally.

Messages before this one inthe application log mayindicate the cause of theabnormal shutdown.


1270030 Cannot proceed: thecube has noaggregations

Essbase cannot clearaggregate views because noaggregate views exist in thedatabase.

Proceed with your next task.You do not need to clearaggregate views becausenone exist in the database.

1270032 The specified view list isinvalid or the views wereselected using a differentoutline

Essbase cannot use the viewlist. Significant changes maywere made to the outlineafter the views were lastselected. Examples ofoutline changes that maymake a view list invalid arechanges to the number ofdimensions or to the numberof levels in a dimension.

After changing an outline,delete obsolete views (thisis not done automatically).

Repeat aggregate viewselection after making majorchanges to the outline.

1270035 Cannot alter tablespace:this tablespace is special

You tried to add, remove,change the location of, orchange the size of the listedlog or metadata tablespace.Altering log or metadatatablespaces is notpermitted.

Check the rules for workingwith tablespaces.

1270036 Cannot add file location:file location directory [%s] already exists. If thisdirectory is not in use byanother application,please remove it and tryagain.

A directory exists at the filelocation specified.

Choose another filelocation.

If you are sure that thedirectory is not used byanother application, removeit and try to create the filelocation again.

1270039 Failed to remove filelocation: file locationalready has blocksallocated

Essbase cannot remove afile location in a tablespaceif the database containsdata.

Clear data from thedatabase, and remove thefile location.

1270040 Data load buffer [%s]does not exist

A data load buffer has notbeen created. When usingMaxL to load data to anaggregate storage database,you must specify a buffer ID.

The data load buffer wasdestroyed. The data load

If using MaxL to load data,ensure you specify a bufferID.

If you encountered aproblem that caused thedata load buffer to bedestroyed, resolve that



buffer is automaticallydestroyed in some cases,such as running out of diskspace during a data load. Itcan also be destroyed usingMaxL, alter database.

problem, and retry the dataload.

1270041 Sort operation ran out ofmemory. Please increasethe size of the aggregatestorage cache

The aggregate storage cachesize is too small.

Increase the aggregatestorage cache size.

1270044 Cube cannot have morethan [%s] aggregates

Essbase cannot createadditional aggregate viewsbecause it has reached theupper limit.

Select fewer aggregateviews.

1270047 Data load buffer [%s] iscurrently in use

Essbase cannot execute theMaxL command, alterdatabase destroyload_buffer, because thedata load buffer is active.The data load buffer is activewhen data is being loaded toit or from it.

Wait until the data load isfinished, and issue thecommand again.

1270052 Failed to aggregateviews. Please seeapplication log for moreinformation

Essbase could not aggregatethe aggregate views.

Additional error or warningmessages in the applicationlog should indicate thecause of the problem.

1270054 Failed to read bytes fromfile: end of file

The database is corrupt. Delete the application usingAdministration Services orMaxL and rebuild it frombackup files. Do not deletethe application from the filesystem.





1270057 Requested file size limitis greater than maximum.

Essbase cannot accept thespecified file size for thetablespace because it is

Specify a file size limit thatis smaller than or equal tothe maximum.

15


Setting file size limit tomaximum

greater than the maximum.Instead, Essbase sets the filesize limit to the maximum.

1270058 No file locations exist intablespace

Essbase cannot write to atablespace because alltablespace file locations areremoved.

Add a file location to thetablespace. It is possible toremove all file locationsfrom a tablespace, but oneor more file locations mustexist before data can bewritten to it.

1270059 Specified maximum disksize is not on 8 MBboundary. Rounding upto nearest 8 MB

The maximum disk size forthe tablespace file locationis set to a number that is nota multiple of 8. Essbaseallocates disk space in 8 MBsegments, so it understandssettings that are multiples of8, for example 8, 16, 24, 32.

Do nothing. Essbaseautomatically rounds up tothe nearest 8 MB.

1270060 Specified maximum filesize is not on 8 MBboundary. Rounding upto nearest 8 MB

The maximum file size for thetablespace file location is setto a number that is not amultiple of 8. Essbaseincrements files in 8 MBsegments, so it recognizessettings that are multiples of8, for example 8, 16, 24, 32.

Do nothing. Essbaseautomatically rounds up tothe nearest 8 MB.

1270063 Attempting to re-createall aggregate storagefiles

Essbase is unable to finddata files (.dat files) whileattempting to start anaggregate storageapplication. It is attemptingto create dummy data files,containing no data, toenable the application tostart. This is because thedata files are corrupt or wereaccidentally deleted.

Restore the original datafiles from a backup copy.

Contact Oracle Support.

1270069 Preselected view listmust begin with inputview; it must be followedby all existing aggregateviews for query-basedview selection

Essbase cannot execute theexecute aggregate selectionMaxL command because theview list provided does notmeet one of theserequirements:

You are selecting viewsbased on query data,and the aggregationscript (.csc) file thatyou are using does notcontain all views in thecurrent aggregation.

Replace the aggregation.

In the using views clause,ensure you list all views inthe aggregation.



In MaxL, you areselecting views based onquery data, and you didnot list all views in theusing clause.

1270070 Serial number [%s] in thepage header doesn'tmatch [%s] in the footer






1270071 Page ID [%s] in the pageheader doesn't matchpage location






1270082 A system error occurredwith error number [%s]:[%s].

The operating systemencountered a problem. Thisis an operating system error.

Check the operating systemdocumentation.

17


Note: The second [%s]is replaced by adescription of the error asreported by the operatingsystem.

1270506 Outline generated toomany warnings. Furtherwarnings ignored

The outline generated morewarnings than Essbase candisplay. Essbase does notdisplay further warnings.

Ignore this message andcontinue to use the outline.Essbase does not preventyou from using an outlinethat generates warnings.

Edit the outline to removeconditions that generatewarnings.

1270517 Hierarchy [%s] is toocomplex: maximal widthmember numberexceeds 64 bits. Seeapplication log for details

The specified hierarchycontains too many levels.

Reduce the number of levelsin the hierarchy.

1270526 Alternate hierarchy[shared] is attached tothe primary hierarchy atan unstored level

A shared member'sprototype can not be a labelonly member.

1270527 Attribute dimension [%s]has an invalidassociation with analternate hierarchy. Foralternate hierarchies,attributes may only beassociated withmembers at level zero.

An attribute dimension cannot be tagged to an upperlevel stored hierarchy unlessit is primary.


31003000 to 1003048: Data Load

Messages

Table 3 lists data load error and informational messages.

Table 3 Data Load Messages 1003000 to 1003048


1003000 Unknown Item itemName inData Load, number RecordsCompleted

Essbase encountered afield in the data sourcethat it did not recognize.

Examine the data load log forother messages that may help toidentify the problem.

Ensure that the data source isvalid. If no records loaded, eitherthe first record is invalid or theentire data source is invalid.

Is the data source corrupt?

Is the data source in thecorrect location?

Is the data source correctlyformatted?

Ensure that the record thatcaused the data load to fail isvalid.

Is a member from eachdimension specified in thedata source or the rules file?

Is each member name in therecord valid?

Are there multiple numericdata fields in the record?

Did you try removing therecord that caused the dataload to fail and running thedata load again?

If you are using a rules file, ensurethat the rules file is valid.

Is the rules file in the correctlocation?

Is the rules file set upcorrectly?

Can you validate the rulesfile?

19


If you are using ESSCMD, ensurethat the ESSCMD syntax is valid.

Check the error log in theESSCMD script to determinewhere the unknown itemexists.

Are the parameters enclosedin quotation marks? Forexample:

IMPORT 2"ACTUALS" 4 "Y" 2"ACTUALS" "Y";

Are the parameters correct?

Do the files you are loadingexist in the correct locations?

Can you run the data loadusing AdministrationServices?

See Also

1003034

1003001 Duplicate Members FromSame Dimension On DataRecord, number RecordsCompleted

Essbase encounteredmultiple members from adimension in one record.Essbase does not loadthis record and skips tothe next record.

Ensure that the data source isvalid.

Does each record contain onlyone member name for eachdimension? For example, theTime dimension can containonly the January member inone record, not January andFebruary. If columns containduplicate members in arecord, ignore those columns.

Is each member namemapped to the correctdimension? For example, inthe Sample Basic databasethe January member shouldbe mapped to the Timedimension and not to theMarket dimension.

Are member or alias namesduplicated in otherdimensions? Member andalias names must be unique.For example, a Januarymember cannot exist in theTime dimension and theMarket dimension. Ifmembers or aliases in otherdimension have matching

20 1003000 to 1003048: Data Load Messages


names, consider adding aprefix or suffix to the membersor aliases in one dimension tomake them unique.

Are ranges set up correctly?

Are all members that mightcontain numbers (such as"100") enclosed in quotationmarks in the data source?

Are two members from thesame dimension on one linein the data source?


Are extra member namesignored in the rules file?

Do you need to move columnsaround to ensure that eachmember is connected to thecorrect dimension?



Check the error log in theESSCMD script to determinewhere the duplicate memberexists.






If you are using IntegrationServices, try these steps:

If the duplicate member is ashared member, ensure that itis tagged as a sharedmember.

If members in otherdimensions have matching

21


names, be sure to addprefixes or suffixes to themember names.

Map all members to thecorrect dimension.

Ensure that you are using thecorrect DataDirect drivers.

Launch Integration Serverusing a non-default value forthe -B parameter.

In Integration ServicesConsole, select the Delete AllMembers First option; inIntegration Services shell, useOTL_CLEAR=[Y].

See Also

1003015

1003003 Unable to Continue Data LoadAfter Item itemName, numberRecords Completed

Essbase aborted thedata load. This errormessage usually occursafter other errormessages that describewhy the data load failed.

Look through the data load errorlog to see why the data loadfailed.

If no data load error log exists, setup the load to create an error logand restart the data load.

Check the error messages thatpreceded this error message todetermine what happened.

In the data source, ensure that alldata fields are after the membername fields. In the rules file,ensure that you define the fieldsusing dimension names insteadof member names.

1003004 Incorrect Number of ColumnMembers in Symmetric FileAfter recordNumber RecordsCompleted

Essbase encounteredmore or fewer columnsthan it expected whilereading the data source.


Are all members that mightcontain possible filedelimiters (such as spaces orcommas) surrounded byquotation marks in the datasource?

Are all ranges set up correctlyin the data source?

See Also

1003005

1003005 Incorrect Number of ColumnMembers in Asymmetric File

Essbase encounteredmore or fewer columns




After recordNumber RecordsCompleted

than it expected whilereading the data source.

Are all members that mightcontain possible filedelimiters (such as spaces orcommas) surrounded byquotation marks in the datasource?

Are all ranges set up correctlyin the data source?

See Also

1003004

1003006 Unknown Text File Type AfterrecordNumber RecordsCompleted

Essbase did notrecognize the text file.

Ensure that the text file is valid.

If multiple records loaded, ensurethat ranges in the data source arecorrectly formatted.

1003007 Data value numericValueEncountered Before AllDimensions Selected

Essbase encountered anumeric data value in thedata source before alldimensions werespecified.


Is a member from eachdimension specified correctlyin the data source or rulesfile?

Is the numeric data field at theend of the record? If not,move the numeric data field inthe data source or move thenumeric data field in the rulesfile.


If you are using a header, isthe header set up correctly?Remember that you can addmissing dimension names tothe header.

Does the data source containextra spaces or tabs?

Has the updated outline beensaved?

1003008 With Data ValuenumericValue, Too ManyValues In Row, numberRecords Completed

Essbase encounteredmore numeric data fieldsin the record than it canmap to the database.



23


Are extra numeric data fieldsin the record? If so, you canignore extra data fields.

Is the numeric data field thelast field in the record? If not,move the numeric data field inthe data source or move thenumeric data field in the rulesfile.

Is each field in the datasource valid?

Is each dimension specified inthe data source or the rulesfile?

Ensure that the rules file is valid.

1003010 Data Value numericValueDoes Not Match #MissingValue in Database, numberRecords Completed

Essbase encountered aproblem when it tried tovalidate the databaseagainst the data sourceto see if both contain thesame values.

Ensure that the data source is thecontains the same values as thedatabase.

Ensure that you are validating thedatabase against the correct datasource.

If you think that the data loadedincorrectly, ensure that the datasource is set up correctly.

See Also

1003011

1003012

1003013

1003011 Data Value numericValueDoes Not Match #Invalid Valuein Database, number RecordsCompleted


Ensure that the data sourcecontains the same values as thedatabase.



See Also

1003010

1003012

1003013

1003012 Data Value numericValue IsGreater Than Value inDatabase, number RecordsCompleted

Essbase encountered aproblem when it tried tovalidate the databaseagainst the data source




to see if both contain thesame values.



See Also

1003010

1003011

1003013

1003013 Data Value numericValue IsLess Than Value in Database,number Records Completed





See Also

1003010

1003011

1003012

1003014 Unknown MembermemberName in Data Load,number Records Completed

Essbase did notrecognize the membername.


Are you using the correct datasource?

Is there an incorrect memberin the data source? If so,delete that member.

Did you try to load the correctdata source with the correctrules file?

Is the file extension correct forthe data source? All text filesmust have a file extensionof .txt. All rules files musthave a file extensionof .rul.

Ensure that the rules file is valid.

Are you using the correct rulesfile?

Is the rules file connected tothe correct outline?

25



Ensure that the member name isvalid.

Are member names orvariable names enclosed inquotation marks wherenecessary?

Does the member exist in theoutline? If not, you can addthe member by modifying theoutline during the data load orby adding the member in theOutline Editor.

Ensure that the member is notspecified in both the headerfile and the text file.


Check the error log in theESSCMD script to determinewhere the unknown membername exists.






If you are using Oracle EssbaseIntegration Services, ensure thatthese conditions are met.

If members in otherdimensions have matchingnames, add a prefix or suffixto the member names tomake them unique.

Ensure that the outline buildis successful before startingthe data load.

1003015 Member memberName is fromthe same dimension as

Essbase aborted theload because two




members defined in HeaderName, number RecordsCompleted

different members werespecified for the samedimension. One memberfrom the dimension wasspecified in the headerrecord and anothermember from the samedimension was specifiedin a record in the datasource.

Did you set the correct recordas the header record?

Do members that you specifyin the header also appear inthe data source? If so, youmust change the headerrecord or the data source.


Did you set the correct recordas the header record?

Are extra member names thatshould be ignored in the rulesfile?


Did you accidentally reject theheader record?

See Also

1003001

1003022 Unable to Open Data File Essbase cannot open thedata file.

Ensure Essbase can find the datafile.

Are the data file name andpath name correct? Check formisspellings.

If Essbase Server is on acomputer running UNIX, iscapitalization correct?

Is the data file in the specifiedlocation? Ensure that no onemoved or deleted the datafile.

Ensure Essbase can use the datafile.

Is the data file locked by aanother user (see UnlockingObjects on page 152)

Is the file extension for thedata file correct? All text filesmust have a file extensionof .txt. All rules files musthave a file extensionof .rul.

Is the data file valid?

Are your permissions correctfor the Essbase database into

27


which you are loading thedata file?

Are your operating systemprivileges correct for the datafile you are trying to load?

If you are using ESSCMD, ensurethat you are using the IMPORTcommand correctly. When youissue the IMPORT command, youhave four options to choose thedata file location.

1 (local/client object):Ensure the data file is in theclient folder.

Ensure you have readaccess to the data file.

If Essbase Server is on aUNIX platform,remember that the filename is case-sensitiveand checkcapitalization.

2 (remote server object):Ensure you have read accessto the data file.


3 (file): Ensure that youspecified the absolute pathname and the full file name(including the file typeextension).

4 (SQL): Check the ODBCconnections.

Ensure Essbase Server is properlyconfigured.

See Also

1003027

1003030

1003023 You have insufficient accessprivileges to perform a lock onthis database

You did not have thenecessary permissionsto lock the database sothat you can load data.

Contact your Essbase systemadministrator.

If you are a system administrator,grant yourself the correctpermissions.



1003024 Data Load Elapsed time :number seconds

Length of time it tookEssbase to load a datasource.

Not applicable

1003025 DATAERRORLIMIT reachednumberOfRecords. Rejectedrecords will no longer belogged

The error log was full.

You have too many errormessages to fit in thedata load or dimensionbuild error log, or you arerejecting too manyrecords to fit in the log.

Fix the errors in the data load ordimension build error log andrestart the data load.

Change the maximum number ofrecords allowed in the data loador dimension build error log.

1. If ESSBASEPATH/bin/essbase.cfg does notexist on the server computer,create one using a text editor.

2. Add or increase theDATAERRORLIMIT setting inthe ESSBASEPATH/bin/essbase.cfg file.

3. Stop and restart EssbaseServer.

4. Restart the data load.

1003027 Unable to open file Essbase cannot open thefile.

Ensure Essbase can find the file.

Are the file name and pathname correct? Check formisspellings.

If Essbase Server is on a UNIXplatform, is capitalizationcorrect?

Is file is in the specifiedlocation? Ensure that no onehas moved or deleted the file.

Ensure Essbase can use the file.

Is the data file locked byanother user (see UnlockingObjects on page 152)?

Does the file have the correctfile extension? All text filesmust have a file extensionof .txt. All rules files musthave a file extensionof .rul.

Is the file valid?

Do you have the correctpermissions for the Essbasedatabase into which you areloading the file?

Do you have the correctoperating system privileges

29


for the file you are trying toload?

If you are using ESSCMD, ensurethat you are using the IMPORTcommand correctly. When youissue the IMPORT command, youhave four options to choose thefile location .

1 (local/client object):Ensure that the data file is inthe client folder.

Ensure that you haveread access to the datafile.


2 (remote server object):Ensure that you have readaccess to the data file.




Ensure Essbase Server is properlyconfigured.

See Also

1003022

1003030

1003028 File fileName is passwordprotected and could not beread

Essbase did not have thenecessary operatingsystem privileges to openthe file you are trying toload.

Ensure that you have readprivileges for the file. See theoperating system documentation.



1003029 Encountered formatting errorin spreadsheet file fileName

Essbase encountered aformatting error in thefile.

Open the file outside of Essbaseand Ensure that the file is valid.

Is the data load runningcorrectly?

Is the file corrupt?

Is the file empty?

Is the file a type that you canload into Essbase?

1003030 Unable to load file fileName;see server logfile for details

Essbase cannot read thefile.

Ensure Essbase can find the file.

Are the file name and pathname correct? Check formisspellings.

If Essbase Server is on a UNIXplatform, is capitalizationcorrect?

Is file is in the specifiedlocation? Ensure that no onehas moved or deleted the file.

Ensure Essbase can use the file.

Is the data file locked byanother user (see UnlockingObjects on page 152)?

Does the file have the correctfile extension? All text filesmust have a file extensionof .txt. All rules files musthave a file extensionof .rul.

Is the file valid?

Do you have the correctpermissions for the Essbasedatabase into which you areloading the file?

Do you have the correctoperating system privilegesfor the file you are trying toload?

If you are using ESSCMD, ensurethat you are using the IMPORTcommand correctly. When youissue the IMPORT command, youhave four options to choose thefile location.

1 (local/client object):Ensure that the data file is inthe client folder.

31


Ensure that you haveread access to the datafile.


2 (remote server object):Ensure that you have readaccess to the data file.




Ensure that Essbase Server isproperly configured.

See Also

1003027

1003022

1003031 Commit at recordrecordNumber duringarithmetic data load

Essbase saved therecord to the Essbasedatabase.

Not applicable

1003032 Input line too long near recordrecordNumber

Essbase encountered arecord that was too longto process. Essbasecannot process recordsthat contain more than32,000 characters.

Ensure that all records areseparated by a carriage return.

Ensure that no single recordcontains more than 32,000characters.

1003034 Invalid membermemberName in data column

Essbase encountered anon-numeric value in thein data column. Datacolumns must containnumeric values only.

Make that sure that the datasource is valid.

Is the data source corrupt?

Is the data source correctlyformatted?

Ensure that the record thatcaused the data load to fail isvalid.



Is a member from eachdimension specified in thedata source or the rules file?

Is each member name in therecord valid?

Are there multiple numericdata fields in the record? If so,you can ignore extra datafields.

Is the numeric data field at theend of the record? If not,move the numeric data field inthe data source or move thenumeric data field in the rulesfile.

Are all member names thatmight contain numbers (suchas "100") enclosed inquotation marks?

Try removing the record thatcaused the data load to failand running the data loadagain.


Is the rules file in the correctlocation?

Is the header record in therules file set up correctly?


Are all dimensions specifiedin the dimensions specified inthe data source or rules file?

See Also

1003000

1003035 No data values modified byload of this data file

Essbase did not changethe values in the Essbasedatabase as a result ofthe data load.

Not applicable

1003036 Cannot load data. Membername too long: memberName

Essbase encountered amember name that wastoo long.

Ensure that the member name isvalid.

Is the member name less than80 bytes?

Did you set the file delimiter?

Does a prefix or suffix makethe member name too long?

33


1003037 Data Load UpdatednumberOfCells cells

Essbase updated theindicated number of cellsin the database.

Not applicable

1003038 Dataload queue overflow onnode nodeNumber


1003039 Cannot load data. Impliedshared membermemberName does not have areal child

Essbase cannot loaddata into the selectedmember because themember is shared.Shared members cannotcontain data.

Ensure that the member is notshared. Members are sharedunder these conditions:

If you tag the member asshared in the outline.

If the member is a parent withonly one child. If a memberonly has one child, the parentand the child share a value.This is called an impliedshare.

If the member has multiplechildren, but only one childthat consolidates to theparent. This is also called animplied share.

1003040 Parallel dataload enabled:number block prepare threads,number write threads.

Parallel data load isenabled.

Not applicable

1003041 Data Unlock Elapsed Time :number seconds

The time required tounlock all locks after theUnlock command isissued in theSpreadsheet Add-in.

Not applicable

1003048 Loading Unicode-encodeddata to non-Unicode modeapplication is not supported

You have attempted toload unicode encodeddata to a non-unicodeapplication.

Verify that you have migrated yourapplication to unicode mode.


41006002 to 1006057: Data Cache

Messages

Table 4 lists data cache error and informational messages.

Table 4 Data Cache Messages 1006002 to 1006057


1006002 Unable to Store InformationIn Page File

Disk space isinadequate forEssbase to store thedata in a page file.

If possible, add more disk space. If youcannot add more disk space, considerspanning disk volumes.

If an operation, such as a calculation, didnot complete, perform recoveryprocedures.

Determine whether the database iscorrupt (see Checking for DatabaseCorruption on page 150).

1006004 Unable to Read InformationFrom Page File

Essbase cannot readthe page file.

Is there a hardware problem? Check yourWindows event log. If you do not knowhow to do this, consult the Windowsdocumentation.

Are the index and page file corrupt?Check them by issuing the VALIDATEcommand in ESSCMD. If the index andpage files are corrupt:

1. Delete the temporary files. Thetemporary files include:

ARBORPATH/app/appName/databaseName/databaseName.inn

ARBORPATH/app/appName/databaseName/essxxxxx.inn

ARBORPATH/app/appName/databaseName/essxxxxx.pan

ARBORPATH/app/appName/databaseName/databaseName.otn

ARBORPATH/app/appName/databaseName/databaseName.esn

35


ARBORPATH/app/appName/databaseName/databaseName.tcu

2. Restart Essbase Server.

3. Determine whether the database iscorrupt (see Checking for DatabaseCorruption on page 150).

1006006 Failed to bring block into thememory. Data cache is toosmall. Please increase thedata cache size.

Essbase cannotstore the block in itsmemory.

Decrease the block size by changing thedense/sparse configuration.

Increase the data cache size to hold atleast 100 blocks.

Increase the memory of the servercomputer.


1006010 Invalid block header:Block's numbers do notmatch

Essbase cannotmatch the blockheader to thenumbers of theblock. The databaseis probably corrupt.The corruption maybe due to oneanomalous event,such as a powerfailure, that causedEssbase to shutdown incorrectly.

To fix the database:

1. Stop Essbase Server.

2. Delete the ARBORPATH/app/appName/databaseName/databaseName.ind file.

3. Start Essbase Server.

4. Start the application.


1006015 Not Enough Memory toAllocate the Data BufferCache. operation aborted

Essbase cannotcomplete the listedoperation becausethere was notenough memory.

Try any of these to fix the problem. Afteryou fix the problem, determine whetherthe database is corrupt (see Checkingfor Database Corruption on page 150).

Check the physical memory on theserver computer. In a Windowsenvironment, 64 MB is the suggestedminimum for one database. In a UNIXenvironment, 128 MB is thesuggested minimum for onedatabase. If the error keepsoccurring, add more memory to theserver computer.

If you are on a UNIX computer, checkthe user limit profile (see Checkingthe User Limit Profile on page151).

Check the block size of the database.If necessary, reduce the block size.

36 1006002 to 1006057: Data Cache Messages


Check the data cache setting. Ifnecessary, increase the data cachesize.

Restart Essbase Server.

Restart the server computer.

1006016 Invalid block header: Illegalblock type

Essbase cannot readthe block header.The database isprobably corrupt.The corruption maybe due to oneanomalous event,such as a powerfailure, that causedEssbase to shutdown incorrectly.







1006023 Data cache is full. Pleaseincrease the data cache sizefor databasedatabaseName.

The data cache wasfull.

Increase the data cache size to hold atleast 100 blocks.

If necessary, decrease the block size.

Ensure that memory is adequate.

Once you fix the problem, determinewhether the database is corrupt (seeChecking for Database Corruption onpage 150).

1006025 Data cache size ==>number bytes, number datapages

Size of the datacache and thenumber of datapages.

Not applicable

1006026 Data file cache size ==>number bytes, number datafile pages

Size of the data filecache and thenumber of data filepages.

Not applicable

1006027 Locking the data cachepages into physicalmemory.

Essbase is lockingthe data cachepages into physicalmemory.

Not applicable

1006028 Turning off cache memorylocking due to lack ofphysical memory. Usingvirtual memory to allocatethe remainder of the datacache.

Essbase ran out ofphysical memoryand is now usingvirtual memory.

If you wish to use physical memory, addmore physical memory to the computer.

1006029 Turning off cache memorylocking due to insufficientprivileges. Using virtualmemory to allocate the

Your privileges areinadequate to usecache memorylocking.

On UNIX, ensure that you have rootprivileges. See the operating systemdocumentation.

37


remainder of the datacache.

On Windows, ensure that you have theSE_INC_BASE_PRIORITY_NAMEprivilege. Users in the Administrators andPower Users groups generally have thisprivilege. See the operating systemdocumentation.

1006030 Failed to bring a data filepage into cache. Data filecache is too small. Pleaseincrease the data file cachesize.

Essbase cannotstore the data filepage in the data filecache.

Increase the data file cache size. Afteryou fix the problem, determine whetherthe database is corrupt (see Checkingfor Database Corruption on page 150).

1006031 Data file cache is full.Please increase the data filecache size for databasedatabaseName.

The data file cachefor the listeddatabase was full.

Increase the data file cache size.


1006032 Invalid stored logical datablock size number.

Essbase cannot readthe data block. Thedatabase is probablycorrupt. Thecorruption may bedue to oneanomalous event,such as a powerfailure, that causedEssbase to shutdown incorrectly.







1006034 Waiting to swap a data filecache page for databasedatabaseName.Performance couldpotentially be improved byincreasing the data filecache size.

Essbase is swappingpages to memory.

Not applicable

To reduce swapping and increaseperformance, increase the data filecache size.

1006035 Error errorNumberencountered while waitingfor completion of a data filecache flush for databasedatabaseName.


After you fix the problem, determinewhether the database is corrupt (seeChecking for Database Corruption onpage 150).

1006036 Data cache output transferbuffer for databasedatabaseName isunavailable.



1006037 Error encountered whilewaiting for an in-transit data


After you fix the problem, determinewhether the database is corrupt (see



page of databasedatabaseName.

Checking for Database Corruption onpage 150).

1006039 Error encountered whilewaiting for an in-transit datafile page of databasedatabaseName.



1006040 Unable to flush to disk adata block within databasedatabaseName.



1006041 A read from file fileName,messageText.

Essbaseencountered a fatalerror.

Check the previous messages in theEssbase Server log to determine whatcaused Essbase Server to crash.


1006042 Completion of a read fromfile fileName, messageText.




1006043 A write to file fileName,messageText.




1006044 Completion of a write to filefileName, messageText.




1006045 Error errorNumberencountered whileattempting to create orextend a data file fordatabase databaseName.

Essbase cannotincrease the pagefile size.

If possible, add more disk space. If youcannot add more disk space, considerspanning disk volumes.

If an operation, such as a calculation, didnot complete, perform recoveryprocedures.

39



1006046 A read from file fileName,messageText.




1006047 A write to file fileName,messageText.




1006048 An attempt to set the filepointer for file fileName,messageText.




1006049 Unable to generate the datafile name for file fileNamefor databasedatabaseName.




1006050 For transactiontransactionNumber,messageText.




1006051 For databasedatabaseName, the InputTransfer Buffer and theOutput Transfer Buffer havebeen freed.

The input and outputtransfer buffers forthe listed databaseare free.

Not applicable

1006052 Data cache input transferbuffer for databasedatabaseName isunavailable.

The operatingsystem resources areinsufficient.




1006053 Error encountered whilewaiting for initialization of adata block of databasedatabaseName.



1006054 Error encountered whilewaiting to fix a data file pageof databasedatabaseName.



1006055 Error encountered whilewaiting to access the datafile buffer pool of databasedatabaseName.



1006056 Error encountered whilewaiting for initialization of adata file page of databasedatabaseName.



1006057 Error encountered whilewaiting for a data file pageof databasedatabaseName that isinvolved in a data blocktransfer.



41

51008001 to 1008152: System

Call Messages

Table 5 lists error and informational messages about system calls.

Table 5 System Call Messages 1008001 to 1008152


1008001 Unable to Allocate Memory Essbase cannot allocateenough memory to performthe operation.

Ensure that the virtualmemory is two to three timesas large as the physicalmemory.

Ensure that the swap space istwo to three times as large asthe RAM.

Check the block size of thedatabase. If necessary,reduce the block size.

Check the data cache setting.If necessary, increase thedata cache size.

Check the index cachesetting. If necessary, increasethe index cache size.

If you are on a UNIXcomputer, check the userlimit profile (see Checkingthe User Limit Profile onpage 151).

Determine whether thesecurity file is corrupt.

If the server computer isrunning the HP-UX operatingsystem, increase MAXDSIZEto at least 2 * (data cachesize + index cache size).

Determine whether anydatabases are corrupt (seeChecking for DatabaseCorruption on page 150).


Ensure that you have enoughRAM.

43


1008006 Unable to Free Memory formemoryToBeFreed infuntionName


1008009 Pointer is NULL - Free Canceled:variableName in functionName

Essbase cannot free thelisted memory.


1008010 Read Failed Essbase cannot read acalculation script locatedon the client.

1. Run the calculation scriptagain.

2. Restart the client andrerun the calculationscript.

3. Copy the calculationscript to the server andrerun the calculationscript.

1008021 Named Pipe Create Failed Essbase cannot create thenamed pipe.

Consult the networkingdocumentation.

1008022 Pipe Create Failed Essbase cannot create thenamed pipe.


1008023 Named Pipe Connect Failed Essbase cannot disconnectfrom the named pipe.


1008024 Named Pipe Disconnect Failed Essbase cannot disconnectfrom the named pipe.


1008025 Named Pipe Peek Failed Essbase cannot peek to thenamed pipe.


1008028 Pipe Read Error Essbase cannot read fromthe named pipe.

Determine whether EssbaseServer is running.

If Essbase Server is notrunning, restart EssbaseServer.

If Essbase Servercrashed, follow theprocedures for anabnormal shutdown.

If Essbase Server hasfrozen, stop EssbaseServer and follow theprocedures for anabnormal shutdown. Ifyou cannot stop EssbaseServer using the standardmethods, end the task(see Ending the ServerTask on page 151).

1008029 Pipe Write Error Essbase cannot write to thenamed pipe.


44 1008001 to 1008152: System Call Messages


1008030 Pipe Open Failed Essbase cannot open thenamed pipe.


1008031 Pipe Close Failed Essbase cannot close thenamed pipe.


1008036 Incorrect # of Bytes Written ToPipe

Essbase cannot finishwriting to the named pipe.


1008037 Find Next Failed Essbase cannot find thenext file in the sequence.

This might occur if Essbase isprocessing multiple files,such as during a copy or aload. If you can determinewhich file is missing, restoreit from backups.

1008039 Find Close Failed Essbase cannot close thenext file in the sequence.

This might occur if Essbase isprocessing multiple files,such as during a copy or aload. If you can determinewhich file is having problems,restore it from backups.

1008089 Error receiving data from Agent Essbase cannot receivedata from the Agent.




If Essbase Server hasfrozen, stop EssbaseServer and follow theprocedures for anabnormal shutdown. Ifyou cannot stop EssbaseServer using the standardmethods, end the task(see Ending the ServerTask on page 151), andrestart Essbase Server.

1008090 Timed out receiving data fromAgent

Essbase cannot receivedata from the Agent.




45


If Essbase Server hasfrozen, stop EssbaseServer and follow theprocedures for anabnormal shutdown. Ifyou cannot stop EssbaseServer using the standardmethods, end the task(see Ending the ServerTask on page 151), andrestart Essbase Server.

1008091 Error sending data to Agent Essbase cannot send datato the Agent.


1008092 Timed out sending data to Agent Essbase cannot send datato the Agent.


1008093 Invalid data type for conversion Contact Oracle Support.

1008099 HALLOC: Possible duplicatememory allocation!variableName in functionName


1008100 HFREE: Pointer already freed!variableName in functionName


1008101 HFREE: Likely memory overwrite!variableName in functionName

The original memoryallocation was overwrittenby a newer allocation to thesame pointer.


1008106 Exception error logerrorLogName.XCP is beingcreated...

Essbase is generating anexception log just before itshuts down abnormally.

Search the exception log forinformation about whatcaused the shut down.

If the server crashes, thelog is written toHYPERION_HOME/logs/essbase; forexample,log00001.xcp.

If the application crashesand the application nameis unknown, the log iswritten toHYPERION_HOME/logs/essbase/app;for example,log00001.xcp.

If the application crashesand the application nameis known, the log is writtento HYPERION_HOME/logs/essbase/app/



appName; for example,sample/log00001.xcp.

If the database crashesand the database nameis unknown, the log iswritten toHYPERION_HOME/logs/essbase/app/appName/; for example,app/sample/log00001.xcp.

If the database crashesand the database nameis known, the log is writtento HYPERION_HOME/logs/essbase/app/appName/databasename; forexample, app/sample/basic/log00001.xcp.

Determine whether thedatabase is corrupt (seeChecking for DatabaseCorruption on page 150).


1008107 Exception error log completed --please contact technical supportand provide them with this file

Essbase finishedgenerating the error log andshuts down.

Search the exception log forinformation about whatcaused the shut down.

If the server crashes, thelog is written toHYPERION_HOME/logs/essbase; forexample,log00001.xcp.

If the application crashesand the application nameis unknown, the log iswritten toHYPERION_HOME/logs/essbase/app/;for example, app/log00001.xcp.

If the application crashesand the application nameis known, the log is writtento HYPERION_HOME/logs/essbase/app/appName/; for example,

47


app/sample/log00001.xcp.

If the database crashesand the database nameis unknown, the log iswritten toHYPERION_HOME/logs/essbase/app/appName/; for example,app/sample/log00001.xcp.

If the database crashesand the database nameis known, the log is writtento HYPERION_HOME/logs/essbase/app/appName/databasename; forexample, app/sample/basic/log00001.xcp.



1008108 Essbase Internal Logic ErrorlogicErrorNumber

Essbase encountered alogic error and shut downabnormally.

Ensure that Essbase Server isrunning.



If Essbase Server hasfrozen, stop EssbaseServer and follow theprocedures for anabnormal shutdown. Ifyou cannot stop EssbaseServer using the standardmethods, end the task(see Ending the ServerTask on page 151).




Ensure that the networkingand computer hardware arerunning correctly.

Ensure that the virtualmemory is two to three timesas large as the physicalmemory. If that is still notlarge enough, increase thememory of the servercomputer.

Check the block size.

Ensure that the data cachecan hold at least 100 blocks.

Ensure that the index cachesize is within therecommended range.

1008109 Unable to Reallocate Memory forpointerName in functionName

Essbase cannot reallocatememory to the listedfunction.

Ensure that you have enoughmemory.

1008110 Unable to Allocate Memory.Refer to the Application Log fordetails.

Essbase cannot allocatememory.

Ensure that the Essbasecomputer has enoughresources. Consult the OracleHyperion EnterprisePerformance ManagementSystem Installation StartHere for systemrequirements. If a resource-intensive application, such asa relational database, isrunning on the samecomputer, the resource-intensive application may beusing the resources thatEssbase needs.


Do not close the EssbaseServer window by clicking the"X" in the title bar.

After you restart EssbaseServer, determine whetherthe database is corrupt (seeChecking for DatabaseCorruption on page 150).

See appName.log.

1008111 Unable to Reallocate Memory forpointerName in functionName.Refer to the Application Log fordetails.

Essbase cannot reallocatememory.

Ensure that the Essbasecomputer has enoughresources. Consult the OracleHyperion Enterprise

49


Performance ManagementSystem Installation StartHere for systemrequirements. If a resource-intensive application, such asa relational database, isrunning on the samecomputer, the resource-intensive application may beusing the resources thatEssbase needs.


Do not close the EssbaseServer window by clicking the"X" in the title bar.

After you restart EssbaseServer, determine whetherthe database is corrupt (seeChecking for DatabaseCorruption on page 150).

See appName.log.

1008112 Memory Allocation error codes:O/S error = errorCode, O/Sreturn code = errorNumber

Essbase could not allocatememory.


Look up the operating systemerror code and the operatingsystem return code in theoperating systemdocumentation.

1008113 Memory Reallocation errorcodes: O/S error = errorCode,O/S return code = errorNumber

Essbase could notreallocate memory.


Look up the operating systemerror code and the operatingsystem return code in theoperating systemdocumentation.

1008114 Allocation request for numberbytes of virtual memory.Percentage of memory in use isnumber %.

Bytes of virtual memoryrequested and thepercentage of virtualmemory currently beingused by Essbase.

Not applicable

1008115 Total physical memory isnumber bytes. Availablephysical memory is numberbytes.

Total bytes of physicalmemory and bytes ofavailable physical memory.

Not applicable

1008116 Total swap space is numberbytes. Available swap space isnumber bytes.

Total bytes of swap spaceand bytes of available swapspace.

Not applicable



1008117 Total virtual memory is numberbytes. Available virtual memoryis number bytes.

Total bytes of virtualmemory and bytes ofavailable virtual memory.

Not applicable

1008118 Memory page size is numberbytes. Allocation granularity isnumber bytes.

Total bytes of memory pagesize and the size thatmemory is allocated in.

Not applicable

1008119 Memory page size is numberbytes

Total bytes of memory pagesize.

Not applicable

1008120 Unable to Allocate PhysicalMemory for pointerName infunctionName

Essbase cannot allocatephysical memory to thelisted function.

Ensure that you have enoughphysical memory.

1008121 Unable to Allocate PhysicalMemory for pointerName infunctionName for reallocation

Essbase cannot reallocatephysical memory to thelisted function.

Ensure that you have enoughphysical memory.

1008122 Unable to Lock the AllocatedMemory for pointerName infunctionName

Essbase cannot lock theneeded memory.

Ensure that the Agent isassigned the correctoperating system privileges(see Determining OperatingSystem Privileges on page152).


Ensure that the memory to belocked is valid. Consult theoperating systemdocumentation.

1008123 Unable to Lock the AllocatedMemory for pointerName infunctionName for reallocation



Ensure that the Essbasecomputer has enoughresources. Consult the OracleHyperion Enterprise

51


Performance ManagementSystem Installation StartHere for systemrequirements. If a resource-intensive application, such asa relational database, isrunning on the samecomputer, the resource-intensive application may beusing the resources thatEssbase needs.

Ensure that the memory to belocked is valid. See theoperating systemdocumentation.

1008124 Unable to Lock the AllocatedMemory pointerName infunctionName, because ofinsufficient quota

Essbase does not haveenough physical memory tolock the memory.

Check the Essbase Servermemory requirements. Ifnecessary, increase thephysical memory.

1008125 Unable to Lock the AllocatedMemory pointerName infunctionName, because ofinsufficient privilege

Essbase is not assigned thecorrect operating systemprivileges to lock thememory.


1008126 Unable to Lock the AllocatedMemory pointerName infunctionName for reallocation,because of insufficient quota



1008127 Unable to Lock the AllocatedMemory pointerName infunctionName for reallocation,because of insufficient privilege

Essbase is not assigned thecorrect operating systemprivileges to lock thememory.


1008128 Unable to Allocate PhysicalMemory for pointerName infunctionName. Refer to theApplication Log for details.


If necessary, decrease thecache sizes.

Ensure that the Essbasecomputer has enoughresources. Consult the OracleHyperion EnterprisePerformance ManagementSystem Installation StartHere for systemrequirements. If a resource-intensive application, such asa relational database, isrunning on the samecomputer, the resource-intensive application may be



using the resources thatEssbase needs.


Check the Essbase Serverphysical memoryrequirements. If necessary,increase the physicalmemory.

See appName.log.

1008129 Unable to Allocate PhysicalMemory for pointerName infunctionName for reallocation.Refer to the Application Log fordetails.






See appName.log.

1008130 Unable to Lock the AllocatedMemory for pointerName. Referto the Application Log for details.



Ensure that the Essbasecomputer has enoughresources. Consult the OracleHyperion EnterprisePerformance ManagementSystem Installation StartHere for systemrequirements. If a resource-intensive application, such asa relational database, isrunning on the samecomputer, the resource-

53


intensive application may beusing the resources thatEssbase needs.

Ensure that the memory to belocked is valid.

See appName.log.

1008131 Unable to Lock the AllocatedMemory for pointerName infunctionName for reallocation.Refer to the Application Log fordetails.




Ensure that the memory to belocked is valid.

See appName.log.

1008132 Unable to Lock the AllocatedMemory pointerName infunctionName, because ofinsufficient quota. Refer to theApplication Log for details.



See appName.log.

1008133 Unable to Lock the AllocatedMemory pointerName infunctionName, because ofinsufficient privilege. Refer to theApplication Log for details.

Essbase is not assigned thecorrect operating systemprivileges to lock theneeded memory.


Ensure that the Essbasecomputer has enoughresources. Consult the OracleHyperion EnterprisePerformance ManagementSystem Installation StartHere for systemrequirements. If a resource-intensive application, such as



a relational database, isrunning on the samecomputer, the resource-intensive application may beusing the resources thatEssbase needs.

See appName.log.

1008134 Unable to Lock the AllocatedMemory pointerName infuntionName for reallocation,because of insufficient quota.Refer to the Application Log fordetails.






See appName.log.

1008135 Unable to Lock the AllocatedMemory pointerName infunctionName for reallocation,because of insufficient privilege.Refer to the Application Log fordetails.

Essbase is not assigned thecorrect operating systemprivileges to lock theneeded memory.

Ensure that the Agent isassigned the correctoperating system priv

essbase error message reference

Documents

e e s s b

s er e

e r r o r

use anddisclosure

general use

safe use

oracle corporation

government rights