Skip Headers
Oracle® Database Error Messages
11g Release 2 (11.2)

Part Number E17766-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
Mobi · ePub

54 AMD-00100 to AMD-00160

AMD-00100: not found: string "string"
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.
AMD-00101: cannot create string "string"; metadata entity already exists
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.
AMD-00102: invalid metadata entity: string "string"
Cause: An OLAP metadata entity was found to be invalid.
Action: Check the mapping to columns in your data warehouse tables or views.
AMD-00103: string "string" does not have a string
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.
AMD-00104: Level "string" cannot be added to the hierarchy; parent and child parameters represent the same level
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.
AMD-00105: Level "string" cannot be added to the hierarchy; the specified parent level "string" is already the parent of "string"
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.
AMD-00106: parent string "string" must be removed before child string "string" can be removed
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.
AMD-00107: no root level in hierarchy: "string"
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.
AMD-00108: Dimension "string" is improperly mapped; the dimension has string hierarchies mapped, but hierarchy level "string" has string columns mapped
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.
AMD-00109: Parent metadata entity has too many child entities. string "string" has more than string string
Cause: A metadata entity was found to have too many dependent entities of another type.
Action: Add the required mapping.
AMD-00110: parameter string of "string" not valid
Cause: A parameter was found to be invalid.
Action: Ensure that the parameter is correctly formed and valid.
AMD-00111: PROCEDURE string, invalid directory: "string"
Cause: Directory name provided to a procedure was found to be invalid.
Action: Ensure that the directory name represents a valid directory.
AMD-00112: PROCEDURE string, invalid mode
Cause: UTL_FILE.INVALID_MODE: An error occurred when accessing a file.
Action: Check that files being accessed have correct permissions, then retry.
AMD-00113: PROCEDURE string, invalid operation
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.
AMD-00114: PROCEDURE string, internal error
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.
AMD-00115: PROCEDURE string, invalid file handle
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.
AMD-00116: PROCEDURE string, read error
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.
AMD-00117: input file "string" not found
Cause: The input text file was not found in the specified location.
Action: Copy the input text file to the specified location, then retry.
AMD-00118: output file "string" already exists
Cause: The output file already exists in the specified location.
Action: Delete or rename the file, then retry.
AMD-00119: analytic workspace dimensions not specified in input
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.
AMD-00120: dimension #string: analytic workspace dimension name not specified
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.
AMD-00121: dimension #string: analytic workspace hierarchy not specified
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.
AMD-00122: dimension #string: analytic workspace hierarchy dimension not specified
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.
AMD-00123: dimension #string: analytic workspace hierarchy dimension value not specified
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.
AMD-00124: dimension #string: analytic workspace GID variable not specified
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.
AMD-00125: dimension #string: analytic workspace column level dimension not specified
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.
AMD-00126: dimension #string: analytic workspace column level relation not specified
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.
AMD-00127: dimension #string: RDBMS dimension column not specified
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.
AMD-00128: dimension #string: RDBMS parent column not specified
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.
AMD-00129: dimension #string: RDBMS GID column not specified
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.
AMD-00130: dimension #string: RDBMS dimension column data type not specified
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.
AMD-00131: dimension #string: RDBMS parent column data type not specified
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.
AMD-00132: dimension #string: RDBMS GID column data type not specified
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.
AMD-00133: measure #string: analytic workspace measure name not specified
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.
AMD-00134: measure #string: RDBMS measure column name not specified
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.
AMD-00135: measure #string: RDBMS measure column data type not specified
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.
AMD-00136: Generation of SQL script "string" failed
Cause: There was a program error or a system resource limit was exceeded.
Action: Verify that sufficient system resources are available, then retry.
AMD-00137: prefix "string" exceeds maximum permitted length of string characters
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.
AMD-00138: level names parameter not null or defaulted
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.
AMD-00139: level names parameter not valid
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.
AMD-00140: internal error: [string] [string] [string] [string] [string]
Cause: This is an internal error.
Action: Contact Oracle Support Services.
AMD-00141: parameter string of "string" not valid starting around "string"
Cause: A parameter was found to be invalid.
Action: Ensure that the parameter is correctly formed and valid.
AMD-00142: Analytic Workspace name "string" must be fully qualified with the Owner.
Cause: A parameter was found to be invalid.
Action: Ensure that the parameter is correctly formed and valid. For example, SCOTT.EMP is a fully qualified name.
AMD-00143: View name "string" must be fully qualified with the Owner.
Cause: A parameter was found to be invalid.
Action: Ensure that the parameter is correctly formed and valid. For example, SCOTT.EMP is a fully qualified name.
AMD-00144: Custom Measure "string" does not exist in Workspace "string"
Cause: A required object does not exist in specified Workspace.
Action: Ensure that the parameter is correctly formed and valid.
AMD-00145: error attaching Workspace "string" in mode "string"
Cause: Either the Workspace does not exist, is already attached in a different mode, or there are insufficient system resources to attach Workspace.
Action: Ensure that workspace name is correct and can be currently attached in the specified mode.
AMD-00146: Custom Measure "string" already exists in Workspace "string"
Cause: You have attempted to create a Custom Measure when it already exists.
Action: Ensure that the Custom Measure name is correct and does not already exist in the specified Workspace.
AMD-00147: invalid Custom Measure creation mode "string" specified
Cause: Custom Measure creation mode must be "PERMANENT" or "TEMPORARY."
Action: Ensure that the Custom Measure creation mode is correct.
AMD-00148: Workspace "string" is not currently open. No update done.
Cause: The Workspace must be attached before a Custom Measure can be updated.
Action: Attach Workspace first before attempting to modify Custom Measure.
AMD-00149: Custom Measure to delete "string" does not exist in Workspace "string"
Cause: The Custom Measure does not exist in specified Workspace.
Action: Ensure that the Custom Measure name is correct and exists in specified Workspace.
AMD-00150: Custom Measure to delete "string" not mapped to View "string"
Cause: The Custom Measure to delete is not mapped to the View specified.
Action: Ensure that the Custom Measure and View Name name are correct, and mapped to each other.
AMD-00151: Creation of Custom Measure "string" in Workspace "string" failed
Cause: Invalid parameters were supplied, or a program error occured.
Action: Ensure that API parameters are correct and sufficient system resources are available.
AMD-00152: Workspace "string" is not currently open.
Cause: The Workspace must be attached before an operation can be performed on it.
Action: Attach the Workspace first before attempting operation.
AMD-00153: error detaching workspace "string"
Cause: The Workspace was not attached or a program error occured.
Action: Ensure the Workspace name is correct and it is attached in the current session.
AMD-00154: Cannot delete session object "string" in Workspace "string"
Cause: You cannot delete a session object. These are deleted automatically when the session is ended.
Action: Ensure that API parameters are correct.
AMD-00155: Object to delete "string" does not exist in Workspace "string"
Cause: The Object slated for deletion does not exist in the Workspace specified.
Action: Ensure that API parameters are correct.
AMD-00156: formula "string" to modify does not exist in Workspace "string"
Cause: Formula does not exist in Workspace specified.
Action: Ensure that API parameters are correct.
AMD-00157: invalid attach mode "string" specified when attempting to attach Workspace "string"
Cause: An invalid parameter supplied.
Action: Attach mode must be "RO" (read only) or "RW" (read/write).
AMD-00158: The Workspace "string" is currently open in read-only mode.
Cause: An invalid parameter was supplied. You may not specify an operation which requires an update when the Workspace is open in read-only mode.
Action: The Creation Mode parameter must be "TEMPORARY" for a Workspace open in read-only mode.
AMD-00159: The Workspace "string" is currently attached in read/write mode.
Cause: An invalid parameter was supplied.
Action: The Creation Mode parameter must be "PERMANENT" for a Workspace open in read/write mode.
AMD-00160: Warning! Exceeded maximum Custom Measure number of "string"
Cause: The system limit has been reached.
Action: Old Custom Measures created against the specified View have to be deleted before new Custom Measures can be created.