Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
15
ORA-32800 to ORA-32999
-
Cause: An unexpected error condition occurred.
-
Action: Contact Oracle Support Services.
-
Cause: An invalid value was given for a parameter.
-
Action: Specify a valid value for the parameter.
-
Cause: An invalid value was given for a parameter.
-
Action: Specify the value as indicated by the message.
-
Cause: An attempt was made to alter a value that cannot be altered.
-
Action: Retry the operation without altering the indicated value.
-
Cause: A value specified for a parameter has the incorrect form.
-
Action: Specify a string of the correct form.
-
Cause: An identifier string exceeded the maximum allowed length.
-
Action: Specify a string whose length is less than the maximum.
-
Cause: A value exceeded it's maximum allowed length.
-
Action: Specify a value whose length is less than the maximum.
-
Cause: A message system link of the specified name already exists.
-
Action: Specify a different name.
-
Cause: A message system link of the specified name does not exist.
-
Action: Specify a message system link name that already exists.
-
Cause: The foreign queue has already been registered for this message system link (NAME@MSGLINK).
-
Action: Specify a different name that is not being used for this message system link.
-
Cause: The foreign queue (NAME@MSGLINK) has not been registered for this message system link.
-
Action: Specify the name of a registered foreign queue.
-
Cause: The specified subscriber identifier already exists.
-
Action: Specify a different identifier.
-
Cause: The specified subscriber identifier does not exist.
-
Action: Specify a subscriber identifier that already exists.
-
Cause: The specified propagation schedule identifier already exists.
-
Action: Specify a different identifier.
-
Cause: The specified propagation schedule identifier does not exist.
-
Action: Specify a schedule identifier that already exists.
-
Cause: An attempt was made to remove a message system link currently referenced by one or more registered foreign queues.
-
Action: Unregister all foreign queues using this message system link and retry the operation.
-
Cause: An attempt was made to unregister a foreign queue currently referenced by one or more subscribers or propagation schedules.
-
Action: Remove all subscribers and propagation schedules using this foreign queue and retry the operation.
-
Cause: An attempt was made to add a propagation subscriber but the message system link was not configured with a log queue for the indicated propagation type.
-
Action: Alter the message system link to configure the link with a log queue for this propagation type.
-
Cause: An operation was attempted where the specified AQ queue does not exist.
-
Action: Specify the name of an AQ queue that already exists.
-
Cause: An operation was attempted where the specified AQ queue exists but is not a normal queue.
-
Action: Specify the name of an AQ queue which was created as a normal queue (NORMAL_QUEUE).
-
Cause: An operation for INBOUND propagation was attempted where the specified subscriber queue and exception queue reference different message system links.
-
Action: Specify an exception queue that is a registered foreign queue of the same message system link as the subscriber queue.
-
Cause: An operation for OUTBOUND propagation was attempted where the AQ queues used for the subscriber queue and exception queue have different payload types.
-
Action: Specify an exception queue that has the same payload type as the subscriber queue.
-
Cause: An administration operation for a subscriber was attempted which is marked for removal. If attempting to remove a subscriber, then the Messaging Gateway agent is not running or is running but unable to remove the subscriber at this time.
-
Action: Do not issue propagation administration commands for a subscriber for which removal is pending. Wait for the subscriber to be removed by the agent or issue REMOVE_SUBSCRIBER with the FORCE option to force the subscriber to be removed.
-
Cause: An attempt was made to create a propagation subscriber when one already exists for the specified queue and destination pair.
-
Action: Specify a different queue and destination pair, or remove the subscriber using that pair and retry the operation.
-
Cause: An attempt was made to create a propagation schedule when one already exists for the specified source and destination pair.
-
Action: Specify a different source and destination pair, or remove the schedule using that pair and retry the operation.
-
Cause: An attempt was made to shut down Messaging Gateway agent when it is not started.
-
Action: No action required.
-
Cause: An attempt was made to start Messaging Gateway agent when it is already started.
-
Action: No action required.
-
Cause: An operation was attempted that requires the Messaging Gateway agent to be shut down.
-
Action: Issue SHUTDOWN, wait for MGW_GATEWAY view to show NOT_STARTED status, and retry the operation. CLEANUP_GATEWAY may need to be issued to reset the gateway state if the agent fails to shut down after a reasonable amount of time.
-
Cause: An operation was attempted that requires the Messaging Gateway agent to be started and responsive.
-
Action: Issue STARTUP, wait for MGW_GATEWAY view to show RUNNING status, and retry the operation.
-
Cause: An attempt was made to shut down Messaging Gateway agent when it is in the process of starting and initializing.
-
Action: Wait for MGW_GATEWAY view to show RUNNING status and retry the operation. CLEANUP_GATEWAY may need to be issued to reset the gateway state if the gateway fails to start after a reasonable amount of time.
-
Cause: Messaging Gateway agent terminated abnormally due to an unexpected error.
-
Action: Review the Messaging Gateway log file for further information regarding the problem. Resolve the problem and start the Messaging Gateway agent. Contact Oracle Support Services if the problem is unable to be resolved.
-
Cause: A timeout occurred when attempting an administration operation. An attempt was made to perform an administration operation while Messaging Gateway agent is starting and initializing, or two administration operations were attempted at the same time.
-
Action: Retry the operation. If Messaging Gateway agent is starting, then wait for MGW_GATEWAY view to show RUNNING status.
-
Cause: An unexpected error occurred trying to acquire administration lock.
-
Action: Retry the operation. Contact Oracle Support Services if the error persists.
-
Cause: An unexpected error occurred trying to release administration lock.
-
Action: Contact Oracle Support Services if the error persists.
-
Cause: Messaging Gateway agent user has not been configured.
-
Action: Create a database user having role MGW_AGENT_ROLE and issue DB_CONNECT_INFO to configure an agent user.
-
Cause: The specified database user does not currently exist.
-
Action: Create the user and grant all necessary privileges and roles.
-
Cause: The specified database user does not have a required role.
-
Action: Grant the user the indicated role.
-
Cause: Unexpected configuration state.
-
Action: Remove and re-create the configured entities. Contact Oracle Support Services if the problem is unable to be identified or resolved.
-
Cause: An attempt was made to alter a property list where the number of properties in the resulting list exceeds the maximum allowed.
-
Action: Order the elements of the alter list differently so the number of elements in the resulting list is less than the maximum.
-
Cause: An attempt was made to specify a reserved name for a property name.
-
Action: Use a non-reserved name.
-
Cause: An attempt was made to use NULL for a property name.
-
Action: Specify a non-NULL name.
-
Cause: An attempt was made to specify an invalid value for a property.
-
Action: Specify a valid property value.
ORA-32800 internal error string
ORA-32801 invalid value string for string
ORA-32802 value for string must be string
ORA-32803 value for string cannot be altered
ORA-32804 invalid value string, string should have form string
ORA-32805 identifier for string too long, maximum length is string characters
ORA-32806 value for string is too long, maximum length is string
ORA-32807 message system link string already exists
ORA-32808 message system link string does not exist
ORA-32809 foreign queue string is already registered
ORA-32810 foreign queue string is not registered
ORA-32811 subscriber string already exists
ORA-32812 subscriber string does not exist
ORA-32813 propagation schedule string already exists
ORA-32814 propagation schedule string does not exist
ORA-32815 message system link string is referenced by a foreign queue
ORA-32816 foreign queue string is referenced by a subscriber or schedule
ORA-32817 message system link string is not configured with a log queue for string
ORA-32818 AQ queue string does not exist
ORA-32819 AQ queue string must be a normal queue
ORA-32820 subscriber queue and exception queue must use same message system link
ORA-32821 subscriber queue and exception queue must have same payload type
ORA-32822 subscriber string is marked for removal
ORA-32823 subscriber exists for queue string and destination string
ORA-32824 schedule exists for source string and destination string
ORA-32825 Messaging Gateway agent has not been started
ORA-32826 Messaging Gateway agent has already been started
ORA-32827 Messaging Gateway agent must be shut down
ORA-32828 Messaging Gateway agent must be running
ORA-32829 Messaging Gateway agent cannot be shut down while it is starting
ORA-32830 result code string returned by Messaging Gateway agent
ORA-32831 timed out trying to acquire administration lock
ORA-32832 failure string trying to acquire administration lock
ORA-32833 failure string trying to release administration lock
ORA-32834 Messaging Gateway agent user has not been set
ORA-32835 database user string does not exist
ORA-32836 database user string must be granted role string
ORA-32837 invalid configuration state string
ORA-32838 exceeded maximum number of properties
ORA-32839 property string is reserved, names with MGWPROP$_ prefix are not valid
ORA-32840 property name cannot be NULL
ORA-32841 invalid value for property string
| ![]() Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
16
ORA-33000 to ORA-65535
-
Cause: The AGGMAP was already compiled by a more recent version of the product than was being used to execute this command.
-
Action: Recompile the AGGMAP in the current version.
-
Cause: A floor argument greater than the ceiling argument was specified.
-
Action: Adjust the floor and ceiling arguments so that the floor is less than the ceiling.
-
Cause: A RELATION clause in the AGGMAP named a workspace object that is not a relation.
-
Action: Name a valid self-relation in the RELATION statement.
-
Cause: A relation was named in a RELATION clause of the AGGMAP that is not a self-relation.
-
Action: Name a valid self-relation in the
RELATION
statement. -
Cause: A relation was named in a RELATION clause of the AGGMAP that is not a relation for a base dimension of the AGGMAP.
-
Action: Name a valid self-relation in the
RELATION
statement, that is, one that has a dimension that dimensions the AGGMAP. -
Cause: Two RELATION statements in the AGGMAP reference the same relation object.
-
Action: Remove the duplicate RELATION statement.
-
Cause: A line in the AGGMAP contains invalid syntax.
-
Action: Change the line to have valid syntax.
-
Cause: Operator variables cannot have the rollup dimension as one of their base dimensions.
-
Action: Modify the definition of the operator variable so that the current rollup dimension is not one of its bases.
-
Cause: An invalid argument was supplied to the OPERATOR clause in the relation statement.
-
Action: Fix the OPERATOR clause so that it specifies either a valid variable name or a valid operator.
-
Cause: An operator variable was supplied whose datatype is not TEXT.
-
Action: Change the operator clause to reference a TEXT variable.
-
Cause: The min argument was greater than the max argument.
-
Action: Adjust the min and max arguments so that min is less than max.
-
Cause: A MEASUREDIM was supplied in the AGGMAP that was not acceptable.
-
Action: Modify the MEASUREDIM clause to specify a valid dimension.
-
Cause: The aggmap contains multiple instances of a clause that can only be specified once.
-
Action: Remove the extra clause.
-
Cause: The AGGMAP either specified multiple PROTECT statements not on a RELATION line, or specified PROTECT statements both independently and on RELATION lines.
-
Action: Correct the AGGMAP to have valid syntax.
-
Cause: An ARGS value had a non-text datatype.
-
Action: Use a text variable for ARGS.
-
Cause: The AGGMAP contained multiple SCREENBY clauses.
-
Action: Remove one of the SCREENBY clauses from the AGGMAP.
-
Cause: The AGGMAP contains incompatible RELATION statements.
-
Action: Remove one of the RELATION statements from the AGGMAP.
-
Cause: The user attempted to aggregate a variable in another analytic workspace.
-
Action: Create an AGGMAP in the other analytic workspace to aggregate that variable.
-
Cause: The user attempted to aggregate a variable with different dimensions than the AGGMAP. This is only possible with undimensioned AGGMAPs.
-
Action: Create a new undimensioned AGGMAP.
-
Cause: The user specified a MIN argument that was greater than or equal to the FLOOR argument.
-
Action: Reduce the MIN argument.
-
Cause: The user specified a MAX argument that was less than or equal to the CEILING argument.
-
Action: Increase the MAX argument.
-
Cause: An invalud ERRORMASK value was specified.
-
Action: Remove the invalid value from the ERRORMASK list.
-
Cause: The user specified an ERRORLOG MAX of 0 or a negative number.
-
Action: Adjust the AGGMAP so that it uses a positive number.
-
Cause: The user specified an invalid hierarchy dimension qualified data reference.
-
Action: Adjust the AGGMAP so that it uses a valid dimension value qualified data reference.
-
Cause: The user specified an invalid qualified data reference for the hierarchy dimension.
-
Action: Adjust the AGGMAP so that it uses a valid dimension value qualified data reference.
-
Cause: The user specified an invalid qualified data reference for the hierarchy dimension.
-
Action: Adjust the AGGMAP so that it uses a valid dimension value qualified data reference.
-
Cause: The user specified two conflicting hierarchy dimension qualified data references.
-
Action: Adjust the AGGMAP so that it uses a consistent qualified data reference.
-
Cause: Multiple dimensions share the same hierarchy dimension, but it is only qualified within a subset of the AGGMAP relations.
-
Action: Adjust the AGGMAP so that it uses consistent qualified data references.
-
Cause: The hierarchy dimension offset is an invalid dimension position.
-
Action: Adjust the AGGMAP so that it uses valid qualified data references.
-
Cause: The hierarchy dimension offset is an invalid dimension position.
-
Action: Adjust the AGGMAP so that it uses valid qualified data references.
-
Cause: The user specified an invalid qualified data reference for the hierarchy dimension.
-
Action: Adjust the AGGMAP so that it uses a valid dimension value qualified data reference.
-
Cause: The user included both RELATION and DIMENSION statements in the AGGMAP referring to the same AGGMAP.
-
Action: Remove one of the conflicting clauses.
-
Cause: The VALUESET statement specified a scalar valueset but did not include a qualified data reference to specify the parent.
-
Action: Add a qualified data reference specifying the parent to the VALUESET statement.
-
Cause: The VALUESET line referred to a dimensioned valueset.
-
Action: Use a non-dimensioned valueset to limit the status of the dimensioned one.
-
Cause: The specified AGGMAP was dimensioned by a conjoint dimension.
-
Action: Use the CHGDFN command to change the conjoint to a composite dimension.
-
Cause: An invalid model name was attached to an AGGMAP.
-
Action: Remove the model from the AGGMAP or create a model with that name.
-
Cause: An inappropriate value was specified for the named option.
-
Action: Set a legal value for the option.
-
Cause: An inappropriate value was specified for the named option.
-
Action: Set a legal value for the option.
-
Cause: The user attempted to insert a value that had too many digits into a NUMBER dimension. For instance, the user might have tried to insert the value 99999 (5 digits) into a dimension with datatype NUMBER(4).
-
Action: Use a smaller number for the dimension value, or define a new dimension with a larger precision and replace the old dimension with the new one.
-
Cause: The user attempted to attach an old OLAP Services analytic workspace that cannot be converted by this version of OLAP Services.
-
Action: Either create a new analytic workspace or try using a version of OLAP Services compatible with the one that created this analytic workspace.
-
Cause: There is no currently active analytic workspace. The command that generated the error requires an active analytic workspace on which to operate.
-
Action: Execute an AW ATTACH or AW CREATE command to establish an active workspace.
-
Cause: The specified analytic workspace is currently not attached to the session, or the name is misspelled.
-
Action: Attach the analytic workspace with the AW ATTACH command, or correct the spelling of the name .
-
Cause: The specified analytic workspace is currently not attached to the session, or the name is misspelled.
-
Action: Attach the analytic workspace with the AW ATTACH command, or correct the spelling of the name .
-
Cause: The command requires a non-temporary analytic workspace on which to operate.
-
Action: Specify an analytic workspace other than EXPTEMP.
-
Cause: The user exported an object with datatype NTEXT, but the EIF file that will result from the EXPORT command is not written in Unicode. Because no non-Unicode file can represent all possible Unicode data, it is possible that some data will be lost when converting from the Unicode NTEXT object to the EIF file. The EIF file will be written in the character set indicated by the "nls_charset" argument of the EXPORT command, or, if no such argument is present, in the database character set.
-
Action: If the user is certain that the contents of the NTEXT object can be represented in the specified character set, then no action is necessary. Otherwise, the user can add "nls_charset 'UTF8'" to the EXPORT command string. This will result in the EIF file being written in UTF8 Unicode, which can represent all the data contained in NTEXT objects.
-
Cause: User attempted to export an object whose datatype is NTEXT, but the EIFVERSION option indicates a version of Express / Oracle OLAP that does not support the NTEXT datatype. The object will be exported as a TEXT object instead.
-
Action: No action required.
-
Cause: User attempted to export an expression whose datatype is NTEXT, but the EIFVERSION option indicates a version of Express / Oracle OLAP that does not support the NTEXT datatype. The expression will be exported as a TEXT object instead.
-
Action: No action required.
-
Cause: A program used an analytic workspace name in a qualified object name. The named analytic workspace is not attached at program run time.
-
Action: No action required. The program will be automatically recompiled. It is likely that the recompile will fail with an appropriate exception code, in which case the signaled condition should be corrected and the program re-run.
-
Cause: When the compiled code was saved, the specified object was a surrogate of a certain dimension. Now the specified object is a surrogate of a different dimension.
-
Action: No action required; program automatically recompiles.
-
Cause: Not all kinds of dimensions can have surrogates. The user attempted to define a surrogate of a prohibited kind of dimension.
-
Action: Do not attempt to define a surrogate on this dimension.
-
Cause: The user attempted to define a surrogate without specifying a valid datatype.
-
Action: Specify the datatype (ID, NTEXT, TEXT, NUMBER, or INTEGER) in the definition of the surrogate.
-
Cause: The user attempted to define a surrogate on a dimension that has type DAY, WEEK, MONTH, or YEAR.
-
Action: Do not attempt to define a surrogate on this dimension.
-
Cause: The user attempted to include both a dimension and its surrogate in the DIMENSION statement of a model.
-
Action: Use either the dimension or the surrogate in the DIMENSION statement of the model, but not both.
-
Cause: The user attempted to include two dimension surrogates of the same dimension in the DIMENSION statement of a model.
-
Action: Use either of the two surrogates in the DIMENSION statement of the model, but not both.
-
Cause: User used the ASSIGN keyword on a DIMENSION target in a FILEREAD or SQL FETCH command.
-
Action: To create a new dimension value in a FILEREAD or SQL FETCH command, use the APPEND keyword.
-
Cause: The user attempted to assign a value to a dimension surrogate whose datatype is INTEGER. INTEGER surrogates, like INTEGER dimensions, cannot have values assigned to them. They can only be referenced by position.
-
Action: Do not attempt to assign values to an INTEGER surrogate. Values will automatically appear and disappear from the INTEGER surrogate as positions are added to or removed from the underlying dimension.
-
Cause: User used the APPEND keyword on a SURROGATE target in a FILEREAD or SQL FETCH command.
-
Action: To assign a value to a SURROGATE in a FILEREAD or SQL FETCH command, use the ASSIGN keyword.
-
Cause: The user attempted to redefine a conjoint dimension as a composite, but the conjoint has one or more surrogates defined. A dimension that has surrogates cannot be redefined as a composite.
-
Action: Either delete all surrogates for the dimension, or do not attempt to redefine the dimension as a composite.
-
Cause: The user attempted to use NUMBER(Precision) or NUMBER(Precision, Scale) as the datatype in a definition for some object other than a DIMENSION or VARIABLE, such as a FORMULA or PROGRAM. This error can also be produced in cases where a NUMBER datatype is not allowed at all.
-
Action: Use the NUMBER type without specifying a precision or scale. If a NUMBER datatype is not allowed at all, then this fix will only change the exception message to something more specific.
-
Cause: The user attempted to define a NUMBER dimension without specifying a precision. The proper format for declaring a number dimension is NUMBER(Precision) or NUMBER(Precision, Scale). NUMBER with no precision or scale is not allowed.
-
Action: Use NUMBER(Precision) or NUMBER(Precision, Scale) to specify the datatype of a NUMBER dimension.
-
Cause: This is an informational message that reminds you that you may not save changes to the specified analytic workspace.
-
Action: No action required, unless it was desired to save changes to the analytic workspace. In that case, detach and reattach the analytic workspace read-write.
-
Cause: The command attempted to operate on an analytic workspace that is not currently attached, or the name of the analytic workspace is misspelled.
-
Action: Attach the analytic workspace or correct the spelling.
-
Cause: The specified analytic workspace is an internal workspace and may not be detached by the user.
-
Action: Specify a different analytic workspace to detach.
-
Cause: The command attempted to operate on an internal analytic workspace used by the system.
-
Action: Specify a different analytic workspace.
-
Cause: The specified analytic workspace is currently in use.
-
Action: The desired action requires an analytic workspace that is not currently in use.
-
Cause: User attempted to use AW UNALIAS on a non-existent alias.
-
Action: Make sure that the command specified the correct analytic workspace and alias. The alias must have been assigned (using AW ALIAS) during the current session and must not have been removed by a previous AW UNALIAS or AW DETACH command.
-
Cause: User included the same name twice in the alias list of an AW ALIAS or AW UNALIAS command.
-
Action: Remove the duplicate name and try again.
-
Cause: The user attempted to use the MAINTAIN command on a dimension surrogate. The MAINTAIN command can only be used with real dimensions, not surrogates.
-
Action: Use the MAINTAIN command to modify the underlying dimension of the surrogate instead.
-
Cause: The user attempted an invalid operation.
-
Cause: When character set conversion happens between TEXT and NTEXT either implicitly or explicitly, some characters are lost due to no mapping characters in the destination character set.
-
Action: Make sure all the characters can be mapped to destination character sets or set the
NLS_NCHAR_CONV_EXCP
initialization parameter tofalse
. -
Cause: The user used incorrect syntax for the ALLOCATE command.
-
Action: Correct the calling syntax.
-
Cause: The user used incorrect syntax for the AGGREGATE command.
-
Action: Correct the calling syntax.
-
Cause: The user used incorrect syntax for the AGGREGATE function.
-
Action: Correct the calling syntax.
-
Cause: The user used the ALLOCMAP command to define the AGGMAP, so the AGGMAP can only be used with the ALLOCATE command, or the AGGMAP has no contents attached to it.
-
Action: Use the AGGMAP command to define the AGGMAP.
-
Cause: When using AGGREGATE, only simple permissions and permissions on base dimensions are valid.
-
Action: Remove the permissions clause from the variable causing problems.
-
Cause: A measure dimension was supplied in the AGGMAP, but a position for the variable was not found in it.
-
Action: Add a position for the variable in the measure dimension.
-
Cause: The user lacked the permissions necessary for the aggregation variable.
-
Action: Remove the restricting permissions from the variable or base dimension.
-
Cause: Either someone improperly changed the COUNTVAR variable, or AGGREGATE has an error.
-
Action: Set the COUNTVAR variable to NA before starting AGGREGATE. If you previously set the COUNTVAR variable to NA, then contact Oracle Support Services.
-
Cause: The ARGS variable specified a weight even though one is not needed.
-
Action: Modify the ARGS variable so that it does not specify a weight for that operation.
-
Cause: The given operator requires a WEIGHT specification, but the ARGS variable did not supply one.
-
Action: Modify the ARGS variable to specify a weight for the operation.
-
Cause: An invalid string was provided for an aggregation operator.
-
Action: Check the spelling of the operator to make sure you are specifying a valid one.
-
Cause: An invalid NAOPERATOR was specified.
-
Action: Specify HFIRST, HLAST or HEVEN.
-
Cause: An invalid REMOPERATOR was specified.
-
Action: Specify one of the legal operators.
-
Cause: The user specified an NAOPERATOR when you were not using PROPORTIONAL or EVEN.
-
Action: Remove the NAOPERATOR clause from the RELATION line.
-
Cause: The user specified a REMOPERATOR without using PROPORTIONAL, EVEN, or HEVEN.
-
Action: Remove the REMOPERATOR clause from the RELATION line.
-
Cause: The user specified MIN, MAX, FLOOR, or CEILING when using an operator other than PROPORTIONAL.
-
Action: Remove the incorrect argument from the RELATION line.
-
Cause: The AGGMAPINFO function was called with an object that is not an AGGMAP.
-
Action: Modify the call to AGGMAPINFO to specify an AGGMAP object.
-
Cause: The call to AGGMAPINFO is invalid.
-
Action: Modify the call to specify a valid syntax.
-
Cause: The user tried to export a NUMBER dimension to an EIF file with the EIFVERSION option set to a number less than 80000. Versions previous to that eversion do not support NUMBER dimensions.
-
Action: A NUMBER dimension cannot be used in a version older than 9.2.0. If the EXPORT file is going to be read by version 9.2.0 or higher, then set EIFVERSION to a number greater than or equal to 80000 and execute the EXPORT command again.
-
Cause: The syntax for the CLEAR command was invalid.
-
Action: Modify your syntax using the correct format.
-
Cause: A calculation in the current AGGREGATE command attempted to divide by zero as a result of an AVERAGE, WAVERAGE, HAVERAGE or HWAVERAGE operation.
-
Action: Either fix the data, or set DIVIDEBYZERO to YES to return NA instead of signalling an error.
-
Cause: While running AGGREGATE in threaded mode, you attempted to specify a WEIGHT variable in another analytic workspace.
-
Action: Use a weight variable from the same analytic workspace as the aggmap and rollup variable.
-
Cause: A model, NATRIGGER, or other object called the AGGREGATE function or command while another AGGREGATE function or command was already in progress.
-
Action: Modify your objects so that they do not need to have two AGGREGATE commands or functions executing at once.
-
Cause: The depth of the hierarchies that are part of a composite exceeded 4 billion levels during the merge.
-
Action: Reduce the number of levels in the hierarchies, reduce the number of dimensions in the composite, or do not aggregate over all dimensions at once.
-
Cause: An application called the INTL.MESG function with an incorrect or uninstalled product / facility combination.
-
Action: Make sure that the appropriate binary message file is stored on the host in the correct location:
ORACLE_HOME/product/facilitylanguage.msb
-
Cause: The caller of INTL.MESG tried to retrieve a non-existent message.
-
Action: Add the message to the application's message file, and recompile or reinstall the binary message file.
-
Cause: An internal Oracle OLAP error occurred. Oracle OLAP attempted to retrieve a message that does not exist in the installed message file
OLAP_HOME
/aps*.msb. -
Action: Ignore this error message.
-
Cause: The dimension of the model is not a dimension of the aggmap.
-
Cause: The dimension of the model must match a hierarchy of the aggmap.
-
Action: Add a RELATION statement to the AGGMAP for that dimension.
-
Cause: An empty union DIMENSION list was specified.
-
Action: Specify a valid list of dimensions when defining a union DIMENSION.
-
Cause: The user cannot specify a prefix list or the UNIQUE keyword when defining a MERGE DIMENSION.
-
Cause: The union dimension's base dimensions have inconsistent datatypes.
-
Action: Specify a valid list of dimensions when defining CONCAT DIMENSION.
-
Cause: An invalid prefix list dimension was specified.
-
Action: Specify a valid prefix list when defining CONCAT DIMENSION.
-
Cause: An invalid or ambiguous prefix was specified.
-
Action: Specify a valid prefix list when defining a union DIMENSION.
-
Cause: A duplicate CONCAT dimension was found.
-
Cause: Union dimension contains a previously detected leaf dimension.
-
Cause: An unknown character set conversion error occurred when converting a TEXT value to an NTEXT value.
-
Cause: An unknown character set conversion error occurred when converting an NTEXT value to a TEXT value.
-
Cause: The user called the UNISTR function on a string that had an invalid escape sequence. The only valid escape sequences in UNISTR are:
-
Action: Make sure that all escape sequences in UNISTR arguments are exactly four hexadecimal digits. To represent codepoints whose value is less than 0x1000, use preceding zeros. WRONG: 0x10; RIGHT: 0x0010.
-
Cause: The user input the wrong format or object types.
-
Action: Make sure number of arguments and all object types are correct.
-
Action: Check the context and permission for dimension maintainance.
-
Cause: Try to limit relation dimension using qdr list.
-
Action: Delete the part of qdr list for relation dimension.
-
Cause: Use other dimensions than dimensions in relation dimensions.
-
Action: Make sure all dimensions of qdrs dimension the relation.
-
Cause: Repeat the qdr dimension.
-
Action: Delete the repeated qdr.
-
Cause: The HIERHEIGHT function was specified incorrectly.
-
Action: Make sure the format is correct.
-
Cause: The level relation is not dimensioned by the source relation dimension.
-
Action: Make sure the level relation has the correct definition.
-
Cause: The destination relation has the wrong definition.
-
Action: Make sure the destination relation has the correct dimensions.
-
Cause: The user supplied an undimensioned (scalar) variable to the ALLOCATE command.
-
Action: Use a dimensioned variable.
-
Cause: The user attempted to execute ALLOCATE with mismatching TARGET and TARGETLOG variables.
-
Action: Use TARGET and TARGETLOG variables with matching dimensionality.
-
Cause: The user specified an invalid source or basis relation on the ALLOCATE command line.
-
Action: Modify the relation to be a one-dimensional self-relation.
-
Cause: The user specified a TARGETLOG variable that had a different datatype from the TARGET variable.
-
Action: Use TARGETLOG and TARGET variables with an identical datatype.
-
Cause: The user specified an ACROSS composite when the BASIS is not a FORMULA.
-
Action: Remove the ACROSS phrase or use a FORMULA for the BASIS.
-
Cause: The user did not have sufficient permissions to run the ALLOCATE command.
-
Action: Change to a user ID with the appropriate permissions, or use objects that you have permission to use.
-
Cause: The user used the AGGMAP command to define the AGGMAP, so either the AGGMAP can only be used with the AGGREGATE command, or the AGGMAP has no contents attached to it.
-
Action: Use the ALLOCMAP command to define the AGGMAP.
-
Cause: The user requested that source values be modified during the allocation, but that is not possible when using a formula source.
-
Action: Either use a VARIABLE source or remove the SOURCEVAL specification for your ALLOCMAP.
-
Cause: The user specified an invalid formatter in the ALLOCERRLOGHEADER or ALLOCERRLOGFORMAT options.
-
Action: Correct the option to have a valid format.
-
Cause: The user specified an ERRORLOG MAX value in the ALLOCMAP, but more errors were encountered while performing the allocation.
-
Action: Either set ERRORLOG NOSTOP, reduce the allocation errors, or// increase the ERRORLOG MAX setting.
-
Cause: The qdr is not in its dimension.
-
Action: Make sure the qdr is in its dimension.
-
Cause: The level relation includes the invalid content.
-
Action: In level relation, all parents should be always either greater or less than their children.
-
Cause: Use other objects than dimension in qdr list.
-
Action: Must use dimensions only in qdr list.
-
Cause: Wrong object type for either source or destination.
-
Action: Give the correct object.
-
Cause: Source relation is not self-relation.
-
Action: Give a self-relation as source.
-
Cause: Destination relation is not dimensioned by source relation dimension.
-
Action: Give a correct destination relation.
-
Cause: Command format is not correct.
-
Action: Check the object type and number, and give the correct format.
-
Cause: Source relation is not a self-relation.
-
Action: Give a source relation as self-relation.
-
Cause: Destination variable is not numeric type variable.
-
Action: Make sure the variable is numeric.
-
Cause: Destination variable/relation does not have enough dimensionality to hold the result from the multi-dimensional source relation.
-
Action: Either limit the status of hierarchy dimensions or redefine the destination variable/relation with the extended dimensionality.
-
Action: Make sure the dimension can be inserted.
-
Cause: The destination relation is not dimensioned by the dimension of the source relation.
-
Action: Change the definition of the destination relation to be dimensioned by the dimension of the source relation.
-
Cause: The destination relation has the wrong dimension type.
-
Action: Change the definition of the destination relation so that its dimension is an Oracle number.
-
Action: Use CDA command to set current directory alias or include the directory alias in the file name.
-
Action: Use
CREATE DIRECTORY
name
AS '
path
'. Then grant privileges to that directory alias. -
Action: Use GRANT command to assign permissions to the directory alias.
-
Cause: The given olap table function used more than one LOOP statement.
-
Action: It is currently impossible to specify more than one LOOP composite, either remove one of the statements (and loop densly over relevant dimensions), or create a new composite that encompasses both loops and have a single loop statement refer to that.
-
Cause: There is no limitmap on the table function and either the datamap does not contain a fetch, or it errored before the fetch was called.
-
Action: Check the datamap for errors, make sure that it executes a fetch statement, if it is not intended to execute the fetch then make sure that the table function has a valid limitmap.
-
Cause: Invalid LIMITMAP syntax, or the name resolution failure of an ANALYTIC WORKSPACE OBJECT.
-
Action: Check the syntax of the limit map, check that the OLAP_TABLE function refers to a valid analytic workspace, and check that all analytic workspace objects within the limitmap actually exist within the analytic workspace.
-
Cause: The limitmap refers to a matching of ADT attribute to AW object, but the ADT attribute is not an element of the specified ADT table. Most commonly this is a typographical error.
-
Action: Add the attribute to the ADT, correct the LIMITMAP, or remove the reference from the LIMITMAP.
-
Cause: Model may include equations other than dimension values, or blocks other than simple blocks.
-
Action: Make sure model only includes the simple blocks with dimension values.
-
Cause: Before the current relation, dynamic model exists.
-
Action: Make sure the dynamic model is the last statement.
-
Cause: Before the current model, the dynamic model exists.
-
Action: Make sure the dynamic model as the last calculation statement, and only at most one dynamic model exists.
-
Cause: There are more than the maximum number of OFFSET or PERIODICITY values.
-
Action: Remove some of the values.
-
Cause: A cycle number was specified in a call to FCQUERY to retrieve forecast data not related to a cycle.
-
Action: Remove the cycle specification from the call to FCQUERY.
-
Cause: A cycle number less than 1 or greater than the maximum value was specified in a call to FCQUERY.
-
Action: Specify a number in the indicated range.
-
Cause: More OFFSET values were specified than PERIODICITY values.
-
Action: Supply only as many OFFSETs as there are PERIODICITY values.
-
Cause: The OFFSET for a cycle exceeded the PERIODICITY for that cycle.
-
Action: Supply an OFFSET less than or equal to the PERIODICITY for the corresponding cycle.
-
Cause: An even number was given for an option that requires an odd number.
-
Action: Supply an odd number or let the option default.
ORA-33000 (AGOPEN00) %a workspace object string AGGMAP %p cannot be accessed because it was compiled by a more recent version of %p.
ORA-33002 (XSAGDNGL00) %a workspace object number number In AGGMAP %p, the FLOOR argument of %p must be less than the CEILING argument of %p.
ORA-33004 (XSAGDNGL01) workspace object is not a relationship array.
ORA-33006 (XSAGDNGL02) The relation workspace object is not related to itself.
ORA-33008 (XSAGDNGL03) %a workspace object workspace object The relation %p is not a relation over a base dimension of AGGMAP %p.
ORA-33010 (XSAGDNGL04) %a workspace object workspace object Relation %p is duplicated in the AGGMAP %p.
ORA-33012 (XSAGDNGL05) AGGMAP workspace object contains invalid syntax.
ORA-33014 (XSAGDNGL06) %a workspace object workspace object workspace object In AGGMAP %p, variable operator %p cannot be dimensioned by rollup dimension %p.
ORA-33016 (XSAGDNGL07) %a workspace object workspace object In AGGMAP %p, %p is not a valid operator or variable name.
ORA-33018 (XSAGDNGL08) %a workspace object workspace object string In AGGMAP %p, the datatype of %p must be TEXT, not %p.
ORA-33020 (XSAGDNGL09) %a workspace object number number In AGGMAP %p, the MIN argument of %p must be less than the MAX argument of %p.
ORA-33022 (XSAGDNGL10) %a workspace object workspace object The measure dimension %p must be a TEXT or ID base dimension that does not dimension AGGMAP %p, but is in the same analytic workspace.
ORA-33024 (XSAGDNGL11) AGGMAP workspace object contains duplicate information.
ORA-33030 (XSAGDNGL14) In AGGMAP workspace object, you can have either a single independent PROTECT statement or PROTECT statements in your RELATION statements.
ORA-33036 (XSAGDNGL17) ARGS option workspace object must be a TEXT variable.
ORA-33046 (XSAGDNGL22) In AGGMAP workspace object, you can specify only one SCREENBY clause.
ORA-33048 (XSAGDNGL23) %a workspace object workspace object workspace object In AGGMAP %p, the relation %p and the relation %p are both over the same base dimension.
ORA-33050 (XSAGDNGL24) %a workspace object workspace object AGGMAP %p cannot be used to aggregate %p, because %p is defined in a different analytic workspace.
ORA-33052 (XSAGDNGL25) AGGMAP workspace object is a dimensioned AGGMAP; it can only be used to aggregate like-dimensioned variables.
ORA-33054 (XSAGDNGL26) %a workspace object number number In AGGMAP %p, a MIN argument of %p must be less than a FLOOR argument of %p.
ORA-33056 (XSAGDNGL27) %a workspace object number number In AGGMAP %p, the MAX argument of %p must be greater than the CEILING argument of %p.
ORA-33058 (XSAGDNGL28) %a workspace object string number In AGGMAP %p, error code %p is greater than the maximum error code of %p.
ORA-33060 (XSAGDNGL29) In AGGMAP workspace object, the value for the ERRORLOG MAX option must be greater than 0.
ORA-33064 (XSAGDNGL31) %a workspace object workspace object In AGGMAP %p, the hierarchy dimension QDR %p cannot refer to the related dimension of the relation.
ORA-33066 (XSAGDNGL32) %a workspace object workspace object In AGGMAP %p, the hierarchy dimension QDR %p must be a hierarchy dimension of the relation.
ORA-33068 (XSAGDNGL33) %a workspace object workspace object In AGGMAP %p, the hierarchy dimension QDR over dimension %p must specify a positive dimension offset.
ORA-33070 (XSAGDNGL34) %a workspace object workspace object In AGGMAP %p, all QDRs of dimension %p must map to the same dimension position.
ORA-33072 (XSAGDNGL35) %a workspace object workspace object In AGGMAP %p, the hierarchy dimension QDR over dimension %p must be specified for every relation dimensioned by that hierarchy dimension.
ORA-33074 (XSAGDNGL36) %a workspace object workspace object number In AGGMAP %p, the offset %p is not a valid offset into dimension %p.
ORA-33076 (XSAGDNGL37) %a workspace object workspace object number In AGGMAP %p, the value '%p' is not a valid value of dimension %p.
ORA-33078 (XSAGDNGL39) %a workspace object workspace object In AGGMAP %p, the hierarchy dimension QDR %p must refer to a dimension.
ORA-33080 (XSAGDNGL40) %a workspace object workspace object In AGGMAP %p, you cannot reference dimension %p with both a RELATION statement and a DIMENSION statement.
ORA-33082 (XSAGDNGL41) %a workspace object workspace object In AGGMAP %p, the non-dimensioned valueset %p must have a parent QDR in its VALUESET statement over the VALUESET's base dimension.
ORA-33084 (XSAGDNGL42) %a workspace object workspace object In AGGMAP %p, you cannot qualify the dimensioned valueset %p.
ORA-33086 (XSAGINIT01) %a workspace object workspace object AGGMAP %p cannot be dimensioned by a conjoint dimension.
ORA-33092 (XSAGCOMP04) number is not the name of a MODEL in any attached analytic workspace.
ORA-33098 (APABBR01) %a string workspace object A value of '%p' is not valid for the %p option.
ORA-33100 (APABBR02) %a number workspace object Value '%p' is not valid for the %p option.
ORA-33218 (CINSERT04) %a value workspace object number number %p is not a valid value for the %p dimension. Values for this dimension can have at most %p significant digits after rounding to %p decimal places.
ORA-33300 (DBERR22) %a string string Analytic workspace %p cannot be opened because it was last modified by an incompatible version of %p.
ORA-33332 (DSSEXIST01) Use the AW command to establish a current analytic workspace. Then start your current activity again.
ORA-33334 (DSSEXIST04) Analytic workspace string is not attached.
ORA-33336 (DSSEXIST04A) Analytic workspace string is not attached.
ORA-33338 (DSSEXIST05) You cannot specify the EXPTEMP analytic workspace.
ORA-33425 (EIFMAKEF15) CAUTION: Exporting NTEXT objects using string for the EIF file character set can cause loss of data. To preserve all NTEXT data, export using the UTF8 character set for the EIF file.
ORA-33427 (EIFMAKEF16) CAUTION: NTEXT object workspace object will be exported with type TEXT.
ORA-33429 (EIFMAKEF17) CAUTION: NTEXT expression will be exported with type TEXT.
ORA-33443 (ESDREAD14) %a workspace object string Discarding compiled code for %p because analytic workspace %p is not attached.
ORA-33468 (ESDREAD13) %a workspace object number workspace object Discarding compiled code for %p because %p is no longer a surrogate of dimension %p.
ORA-33918 (MAKEDCL33) %a workspace object string You cannot define a surrogate of dimension %p because it is a %p.
ORA-33920 (MAKEDCL34) The string SURROGATE must have one of the following datatypes: ID, NTEXT, TEXT, NUMBER, or INTEGER.
ORA-33922 (MAKEDCL35) You cannot define a surrogate of dimension workspace object because it is a date dimension.
ORA-33998 (MODCOMP12) %a workspace object workspace object workspace object workspace object You cannot use both %p and %p as model dimensions, because %p is a surrogate of %p.
ORA-34000 (MODCOMP13) %a workspace object workspace object workspace object You cannot use both %p and %p as model dimensions, because they are both surrogates of dimension %p.
ORA-34141 (MXCGPUT00) You cannot use the ASSIGN keyword with DIMENSION workspace object.
ORA-34143 (MXCGPUT02) You cannot assign values to SURROGATE workspace object because it is type INTEGER.
ORA-34145 (MXCGPUT03) You cannot use the APPEND keyword with SURROGATE workspace object.
ORA-34210 (MXCHGDCL18) You cannot change workspace object to a dimension composite because one or more surrogates has been defined for it.
ORA-34276 (MXDCL33) (Precision, Scale) arguments can only be used with a NUMBER variable or dimension.
ORA-34296 (MXDCL36) A NUMBER dimension must be defined with a fixed precision and scale, using the form NUMBER(precision) or NUMBER(precision, scale).
ORA-34342 (MXDSS01) IMPORTANT: Analytic workspace string is read-only. Therefore, you will not be able to use the UPDATE command to save changes to it.
ORA-34344 (MXDSS03) Analytic workspace string is not attached.
ORA-34346 (MXDSS04) The string analytic workspace cannot be detached.
ORA-34348 (MXDSS05) string is used only for internal purposes and cannot be accessed as an analytic workspace.
ORA-34350 (MXDSS06) string is an open analytic workspace.
ORA-34357 (MXDSS10) %a string string %p is not an alias of analytic workspace %p.
ORA-34359 (MXDSS11) string appears twice in the alias list.
ORA-34489 (MXMAINT06) You cannot maintain workspace object because it is a SURROGATE.
ORA-34514 (MXOPERR) %a string string string You cannot %p %p data in the expression that begins with '%p'.
ORA-34719 (NLSCHARSET03) Character data loss in NTEXT/TEXT conversion
ORA-35276 (SNSYN163) The format of the ALLOCATE command is: ALLOCATE varname [SOURCE svarname] [BASIS bvarname [ACROSS dimname]] [TARGET tvarname [TARGETLOG logvarname]] USING aggmap
ORA-35280 (SNSYN165) The format of the AGGREGATE command is: AGGREGATE varname1 [varname2 varname3 ...] USING aggmap-name [COUNTVAR intvar-name1 [intvar-name2 intvar-name3 ...]] [FUNCDATA] [THREADS #]
ORA-35282 (SNSYN166) The format of the AGGREGATE function is: AGGREGATE(varname USING aggmap-name [COUNTVAR intvar-name] [FORCECALC])
ORA-36178 (XSAGGR01) To be used with AGGREGATE, AGGMAP workspace object must be declared with the AGGMAP command.
ORA-36180 (XSAGGR08) AGGREGATE cannot function because there is a permission clause associated with variable workspace object.
ORA-36182 (XSAGGR09) %a workspace object number Could not locate a value for variable %p in measure dimension %p.
ORA-36184 (XSAGGR10) You do not have sufficient permissions for the variable workspace object.
ORA-36188 (XSAGGR16) AGGREGATE read a value less than 1 out of COUNTVAR variable workspace object. Either the values of the COUNTVAR variable are stored improperly, or there is a problem in AGGREGATE. If no one has modified the values in this COUNTVAR, contact Oracle Support Services.
ORA-36198 (XSAGGR33) %a string workspace object number workspace object The AGGREGATE operator %p does not require a weight, but ARGS variable %p with text 'number' specified %p as a weight.
ORA-36200 (XSAGGR34) %a string workspace object string AGGREGATE operator %p requires a WEIGHTBY clause, but ARGS variable %p did not specify one with text expression "%p".
ORA-36202 (XSAGOP01) 'number' is not a valid aggregation operator.
ORA-36204 (XSAGOP04N) %a workspace object string In AGGMAP %p, the NAOPERATOR %p must be HFIRST, HLAST or HEVEN.
ORA-36206 (XSAGOP04R) %a workspace object string In AGGMAP %p, REMOPERATOR %p must be MIN, MAX, FIRST, LAST, HFIRST, or HLAST.
ORA-36208 (XSAGOP05N) %a workspace object string string In AGGMAP %p, you can only specify NAOPERATOR %p with the PROPORTIONAL or EVEN operators, not %p.
ORA-36210 (XSAGOP05R) %a workspace object string string In AGGMAP %p, you can only specify the REMOPERATOR %p with the PROPORTIONAL, EVEN, or HEVEN operators, not %p.
ORA-36212 (XSAGOP06) %a workspace object string In AGGMAP %p, you can only specify the MIN, MAX, FLOOR, and CEILING arguments while using the PROPORTIONAL operator, not %p.
ORA-36258 (XSAGINFO00) When the AGGMAPINFO function is called, workspace object must be an AGGMAP.
ORA-36260 (XSAGINFO01) You specified an invalid keyword when calling the AGGMAPINFO function.
ORA-36290 (EIFMAKEF14) %a workspace object number You cannot export object %p, because EIFVERSION is set to %p. That version does not support dimensions of type NUMBER.
ORA-36342 (SNSYN200) The format of the CLEAR command is: CLEAR [ ALL | STATUS ] [ CHANGES | PRECOMPUTES | NONPRECOMPUTES | CACHE ] FROM var1 [var2, var3...] [USING aggmap]
ORA-36376 (XSAGZERO) AGGREGATE attempted to divide by zero. Set DIVIDEBYZERO to YES if you want NA to be returned as the result of a division by zero.
ORA-36378 (XSAGTHRWEIGHT) %a workspace object workspace object workspace object While running AGGREGATE with multiple threads, the weight variable %p specified by your ARGS variable %p must exist in the same analytic workspace as your AGGMAP %p.
ORA-36380 (AGGRECURSE) AGGREGATE was called recursively, which is not allowed.
ORA-36608 (XSAGHOVERFLOW) The depth of the hierarchies encountered while processing a composite dimension in AGGREGATE caused a counter overflow.
ORA-36610 (XSLMS00) %a value value Unable to locate a message file for product '%p' and facility '%p'.
ORA-36612 (XSLMS01) %a value value value An application attempted to retrieve a non-existent user message. (Product: %p, Facility: %p, Message Number: %p)
ORA-36614 (XSLMS02) %a string number %p attempted to retrieve a nonexistent user message. (Message number %p)
ORA-36616 (XSAGMODHIER01) %a workspace object workspace object MODEL %p cannot be added to AGGMAP %p, because it is dimensioned by a dimension not contained in the AGGMAP.
ORA-36628 (XSAGMODLIST03) %a workspace object workspace object MODEL %p could not be added to AGGMAP %p.
ORA-36630 (XSDUNION00) An empty CONCAT dimension list was specified.
ORA-36634 (XSDUNION02) INTEGER dimension workspace object cannot be used as a CONCAT dimension base.
ORA-36636 (XSDUNION03) The CONCAT base dimensions have inconsistent datatypes.
ORA-36638 (XSDUNION04) workspace object is an invalid CONCAT prefix dimension.
ORA-36640 (XSDUNION05) An invalid or ambiguous prefix was specified for workspace object.
ORA-36642 (XSDUNION06) Duplicate CONCAT dimension workspace object found
ORA-36644 (XSDUNION07) CONCAT dimension workspace object contains a previously detected leaf dimension.
ORA-36688 (NTEXTCNV00) Error during conversion from TEXT to NTEXT
ORA-36690 (NTEXTCNV01) Error during conversion from NTEXT to TEXT
ORA-36691 (NTEXTCNV02) Invalid escape sequence in argument to UNISTR function: string
ORA-36692 (XSRELTBL00) The format of the HIERHEIGHT command is: HIERHEIGHT relation1[(dimension dimvalue, ...)] into relation2 [using relation3 | a | d]
ORA-36694 (XSRELTBL01) The value cannot be added to dimension workspace object.
ORA-36696 (XSRELTBL02) QDR dimension workspace object should not be the related dimension of the relation.
ORA-36698 (XSRELTBL03) QDR dimension workspace object should be in the dimension list that dimensions the relation.
ORA-36700 (XSRELTBL04) QDR dimension workspace object repeats.
ORA-36702 (XSRELTBL05) The format of the HIERHEIGHT function is: HIERHEIGHT(relation [,] level) level >= 1.
ORA-36704 (XSRELTBL06) %a workspace object workspace object %p should be dimensioned by %p.
ORA-36706 (XSRELTBL07) %a workspace object workspace object %p should be dimensioned by %p and one integer/number dimension.
ORA-36708 (XSMXALLOC00) Variable workspace object must be dimensioned to be used by the ALLOCATE command.
ORA-36710 (XSMXALLOC01) %a workspace object workspace object TARGETLOG variable %p must be dimensioned identically to TARGET variable %p.
ORA-36712 (XSMXALLOC02) Relation workspace object must be a one-dimensional self-relation to be used as a SOURCE or BASIS with ALLOCATE.
ORA-36714 (XSMXALLOC03) %a workspace object workspace object TARGETLOG variable %p must have the same datatype as TARGET variable %p.
ORA-36716 (XSMXALLOC04) %a workspace object workspace object You can only use the ACROSS phrase when allocation BASIS %p is a FORMULA.
ORA-36718 (XSALLOC00) You do not have the necessary permissions to use AGGMAP workspace object.
ORA-36720 (XSALLOC01) To be used with ALLOCATE, your AGGMAP workspace object must be defined with the ALLOCMAP command.
ORA-36722 (XSALLOC02) %a workspace object workspace object In AGGMAP %p, you specified an NA or ZERO sourceval but supplied formula %p as your source for ALLOCATE.
ORA-36726 (XSALERR00) The character 'character' is not a valid format specifier for the ALLOCATE error log.
ORA-36728 (XSALERR01) %a workspace object number While performing the ALLOCATE command with AGGMAP %p, the error logging limit of %p was exceeded.
ORA-36742 (XSRELTBL08) %a string workspace object %p is not a valid qualified data reference for dimension %p.
ORA-36744 (XSRELTBL09) workspace object is not a valid level relation.
ORA-36746 (XSRELTBL10) workspace object must be a dimension.
ORA-36748 (XSRELTBL11) workspace object must be a relation.
ORA-36750 (XSRELTBL12) workspace object must be a self-relation.
ORA-36752 (XSRELTBL13) %a workspace object workspace object Relation %p must be dimensioned by %p.
ORA-36756 (XSRELGID00) The format of the GROUPINGID command is: GROUPINGID relation1 INTO {variable | relation2}
ORA-36758 (XSRELGID01) workspace object must be a self-relation.
ORA-36760 (XSRELGID02) Variable workspace object must have a numeric datatype.
ORA-36762 (XSRELGID03) The grouping variable/relation workspace object must be dimensioned by all dimensions of the source relation workspace object which have more than one element in status.
ORA-36764 (XSRELGID04) A value cannot be inserted into dimension workspace object.
ORA-36766 (XSRELGID05) %a workspace object workspace object Relation %p must be dimensioned by %p.
ORA-36768 (XSRELGID06) The related dimension of relation workspace object must be of type NUMBER.
ORA-36780 (IOSEC01) Current Directory Alias is not set. Cannot complete string.
ORA-36782 (IOSEC02) Directory Alias used in string does not exist, or you do not have sufficient privileges to access it.
ORA-36788 (IOSEC05) Access to the directory specified by string denied.
ORA-36800 (XSTBLFUNC00) The OLAP_TABLE function can only have a single LOOP statement within the LIMITMAP
ORA-36802 (XSTBLFUNC01) The OLAP_TABLE function must contain a DATAMAP that executes a FETCH command or a LIMITMAP
ORA-36804 (XSTBLFUNC02) The OLAP_TABLE function encountered an error while parsing the LIMITMAP
ORA-36806 (XSTBLFUNC03) The OLAP_TABLE function refers to an invalid ADT attribute: string
ORA-36902 (XSAGDNGL43) %a workspace object workspace object In AGGMAP %p, MODEL %p cannot be calculated dynamically because it contains simultaneous/step equations or equations which refer to variables.
ORA-36904 (XSAGDNGL44) %a workspace object workspace object In AGGMAP %p, RELATION %p occurs after a dynamic model. The dynamic model must be the last calculation within the AGGMAP.
ORA-36906 (XSAGDNGL45) %a workspace object workspace object AGGMAP %p, MODEL %p occurs after a dynamic model. The dynamic model must be the last calculation within the AGGMAP.
ORA-36950 (XSFCAST22) %a string number number The list of %p values cannot have more than %p members. You supplied %p.
ORA-36952 (XSFCAST23) You cannot specify a cycle number when querying the string forecasting option.
ORA-36954 (XSFCAST24) %a number number The cycle number must be between 1 and %p. You specified %p.
ORA-36956 (XSFCAST25) There are only number PERIODICITY values. You cannot specify more OFFSET values.
ORA-36958 (XSFCAST26) %a number number number The OFFSET value for cycle %p cannot be greater than the cycle's PERIODICITY, which is %p. You specified %p.
ORA-36960 (XSFCAST27) %a string number The value of the %p expression must be an odd number. You specified %p.
| ![]() Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|