Aggregate Storage Errors

This document describes aggregate storage error, information, and warning messages. The discussions of error messages include possible causes and possible solutions for each problem, with links to the Analytic Services Database Administrator's Guide and the Analytic Services Technical Reference for more information on how to fix errors.  In Analytic Services documentation, "Enterprise Analytics" refers to aggregate storage databases.

Click an error message number to view information about that error message.

1002122 1003055 1013294, 1241164
1060145, 1150091 1060147 1060149
1060172 1060175 1060180
1150085 1150086 1150090
1270001 1270004 1270005
1270006 1270009 1270011
1270018 1270022 1270024
1270030 1270032 1270035
1270036 1270039 1270040
1270041 1270052 1270054
1270057 1270058 1270059
1270060 1270063 1270069
1270070 1270071 1270082
1270506 1270517
 

1002122 Aggregate storage applications ignore disk volume settings in essbase.cfg

Analytic Services uses tablespaces to optimize data storage and retrieval for aggregate storage data files and work files. Tablespaces are location definitions that map data objects, such as aggregate views and aggregations to files.

Possible Problems

A DISKVOLUMES setting that applies to this database is specified in the essbase.cfg file. Analytic Services ignores this setting as it  does not use disk volume settings to allocate storage for aggregate storage databases.

Possible Solutions

Allocate storage by defining tablespace properties in the Administration Services Console or by using MaxL.


1003055 Aggregate storage applications ignore update to derived cells. [%s] cells skipped

Possible Problems

The data source contains data values for upper level aggregate cells or for members with formulas. For aggregate storage databases, you cannot load data to upper level cells or cells whose values depend on formulas in the outline.

Possible Solutions

Load data only to level zero cells whose values do not depend on formulas in the outline.


1013294, 1241164 A stopping size strictly greater than 1.0 is required for aggregate selection

Possible Problems

Analytic Services cannot select aggregate views because the storage stopping value, specified using MaxL, is smaller than 1.0.

The stopping value is the size of the database, expressed as a multiple of the size of the unaggregated level-0 data. For example, a stopping value of 1.5 means that the aggregation should increase the size of the database by no more than 50%. It does not make sense to specify a value lower than 1.0, because that would mean the size of the aggregated database is smaller than the size of the original unaggregated level-0 data.

Possible Solutions

Specify a storage stopping value that is 1.0 or greater.


1060145, 1150091 It is not possible to have a formula on a label member

Possible Problems

A label only member has a formula associated with it. Label only members do not have data associated with them, so it does not make sense for them to have formulas.

Possible Solutions


1060147 Aggregate storage outlines require non level-0 members in accounts dimension and dynamic hierarchies to be either non-stored members or have internal/external formula

Possible Problems

A non level-0 member in the accounts dimension or in a dynamic hierarchy has all of following traits:

Possible Solutions

Make sure that all non level-0 members in the accounts dimension and in dynamic hierarchies are tagged as label only, have a child that rolls up, or have a member formula.


1060149 Label-only members must span all of the uppermost levels.

Possible Problems

In a stored hierarchy, either:

Possible Solutions


1060172 Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.

Possible Problems

A stored hierarchy in a dimension where multiple hierarchies are enabled contains either:

Possible Solutions

Be sure that stored hierarchies in dimensions with multiple hierarchies enabled do not contain two shared instances of the same member or one non-shared and one shared instance of the same member.


1060175 Top member in dimensions with multiple hierarchies must be tagged as Label.

Possible Problems

The label only tag has been removed from the top member in a dimension with multiple hierarchies enabled. When you tag the top level member as multiple hierarchies enabled, it is automatically tagged as label only, but it is possible to remove the tag. If the label only tag is removed, the outline fails verification.

Possible Solutions

Tag the top level member as label only.


1060180 The primary hierarchy must be tagged as Stored.

Possible Problems

The member representing the first hierarchy (top level member of the hierarchy) in a dimension that has multiple hierarchies enabled is not tagged as a stored hierarchy. Analytic Services requires such a hierarchy to be a stored hierarchy.

Possible Solutions

Tag as a stored hierarchy, the top-level member of the first hierarchy in the dimension.


1150085 OUTLINE SYNC VERIFY: Member %s has an incorrect label tag.  Label only members must span all of the uppermost levels.

Possible Problems

In a stored hierarchy, either:

Possible Solutions


1150086 OUTLINE SYNC VERIFY: Member %s has an incorrect aggregation operator.  Aggregate storage outlines require all members of non-accounts dimensions to have ADD (+) aggregation, except for label-only members and their children

When editing aggregate storage outlines that were created in release 7.1, the restrictions on release 7.1 aggregate storage outlines apply, even if you are using a later release of Analytic Services.

Possible Problems

A member of a dimension that is not the accounts dimension in a release 7.1 outline does not have an addition (+) consolidation operator and it is not tagged as:

Possible Solutions

Apply the addition (+) consolidation operator to the member.


1150090 OUTLINE SYNC VERIFY: Aggregate storage outlines require non level-0 member %s in accounts dimension to be either non-stored members or have internal/external formula

Possible Problems

A non-level 0 member in the accounts dimension or in a dynamic hierarchy is not tagged as label only, does not have a member formula, and is not an aggregated value.

Possible Solutions

Make sure that all non-level 0 members in the accounts dimension and in dynamic hierarchies are tagged as label only, have at least one child that rolls up, or have a member formula.


1270001 Memory allocation failed

Possible Problems

Analytic Services cannot complete the requested operation because it ran out of memory.

Possible Solutions


1270004 Cannot complete operation: insufficient aggregate storage cache size

Possible Problems

Analytic Services cannot perform the requested operation because the aggregate storage cache size is insufficient.

Possible Solutions

Use these guidelines to estimate the correct aggregate storage cache size.


1270005 Fatal error: invalid page encountered in aggregate storage file at location [%s]

Possible Problems

The database is corrupt.

Possible Solutions


1270006 Failed to extend tablespace [%s].  Please see application log for details

Analytic Services uses tablespaces to optimize data storage and to optimize retrieval for data files and work files. Tablespaces define one or more location definitions that map data objects, such as aggregate views and aggregations, to files. You can specify the maximum file size allowed within each location in a tablespace.

As needed, Analytic Services allocates disk space in fixed size increments. When Analytic Services fails to extend a tablespace, it prints a warning message to the application log, indicating why it could not extend the tablespace. After each failure, Analytic Services makes another attempt to extend the tablespace. After repeated failures, this error message is displayed.

Possible Problems

Analytic Services cannot extend any existing files, and it cannot create any new files in any of the file locations in the tablespace. Possible causes of this problem include:

Possible Solutions


1270009 Failed to remove tablespace: operation not allowed on this special tablespace

Analytic Services sets up two tablespaces that cannot be altered (log and metadata). You cannot remove the system defined tablespaces. In addition, you cannot delete a file location within a default or temp tablespace if it contains data.

Possible Problems

You specified for removal a tablespace that cannot be removed.

Possible Solutions


1270011 Failed to create file location [%s]: that file location is already used by this tablespace

Possible Problems

Analytic Services cannot create the listed file location because the file location is already specified.

Possible Solutions

Specify a different file location.


1270018 Failed to create file location: path too long

Possible Problems

The path that you specified for the tablespace file location is too long.

Possible Solutions

Specify a file location path that is 460 bytes or less.


1270022 Failed to extend file: user limit reached

Analytic Services uses tablespaces to optimize data storage and to optimize retrieval for data files and work files. Tablespaces define one or more location definitions that map data objects, such as aggregate views and aggregations, to files. You can specify the maximum file size allowed within each location in a tablespace.

Possible Problems

Analytic Services cannot further increase the size of the listed file because it has reached the specified maximum file size for that location in the tablespace.

Possible Solutions

Increase the maximum file size setting for that tablespace location.


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

Possible Problems

The aggregate storage application is about to shut down abnormally.

Possible Solutions


1270030 Cannot proceed: the cube has no aggregations

Possible Problems

Analytic Services cannot clear aggregate views because no aggregate views exist in the database.

Possible Solutions

Proceed with your next task. There is no need to clear aggregate views because none exist in the database.


1270032 The specified view list is invalid or the views were selected using a different outline

Possible Problems

Analytic Services cannot use the existing view list. Significant changes may have been made to the outline after the views were last selected. Examples of outline changes that may make a view list invalid are changes to the number of dimensions or to the number of levels in a dimension.

Possible Solutions


1270035 Cannot alter tablespace: this tablespace is special

Possible Problems

You tried to add, remove, change the location of, or change the size of the listed log or metadata tablespace. Altering log or metadata tablespaces is not permitted.

Possible Solutions

Check the rules for working with tablespaces.


1270036 Cannot add file location: file location directory [%s] already exists. If this directory is not in use by another application, please remove it and try again.

Possible Problems

A directory already exists at the file location specified.

Possible Solutions


1270039 Failed to remove file location: file location already has blocks allocated

Possible Problems

Analytic Services cannot remove a file location in a tablespace if the database already contains data.

Possible Solutions

Clear data from the database and then remove the file location.


1270040 Data load buffer [%s] does not exist

Possible Problems

Possible Solutions


1270041 Sort operation ran out of memory. Please increase the size of the aggregate storage cache

Possible Problems

The aggregate storage cache size is too small.

Possible Solutions

Increase the size of the aggregate storage cache. Use these guidelines to estimate the appropriate aggregate storage cache size.


1270044 Cube cannot have more than [%s] aggregates

Possible Problems

Analytic Services cannot create additional aggregate views because it has reached the upper limit.

Possible Solutions

Select fewer aggregate views.


1270047 Data load buffer [%s] is currently in use

Possible Problems

Analytic Services cannot execute the MaxL command, alter database destroy load_buffer, because the data load buffer is active. The data load buffer is active when data is being loaded to it or from it.

Possible Solutions

Wait until the data load is finished and then issue the command again.


1270052 Failed to aggregate views. Please see application log for more information

Possible Problems

Analytic Services could not aggregate the aggregate views.

Possible Solutions

Additional error or warning messages in the application log should indicate the cause of the problem.


1270054 Failed to read bytes from file: end of file

Possible Problems

The database is corrupt.

Possible Solutions


1270057 Requested file size limit is greater than maximum. Setting file size limit to maximum

Possible Problems

Analytic Services cannot accept the specified file size for the tablespace because it is greater than the maximum. Instead, Analytic Services sets the file size limit to the maximum.

Possible Solutions

Specify a file size limit that is equal to or smaller than the maximum.


1270058 No file locations exist in tablespace

Possible Problems

Analytic Services cannot write to a tablespace because all of the tablespace file locations have been removed.

Possible Solutions

Add a file location to the tablespace. It is possible to remove all of the file locations from a tablespace, but one or more file locations must exist before data can be written to it.


1270059 Specified maximum disk size is not on 8 MB boundary.  Rounding up to nearest 8 MB

Possible Problems

The maximum disk size for the tablespace file location is set to a number that is not a multiple of 8. Analytic Services allocates disk space in 8MB segments, so it understands settings that are multiples of 8, for example 8, 16, 24, 32.

Possible Solutions

You do not need to do anything. Analytic Services automatically rounds up to the nearest 8 MB.


1270060 Specified maximum file size is not on 8 MB boundary.  Rounding up to nearest 8 MB

Possible Problems

The maximum file size for the tablespace file location is set to a number that is not a multiple of 8. Analytic Services increments files in 8MB segments, so it recognizes settings that are multiples of 8, for example 8, 16, 24, 32.

Possible Solutions

You do not need to do anything. Analytic Services automatically rounds up to the nearest 8 MB.


1270063 Attempting to re-create all aggregate storage files

Possible Problems

Analytic Services is unable to find data files (.dat files) while attempting to start an aggregate storage application. It is attempting to create dummy data files, containing no data, to enable the application to start. This is because the data files have become corrupted or accidentally deleted.

Possible Solutions


1270069 Pre-selected view list must begin with input view; it must be followed by all existing aggregate views for query-based view selection

Possible Problems

Analytic Services cannot execute the execute aggregate selection MaxL command because the view list provided does not meet one of the following  requirements:

Possible Solutions


1270070 Serial number [%s] in the page header doesn't match [%s] in the footer

Possible Problems

The database is corrupt.

Possible Solutions


1270071 Page ID [%s] in the page header doesn't match page location

Possible Problems

The database is corrupt.

Possible Solutions


1270082 A system error occurred with error number [%s]: [%s].

The second [%s] is replaced by a description of the error as reported by the operating system.

Possible Problems

The operating system encountered a problem. This is an operating system error.

Possible Solutions

Check the operating system documentation.


 

1270506 Outline generated too many warnings. Further warnings ignored

Possible Problems

The outline generated more warnings than Analytic Services can display. Analytic Services will not display any further warnings.

Possible Solutions


1270517 Hierarchy [%s] is too complex: maximal width member number exceeds 64 bits.  See application log for details

Possible Problems

The total number of levels in the specified hierarchy is too large.

Possible Solutions

Reduce the number of levels in the hierarchy.