1002112

1002122

Aggregate storage applications ignore disk volume settings in essbase.cfg

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

Essbase 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.

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

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.

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

1013101

Cannot restructure. There are other active users on database [%s]

You cannot restructure a database if there are other users active on the database.

Log off other users.

1013294, 1241164

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

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

Specify a storage stopping value that is 1.0 or greater.

The stopping value is the database size, 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 database size by no more than 50%. It does not make sense to specify a value lower than 1.0, because that would mean the aggregated database size is smaller than the size of the original unaggregated level 0 data.

1060145, 1150091

It is not possible to have a formula on a label member

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

Remove the formula.

Convert the label only member to a non-label only member of a dynamic hierarchy (stored hierarchies cannot have formulas).

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

A non level 0 member in the accounts dimension or in a dynamic hierarchy has these traits:

Ensure 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.

In a stored hierarchy, either:

Ensure that the parents of label only members are also label only.

Ensure that members at the same level as label only members are also label only.

1060172

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

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

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

1060175

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

The label only tag was 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.

Tag the top level member as label only.

1060180

The primary hierarchy must be tagged as Stored.

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. Essbase requires such a hierarchy to be a stored hierarchy.

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.

In a stored hierarchy, either:

Ensure that the parents of label only members are also label only.

Ensure that members at the same level as label only members are also label only.

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

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

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

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

Ensure 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.

1150091

See 1060145, 1150091

1241164

See 1013294, 1241164

1270001

Memory allocation failed

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

Check the Essbase Server memory requirements.

Configure the operating system to handle more memory.

If necessary, increase the physical memory.

1270004

Cannot complete operation: insufficient aggregate storage cache size

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

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

1270005

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

The database is corrupt.

Delete the application using Oracle Essbase Administration Services or MaxL and rebuild it from backup files. Do not delete the application from the file system.

If you cannot delete the application, delete all tablespace directories and file locations, and reload data.

Tablespace directories:

ARBORPATH/app/default
ARBORPATH/app/log
ARBORPATH/app/metadata
ARBORPATH/app/temp

Call Oracle Support.

1270006

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

Essbase cannot extend files, nor can it create files in the tablespace file locations. Possible causes of this problem include:

Essbase 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, Essbase allocates disk space in fixed size increments. When Essbase 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, Essbase makes another attempt to extend the tablespace. After repeated failures, this error message is displayed.

Look in the application log for warning messages that led up to this error.

Specify additional file locations to accommodate the application.

Call Oracle Support.

1270009

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

You specified for removal a tablespace that cannot be removed.

Essbase 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.

Check whether this is the metadata or log tablespace. Essbase cannot remove metadata and log tablespaces.

Check whether the tablespace contains data. Essbase cannot remove tablespaces that contain data.

1270011

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

Essbase cannot create the listed file location because the file location is used.

Specify another file location.

1270018

Failed to create file location: path too long

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

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

1270022

Failed to extend file: user limit reached

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

Essbase 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.

Increase the maximum file size setting for that tablespace location.

1270024

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

The aggregate storage application is about to shut down abnormally.

Messages before this one in the application log may indicate the cause of the abnormal shutdown.

Call Oracle Support.

1270030

Cannot proceed: the cube has no aggregations

Essbase cannot clear aggregate views because no aggregate views exist in the database.

Proceed with your next task. You do not 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

Essbase cannot use the view list. Significant changes may were 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.

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

Repeat aggregate view selection after making major changes to the outline.

1270035

Cannot alter tablespace: this tablespace is special

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.

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.

A directory exists at the file location specified.

Choose another file location.

If you are sure that the directory is not used by another application, remove it and try to create the file location again.

1270039

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

Essbase cannot remove a file location in a tablespace if the database contains data.

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

1270040

Data load buffer [%s] does not exist

A data load buffer has not been created. When using MaxL to load data to an aggregate storage database, you must specify a buffer ID.

The data load buffer was destroyed. The data load buffer is automatically destroyed in some cases, such as running out of disk space during a data load. It can also be destroyed using MaxL, alter database.

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

If you encountered a problem that caused the data load buffer to be destroyed, resolve that problem, and retry the data load.

1270041

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

The aggregate storage cache size is too small.

Increase the aggregate storage cache size.

1270044

Cube cannot have more than [%s] aggregates

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

Select fewer aggregate views.

1270047

Data load buffer [%s] is currently in use

Essbase 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.

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

1270052

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

Essbase could not aggregate the aggregate views.

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

The database is corrupt.

Delete the application using Administration Services or MaxL and rebuild it from backup files. Do not delete the application from the file system.

If you cannot delete the application, delete all tablespace directories and file locations, and reload data.

Tablespace directories:

ARBORPATH/app/default
ARBORPATH/app/log
ARBORPATH/app/metadata
ARBORPATH/app/temp

Call Oracle Support.

1270057

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

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

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

1270058

No file locations exist in tablespace

Essbase cannot write to a tablespace because all tablespace file locations are removed.

Add a file location to the tablespace. It is possible to remove all 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

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

Do nothing. Essbase 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

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

Do nothing. Essbase automatically rounds up to the nearest 8 MB.

1270063

Attempting to re-create all aggregate storage files

Essbase 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 are corrupt or were accidentally deleted.

Restore the original data files from a backup copy.

Contact Oracle Support.

1270069

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

Essbase cannot execute the execute aggregate selection MaxL command because the view list provided does not meet one of these requirements:

Replace the aggregation.

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

1270070

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

The database is corrupt.

Delete the application using Administration Services or MaxL and rebuild it from backup files. Do not delete the application from the file system.

If you cannot delete the application, delete all tablespace directories and file locations, and reload data.

Tablespace directories:

ARBORPATH/app/default
ARBORPATH/app/log
ARBORPATH/app/metadata
ARBORPATH/app/temp

Call Oracle Support.

1270071

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

The database is corrupt.

Delete the application using Administration Services or MaxL and rebuild it from backup files. Do not delete the application from the file system.

If you cannot delete the application, delete all tablespace directories and file locations, and reload data.

Tablespace directories:

ARBORPATH/app/default
ARBORPATH/app/log
ARBORPATH/app/metadata
ARBORPATH/app/temp

Call Oracle Support.

1270082

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

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

Check the operating system documentation.

1270506

Outline generated too many warnings. Further warnings ignored

The outline generated more warnings than Essbase can display. Essbase does not display further warnings.

Ignore this message and continue to use the outline. Essbase does not prevent you from using an outline that generates warnings.

Edit the outline to remove conditions that generate warnings.

1270517

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

The specified hierarchy contains too many levels.

Reduce the number of levels in the hierarchy.

1270526

Alternate hierarchy [shared] is attached to the primary hierarchy at an unstored level

A shared member's prototype can not be a label only member.

1270527

Attribute dimension [%s] has an invalid association with an alternate hierarchy. For alternate hierarchies, attributes may only be associated with members at level zero.

An attribute dimension can not be tagged to an upper level stored hierarchy unless it is primary.