Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
This chapter lists Oracle OLAP Catalog Metadata messages. For more information about Oracle OLAP, refer to the Oracle9i OLAP User's Guide.
Cause: A metadata entity could not be found in the OLAP Catalog.
Action: Check that the metadata entity name and owner are properly specified. Refer to the OLAP Catalog union views named with the OLAP2U prefix) for existing OLAP metadata entity names.
Cause: A metadata entity could not be created, because it already exists in the OLAP Catalog.
Action: When creating a new metadata entity, specify an entity name that is unique for the entity owner. Refer to the OLAP Catalog union views (named with the OLAP2U prefix) for existing OLAP metadata entity names.
Cause: An OLAP metadata entity was found to be invalid.
Action: Check the mapping to columns in your data warehouse tables or views.
Cause: A required child entity was not found for a metadata entity.
Action: Refer to the Oracle9i OLAP User's Guide to determine which metadata entities require dependent entities.
Cause: The same level name was specified for both the parent and the child parameters of the ADD_LEVEL_TO_HIERARCHY
procedure.
Action: Determine which level should be the parent of the new level being added to the hierarchy. Specify the parent in the parent parameter and the new level in the child parameter of the ADD_LEVEL_TO_HIERARCHY
procedure. Re-run the procedure.
Cause: The level specified as the parent in the ADD_LEVEL_TO_HIERARCHY
procedure could not be used, because it was the parent of another level within the hierarchy.
Action: In the ADD_LEVEL_TO_HIERARCHY
procedure, specify a parent that is not already a parent of another level within a hierarchy.
Cause: A metadata entity could not be removed, because it was the child of another metadata entity.
Action: Remove the parent metadata entity. All the dependent entities will be removed with the parent.
Cause: A hierarchy was found to have no root level.
Action: Use the ADD_LEVEL_TO_HIERARCHY
procedure to add a level to the hierarchy. Specify the root level in the child parameter and leave the parent parameter blank.
Cause: Dimension table columns could not be accessed, because dimension hierarchies were incorrectly mapped.
Action: Add or remove dimension hierarchies or hierarchy level mappings. The number of dimension hierarchies must equal the number of hierarchy level columns.
Cause: A metadata entity was found to have too many dependent entities of another type.
Action: Add the required mapping.
Cause: A parameter was found to be invalid.
Action: Ensure that the parameter is correctly formed and valid.
Cause: Directory name provided to a procedure was found to be invalid.
Action: Ensure that the directory name represents a valid directory.
Cause: UTL_FILE.INVALID_MODE
: An error occurred when accessing a file.
Action: Check that files being accessed have correct permissions, then retry.
Cause: UTL_FILE.INVALID_OPERATION
: An error occurred when accessing a file.
Action: Check that the file being accessed is not already opened by another program, then retry.
Cause: UTL_FILE.INTERNAL_ERROR
: Possible hardware or software problem when accessing a file.
Action: Verify that hardware is functioning normally, then retry. Contact Oracle Support Services if needed.
Cause: UTL_FILE.INVALID_FILEHANDLE
: Possible software or hardware problem when accessing a file.
Action: Verify that hardware is functioning normally, then retry. Contact Oracle Support Services if needed.
Cause: UTL_FILE.READ_ERROR
: Possible software or hardware problem when accessing a file.
Action: Verify that hardware is functioning normally, then retry. Contact Oracle Support Services if needed.
Cause: The input text file was not found in the specified location.
Action: Copy the input text file to the specified location, then retry.
Cause: The output file already exists in the specified location.
Action: Delete or rename the file, then retry.
Cause: Either the input text file or the input string did not specify an analytic workspace dimension.
Action: Add one or more dimensions to the input text file or the input string. At least one dimension is required.
Cause: Dimension name was not specified in either the input text file or the input string.
Action: Modify the input text file or the input string to include the missing dimension name.
Cause: Hierarchy for this dimension was not specified in either the input text file or the input string.
Action: Modify the input text file or the input string to include the missing hierarchy.
Cause: Hierarchy dimension for this dimension was not specified in either the input text file or the input string.
Action: Modify the input text file or the input string to include the missing hierarchy dimension.
Cause: Hierarchy dimension value for this dimension was not specified in either the input text file or the input string.
Action: Modify the input text file or the input string to include the missing hierarchy dimension value.
Cause: Analytic workspace GID variable for this dimension was not specified in either the input text file or the input string.
Action: Modify the input text file or the input string to include the missing Analytic Workspace GID variable.
Cause: Analytic workspace column level dimension for this dimension was not specified in either the input text file or the input string.
Action: Modify the input text file or the input string to include the missing analytic workspace column level dimension.
Cause: Analytic workspace column level relation for this dimension was not specified in either the input text file or the input string.
Action: Modify the input text file or the input string to include the missing analytic workspace column level dimension.
Cause: RDBMS dimension column for this dimension was not specified in either the input text file or the input string.
Action: Modify the input text file or the input string to include the missing RDBMS dimension column.
Cause: RDBMS parent column for this dimension was not specified in either the input text file or the input string.
Action: Modify the input text file or the input string to include the missing RDBMS parent column.
Cause: RDBMS GID column for this dimension was not specified in either the input text file or the input string.
Action: Modify the input text file or the input string to include the missing RDBMS GID column.
Cause: RDBMS dimension column data type for this dimension was not specified in either the input text file or the input string.
Action: Modify the input text file or the input string to include the missing RDBMS dimension column data type.
Cause: RDBMS dimension column data type for this dimension was not specified in either the input text file or the input string.
Action: Modify the input text file or the input string to include the missing RDBMS dimension column data type.
Cause: RDBMS dimension column data type for this dimension was not specified in either the input text file or the input string.
Action: Modify the input text file or the input string to include the missing RDBMS dimension column data type.
Cause: Analytic workspace measure name for this measure was not specified in either the input text file or the input string.
Action: Modify the input text file or the input string to include the missing analytic workspace measure name.
Cause: RDBMS measure column name for this measure was not specified in either the input text file or the input string.
Action: Modify the input text file or the input string to include the missing RDBMS measure column name.
Cause: RDBMS measure column data type for this measure was not specified in either the input text file or the input string.
Action: Modify the input text file or the input string to include the missing RDBMS measure column data type.
Cause: There was a program error or a system resource limit was exceeded.
Action: Verify that sufficient system resources are available, then retry.
Cause: A prefix supplied to an API call was too long.
Action: Change the prefix so that it is within the permitted length, then re-issue the API call.
Cause: Level names were provided to the LEVELS_LIST
parameter, but the LEVELS
parameter did not specify the number of levels.
Action: Either set the LEVELS_LIST
parameter to null (the default) or set the LEVELS
parameter to the number of levels.
Cause: The number of names in the LEVELS_LIST
parameter did not equal the number specified by the LEVELS
parameter.
Action: Ensure that the LEVELS_LIST
parameter is correctly formed and that it holds the number of names specified by the LEVELS
parameter.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: A parameter was found to be invalid.
Action: Ensure that the parameter is correctly formed and valid.
|
Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|