OracleFree referencePDF, Excel, Word exportOracle Hyperion / EssbaseAll Oracle Hyperion and Essbase tools

Essbase Error Codes Reference: Data Load, Outline and Calc Messages

This is a searchable list of Essbase message numbers that admins hit during data loads, outline builds, calculations and logins, each with a short message, the likely cause and a fix. It covers Essbase 11.1.2.x and the same message numbers carried into 21c.

Download:

Error number	Message (short)	Category	Likely cause	Fix
1003000	Unknown item in data load	Data load (1003xxx)	A field in the record is not a member, alias or recognised token	Add the member, map it in the rules file, or ignore the field
1003001	Duplicate members from same dimension on data record	Data load (1003xxx)	Two fields on one record resolve to members of the same dimension	Fix the field mapping or drop one field in the rules file
1003003	Unable to continue data load after item	Data load (1003xxx)	Load stopped on a fatal record problem	Read the preceding message and the error file, fix the record, reload
1003004	Incorrect number of column members in symmetric file	Data load (1003xxx)	Header defines more or fewer data columns than the rows carry	Check delimiters, quotes and blank trailing columns
1003007	Data value encountered before all dimensions selected	Data load (1003xxx)	A number appears before every dimension has a member (missing field, header or mapping)	Make sure each dimension is in the record, header or rules file; check numbers in member columns
1003008	Too many values in row	Data load (1003xxx)	More data values than data columns defined	Fix the delimiter or the column header in the rules file
1003014	Unknown member in data load	Data load (1003xxx)	Member name or alias not in the outline (new account, entity, typo, trailing space)	Build the member first or correct the source value; reload rejected records
1003015	Member is from the same dimension as members defined in header	Data load (1003xxx)	Record field and header both supply the same dimension	Remove the dimension from the header or the record
1003025	DATAERRORLIMIT reached; rejected records no longer logged	Data load (1003xxx)	More rejects than the DATAERRORLIMIT setting	Fix the root cause of the first rejects; raise DATAERRORLIMIT in essbase.cfg only if needed
1003032	Input line too long near record	Data load (1003xxx)	Line exceeds the maximum length, often a missing line break	Check line endings and file encoding
1003034	Invalid member in data column	Data load (1003xxx)	A non-numeric value sits in a field Essbase treats as a data column	Check delimiters, quotes and the rules file field types so text does not land in data columns
1003035	No data values modified by load of this data file	Data load (1003xxx)	All records rejected, filtered by select/reject rules, or values unchanged	Review the error file and rules file select criteria
1003036	Member name too long	Data load (1003xxx)	Field exceeds the member name length limit	Trim or map the source value
1003039	Implied shared member does not have a real child	Data load (1003xxx)	Loading to a parent with a single child that Essbase treats as implied share	Load to the child, or set the parent to Never Share
1003048	Unicode-encoded data to non-Unicode application not supported	Data load (1003xxx)	UTF-8 file loaded into a non-Unicode application	Convert the file encoding or migrate the application to Unicode mode
1003055	Aggregate storage applications ignore update to derived cells	Data load, ASO	Data file contains upper-level values for an ASO cube	Load level-0 only; ASO calculates upper levels
1019026	Unknown member found while processing string	Outline / database object	Formula, filter or string references a member not in the outline	Correct the member reference or restore the member
1013101	Cannot restructure; other active users on database	Outline / dimension build	Restructure after a dimension build blocked by sessions	Disable connects, log users off, rerun the build or restructure
1060147	ASO outlines require non level-0 accounts and dynamic hierarchy members to be non-stored or have formulas	Outline verification, ASO	Upper-level member in Accounts or a dynamic hierarchy is stored without a formula	Tag it label only or add a formula
1060149	Label-only members must span all of the uppermost levels	Outline verification, ASO	Label-only member below a non-label parent in a stored hierarchy	Tag the parents label only or remove the tag
1060172	Shared member allowed once in a stored hierarchy	Outline verification, ASO	Same member shared twice in one stored hierarchy	Move the extra share to a dynamic or alternate hierarchy
1060180	The primary hierarchy must be tagged as Stored	Outline verification, ASO	First hierarchy of a multiple-hierarchy dimension set to dynamic	Tag the first hierarchy Stored
1012000	Invalid syntax: not a CALC command	Calculation (1012xxx)	Unknown command or missing semicolon in calc script	Check spelling and semicolons near the reported command
1012001	Invalid calc script syntax	Calculation (1012xxx)	Syntax error in the script	Validate the script in EAS or the 21c editor and fix the reported line
1012015	CALC ALL cannot be used in restricted calculation	Calculation (1012xxx)	CALC ALL inside FIX/ENDFIX	Use CALC DIM or AGG inside the FIX
1012023	Aggregating on dense dimension not supported	Calculation (1012xxx)	AGG used on a dense dimension	Use CALC DIM for dense dimensions
1012042	Substitution variable does not exist	Calculation (1012xxx)	&Variable not defined at server, app or database level	Create the substitution variable or fix its name
1012051	FIX statement cannot contain Dynamic Calc member	Calculation (1012xxx)	FIX on a Dynamic Calc member	FIX on stored members only
1012055	Expression inside FIX evaluates to an empty set	Calculation (1012xxx)	FIX members or functions return nothing (wrong UDA, deleted member, empty variable)	Check members, UDAs and substitution variable values
1012500	Requested calc script not found	Calculation (1012xxx)	Script not in the database directory or wrong name	Check the .csc file location and name
1012704	Dynamic Calc processor cannot lock more than n ESM blocks	Calculation (1012xxx)	Dynamic calcs need more blocks than CALCLOCKBLOCK or the data cache allows	Raise the CALCLOCKBLOCK setting and the data cache, or reduce dynamic members in the query
1006023	Data cache is full	Cache	Data cache too small for the operation	Increase the data cache size for the database
1053010	Object is already locked by user	Agent / objects	Another user or a crashed session holds the outline or script lock	Wait, or unlock the object in EAS or MaxL
1051004	Logins are currently not permitted	Agent / session	Connects disabled for maintenance	Enable connects after the maintenance window

Message text is paraphrased from the Oracle Essbase Error Message Reference (11.1.2): data load 1003000 to 1003048, calculation 1012000 to 1012750, data cache, database object, agent and aggregate storage messages. Codes in the 1020xxx, 1200xxx and 1260xxx ranges (for example 1020098 or 1260046, often seen in Smart View or Fusion GL reports) are not listed in that reference, so they are left out here rather than guessed; read the full text Essbase prints with them.

Send us a failing load

Share the error file and rules file field list; we will tell you which mapping or member is causing the rejects.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How to use it

Type the seven-digit number from the log or the Smart View pop-up into the search box. The message column is a short paraphrase; the real message includes the member, file or record number, which usually tells you exactly where to look. Export the table to Excel if you want to add your own codes and fixes for your applications, such as the rejected records your nightly load produces most often.

1003xxx: data load messages, mostly about the record or the rules file.
1012xxx: calculation script and formula messages.
1060xxx: aggregate storage outline verification.
1051xxx to 1053xxx: agent, session and object locks.

Where to read the full message

On 11.1.2.x the application log is appname.log under EPM_ORACLE_INSTANCE/diagnostics/logs/essbase/essbase_0/app/appname (with an ODL-format log alongside it, depending on configuration). Rejected data load records go to the error file you name in EAS or MaxL, often dataload.err; each rejected line is written with the message in front of it, so you can fix and reload just that file. In 21c the job details in the web interface show the error file and the job output, and the REST GET /jobs/{id} response includes jobOutputInfo. Smart View shows only the first message, so always cross-check the server log.

Worked example: error 1003007

A load fails with Data value 1.03134e+007 encountered before all dimensions selected. Essbase read a number while at least one dimension still had no member. Typical causes are a missing column in the source extract, a header definition that lost a dimension after a rules file change, a new member (for example a new year) not mapped in the rules file, or a number sitting in a member column because a delimiter is wrong. Open the error file, take the first rejected record and count fields against the rules file field list. Fixing the mapping and reloading the error file usually clears the rest.

Common mistakes

Raising DATAERRORLIMIT hides the problem instead of fixing it. Loading upper-level values into an ASO cube produces 1003055 and the values are skipped. Duplicate member name outlines need qualified names in the source, otherwise members can resolve wrongly or be rejected. After an outline restructure, check the application log for 1013101 before assuming the build succeeded. For calc errors, the line reported is where the parser gave up, so look one or two lines earlier for a missing semicolon or unbalanced parenthesis (1012019).

Frequently Asked Questions

What does Essbase error 1003007 mean?

Data value encountered before all dimensions selected. Essbase found a number on a record before it had a member for every dimension. Check that each dimension is supplied by the record, the header or the rules file, that new members are mapped, and that delimiters are correct so numbers do not slide into member columns.

Where is the Essbase data load error file?

You choose it when you run the load: in EAS it is the error file field on the data load dialog, and in MaxL it is the on error write to clause of import database. In 21c jobs the error file is listed in the job details. Each rejected record is written with its message so you can fix and reload it.

Why is error 1020098 or 1260046 not in this list?

These numbers are not in the 11.1.2 Essbase Error Message Reference ranges this list is built from, and we only list codes we could confirm. When you see them, read the full text Essbase or Smart View prints with the code, which names the member or problem, and check the server application log for the matching entry.

How do I fix unknown member errors during an Essbase load?

Error 1003014 means the member or alias in the record is not in the outline. Run the dimension build before the data load, check for trailing spaces and case differences, confirm the right alias table is active, and reload only the rejected records from the error file once the outline is fixed.

If you want a private assistant that reads your Essbase logs and error files and explains each reject in plain English, we can run it on your own servers.

Talk to an Expert Explore More Free Tools