88 ORA-33000 to ORA-37999

ORA-33000: (AGOPEN00) AGGMAP workspace object cannot be accessed because it was compiled by a more recent version of string.

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.

ORA-33002: (XSAGDNGL00) In AGGMAP workspace object, the FLOOR argument of number must be less than the CEILING argument of number.

Cause: The user specified a floor argument greater than the ceiling argument.

Action: Adjust the floor and ceiling arguments so that the floor is less than the ceiling. OBSOLETE, please remove this

ORA-33003: (XSAGDIMDROP) workspace object, to be transformed during data load, must be a base dimension and not otherwise referenced in the AGGMAP.

Cause: The user tried to specify a dimension in a dataflow-related clause in an aggmap which is already in another RELATION statement, DIMENSION statement, or possibly dimensioning the AGGMAP, or they specified a composite or conjoint dimension, or an object which is not a dimension

Action: Remove the conflicting reference or specify a valid object

ORA-33004: (XSAGDNGL01) workspace object is not a relationship array.

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.

ORA-33005: (XSAGDIMBREAK) invalid breakout for dimension workspace object

Cause: An invalid dimension or relation in a BREAKOUT DIMENSION statement in an AGGMAP command was specified. Either the object was not a valid relation, was not over the specified dimension, or was multidimensional.

Action: Specify a valid relation.

ORA-33006: (XSAGDNGL02) The relation workspace object is not related to itself.

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.

ORA-33007: (XSAGPVAR) workspace object may only be used as one of: an OPERATOR, ARGS, or FROMVAR variable.

ORA-33008: (XSAGDNGL03) The relation workspace object is not a relation over a base dimension of AGGMAP workspace object.

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.

ORA-33009: (XSAGDNGLPREC) In AGGMAP workspace object, PRECOMPUTE can only be specified either for the entire AGGMAP or for individual RELATION statements.

Cause: PRECOMPUTE was either specified both as a line in the AGGMAP and on at least one of the RELATION lines, or it was specified more than once as a line of the AGGMAP.

Action: Remove either the PRECOMPUTE line, or the PRECOMPUTE specification for all of the RELATION lines.

ORA-33010: (XSAGDNGL04) Relation workspace object is duplicated in the AGGMAP workspace object.

Cause: Two RELATION statements in the AGGMAP reference the same relation object.

Action: Remove the duplicate RELATION statement.

ORA-33012: (XSAGDNGL05) AGGMAP workspace object contains invalid syntax.

Cause: A line in the AGGMAP contains invalid syntax.

Action: Change the line to have valid syntax.

ORA-33014: (XSAGDNGL06) In AGGMAP workspace object, variable operator workspace object cannot be dimensioned by rollup dimension workspace object.

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.

ORA-33016: (XSAGDNGL07) In AGGMAP workspace object, workspace object is not a valid operator or variable name.

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.

ORA-33018: (XSAGDNGL08) In AGGMAP workspace object, the data type of workspace object must be TEXT, not string.

Cause: An operator variable was supplied whose data type is not TEXT.

Action: Change the operator clause to reference a TEXT variable.

ORA-33022: (XSAGDNGL10) The measure dimension workspace object must be a TEXT or ID base dimension that does not dimension AGGMAP workspace object, but is in the same analytic workspace.

Cause: A MEASUREDIM was supplied in the AGGMAP that was not acceptable.

Action: Modify the MEASUREDIM clause to specify a valid dimension.

ORA-33024: (XSAGDNGL11) AGGMAP workspace object contains duplicate information.

Cause: The aggmap contains multiple instances of a clause that can only be specified once.

Action: Remove the extra clause.

ORA-33026: (XSAGDNGL12) In AGGMAP workspace object, workspace object is not a valid valueset.

Cause: A line in the AGGMAP contains an invalid element where a valid valueset is required.

Action: Change the line to have a valid valueset.

ORA-33028: (XSAGDNGL13) In AGGMAP workspace object, workspace object should be scalar, not a dimensioned valueset.

Cause: A line in the AGGMAP contains a dimensioned valueset where a scalared valueset is required.

Action: Change the line to have a scalar valueset.

ORA-33030: (XSAGDNGL14) In AGGMAP workspace object, you can have either a single independent PROTECT statement or PROTECT statements in your RELATION statements.

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.

ORA-33032: (XSAGDNGL15) In AGGMAP workspace object, VALUESET workspace object must be in extra dimensions of the relation.

Cause: The RELATION phrase contains a VALUESET which is not over the extra dimension of the RELATION.

Action: Correct the RELATION phrase to contain a valueset over the extra dimension or not to contain any valueset.

ORA-33034: (XSAGDNGL16) In AGGMAP workspace object, VALUESET workspace object in PRECOMPUTE phrase must be in the self dimension of the relation.

Cause: The precompute phrase contains a valueset which is not over the self dimension of the relation.

Action: Correct the relation phrase to contain a valueset over the self dimension or not to contain any valueset.

ORA-33036: (XSAGDNGL17) ARGS option workspace object must be a TEXT variable.

Cause: An ARGS value had a non-text data type.

Action: Use a text variable for ARGS.

ORA-33038: (XSAGDNGL18) In AGGMAP workspace object, RELATION workspace object contains hierarchy dimensions that are also dimensions of the AGGMAP.

Cause: Hierarchy dimensions(extra dimensions) of a RELATION in the AGGMAP are base dimensions of the AGGMAP.

Action: Correct the RELATION not to have hierarchy dimensions(extra dimensions) which are also base dimensions of the AGGMAP.

ORA-33040: (XSAGDNGL19) In AGGMAP workspace object, VALUESETS workspace object and workspace object are both over the same hierarchy dimension.

Cause: Two or more different VALUESETs over the same hierarchy dimension are used in the AGGMAP.

Action: Use the same VALUESET for two RELATION phrases or use two different VALUESETs over two different hierachy dimensions.

ORA-33042: (XSAGDNGL20) In AGGMAP workspace object, VALUESET workspace object must qualify all relations dimensioned by workspace object.

Cause: A VALUESET over a hierarchy dimension qualifies some RELATIONs but not all RELATIONs dimensioned by the same hierarchy dimension.

Action: Use the same VALUESET to qualify all the RELATIONs dimensioned by the same hierarchy dimension.

ORA-33044: (XSAGDNGL21) AGGREGATE operator string requires a WEIGHTBY clause, but the ARGS clause in AGGMAP workspace object did not specify one.

Cause: The user used an operator which needs weight values but not provided the weight values.

Action: Provide weight values using a WEIGHTBY cluase.

ORA-33045: (XSAGDNGL51) The AGGREGATE operator string does not require a weight, but ARGS clause in AGGMAP workspace object specified workspace object as a weight.

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.

ORA-33046: (XSAGDNGL22) In AGGMAP workspace object, you can specify only one SCREENBY clause.

Cause: The AGGMAP contained multiple SCREENBY clauses.

Action: Remove one of the SCREENBY clauses from the AGGMAP.

ORA-33048: (XSAGDNGL23) In AGGMAP workspace object, the relation workspace object and the relation workspace object are both over the same base dimension.

Cause: The AGGMAP contains incompatible RELATION statements.

Action: Remove one of the RELATION statements from the AGGMAP.

ORA-33050: (XSAGDNGL24) AGGMAP workspace object cannot be used to aggregate workspace object, because it is defined in a different analytic workspace.

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.

ORA-33052: (XSAGDNGL25) AGGMAP workspace object is a dimensioned AGGMAP; it can only be used to aggregate like-dimensioned variables.

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.

ORA-33058: (XSAGDNGL28) In AGGMAP workspace object, error code string is greater than the maximum error code of number.

Cause: The user specified an invalid ERRORMASK value.

Action: Remove the invalid value from the ERRORMASK list.

ORA-33060: (XSAGDNGL29) In AGGMAP workspace object, the value for the ERRORLOG MAX option must be greater than 0.

Cause: The user specified an ERRORLOG MAX of 0 or a negative number.

Action: Adjust the AGGMAP so that it uses a positive number.

ORA-33062: (XSAGDNGL30) In ALLOCMAP workspace object, WEIGHTBY option workspace object must be a numerical VARIABLE or FORMULA.

Cause: The WEIGHTBY clause requires numerical VARIABLE or FORMULA but the user used invalid objects.

Action: Correct the WEIGHTBY cluase to use a valid numerical VARIABLE or FORMULA.

ORA-33064: (XSAGDNGL31) In AGGMAP workspace object, the hierarchy dimension QDR workspace object cannot refer to the related dimension of the relation.

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.

ORA-33066: (XSAGDNGL32) In AGGMAP workspace object, the hierarchy dimension QDR workspace object must be a hierarchy dimension of the relation.

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.

ORA-33068: (XSAGDNGL33) In AGGMAP workspace object, the hierarchy dimension QDR over dimension workspace object must specify a positive dimension offset.

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.

ORA-33070: (XSAGDNGL34) In AGGMAP workspace object, all QDRs of dimension workspace object must map to the same dimension position.

Cause: The user specified two conflicting hierarchy dimension qualified data references.

Action: Adjust the AGGMAP so that it uses a consistent qualified data reference.

ORA-33072: (XSAGDNGL35) In AGGMAP workspace object, the hierarchy dimension QDR over dimension workspace object must be specified for every relation dimensioned by that hierarchy dimension.

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.

ORA-33074: (XSAGDNGL36) In AGGMAP workspace object, the offset number is not a valid offset into dimension workspace object.

Cause: The hierarchy dimension offset is an invalid dimension position.

Action: Adjust the AGGMAP so that it uses valid qualified data references.

ORA-33076: (XSAGDNGL37) In AGGMAP workspace object, the value 'number' is not a valid value of dimension workspace object.

Cause: The hierarchy dimension offset is an invalid dimension position.

Action: Adjust the AGGMAP so that it uses valid qualified data references.

ORA-33078: (XSAGDNGL39) In AGGMAP workspace object, the hierarchy dimension QDR workspace object must refer to a dimension.

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.

ORA-33080: (XSAGDNGL40) In AGGMAP workspace object, you cannot reference dimension workspace object with both a RELATION statement and a DIMENSION statement.

Cause: The user included both RELATION and DIMENSION statements in the AGGMAP referring to the same AGGMAP.

Action: Remove one of the conflicting clauses.

ORA-33082: (XSAGDNGL41) In AGGMAP workspace object, the non-dimensioned valueset workspace object must have a parent QDR in its VALUESET statement over the VALUESET's base dimension.

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.

ORA-33084: (XSAGDNGL42) In AGGMAP workspace object, you cannot qualify the dimensioned valueset workspace object.

Cause: The VALUESET line referred to a dimensioned valueset.

Action: Use a non-dimensioned valueset to limit the status of the dimensioned one.

ORA-33086: (XSAGINIT01) AGGMAP workspace object cannot be dimensioned by a conjoint dimension.

Cause: The specified AGGMAP was dimensioned by a conjoint dimension.

Action: Use the CHGDFN command to change the conjoint to a composite dimension.

ORA-33088: (XSAGINIT03) You do not have read permission for AGGMAP object workspace object.

ORA-33090: (XSAGINIT05) AGGMAP workspace object requires read permission on workspace object

Cause: The AGGMAP referenced an object to which the user did not have read permission.

Action: Grant read permission on the specified object.

ORA-33092: (XSAGCOMP04) number is not the name of a MODEL in any attached analytic workspace.

Cause: An invalid model name was attached to an AGGMAP.

Action: Remove the model from the AGGMAP or create a model with that name.

ORA-33094: (XSAGGMAPLIST01) Your expression uses too much execution space. Eliminate recursion or reduce the levels of nesting.

Cause: formulas likely refer to each other recursively or with a great deal of depth.

Action: eliminate recursion and flatten formula trees.

ORA-33098: (APABBR01) A value of '%V' is not valid for the workspace object option.

Cause: An invalid value was specified for the named option.

Action: Set a valid value for the option.

ORA-33100: (APABBR02) A value of 'number' is not valid for the workspace object option.

Cause: An invalid value was specified for the named option.

Action: Set a valid value for the option.

ORA-33106: (APESCBAS01) 'string' is not a valid value for the ESCAPEBASE option. Valid values are 'd' and 'x'.

Cause: An invalid value was specified for the ESCAPEBASE option.

Action: Specify one of the valid values 'd' or 'x'.

ORA-33108: (APFTMAX01) MAXFETCH must be in the range of 1,000 to 2,147,483,647.

Cause: The value specified for the MAXFETCH option was out of range.

Action: Supply a MAXFETCH value in the range of 1,000 to 2,147,483,647.

ORA-33112: (APFTBUFF01) FETCHBUFFER must be between 1,000 and 64,512.

Cause: A value was specified for the FETCHBUFFER option that was out of range.

Action: Specify a FETCHBUFFER value between 1,000 and 64,512.

ORA-33114: (APLIKESC01) string is not a valid value for the LIKEESCAPE option because it is more than one character long.

Cause: An invalid value was specified for the LIKEESCAPE option.

Action: Specify a LIKEESCAPE value that is only one character long.

ORA-33116: (APMSTYPE00) MODSIMULTYPE must be either AITKENS or GAUSS.

Cause: An invalid value was specified for the MODSIMULTYPE option.

Action: Specify one of the valid MODSIMULTYPE values, AITKENS, or GAUSS.

ORA-33118: (APMTOLER00) Value number is out of range for MODTOLERANCE.

Cause: A value was specified for the MODTOLERANCE option that was out of range.

Action: Specify a MODTOLERANCE value between -308 and 308.

ORA-33120: (APMOVFLO00) Value number is out of range for MODOVERFLOW.

Cause: A value was specified for the MODOVERFLOW option that was out of range.

Action: Specify a MODOVERFLOW value between -308 and 308.

ORA-33122: (APMGAMMA00) MODGAMMA must be a whole number greater than or equal to zero.

Cause: An invalid value was specified for the MODGAMMA option.

Action: Specify a MODGAMMA value greater than or equal to zero.

ORA-33124: (APMITERS00) MODMAXITERS must be a whole number greater than zero.

Cause: An invalid value was specified for the MODMAXITERS option.

Action: Specify a MODMAXITERS value greater than zero.

ORA-33126: (APMDAMPF00) MODDAMP must be greater than or equal to zero and less than one.

ORA-33128: (APMERROR00) MODERROR must be either STOP, CONTINUE, or DEBUG.

Cause: An invalid value was specified for the MODERROR option.

Action: Specify a MODERROR option that is one of the valid values STOP, CONTINUE, or DEBUG.

ORA-33130: (APMERROR01) The current connection type does not support interactive debugging.

Cause: A value of DEBUG was supplied for the MODERROR option in an environment that does not support interactive debugging.

Action: Specify one of the other valid MODERROR values, STOP or CONTINUE.

ORA-33132: (APPGMGR00) The workspace object option value must be between 0 and number.

Cause: The option value specified was outside the range of valid values.

Action: Specify an option value within the valid range.

ORA-33134: (APSORTBUFSZ01) The value of SORTBUFFERSIZE must be a number between 0 and number. You supplied number.

Cause: An invalid value was specified for the SORTBUFFERSIZE option.

Action: Supply a value in the range indicated by the error message.

ORA-33136: (APSPARSX01) The value of SPARSEINDEX cannot be a multi-line string.

Cause: The value specified for the SPARSEINDEX option consisted of more than one line of text.

Action: Specify a SPARSEINDEX value containing only a single line of text.

ORA-33138: (APSPARSX02) The value 'number' is not valid for SPARSEINDEX.

Cause: An invalid value was specified for the SPARSEINDEX option.

Action: Specify a value for SPARSEINDEX that is one of BTREE, BTREE64, or HASH.

ORA-33140: (AUTOCOMP1) workspace object is being compiled automatically.

Cause: The named OLAP object needed to be recompiled because of a change in one or more of the objects to which it referred.

Action: No action is required.

ORA-33141: (XSAWFREEZE1) The analytic workspace string is already frozen.

Cause: An attempt was made to freeze an analytic workspace that was already frozen.

Action: Thaw the analytic workspace before trying to freeze it again.

ORA-33142: (BADSYN00) The format of the string command is incorrect.

Cause: There was an error in the syntax of the indicated command.

Action: Consult Oracle documentation for the correct command syntax.

ORA-33143: (XSAWFREEZE2) The analytic workspace string must be attached RW or RX.

Cause: The analytic workspace must be writable to change the freeze state.

Action: The analytic workspace must be detached and attached either RW or RX before freezing or thawing it again.

ORA-33145: (XSAWFREEZE3) Cannot rollback analytic workspace string; generations are in use.

Cause: One or more generations due to be destroyed as part of a rollback to freeze command are currently in use.

Action: Get sessions using those generations to detach the AW.

ORA-33146: (BINENG00) The width argument for binary conversion can only be specified for INTEGER and BOOLEAN data.

Cause: Only INTEGER and BOOLEAN data types have a fixed width.

Action: Omit the width argument.

ORA-33147: (XSAWFREEZE4) The analytic workspace string is not frozen.

Cause: An attempt was made to "rollback to freeze" an analytic workspace that is not frozen.

Action: Only execute this command on a frozen analytic workspace.

ORA-33148: (BINENG01) The width argument for binary conversion must be 1, 2, or 4.

ORA-33150: (BOOLTOK01) string is not a Boolean.

Cause: Valid Boolean values are yes, no, y, n, on, off, true, or false.

Action: Use a valid Boolean value.

ORA-33152: (CDELETE03) The workspace object dimension does not have a value at position number.

Cause: This physical position cannot be deleted because it does not exist.

Action: This is an internal error. Contact Oracle Support.

ORA-33154: (CFINDVAL01) The workspace object dimension does not have identifiers.

ORA-33156: (CFINDVAL02) exceeds 2**63.

Cause: This dimension is too large.

Action: Convert this application to use partitions.

ORA-33158: (CGETPOS02) The workspace object dimension does not have a value numbered number.

ORA-33160: (CGETSEQ02) The workspace object dimension does not have a value at position number.

Cause: This physical position does not exist.

Action: This may be an internal error. Contact Oracle Support.

ORA-33166: (CGFIN02) The number of periods of the string function cannot be dimensioned by time.

ORA-33168: (CGFIN03) The salvage value argument of the string function must be dimensioned by the time dimension.

ORA-33170: (CGFIN04) The decline factor argument of the string function cannot be dimensioned by the time dimension.

Cause: The decline factor argument was dimensioned by the TIME dimension.

Action: Use a scalar decline factor argument.

ORA-33172: (CGFIN05) The portion argument of the string function cannot be dimensioned by time.

ORA-33174: (CGFIN06) The switch period argument of the DEPRDECLSW function cannot be dimensioned by time.

ORA-33176: (CGMCALC01) The member list expression in aggregation phrase number is multidimensional.

Cause: The MCALC function requires a member list with one dimension.

Action: Use a list with one dimension.

ORA-33178: (CGMCALC02) workspace object appears as the dimension of more than one member list expression.

ORA-33180: (CGMCALC03) WEIGHTBY can only be specified for the AVERAGE aggregation method.

ORA-33182: (CGMCALC04) The base measure expression is not dimensioned by workspace object.

ORA-33184: (CGMCALC05) A valueset argument to MCALC must have one dimension and be a valueset of the same dimension.

Cause: The VALUESET argument to MCALC must be a self relation of a single dimension.

Action: Use a VALUESET that has one dimension that is the same as its VALUESET // dimension.

ORA-33186: (CGMODSET01) The ACROSS option is not supported in model equations.

ORA-33188: (CGMODSET02) The left-hand side of an equation involves the workspace object dimension, whereas the 'number' term on the right-hand side involves workspace object.

Cause: A dimension mismatch was detected in a model equation.

Action: Ensure that the target and source expressions of the equation refer to the same model dimension.

ORA-33190: (CGMODSET03) MODEL assignment triggered in unexpected context.

Cause: An internal error caused Oracle OLAP to attempt to compile a MODEL assignment when no MODEL was being compiled.

Action: If the problem persists, contact Oracle Support Services.

ORA-33192: (CGTCVT00) TCONVERT requires an argument dimensioned by time.

ORA-33194: (CGTCVT01) The argument to TCONVERT cannot be dimensioned by more than a single time dimension.

ORA-33196: (CGTCVT03) Invalid conversion method for TCONVERT.

ORA-33198: (CGTCVT04) The two conversion methods requested of TCONVERT are incompatible.

Cause: This is a syntax error using the TCONVERT dimension.

Action: Check Oracle documentation on Compatible Aggregation and Allocation Methods and retry.

ORA-33200: (CGTCVT05) You cannot convert by both DAY and PERIOD. You must use one or the other.

ORA-33202: (CGTCVT06) The breakout dimension workspace object is not a time dimension.

ORA-33204: (CGTCVT07) In converting data from time dimension workspace object to workspace object using TCONVERT, a conversion direction must be given.

ORA-33206: (CGTCVT08) It is not possible to convert data dimensioned by workspace object to be dimensioned by workspace object.

ORA-33208: (CGTDF00) You can only find the start or end of a time period.

ORA-33210: (CGTDF01) The argument of the BEGINDATE or ENDDATE function must be dimensioned by exactly one time dimension.

ORA-33213: (CINSERT06) The target position for MAINTAIN ADD or MAINTAIN MOVE cannot fall in the range of session-only values.

Cause: The user specified either a BEFORE or AFTER clause specifying a position in the range of SESSION dimension values.

Action: Do not use a position clause, or specify a position before the first SESSION value.

ORA-33214: (CINSERT02) The workspace object dimension is too large.

Cause: The dimension has too many values.

Action: Deleted values can still take up space in the dimension and cause this error. Try removing the deleted values by exporting the dimension to EIF and reimporting it with the REPLACE DELETE option.

ORA-33215: (CINSERT07) You cannot add session-only values to the workspace object dimension.

Cause: The user tried to add a SESSION dimension value while a spreadsheet spreadsheet cursor was open.

Action: Try adding the SESSION value while the cursor is not active.

ORA-33216: (CINSERT03) The workspace object dimension does not have a value numbered number.

ORA-33217: (CINSERT20) Custom member values cannot be added to concat dimension workspace object, or to any of its bases, because it is not defined as UNIQUE.

Cause: Only UNIQUE concat dimensions can have custom member values.

Action: Use the CHGDFN command to change the concat dimension to UNIQUE and retry.

ORA-33218: (CINSERT04) %K is not a valid value for the workspace object dimension. Values for this dimension can have at most number significant digits after rounding to number decimal places.

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 data type 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.

ORA-33219: (CINSERT05) %K cannot be added to workspace object because it is already a value of the dependent UNIQUE concat dimension workspace object, from leaf dimension workspace object.

Cause: A value cannot be added to a dimension if it conflicts with an existing value in a unique concat dimension containing this dimension.

Action: The concat(s) causing the conflict could be CHGDFNed to NOT UNIQUE, or either of the duplicate values could be renamed to make them UNIQUE.

ORA-33220: (CLOPEN01) The time dimension workspace object cannot be accessed because it consists of time periods not recognized in this release of string.

ORA-33222: (CLOPEN02) The dimension workspace object cannot be accessed because it was created by an incompatible version of string.

ORA-33223: (CMOVE03) You cannot move a session-only dimension value.

Cause: The user named a SESSION dimension value in the MAINTAIN MOVE command.

Action: Do not try to MAINTAIN MOVE session-only dimension values.

ORA-33224: (CMOVE02) The workspace object dimension does not have a value at position number.

ORA-33226: (COLDEL01) The starting column must be between 1 and the maximum width of a text value (number). You cannot start removing at column number.

ORA-33228: (COLDEL02) The columns to be removed must be between 1 and the maximum width of a text value (number). You cannot remove column number.

Cause: The column number is invalid.

Action: Choose a valid column number.

ORA-33230: (COLDEL03) The number of columns to be removed must be greater than zero. You cannot remove number columns.

ORA-33232: (COLEXTR01) The starting column must be between 1 and the maximum width of a text value (number). number is out of range.

ORA-33234: (COLEXTR02) The columns to be extracted must be between 1 and the maximum width of a text value (number). You cannot extract column number.

ORA-33236: (COLEXTR03) The number of columns to be extracted must be greater than or equal to zero. You cannot extract number columns.

ORA-33238: (COLINS01) The starting column must be between 0 and the maximum width of a text value (number). You cannot start inserting at column number.

ORA-33240: (COLREP01) The starting column must be between 1 and the maximum width of a text value (number). You cannot start replacing at column number.

ORA-33242: (COMPOSITE01) workspace object is a dimension composite and does not have position numbers that can be used in this context.

ORA-33243: (XSDPART51) workspace object is a PARTITION TEMPLATE and does not have position numbers that can be used in this context.

Cause: An attempt was made to discover or supply the position number associated with a member of a PARTITION TEMPLATE.

Action: Avoid referring to PARTITION TEMPLATE values by their position numbers.

ORA-33244: (CRENAME01) The workspace object dimension does not have a value at position number.

ORA-33246: (CRENAME02) The workspace object dimension does not have identifiers that can be renamed.

ORA-33247: (CRENAME03) %K is already a value of the dependent UNIQUE concat dimension workspace object, from leaf dimension workspace object.

Cause: A value cannot be renamed in a dimension if the new value conflicts with an existing value in a unique concat dimension containing this dimension.

Action: The concat(s) causing the conflict could be CHGDFNed to NOT UNIQUE, or either of the duplicate values could be changed to make them UNIQUE.

ORA-33248: (CTDDEL04) Deletions from time dimension workspace object must occur at either end. number values were not deleted.

ORA-33250: (CTDINSRT00) You attempted to add a value that was outside the allowable range of dates for time dimension workspace object.

ORA-33252: (CTXENG00) The CONTEXT name cannot be NA.

ORA-33254: (CTXENG01) CONTEXT 'number' already exists.

ORA-33256: (CTXENG02) CONTEXT 'number' does not exist.

ORA-33258: (CTXENG03) workspace object has not been saved in CONTEXT 'number'.

ORA-33260: (DIMSHOW01) Partition number does not exist.

Cause: The DIMSHOW command specified a nonexistent partition.

Action: Specify the name of an existing partition, or remove the PARTITION qualification from the DIMSHOW command.

ORA-33261: (DIMSHOW02) A partition name may be specified only for a partitioned variable.

Cause: A PARTITION qualification was provided for an object other than a partitioned variable.

Action: Remove the PARTITION qualification.

ORA-33262: (DBERR01) Analytic workspace string does not exist, or you do not have sufficient privileges to access it.

Cause: The analytic workspace requested does not seem to be in the current database

Action: Check that you are in the correct schema and have access to the requested AW.

ORA-33263: Could not create analytic workspace string

Cause: A serious error was encountered while trying to set up the tables for the named analytic workspace. Possible causes for this error include: - A tablespace that cannot be written to. - Corrupt metadata about which analytic workspace exist. - Table names that the code cannot use. - There are remains of a partially removed analytic workspace.

Action: There should be another error on the error stack. Consult this error to determine what is causing the problem and remove that table.

ORA-33264: (DBERR02) Analytic workspace string cannot be accessed because it has been damaged or belongs to an incompatible version of string.

ORA-33265: (DBERRBSZ) Analytic workspace string cannot be opened. Tablespace blocksize number does not match database cache size number.

Cause: The blocksize of the containing tablespace did not match the database cache size.

Action: Change either size to make them consistent, or set the OLAP_PAGE_POOL_SIZE parameter to 0 to allow automatic OLAP pool management when the compatibility is greater than 10.2.

ORA-33266: (DBERR03) Analytic workspace (AW) string cannot be accessed because it was last modified by an incompatible version of string.

Cause: The online analytical processing (OLAP) code was unable to process the internal metadata for the specified AW when attaching the AW.

Action: This is most commonly encountered when the AW was previously used on a different platform (for example, Windows 32-bit and Windows 64 bit). The AW needs to be re-created on the current platform.

ORA-33267: (DBERRRLS) Analytic workspace string cannot be accessed because it has fine-grained access control applied to it

Cause: An attempt was made to access the specified analytic workspace's LOB table. The OLAP option detected the table had fine-grained security applied to it. The OLAP option requires full access to this table to operate correctly.

Action: Remove the fine-grained access control.

ORA-33268: (DBERRTHW) Analytic workspace string cannot be attached with the THAW option because it was frozen with the NOTHAW option

Cause: An attempt to attach the AW using the thaw option was made; the AW was frozen using the NOTHAW option.

Action: Either attempt the command again without the THAW option.

ORA-33269: error while operating on 'string'

Cause: Creation of an analytic workspace for the specified object failed.

Action: This error is always signaled with another error to provide more context. Resolve the error for the named object in order for the analytic workspace creation to succeed.

ORA-33270: (DBERR05) Analytic workspace string already exists.

Cause: The AW CREATE command was passed the name of an analytic workspace that already exists

Action: Specify a different name.

ORA-33272: (DBERR06) Analytic workspace string cannot be opened.

ORA-33273: (XSCHKRLS01) Analytic workspace string has open cursors and cannot be detached.

Cause: A session attempted to detach an analytic workspace while there are cursors open against it.

Action: Close the open cursor before attempting to close the analytic workspace.

ORA-33274: (DBERR07) Timed out while trying to lock analytic workspace string for string.

Cause: A lock operation that was supposed to happen very quickly was taking too long. It can be due to another session being stopped while holding that lock, another session crashing while holding that lock, or an internal error.

Action: If another session is stopped, resume that session to let it release the lock. If another session has crashed, wait for a few minutes while a background process recovers the lock. Contact Support if none of the situations above apply.

ORA-33275: Autonomous transaction query of an UPDATEd analytic workspace is not supported

Cause: The user made attempt to reference an anayltic workspace that has uncommited updates within an autonomous query.

Action: Either COMMIT or ROLLBACK your uncommited changes, or don't use an autonomous transaction.

ORA-33276: (DBERR08) Another user has analytic workspace string attached.

ORA-33277: Analytic Workspace string.string could not be upgraded.

Cause: A serious error was encountered while trying to alter the tables for the named analytic workspace. Possible causes for this error include: - A tablespace could not be written to. - The metadata for this analytic workspace may be corrupt. * Table names that the code cannot use. * There are remains of a partially removed analytic workspace.

Action: There should be another error on the error stack. Consult this error to determine what is causing the problem and remove that table.

ORA-33278: (DBERR09) Analytic workspace string cannot be attached in RW or EXCLUSIVE mode until the changes made and updated in MULTI mode are committed or rolled back.

Cause: There are still changes to this analytic workspace that were updated and not committed when the workspace was attached in MULTI mode.

Action: Either try attaching the workspace is RO or MULTI mode or commit or roll back the transaction before trying to attach the workspace in RW or EXCLUSIVE mode.

ORA-33279: (DBERRDDP) Analytic workspace string cannot be accessed because the AWLOB column has deduplication enabled.

Cause: An attempt was made to access the specific LOB table of the analytic workspace. The OLAP option detected that the LOB column has deduplication enabled. The OLAP option does not support deduplication.

Action: Alter the table to disable LOB deduplication.

ORA-33280: (DBERR10) Analytic workspace string cannot be attached in MULTI mode until the changes made and updated in RW or EXCLUSIVE mode are committed or rolled back.

Cause: There were still changes to this analytic workspace that were updated and not committed when the workspace was attached in RW or EXCLUSIVE mode.

Action: Either try attaching the workspace in RO, RW, or EXCLUSIVE mode or commit or roll back the transaction before trying to attach the workspace in MULTI mode.

ORA-33281: Analytic workspace string cannot be modified during a Data Guard rolling upgrade.

Cause: An attempt was made to attach the specified analytic workspace for write while the instance was in the middle of a Data Guard rolling upgrade. The Oracle OLAP option does not support this.

Action: Delay the modifications until after the rolling upgrade completes.

ORA-33282: (DBERR11) cannot wait for analytic workspace string to become available since doing so would cause a deadlock.

Cause: The attempt to attach the analytic workspace using the WAIT keyword caused a deadlock situation. The WAIT keyword is not allowed. This was an error in the application.

Action: Attach the multiple analytic workspaces in the same order that they were locked to avoid deadlock if these analytic workspaces were locked at the same time.

ORA-33284: (DBERR12) Analytic workspace string cannot be opened in MULTI mode before converting it by the latest version of string.

Cause: The AW is stored in 9i format.

Action: Convert the AW to a later format

ORA-33285: This operation is not permitted on analytic workspaces.

Cause: An attempt was made to directly modify the contents of a table containing an analytic workspace.

Action: Do not modify the table directly; let the OLAP option modify it.

ORA-33286: (DBERR14) The specified access mode for analytic workspace string is invalid.

Cause: An attempt was made to change the access status for the specified analytic workspace to an invalid value.

Action: The only access modes accepted by the AW PROMOTE command are RW and RO, possibly with a WAIT or NOWAIT added.

ORA-33287: This DDL operation is not allowed on table "string"."string"

Cause: A DDL operation was attempted on an analytic workspace table.

Action: No action required. Many DDL operations on analytic workspace tables are restricted to Oracle only.

ORA-33288: (DBERR15) Another user has incompatible access to analytic workspace string, and the wait timeout has expired.

Cause: An attempt to access an analytic workspace conflicted with another user's access, and the timeout specified has elapsed.

Action: Wait until the conflicting user is done.

ORA-33289: The Flashback Table operation is not supported on OLAP analytic workspace tables.

Cause: An attempt was made to perform the Flashback Table operation on a table containing an analytic workspace, which is not allowed.

Action: Do not perform a Flashback Table operation on analytic workspace tables.

ORA-33290: (DBERR17) Analytic workspace string cannot be attached in the mode you requested because another user has it attached in an incompatible mode.

Cause: The attempt to access an analytic workspace conflicted with another user's access, and no timeout was specified

Action: Wait until the conflicting user is finished.

ORA-33291: (DBERRSYNC) Analytic workspace string cannot be attached RW until a RESYNC command has brought it up to the current generation.

Cause: Another session has updated the analytic workspace since it was attached in the current session.

Action: Use a RESYNC AW command to bring the analytic workspace up to the most recent version.

ORA-33292: An attached analytic workspace is blocking this command.

Cause: An attempt was made to drop a tablespace containing an analytic workspace that is currently attached.

Action: Detach the analytic workspace before dropping the tablespace.

ORA-33293: There are OLAP cubes and dimensions referencing an analytic workspace in the tablespace.

Cause: An attempt was made to drop a tablespace containing an analytic workspace that is referenced by OLAP cube and dimension objects.

Action: Drop the OLAP cube and dimension objects before dropping the tablespace.

ORA-33294: (DBERR19) Analytic workspace string cannot be created, deleted, or renamed while flashback mode is in effect.

ORA-33296: (DBERR21) Analytic workspace string can only be attached read-only (RO) while tablespace string is READONLY.

Cause: The underlying tablespace of the analytic workspace is in READONLY status.

Action: Attach the analytic workspace in RO mode or alter the tablespace.

ORA-33297: (DBERR22) Analytic workspace string cannot be opened because it was last modified by an incompatible version of string.

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.

ORA-33298: (AWUPG01) Analytic workspace string is already in the newest format allowed by the current compatibility setting.

Cause: You ran the DBMS_AW.CONVERT procedure on an analytic workspace that was created in or previously upgraded to the current compatibility mode.

Action: If upgrading the analytic workspace is necessary, upgrade the database instance and then re-run DBMS_AW.CONVERT. If the new features offered by upgrading the analytic workspace are not required, then no action is needed.

ORA-33300: (DBERRPLAT) Analytic workspace string encountered an error that may indicate that it was created on a different platform.

Cause: An attempt to transport an analytic workspace from a different platform failed.

Action: Transport the analytic workspace using a supported method, either by using export/import or by rebuilding it using an XML template.

ORA-33301: Unsupported ALTER TABLE operation attempted on analytic workspace table "string"."string"

Cause: An attempt was made to modify an analytic workspace table using the ALTER TABLE statement.

Action: The OLAP option can manage the table.

ORA-33303: Operation disallowed on OLAP analytic workspace table "string"."string".

Cause: An attempt was made to perform an operation on an analytic workspace table that was not allowed.

Action: Do not perform the action on the table.

ORA-33304: (DBVALID02) Note: Record number was allocated but not used. This can result in wasted space.

Cause: This is a benign message. The AW VALIDATE command found an analytic workspace has some inaccessible space.

Action: Either nothing, or export and recreate the analytic workspace

ORA-33307: Oracle OLAP analytic workspace table was renamed to an invalid name

Cause: An attempt was made to rename an Oracle OLAP analytic workspace (AW) table to a name that did not start with \"AW$\" or that contained characters that may occur only in quoted identifiers which are not supported by Oracle OLAP DML.

Action: Do not rename the Oracle OLAP AW table to an invalid name.

ORA-33310: (DECIMAL) The number of decimal places must be between number and number, or number. It cannot be number.

Cause: A value was specified for the DECIMALS option that was out of range.

Action: Supply a value for DECIMALS that is within the range specified by the error message text.

ORA-33311: The schema cannot be specified when renaming an analytic workspace.

Cause: An attempt was made to rename an analytic workspace that was not in the user's schema. This is not allowed.

Action: Connect as the owner of the analytic workspace to rename it or use DBMS_AW.AW_COPY to move it.

ORA-33312: (DELDENT01) workspace object cannot be deleted while there are objects dimensioned by it, or formulas, programs, valuesets, or relations that use it.

ORA-33313: (DELDENT05) workspace object cannot be deleted because it is the target of an external partition of a partitioned variable.

Cause: User attempted to delete a variable, but some partitioned variable was defined to use that variable as the target of one of its external partitions.

Action: DELETE the partitioned variable or CHGDFN DROP PARTITION the the external partition from the partitioned variable, then delete the target variable.

ORA-33314: (DELDENT02) workspace object cannot be deleted while it is executing.

ORA-33315: (XSDELDENTANON) You cannot delete workspace object while looping over unnamed composite workspace object.

Cause: While looping over the named anonymous composite, an attempt was made to delete an object which is dimensioned by it.

Action: Delete the object outside of a loop over the dimension.

ORA-33316: (DELDENT03) You cannot delete workspace object because you do not have PERMIT permission for it or it is readonly.

ORA-33318: (DELDENT04) The variable workspace object cannot be deleted while its NA trigger is executing.

ORA-33320: (DNAMELEN00) The object name string has more than number characters.

ORA-33324: (DOSCMD01) The current directory is string.

Cause: The user entered a CDA command with no arguments.

Action: This is an informational message. No user action is required.

ORA-33325: (DOSCMD02) Current directory alias is not set.

Cause: A file name was specified without a directory component, and there was no current directory alias set to supply the missing directory name.

Action: Use the CDA command to establish a current directory alias, or provide a file name with an explicit directory component.

ORA-33332: (DSSEXIST01) Use the AW command to establish a current analytic workspace. Then start your current activity again.

Cause: There is no currently active analytic workspace. The command that generated the error requires an active analytic workspace to operate on.

Action: Run an AW ATTACH or AW CREATE command to establish an active workspace.

ORA-33334: (DSSEXIST04) Analytic workspace string is not attached.

Cause: The specified analytic workspace was currently not attached to the session, or the name was misspelled.

Action: Attach the analytic workspace with the AW ATTACH command, or correct the spelling of the name.

ORA-33336: (DSSEXIST04A) Analytic workspace string is not attached.

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 .

ORA-33338: (DSSEXIST05) You cannot specify the EXPTEMP analytic workspace.

Cause: The command requires a permanent analytic workspace to operate on.

Action: Specify an analytic workspace other than EXPTEMP.

ORA-33339: You cannot detach analytic workspace string. It is in use by an API branch.

Cause: The OLAP API is in a branch, and you are not allowed to detach the AW while the branch is active.

Action: End the branch before detaching the AW.

ORA-33340: (DTINFRMT00) A format cannot be an empty string.

ORA-33342: (DTINFRMT01) 'number' is not a valid format for a string value because it has a single angle bracket > that is not part of a field specification.

ORA-33344: (DTINFRMT02) 'number' is not a valid format for a string value because an angle bracket (<) cannot be the last character.

Cause: The command was truncated or an angle bracket was specified as the last character which is an invalid format.

Action: Remove the last character or restore the truncated text.

ORA-33346: (DTINFRMT03) 'number' is not a valid format for a string value because 'string' is an unrecognized specification.

ORA-33348: (DTINFRMT04) number is not a valid format because the B specifier cannot be used with a date.

ORA-33350: (DTINFRMT05) 'number' is not a valid format because the 'string' specification cannot be used with a date.

Cause: The format specified in the error only applies to dimensions.

Action: Choose a format that is valid for date data.

ORA-33352: (DTINFRMT06) 'number' is not a valid format for a string value because the B specifier cannot be used with a period field.

ORA-33354: (DTINFRMT07) 'number' is not a valid format because the NAME specification can only be used once.

ORA-33356: (DTINFRMT08) 'number' is not a valid VNF format because it contains an ordinal specification.

ORA-33358: (DTINFRMT09) 'number' is an ambiguous VNF format. The 'string' specification must be followed by a space or separation character.

Cause: Space or separation character was missing.

Action: Add a space or separation character.

ORA-33360: (DTINFRMT10) 'number' is not a valid VNF format because at least two of the specifications are of the same type.

ORA-33362: (DTINFRMT11) 'number' is not a valid VNF format because it does not contain enough fields to match one of the defined VNF templates.

ORA-33364: (DTINFRMT12) 'number' is not a valid VNF format because it contains more information than is allowed.

ORA-33366: (DTINFRMT13) 'number' is not a valid format for a string value because the 'string' specification has no closing angle bracket >.

ORA-33368: (DTINFRMT14) 'number' is not a valid format for a string value because it contains more than one line of text.

ORA-33370: (DTTOVC01) Unable to print dates longer than number characters.

ORA-33372: (DUPCLCHK01) workspace object appears more than once in the dimension list.

ORA-33374: (DUPCLCHK02) workspace object appears more than once in the dimension list. (It is also a base dimension of workspace object.)

Cause: The dimension appeared once at the top level of the dimension list and also appeared somewhere further down in a conjoint or a composite.

Action: Remove either the dimension itself or the conjoint that contains it from the dimension list.

ORA-33376: (DUPCLCHK03) workspace object and workspace object cannot both appear in a dimension list because they share at least one base dimension (workspace object).

ORA-33381: (EIFEXPRT20) You cannot EXCLUDE bases from workspace object, because it is not a concat dimension.

ORA-33382: (EIFEXPRT01) You cannot export two objects with the same name (string).

ORA-33383: (EIFEXPRT21) You cannot EXCLUDE workspace object because it is not a base of workspace object.

ORA-33384: (EIFEXPRT02) You cannot rename a dimension (workspace object) when you export it.

ORA-33385: (EIFEXPRT22) You cannot EXCLUDE workspace object, because it is not a dimension.

ORA-33386: (EIFEXPRT03) The expression beginning with string has no data type.

ORA-33387: (EIFEXPRT23) EXCLUDE or EXCLUDING can only be used following the name of a concat dimension.

ORA-33388: (EIFEXPRT04) The expression beginning with string has too many dimensions.

ORA-33389: (EIFEXPRT24) Concat dimension workspace object has number bases. You cannot EXCLUDE more than number of them.

ORA-33390: (EIFEXPRT05) There are no objects to export.

ORA-33391: (EIFEXPRT25) concat dimension workspace object has only 1 base, which cannot be EXCLUDED.

ORA-33392: (EIFEXPRT07) SCATTER name workspace object must be a text variable of one dimension shared with the expression.

ORA-33393: (EIFIMPRT01) Object string exists in both the EIF file and the current analytic workspace.

Cause: An object with the given name was found in both the EIF file and the current analytic workspace.

Action: Rename the object in the analytic workspace that is causing the name conflict. If the object named in the error message belongs to a cube or a cube dimension, rename that cube or cube dimension.

ORA-33394: (EIFEXPRT08) SCATTER type workspace object must be a text variable with the same dimension as the name.

ORA-33396: (EIFEXPRT09) The SCATTER expression must have at least two dimensions and be numeric if TYPE is given.

ORA-33398: (EIFEXPRT10) The SCATTER type value must be INTEGER, SHORTINTEGER, SHORT, or DECIMAL, not number.

Cause: An attempt was made to specify a non-numeric SCATTER type value.

Action: Ensure that the SCATTER value is of type INTEGER, SHORTINTEGER, SHORT, or DECIMAL.

ORA-33400: (EIFEXPRT11) The scatter name value number is not a valid EIF object name.

ORA-33402: (EIFEXPRT12) You cannot export an unnamed dimension composite by itself, but only with an object dimensioned by it.

ORA-33404: (EIFEXPRT13) The format for exporting an expression is:\n EXPORT expression AS name

ORA-33406: (EIFEXPRT14) workspace object is not a legal name for an EIF file object.

ORA-33408: (EIFEXPRT15) You cannot use the SCATTER AS syntax because EIFVERSION is set to number, and that version cannot import scattered objects.

ORA-33409: (EIFEXPRT16) You cannot use the FULLMAPID or RELATIVEMAPID syntax because NOAPI has been specified.

Cause: An attempt was made to specify FULLMAPID or RELATIVEMAPID syntax with the NOAPI option.

Action: Either specify the API option instead of NOAPI, or remove the FULLMAPID or RELATIVEMAPID option.

ORA-33416: (EIFPATHLIST) You tried to set EIFEXTENSIONPATH to one or more illegal path names.

ORA-33420: (EIFMAKEF03) The EXPORT command has terminated because of insufficient disk space. One or more files could not be created.

ORA-33422: (EIFMAKEF04) Due to insufficient disk space, the extension count of the EIF files(s) could not be recorded. To avoid any potential errors when the file is imported, DO NOT move, delete, or rename any of the EIF extension files. These are files of the form string.string, where %3p is the extension number. There are number such files.

ORA-33424: (EIFMAKEF05) workspace object cannot be exported because EIFVERSION is set to number, and objects cannot have more than 6 dimensions in that version.

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.

Cause: The user exported an object with data type 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.

ORA-33426: (EIFMAKEF06) The expression named string cannot be exported because EIFVERSION is set to number, and objects cannot have more than 6 dimensions in that version.

ORA-33427: (EIFMAKEF16) CAUTION: NTEXT object workspace object will be exported with type TEXT.

Cause: User attempted to export an object whose data type is NTEXT, but but the EIFVERSION option indicates a version of Express / Oracle OLAP that does not support the NTEXT data type. The object will be exported as a TEXT object instead.

Action: No action needed.

ORA-33428: (EIFMAKEF07) One or more SCATTER AS expressions cannot be exported because EIFVERSION is set to number, and objects cannot have more than 6 dimensions in that version.

ORA-33429: (EIFMAKEF17) CAUTION: NTEXT expression will be exported with type TEXT.

Cause: User attempted to export an expression whose data type is NTEXT, but but the EIFVERSION option indicates a version of Express / Oracle OLAP that does not support the NTEXT data type. The expression will be exported as a TEXT object instead.

Action: No action needed.

ORA-33430: (EIFMAKEF08) workspace object cannot be exported because EIFVERSION is set to number, and that version does not use string objects.

ORA-33432: (EIFMAKEF09) You cannot use the name string, because EIFVERSION is set to number. That version does not allow object names longer than number bytes.

Cause: The object name was too long for the analytic workspace format represented by the current setting of the EIFVERSION option.

Action: Change the value of the EIFVERSION option, or remove the object from the list of objects to be exported.

ORA-33433: (EIFMAKEF09A) You cannot use the name string, because EIFVERSION is set to number. That version does not allow object names longer than number characters.

Cause: The object name was too long for the analytic workspace format represented by the current setting of the EIFVERSION option.

Action: Change the value of the EIFVERSION option, or remove the object from the list of objects to be exported.

ORA-33434: (EIFMAKEF10) You cannot export the AGGMAP object workspace object from this version of string to version 6.3. The internal format of an AGGMAP has changed too much.

ORA-33436: (EIFMAKEF11) You cannot write an EIF file using the string character set, because EIFVERSION is set to number. That version does not support that character set.

ORA-33438: (EIFSPARS00) number values of workspace object will be exported as NA, because they are not in the current status of its base dimensions.

ORA-33440: (EQUPDATE01) The expression for formula workspace object contains invalid syntax.

ORA-33442: (ESDREAD01) Discarding compiled code for workspace object because there is no NAME dimension.

ORA-33443: (ESDREAD14) Discarding compiled code for workspace object because analytic workspace string is not attached.

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

ORA-33444: (ESDREAD02) Discarding compiled code for workspace object because number could not be found.

ORA-33445: (ESDREAD15) Discarding compiled code for workspace object because workspace object and workspace object, which were not partition-dependent when the code was compiled, are now partition-dependent.

Cause: Two variables are "partition-dependent" if they share any external partition target variables, or if one is the target of an external partition of the other. If object names referred to non-partition-dependent variables at compile time but refer to partition-dependent variables in the run-time context, the OLAP DML program, formula, or model will be automatically recompiled.

Action: None needed.

ORA-33446: (ESDREAD03) Discarding compiled code for workspace object because number is now a string. It was another kind of object when the code was compiled.

ORA-33447: (ESDREAD16) Discarding compiled code for workspace object because workspace object and workspace object, which were partition-dependent when the code was compiled, are now not partition-dependent.

Cause: Two variables are "partition-dependent" if they share any external partition target variables, or if one is the target of an external partition of the other. If object names referred to partition-dependent variables at compile time but refer to non-partition-dependent variables in the run-time context, the OLAP DML program, formula, or model will be automatically recompiled.

Action: None needed.

ORA-33448: (ESDREAD04) Discarding compiled code for workspace object because number now has string data, whereas it had string data when the code was compiled.

Cause: The data type of the specified variable has changed.

Action: None

ORA-33449: (ESDREAD17) Discarding compiled code for workspace object because the partition method or partition dimension of number has changed since it was compiled.

Cause: The partitioning method (LIST, RANGE, or CONCAT) or the partition dimension of the partition template was different from what it was when the code was compiled. This required recompilation of the code.

Action: None needed.

ORA-33450: (ESDREAD05) Discarding compiled code for workspace object because number now has more or fewer dimensions than it had when the code was compiled.

Cause: The dimensionality of the specified object has changed.

Action: None needed.

ORA-33452: (ESDREAD06) Discarding compiled code for workspace object because number is now dimensioned by workspace object. It was dimensioned by workspace object when the code was compiled.

Cause: The dimensionality of the specified object has changed.

Action: None needed.

ORA-33454: (ESDREAD07) Discarding compiled code for workspace object because number is now string workspace object, whereas it was string workspace object when the code was compiled.

Cause: The specified object has changed.

Action: None needed.

ORA-33456: (ESDREAD08) Discarding compiled code for workspace object because number is a(n) string, which string did not expect to find in a compiled program.

Cause: The type of the specified object has changed.

Action: None needed.

ORA-33458: (ESDREAD09) Discarding compiled code for workspace object because number is now type string, whereas it was type string when the code was compiled.

Cause: The type of the specified object has changed.

Action: None needed.

ORA-33460: (ESDREAD10) Discarding compiled code for workspace object because object workspace object is not in analytic workspace string.

Cause: The specified object is not in the same analytic workspace it was in when the compiled object was compiled.

Action: None needed.

ORA-33462: (ESDREAD10A) Discarding compiled code for workspace object because object number is not in analytic workspace string.

Cause: The specified object was not in the same analytic workspace it was when the compiled object was compiled

Action: None needed.

ORA-33464: (ESDREAD11) Discarding compiled code for workspace object because two external objects that were different at compile time are now the same object (workspace object).

ORA-33466: (ESDREAD12) Discarding compiled code for workspace object because model dimension number is not in the same analytic workspace as solution variable number.

ORA-33468: (ESDREAD13) Discarding compiled code for workspace object because number is no longer a surrogate of dimension workspace object.

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 needed; program automatically recompiles.

ORA-33472: (EXPCHECK1) The workspace object formula cannot be edited or compiled while it is executing.

ORA-33474: (EXPCOMP01) The calculation expression in formula workspace object contains a format error.

ORA-33475: (EXPCOMP02) Invalid expression 'number'.

Cause: The expression had a syntax error.

Action: Consult the Oracle OLAP Expression syntax documentation to correct your expression syntax.

ORA-33476: (EXPORT00) Target file (string) already exists. No data is being exported.

ORA-33478: (FCFINI02) too many NA values in the input data to FORECAST

Cause: The input data provided for the FORECAST command contained too many NA values, preventing FORECAST from generating interpolated values.

Action: Reduce the number of NA values in the input data, or choose a different forecasting method.

ORA-33480: (FCFINI04) An error occurred while filling in the NA values in the input data.

Cause: A mathematical error occurred while FORECAST was attempting to fill in NA values in the input data. This may have been caused by an attempt to raise a number to a negative exponent or to take the square root of a negative number.

Action: Set the DIVIDEBYZERO and ROOTOFNEGATIVE options to TRUE and reexecute the FORECAST.

ORA-33482: (FCFINI05) Calculation of starting values and handling of NA values in the input data require at least two cycles of input data.

Cause: There were not enough values in the input data to allow for the calculation of starting values or for the filling in of NA values.

Action: Provide at least two cycles of input data.

ORA-33484: (FCFINI06) An error occurred while calculating starting values for the smooth, trend, and seasonal series.

ORA-33486: (FCFINI07) string cannot calculate starting values from this input data.

ORA-33488: (FCFINI08) The forecast input has resulted in a divide-by-zero error in the calculation of the smoothed data series.

ORA-33490: (FCFINI09) The forecast input has resulted in a divide-by-zero error in the calculation of the seasonal index series.

ORA-33492: (FCINFO00) There is no saved forecast calculation for the INFO function to retrieve.

ORA-33494: (FCREATE01) File string is already open on file unit number number.

ORA-33508: (FILEREAD01) Fileunit number is invalid. FILEREAD and FILEVIEW can only access input files opened with the FILEOPEN function.

Cause: The specified fileunit number did not refer to a file opened for input by FILEOPEN.

Action: Use the LISTFILES command to list available files, or the FILEOPEN function to open a new input file.

ORA-33510: (FILEREAD04) Unexpected EOF encountered in string while importing data.

ORA-33512: (FILESET01A) The value of the PAGESIZE option must be greater than the combined values of TMARGIN and BMARGIN.

Cause: You must leave at least one line on the page for content.

Action: Increase PAGESIZE or decrease the margins.

ORA-33514: (FILESET02) The value of the TABEXPAND option must be between 0 and 100 inclusive. You specified number.

ORA-33516: (FILESET04) You can set the string attribute only if the fileunit is used exclusively for output.

ORA-33520: (FINENG01) The number of periods specified in the string function must be greater then 0 and less than or equal to number.

ORA-33522: (FINENG02) The second argument of the string function cannot be NA while the corresponding first argument is not NA.

ORA-33524: (FINENG03) Both the first and second arguments of the string function must be nonnegative.

ORA-33526: (FINENG04) An asset value cannot be NA when the corresponding salvage value is not NA.

ORA-33528: (FINENG05) The asset value must be greater than the salvage value.

ORA-33530: (FINENG06) The first period depreciation strategy argument of the string function cannot be NA.

ORA-33532: (FINENG07) The first period depreciation strategy argument of the string function must evaluate to the word FULL or HALF.

ORA-33534: (FINENG08) The rate argument of payment or interest function cannot be NA while the corresponding principal argument is not NA.

ORA-33536: (FINENG09) Both the principal and rate arguments of the payment and interest functions must be nonnegative.

ORA-33538: (FINENG10) An internal error (number) has occurred while evaluating an interest or payment function.

ORA-33540: (FINENG11) The decline-factor argument must be greater than 0.

ORA-33542: (FISOPEN01) A file identifier cannot exceed number characters.

ORA-33546: (FNAMEQRY01) You must specify a file unit number for the string option of FILEQUERY.

ORA-33554: (FORCHECK01) The status or contents of workspace object cannot be changed while looping over it.

Cause: A program has attempted to change or limit a dimension while inside a loop over that dimension.

Action: To handle this error in your program, use the TRAP command to catch the 'FORCHECK01' error.

ORA-33555: (FORCHECK03) While looping over alias dimension workspace object, you cannot change the contents of its base workspace object.

ORA-33556: (FORCHECK51) While looping over concat dimension workspace object, you cannot change the contents of its leaves.

ORA-33557: (MAINTCHK01) You cannot string values of dimension workspace object during a loop over it.

Cause: An attempt was made to insert or delete a value of the specified dimension while some loop over that dimension was active. - The loop could be an explicit FOR or ACROSS loop, or a natural expression evaluation or OLAP_TABLE loop. - The loop could be over the dimension itself or over a derived dimension (like a composite or partition template) or dimension alias that included it. * The insert or delete could be explicitly caused by the MAINTAIN command. * An attempt to assign a value to a variable or partition dimensioned by a composite during a loop over that composite using a qualified data reference (QDR), and that the exception was generated by the engine's attempt to insert a new position in the composite to hold the new value.

Action: Move the dimension maintenance or QDR-based variable assignment outside the dimension loop.

ORA-33558: (LOCKCHECK01) The status or contents of the workspace object dimension cannot be changed while the LOCK_LANGUAGE_DIMS option is set to value.

Cause: A LIMIT or MAINTAIN was attempted on the named language dimension while the boolean option LOCK_LANGUAGE_DIMS was set to YES.

Action: SET LOCK_LANGUAGE_DIMS to NO and retry the MAINTAIN or LIMIT.

ORA-33560: (FORECAST00) The time dimension (workspace object) has no values in status. The forecast cannot be calculated.

ORA-33562: (FORECAST01) The forecast LENGTH must be an non-NA value that is greater than or equal to zero.

ORA-33564: (FORECAST02) Sum of forecast LENGTH and number of time dimension values in status equals number. The maximum is number.

ORA-33566: (FORECAST03) The values of ALPHA, BETA, and GAMMA must be greater than zero and less than or equal to one.

ORA-33568: (FORECAST04) The forecast PERIODICITY must be greater than or equal to 2.

ORA-33570: (FORECAST05) The forecast PERIODICITY must be less than or equal to the number of historical observations in the input data.

ORA-33572: (FORECAST07) In a forecast calculation, the time dimension (number) must have consecutive values in status.

ORA-33574: (FORECAST09) The forecast length extends beyond the end of the time dimension (number). Only number values will be calculated.

ORA-33576: (FORECAST10) The number of non-NA observations must be greater than 1 to calculate a TREND forecast.

ORA-33578: (FORECAST11) The number of positive observations must be greater than 1 to calculate an EXPONENTIAL forecast.

ORA-33580: (FORECAST12) The number of historical periods (number) exceeds the number of values in the current status of workspace object (number).

ORA-33582: (FORECAST13) The number of historical periods must be a non-NA value greater than zero.

ORA-33596: (FORECAST106) No forecast values can be shown since no FCNAME variable was specified to hold the results of the forecast.

ORA-33610: (FORSTEP01) Program control transferred into a FOR loop from outside the loop. This transfer is not allowed.

ORA-33612: (FPUTENG01) The file unit operand of the FILEPUT command does not have a value.

ORA-33614: (FPUTENG02) File string was opened for input only.

Cause: An attempt was made to write to a file that was opened for READ access.

Action: Close the file and then open it for WRITE or APPEND access.

ORA-33616: (FPUTENG04) The FROM file unit operand of the FILEPUT command does not have a value.

ORA-33618: (FPUTENG05) There is not sufficient room on the page to write data. Check your PAGESIZE, TMARGIN, BMARGIN and header values.

ORA-33620: (FRACRPOS01) string is not a valid field option for a record in string format.

ORA-33622: (FRAPPEND01) You cannot specify a position when appending to an INTEGER dimension.

ORA-33624: (FRASSIGN01) workspace object is a WORKSHEET. You cannot use the Data Reader to assign values to it.

ORA-33625: (FRASSIGN02) You cannot use the APPEND keyword with concat dimension workspace object.

Cause: User used the APPEND keyword on a CONCAT target in a FILEREAD, SQL FETCH or SQL SELECT command.

Action: APPENDing a value to one of the CONCATs leaves automatically appends to the CONCAT.

ORA-33626: (FRATPUSH01) string is not a valid field option for a record in string format.

ORA-33628: (FRATPUSH02) Dimension maintenance attributes can only be specified on the left side of the equal sign.

ORA-33630: (FRCBCHEK01) Invalid file unit number. Files read by FILEREAD or FILEVIEW must be input files opened via the FILEOPEN function.

ORA-33632: (FRCBCHEK02) No current record is available for file unit number.

ORA-33634: (FRCBSET01) string is not a valid value for the ORIGIN option of FILESET. Valid values are: string.

ORA-33636: (FRERROR01) number is not a valid value for string. Values for this attribute cannot be less than 1.

ORA-33638: (FRERROR02) number is not a valid value for SPACE because it results in a string value of number.

ORA-33640: (FRERROR03) There is no field of width number at column number. The current record is only number bytes long.

ORA-33642: (FRERROR04) number is not a valid width for string string data.

ORA-33644: (FRERROR05) NA is not a valid width for string string data. There is no default width for this data type.

ORA-33646: (FRERROR06) The string 'string' is not a valid string value.

ORA-33648: (FRERROR07) The current packed field contains the invalid hexadecimal digit "character".

ORA-33650: (FRERROR08) The current packed field contains the invalid sign digit "character".

ORA-33652: (FRERROR09) value is not a valid workspace object.

ORA-33654: (FRERROR10) The workspace object dimension does not have a value numbered number.

ORA-33656: (FRERROR11) The time dimension workspace object is empty. You cannot append integer positions to it unless it has at least one value.

ORA-33658: (FRFILPUT01) File string is invalid. Source files for FILEPUT must be input files opened via the FILEOPEN function.

ORA-33660: (FRFILPUT02) You cannot write from file string to file string, because the output file was not opened with the BINARY option.

ORA-33662: (FRFILPUT03) You cannot write from file string to file string, because the output file was opened with the BINARY option.

ORA-33664: (FRSPARSE01) You cannot specify a dimension list for workspace object because it is not a conjoint dimension.

ORA-33666: (FRSTRDLM01) The string expression cannot have more than one line.

ORA-33668: (FRSTRDLM02) number is not a valid value for the string expression.

ORA-33670: (FRSTRDLM03) The string and DELIMITER expressions cannot have the same value.

ORA-33672: (FRSTRDLM04) A CSV DELIMITER cannot be set to a double quote or NULL.

ORA-33674: (FTCODE00) Data block size number exceeds the maximum size of number.

ORA-33678: (GETSCAL00) The text expression specifying a DIMENSION data type cannot evaluate to NA.

ORA-33680: (GETTIMER00) first

ORA-33682: (GETTIMER01) The number parameter to string is dimensioned by more than one time dimension.

ORA-33684: (GETTIMER02) The number parameter to string must be dimensioned by a time dimension, or an explicit time dimension must be given.

Cause: If you use a DAY, WEEK, MONTH, or QUARTER dimension, the time dimension will be chosen by this command or function.

Action: If you do not use one of these dimensions, this command or function requires that you supply a time dimension.

ORA-33686: (GETTIMER03) The number parameter to string is not dimensioned by workspace object.

ORA-33688: (GETTIMER04) The dimension composite workspace object cannot be used as a time dimension.

ORA-33690: (GETXVAL01) The formula workspace object cannot be recursively evaluated because the RECURSIVE option is set to NO.

ORA-33692: (GROWENG01) GROWRATE requires a time dimension with at least two values in status.

Cause: The formula for GROWRATE returned a divide-by-zero error with a status length of zero or one.

Action: Change the time dimension status to include the first and last values for GROWRATE.

ORA-33694: (GROWENG02) The expression in the GROWRATE function must have non-NA values at the beginning and end of the given time interval.

ORA-33696: (GROWENG03) The beginning and ending values of the expression in GROWRATE must both be positive or both be negative.

ORA-33698: (GROWENG04) Cannot calculate the growrate for the values given

ORA-33700: (GROWENG05) The first value of the expression in the GROWRATE function must not be zero.

Cause: The first value provided in the GROWRATE function was invalid.

Action: The first value in the GROWRATE function must not be zero.

ORA-33704: (ILPCHECK01) workspace object is not a program.

ORA-33706: (ILPCHECK12) The workspace object program cannot be compiled because it contains structural errors.

ORA-33708: (ILPCHECK13) The workspace object program cannot be compiled while it is executing.

ORA-33712: (ILPCHECK22) The workspace object program cannot be executed because it contains structural errors.

ORA-33720: (ILPCHECK43) The workspace object program cannot be hidden or unhidden while it is executing.

ORA-33722: (ILPCOMP05) All string statements must precede the first non-declarative statement.

ORA-33724: (ILPCOMP07) The workspace object program could not be compiled because of an unrecoverable error.

Cause: The previous errors prevent the program from compiling.

Action: Fix the program and retry.

ORA-33726: (ILPENG02) workspace object cannot be used more than once in simultaneous or nested FOR statements or ACROSS commands.

ORA-33728: (ILPINIT01) You cannot initialize workspace object because it is currently running.

ORA-33730: (ILPLNK01) Discarding compiled code for workspace object because it was compiled with code version number. The current code version is number.

ORA-33732: (ILPONLY) The string function can only be used in a program.

ORA-33734: (ILPPUT01) Label string conflicts with at least one other label in workspace object. Labels must be unique for the first 8 characters.

Cause: There was a compiler error.

Action: Find the duplicate label and give it a unique name.

ORA-33736: (ILPPUT02) The workspace object program contains unmatched DO or DOEND statements.

Cause: The program has a compiler error.

Action: Fix the unmatched DO or DOEND statements.

ORA-33738: (ILPPUT03) Program workspace object either contains unmatched IF, WHILE, TEMPSTAT, FOR, or IF THEN ELSE statement, or contains duplicate labels.

Cause: There was a compiler error.

Action: Find the structural error and fix it.

ORA-33740: (ILPPUT04) On the line defining label string in the workspace object program, the text following the label is ignored.

Cause: Extra text following the label was ignored.

Action: Remove the extraneous text.

ORA-33742: (ILPPUT06) The workspace object program contains too many source lines. The limit is number lines. The program has been truncated.

Cause: A program was automatically truncated because there were too many source lines.

Action: Change the code that generates programs to handle a large number of commands with multiple programs.

ORA-33744: (ILPPUT07) Program workspace object contains text on the same line as a DO or DOEND statement.

Cause: There was a program compiler error.

Action: Remove the extraneous text.

ORA-33746: (ILPPUT08) number must be preceded by an IF clause.

Cause: There was a compiler error.

Action: Add the missing IF clause.

ORA-33748: (ILPPUT09) number must be preceded by a THEN clause.

Cause: There was a compiler error.

Action: Add the missing THEN clause.

ORA-33750: (ILPXEQ01) A referenced object can no longer be located. Execution will continue in interpreted mode.

Cause: This is a warning message that is only printed when COMPILEWARN is on.

Action: Turn off COMPILEWARN if you do not want to see this message.

ORA-33756: (ILTRK01) No data has been recorded by the TRACKPRG command.

ORA-33758: (IMPQUAF0) The EIF file string does not have any objects in it.

ORA-33760: (IMPQUAF02) \nThere are number objects in the EIF file:

ORA-33762: (XSCHGDIM01) Invalid LIMIT argument starting at string.

ORA-33766: (INFOFC00) Invalid second argument to INFO(FORECAST string).

ORA-33768: (INFOMOD00) Invalid second argument to INFO(MODEL string).

ORA-33770: (INFOPARS01) Invalid second argument to INFO(PARSE string).

ORA-33772: (INFORG00) Invalid second argument to INFO(REGRESS string).

ORA-33774: (INTERP1) string is not a command.

ORA-33776: (INTERP1A) workspace object is not a command.

ORA-33780: (INTERP3) The string command can only be used in a program.

ORA-33782: (INTERP4) The string command cannot be executed by ampersand substitution.

ORA-33784: (INTERP5) Ampersand substitution is not permitted in a string statement.

Cause: An ampersand substitution was attempted. This is not allowed in ARGUMENT or VARIABLE commands.

Action: Rewrite the program to work around this limitation.

ORA-33788: (INTTOK01) string is not composed solely of digits.

ORA-33790: (IOERROR01) I/O error on file string: string.

ORA-33792: (IOERROR02) I/O error on file string: Error text not available.

ORA-33796: (IOEXECUT00) The file identifier argument of string does not have a value.

ORA-33798: (IOEXECUT01) File string is the current OUTFILE or LOG unit, and cannot be closed with the FILECLOSE command.

ORA-33800: (IOEXECUT02A) The LENGTH argument to the FILEGET function (number) is negative.

ORA-33802: (IOEXECUT02B) File string was opened for writing.

ORA-33804: (IOEXECUT02C) File string was opened for binary input. You must use FILEREAD or FILENEXT to read data from this file.

ORA-33806: (IOEXECUT03A) The string option of FILEQUERY is not supported in this version of string.

ORA-33808: (IOEXECUT03B) You have requested a FILEQUERY option that is not supported in this version of string.

ORA-33810: (IOEXECUT04A) The string option of FILESET is not supported in this version of string.

ORA-33812: (IOEXECUT04B) The string option of a file cannot be changed by the FILESET command.

ORA-33814: (IOEXECUT04C) The value to be set for the string option cannot be NA.

ORA-33816: (IOEXECUT04D) You have requested a FILESET option that is not supported in this version of string.

ORA-33818: (IOEXECUT05) File unit number is invalid. string can access only input files opened via the FILEOPEN function.

ORA-33820: (IOEXECUT06) The file name argument to string cannot be null or blank.

ORA-33822: (IRR01) Time dimension workspace object has a range in status of number periods. The maximum range allowed by the IRR function is number periods.

ORA-33824: (ISDBUILD01) A local scalar named string already exists.

ORA-33826: (LINEDEL01) The number of the first line to remove must be between 1 and the total number of lines of the expression. number is out of range.

Cause: The line number of the expression to be removed was larger than the number of lines in the expression.

Action: Change the line number to be removed to be between 1 and the total number of lines in the expression.

ORA-33828: (LINEDEL02) You must remove at least one line. You cannot remove number lines.

ORA-33830: (LINEINS01) The line number after which inserting begins (number) is negative.

ORA-33832: (LINEREP01) The number of the first line to replace must be between 1 and the expression's total number of lines. number is out of range.

ORA-33834: (LINEXTR01) The line number of the first line to extract must be greater than 0. You cannot start extracting at line number.

ORA-33836: (LINEXTR02) You must extract at least one line. You cannot extract number lines.

ORA-33838: (LLPINIT05) You attempted to loop over the time dimension workspace object beyond the allowable range of dates.

ORA-33840: (LOOPCODE01) Multiple relations exist between workspace object and the dimensions of the expression to be aggregated. One is workspace object, and another is workspace object.

ORA-33842: (LOOPCODE02) workspace object cannot be used for aggregation. It is unrelated to the data's dimensions, or it is less aggregate than one of them.

ORA-33844: (LOOPCODE03) Time dimensions workspace object and workspace object are both dimensions of the data. Breaking out the aggregation by time is ambiguous.

ORA-33846: (LXNXTREC00) The input line was terminated by an end-of-file that occurred sooner than expected. The line might be incomplete.

ORA-33848: (LXNXTREC01) The input line was truncated to the maximum allowable size of number characters.

ORA-33852: (LXPARSE01) You provided extra input starting at 'string'.

ORA-33854: (LXTOKEN01) The statement cannot be parsed because it is too long or too complex.

ORA-33856: (LXSUBST01) string is not a valid ampersand-substitution expression.

ORA-33858: (LXSUBST02) The value of the ampersand-substitution expression is NA.

ORA-33860: (MAKEDCL01) You have no current analytic workspace. You must attach or create an analytic workspace before defining a new object.

ORA-33862: (MAKEDCL02) You must specify a data type when you define a string.

ORA-33864: (MAKEDCL03) You cannot use the data type attribute when you define a string.

Cause: This object type does not accept a user specified data type.

Action: Omit the data type.

ORA-33866: (MAKEDCL04) Your current analytic workspace does not contain an object named workspace object.

ORA-33868: (MAKEDCL05) You must specify two or more dimensions when you supply a dimension list for a WORKSHEET.

ORA-33870: (MAKEDCL06) You cannot use the string attribute when you define a string.

ORA-33872: (MAKEDCL07) The string DIMENSION must have a data type (ID, NTEXT, TEXT, NUMBER, DATETIME, TIMESTAMP, or INTEGER), a time period, or a list of bases for a conjoint dimension.

ORA-33874: (MAKEDCL08) string is not the name of a valid option.

ORA-33876: (MAKEDCL09) string must be an INTEGER dimension.

ORA-33878: (MAKEDCL10) Nested composites are not supported when compatability is 11 or greater.

ORA-33880: (MAKEDCL11) Dimensions specified for a WORKSHEET must be INTEGER dimensions.

Cause: A WORKSHEET requires two integer dimensions.

Action: Accept the default WORKSHEET dimensions WKSCOL and WKSROW, or define your own integer dimension.

ORA-33882: (MAKEDCL12) You cannot use the string attribute when you define a string of type string.

ORA-33883: (MAKEDCL36) You cannot use the string attribute when you define an EXTERNAL partition with an existing target.

Cause: User gave the TEMPORARY keyword in the definition of an external partition whose target variable was previously defined.

Action: Any storage characteristics of the external partition are determined by the target variable. These attributes should be set when the target is defined, not when the external partition is defined.

ORA-33884: (MAKEDCL13) You can specify the TEMPORARY attribute only for a variable, dimension, relation, valueset, or worksheet.

ORA-33886: (MAKEDCL14) You cannot define an object dimensioned by NAME, because it is a special reserved dimension used to organize your analytic workspace dictionary.

ORA-33888: (MAKEDCL15) You cannot use the string attribute when you define a fixed-width TEXT string.

Cause: OWNSPACE and SHAREDSPACE attributes were not supported in a version 9 analytic workspace.

Action: Upgrade to a more recent version.

ORA-33890: (MAKEDCL16) You cannot use the dimension list attribute when you define a string.

ORA-33892: (MAKEDCL17) You cannot use the string attribute when you define a scalar string.

ORA-33893: (MAKEDCL18) The TEMPORARY attribute cannot be specified for this type of dimension

ORA-33894: (MAKEDCL20) The WIDTH attribute can only be used with non-scalar TEXT and INTEGER variables, or with TEXT dimensions.

ORA-33895: (MAKEDCL19) You can specify the SHAREMAP attribute only for a multiply dimensioned variable, relation, valueset, or worksheet.

ORA-33896: (MAKEDCL21) The WIDTH attribute for TEXT data must be a number between 1 and 4000.

ORA-33898: (MAKEDCL22) The WIDTH attribute for INTEGER data must be 1.

ORA-33900: (MAKEDCL23) The NOHASH attribute is only valid for conjoint dimensions.

ORA-33902: (MAKEDCL24) The string attribute is only valid for conjoint dimensions and dimension composites.

ORA-33904: (MAKEDCL25) workspace object is a dimension composite or is dimensioned by a dimension composite. You cannot use it as the type of a string.

ORA-33908: (MAKEDCL27) You cannot use the string attribute when you define a DIMENSION ALIAS, CONCAT, or PARTITION TEMPLATE.

Cause: The specified attribute could not be applied to a DIMENSION ALIAS, CONCAT, or PARTITION TEMPLATE.

Action: Remove the attribute from the DIMENSION ALIAS, CONCAT, or PARTITION TEMPLATE definition and retry the operation.

ORA-33910: (MAKEDCL28) You cannot specify a data type when you define a DIMENSION ALIAS, CONCAT, or PARTITION TEMPLATE.

ORA-33911: (MAKEDCL29) You cannot define a string in analytic workspace string because it has not been upgraded to version string.

Cause: User attempted to define an object that requires a certain compatibility setting in an AW that has not been upgraded to that compatibility level.

Action: Make sure that the database is running in the appropriate compatibility mode, and upgrade the AW.

ORA-33912: (MAKEDCL30) An AGGMAP cannot be dimensioned by a conjoint dimension.

ORA-33914: (MAKEDCL31) You cannot define a dimension alias of another dimension alias.

ORA-33916: (MAKEDCL32) The dimension alias target workspace object is not a simple dimension.

ORA-33918: (MAKEDCL33) You cannot define a surrogate of dimension workspace object because it is a string.

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.

ORA-33920: (MAKEDCL34) The string SURROGATE must have one of the following data types: ID, NTEXT, TEXT, NUMBER, DATETIME, TIMESTAMP, or INTEGER.

Cause: The user attempted to define a surrogate without specifying a valid data type.

Action: Specify the data type (ID, NTEXT, TEXT, NUMBER, or INTEGER) in the definition of the surrogate.

ORA-33922: (MAKEDCL35) You cannot define a surrogate of dimension workspace object because it is a time dimension.

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.

ORA-33934: (MISCOPTI01) OFF

ORA-33936: (MISCOPTI04) NA

ORA-33938: (MISCOPTI05) Press Enter to continue.

ORA-33940: (MISCOPTI06) DDMTXTYY

ORA-33942: (MODCALL01) Model workspace object cannot be run because another model is already active.

ORA-33944: (MODCALL02) Model workspace object needs a solution variable; one was not provided.

ORA-33946: (MODCALL03) Model workspace object does not take a solution variable, because it has no model dimensions.

ORA-33948: (MODCALL04) A solution variable must be provided for model workspace object; however, workspace object is not a variable.

ORA-33950: (MODCALL05) The solution variable specified for the model workspace object must be numeric. Variable workspace object is type string.

ORA-33952: (MODCALL08) A solution variable must be specified for model workspace object; however, workspace object has no dimensions.

ORA-33954: (MODCALL09) Solution variable workspace object is not dimensioned by workspace object, which is a dimension of model workspace object.

ORA-33956: (MODCALL10) The execution of model workspace object cannot be completed due to an internal error (TYPE = number).

ORA-33958: (MODCALL11) The syntax for invoking a model is:\n model-name [solution-variable] [NOWARN]

ORA-33960: (MODCALL14) Model workspace object contains simultaneous equations.

ORA-33962: (MODCALL15) Model workspace object failed to converge after number iterations in block number.

ORA-33964: (MODCALL16) Model workspace object diverged during iteration number in block number while executing statement number of model workspace object.

ORA-33966: (MODCALL17) The solution variable workspace object is referenced as a variable in model workspace object.

ORA-33968: (MODCALL18) Solution variable workspace object is dimensioned by workspace object, which is not a dimension of model workspace object but is a dimension of a model execution block.

ORA-33970: (MODCALL19) Solution variable workspace object is not dimensioned by workspace object, but model workspace object contains dimension-based equations that reference its values.

ORA-33972: (MODCHECK01) workspace object is not a model.

ORA-33973: (MODCHECK02) The workspace object model cannot be compiled while it is executing.

ORA-33974: (MODCHECK12) The workspace object model cannot be compiled because it contains structural errors.

ORA-33975: (MODCHECK13) The workspace object model cannot be hidden or unhidden while it is executing.

ORA-33976: (MODCHECK22) The workspace object model cannot be executed because it contains structural errors.

ORA-33978: (MODCOMP01) workspace object has already been named in a DIMENSION statement in this model.

ORA-33980: (MODCOMP02) DIMENSION statements are not allowed after an equation has appeared.

ORA-33982: (MODCOMP03) DIMENSION statements are not allowed after an INCLUDE statement has appeared.

ORA-33983: (MODCOMP15) The DIMENSION statement must list the dimensions of any included models.

ORA-33984: (MODCOMP04) INCLUDE statements are not allowed after an equation has appeared.

ORA-33986: (MODCOMP05) Only one INCLUDE statement is allowed in a model.

ORA-33988: (MODCOMP06) An INCLUDE statement must refer to another model; workspace object is not a model.

ORA-33990: (MODCOMP08) Models cannot be included recursively; workspace object has already been included.

ORA-33992: (MODCOMP09) The format of the DIMENSION command is:\n DIMENSION dimension1 [dimension2...]

ORA-33994: (MODCOMP10) The format of the INCLUDE command is:\n INCLUDE model

ORA-33996: (MODCOMP11) workspace object is not named in a DIMENSION statement in this model.

ORA-33998: (MODCOMP12) You cannot use both workspace object and workspace object as model dimensions, because workspace object is a surrogate of workspace object.

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.

ORA-34000: (MODCOMP13) You cannot use both workspace object and workspace object as model dimensions, because they are both surrogates of dimension workspace object.

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.

ORA-34001: (MODCOMP14) Concat leaf dimension workspace object already is used in a DIMENSION statement, either explicitly or as a leaf of another concat dimension.

Cause: Either two concat dimensions which share a common leaf dimension, or a concat and one of its leaves where both specified in the DIMENSION statement(s).

Action: Do not specify overlapping concat dimensions, or any leaves of specified concat dimensions.

ORA-34004: (MODGRAPH01) The model workspace object cannot be compiled due to internal error number. Contact Oracle OLAP Technical support.

ORA-34006: (MODINFO00) There is no saved model information for the INFO function to retrieve.

ORA-34008: (MODINFO01) Model workspace object has not been compiled; the information requested is available only after compilation.

ORA-34010: (MODINFO02) Model workspace object has not been executed; the information requested is available only after execution.

ORA-34012: (MODPUT06) The workspace object model contains too many source lines. The limit is number lines. The model has been truncated.

ORA-34014: (MONITOR01) No data has been recorded by the MONITOR command.

ORA-34016: (MONITOR02) No program name has been supplied for the MONITOR command.

ORA-34018: (MSCGADD01) workspace object is an INTEGER dimension. Specify only the number of values to be added, not the specific values themselves.

ORA-34019: (MSCGADD03) workspace object is not a LIST PARTITION TEMPLATE.

Cause: User attempted to MAINTAINT ADD or DELETE a list value from a RANGE or CONCAT partition template.

Action: Partitioning in a RANGE or CONCAT partition template cannot be changed using the MAINTAIN command.

ORA-34020: (MSCGADD02) workspace object is not a time dimension. You cannot add time periods to it.

ORA-34021: (MSCGADD04) You must specify a partition when maintaining PARTITION TEMPLATE workspace object.

Cause: User attempted to MAINTAINT ADD or DELETE a list value from a LIST partition template, but didn't specify which partition to add to or delete from.

Action: Specify the partition: maintain (template) add to partition (partitionname) (values) or maintain (template) delete from partition (partitionname) (values)

ORA-34022: (MSCGDEL02) You can only delete time periods from a time dimension.

ORA-34024: (MSCGMRG01) The RELATE keyword cannot be specified when the MERGE expression has no dimensions.

Cause: The MERGE expression did not contain dimensions.

Action: Specify a valid MERGE expression or refer to Oracle Database documentation for the correct syntax. Dimensions are required in the MERGE expression when using the RELATE keyword.

ORA-34026: (MSCGMRG02) workspace object is not a relationship between workspace object and the dimensions of the source expression.

ORA-34028: (MSCGMRG03) workspace object, the value of the RELATE relation, is not one of the dimensions of the source expression.

ORA-34030: (MSCGPOS00) workspace object is a time dimension. You can add values to it only FIRST or LAST.

Cause: There are no gaps in time dimensions. New periods must be added to the beginning or the end.

Action: The only acceptable syntax is n PERIODS FIRST or n PERIODS LAST.

ORA-34031: (MSCGPOS02) Position keywords may not be specified when adding values to DATETIME dimension workspace object.

Cause: The position of DATETIME dimension values is automatically maintained. Dimension values are automatically maintained in a sorted order.

Action: Do not specify BEFORE, AFTER, FIRST or LAST for DATETIME dimension values.

ORA-34032: (MSCGPOS01) Position keywords may not be specified when adding values to dimension composite workspace object.

Cause: You cannot specify a position when adding values to it. You cannot specify a position for new composite dimension values.

Action: Do not use FIRST, LAST, BEFORE, or AFTER.

ORA-34034: (MSEXECUT00B) value is already a value of workspace object.

ORA-34036: (MSEXECUT00C) number is already a value of workspace object.

ORA-34038: (MSEXECUT01) The expression for the position to add, merge, or delete is NA.

Cause: The position argument was NA.

Action: Use a correct position argument.

ORA-34039: (TRGPRG02) workspace object cannot be deleted while its trigger is executing.

ORA-34040: (TRGSET01) The TRIGGERASSIGN command can only be used in an ASSIGN TRIGGER.

ORA-34041: (TRGPRG01) A TRIGGER cannot be called recursively for the same object and event.

ORA-34042: (MSEXECUT03A) The expression for the position to be renamed is NA.

ORA-34044: (MSEXECUT03B) The expression for the new dimension value is NA.

ORA-34046: (MSEXECUT03C) value is already a value of workspace object.

Cause: An attempt to rename a dimension value failed because the new value already exists.

Action: Rename the dimension member to a unique value.

ORA-34048: (MSEXECUT04) Time dimension workspace object is empty. You must give it a value before you can add periods to its beginning or end.

ORA-34050: (MSEXECUT05) The expression for the argument to BEFORE or AFTER is NA.

ORA-34052: (MSEXECUT06) All dimension values must be single line values.

ORA-34054: (MSEXECUT07) number is already a value of workspace object.

ORA-34056: (MSEXECUT08) The number of periods to add cannot be negative, zero, or NA.

ORA-34058: (MSEXECUT09) The number of periods to delete cannot be negative, zero, or NA.

Cause: The number of periods was not valid.

Action: Use a positive integer for the number of periods.

ORA-34059: (MSEXECUT12) You cannot delete non session-only dimension values from unique concat dimension workspace object.

Cause: The user tried to apply MAINTAIN DELETE to a non-SESSION value.

Action: Only use MAINTAIN DELETE to remove SESSION values from a concat dimension.

ORA-34060: (MSEXECUT10) You do not have permission to maintain workspace object.

ORA-34061: (MSEXECUT11) Session-only values cannot be added to non-unique concat dimension workspace object, or any of its base dimensions.

Cause: Only UNIQUE concat dimensions can have custom member values.

Action: Use the CHGDFN command to change the concat dimension to UNIQUE and retry.

ORA-34062: (MXARGS01) = Args:

ORA-34066: (MXARGS03) values of

ORA-34068: (MXBREAK01) The BREAK statement can only be used within a FOR or WHILE loop or within a SWITCH statement.

ORA-34070: (MXBREAK02) The CONTINUE statement can only be used within a FOR or WHILE loop.

ORA-34072: (MXCALL01) workspace object is not a PROGRAM.

ORA-34074: (MXCGAF01) The string function cannot be used with string data.

ORA-34076: (MXCGAF02) workspace object is neither a dimension nor the name of a relationship array.

ORA-34078: (MXCGAF03) The dimension workspace object appears more than once as an argument to string.

ORA-34082: (MXCGAF05) Specify the STATUS keyword only if at least one of the breakout dimensions is not a dimension of the expression argument.

ORA-34084: (MXCGAF06) You cannot specify workspace object as a breakout dimension because it is a dimension composite.

ORA-34086: (MXCGAF07) You can only specify a qualified data reference to a breakout relation object. workspace object is not a relation.

ORA-34088: (MXCGCE04) The THEN and ELSE expressions must evaluate to values of the same dimension.

ORA-34090: (MXCGCHRL01) The expression argument to string is not dimensioned by workspace object.

ORA-34092: (MXCGCON01) The use of a hexadecimal value (string) is not supported.

ORA-34094: (MXCGCUM00) In the CUMSUM function, the relation (workspace object) must refer to the accumulation dimension (workspace object).

ORA-34096: (MXCGCUM01) The reset parameter 'workspace object' is neither a RELATION nor a DIMENSION.

Cause: The reset parameter was not valid.

Action: Find or define a valid reset parameter.

ORA-34098: (MXCGCUM02) The STATUS keyword has no effect unless the first argument has more than one dimension.

ORA-34100: (MXCGCVT01) Values of type string are expected.

ORA-34102: (MXCGFIOF01) The string option of FILEQUERY is not supported in this version of string.

ORA-34104: (MXCGGET01) workspace object is not a type of object that contains data values.

ORA-34106: (MXCGGET03) FILEREAD attributes can be specified only in the context of a FILEREAD or FILEVIEW command.

ORA-34108: (MXCGGET04) FILEREAD attributes cannot be specified for the NAME dimension.

Cause: An attempt was made to use the GET function to read NAME dimension values in a FILEREAD or FILEVIEW command.

Action: If you need this list of names read them into a text variable.

ORA-34110: (MXCGGET05) FILEREAD attributes cannot be specified for a constant.

ORA-34112: (MXCGGT01) Values of type string cannot be read with the MANY option.

ORA-34114: (MXCGGT02) The RAW attribute applies only to TEXT.

ORA-34116: (MXCGHCVT00) To convert TEXT to date use:\n CONVERT(expression DATE [dateorder])

ORA-34118: (MXCGHCVT01) To convert date to TEXT or ID use:\n CONVERT(expression {ID|TEXT} [dateformat])

ORA-34120: (MXCGHCVT02) To convert time dimension periods to TEXT or ID use:\n CONVERT(expression {ID|TEXT} [vnf-format])

ORA-34124: (MXCGHCVT04) CONVERT(expression string\nTo [format])

ORA-34126: (MXCGKEY01) The first argument to the KEY function must be an expression yielding a dimension value.

Cause: The First argument is not a dimension value.

Action: Specify the name of a dimension or a relation.

ORA-34128: (MXCGKEY02) You cannot apply the KEY function to workspace object because it is not a conjoint dimension or composite.

Cause: The first argument must be a conjoint or composite dimension.

Action: The KEY function cannot be used with this dimension.

ORA-34130: (MXCGKEY03) workspace object is not a component of conjoint dimension workspace object.

Cause: The second argument must be a base dimension of the first.

Action: Choose a valid base dimension.

ORA-34132: (MXCGKEY04) workspace object is not a component of composite workspace object.

Cause: The second argument must be a base dimension of the first.

Action: Choose a valid base dimension.

ORA-34134: (MXCGLA01) You are trying to perform an invalid operation. Dates cannot be exponentiated.

ORA-34136: (MXCGMOVE00) The first argument to the string function is not dimensioned by workspace object.

Cause: The expression argument was not dimensioned by the dimension argument.

Action: Specify one of the expression's dimensions.

ORA-34138: (MXCGNPV03) The interest rate expression in the NPV function cannot be dimensioned by workspace object.

ORA-34140: (MXCGPFC01) Argument number number in the call to workspace object is not a simple expression.

ORA-34141: (MXCGPUT00) You cannot use the ASSIGN keyword with DIMENSION workspace object.

Cause: User used the ASSIGN keyword on a DIMENSION target in a FILEREAD, SQL FETCH or SQL SELECT command.

Action: To create a new dimension value in a FILEREAD, SQL FETCH or SQL SELECT command, use the APPEND keyword.

ORA-34142: (MXCGPUT01) You cannot assign values to a string.

ORA-34143: (MXCGPUT02) You cannot assign values to SURROGATE workspace object because it is type INTEGER.

Cause: The user attempted to assign a value to a dimension surrogate whose data type 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.

ORA-34144: (MXCGPUT04) A model cannot assign values to a string.

ORA-34145: (MXCGPUT03) You cannot use the APPEND keyword with SURROGATE workspace object.

Cause: User used the APPEND keyword on a SURROGATE target in a FILEREAD, SQL FETCH or SQL SELECT command.

Action: To assign a value to a SURROGATE in a FILEREAD, SQL FETCH or SQL SELECT command, use the ASSIGN keyword.

ORA-34146: (MXCGQDR01) A qualified data reference (QDR) has this format:\n name(dimension1 dimvalue1 [dimension2 dimvalue2...])

ORA-34148: (MXCGQDR02) workspace object cannot be used as a qualifier because it is a COMPOSITE or PARTITION TEMPLATE. You can use its component dimensions instead.

ORA-34150: (MXCGQDR05) A dimension can be named only once in a qualified data reference. workspace object has been named more than once.

ORA-34152: (MXCGQDR06) The dimensions named in a qualified data reference must be dimensions of the qualified object. workspace object is not dimensioned by workspace object.

ORA-34154: (MXCGQDR10) workspace object has no dimensions, so it cannot have a qualified data reference.

ORA-34156: (MXCGRA00) You cannot compare time periods of different lengths or phases.

ORA-34158: (MXCGRA01) cannot subtract time periods of different lengths or phases

Cause: The expression contained two incompatible time periods.

Action: Specify time periods with the same length and phase.

ORA-34160: (MXCGRA02) The format of the IN operator is\n date IN time dimension value.

ORA-34162: (MXCGRAVL01) The expression to be unraveled is not dimensioned by workspace object.

ORA-34164: (MXCGVAR01) A dimension used to define a local string variable cannot be located. Execution cannot continue.

Cause: A local relation or valueset has become invalid, most probably because an object used by the currently executing program has been deleted.

Action: This is an internal error that should be referred to Oracle technical support.

ORA-34168: (MXCGVFC01) Invalid context for the VALUE function.

ORA-34170: (MXCGVFC02) Data Reader attributes apply to the VALUE function only when it is used in a FILEREAD or FILEVIEW command.

ORA-34172: (MXCGWKDT01) The argument to the WKSDATA function must be the name of a WORKSHEET.

ORA-34176: (MXCHGDCL01) workspace object is not the kind of object whose index type can be changed.

ORA-34177: (MXCHGDCL19) number cannot be deleted because one or more partitioned variables instantiate it.

Cause: User attempted to CHGDFN DELETE a partition template, but some partitioned variable had data in the partition specified for deletion.

Action: Drop the partitions that are causing the problem, then retry.

ORA-34178: (MXCHGDCL02) workspace object cannot be changed to NOHASH. Only an object that was originally defined as NOHASH can be changed back to NOHASH.

ORA-34179: (MXCHGDCL20) workspace object is not a PARTITION TEMPLATE.

Cause: User specified an object that is not a partition template where a partition template is required.

Action: Supply the name of a partition template.

ORA-34180: (MXCHGDCL03) workspace object is not a conjoint dimension and cannot be changed in this manner.

ORA-34181: (MXCHGDCL21) workspace object is not a partitioned VARIABLE.

Cause: User specified an object that is not a partitioned variable in a place where a partitioned variable is required.

Action: Supply the name of a partitioned variable.

ORA-34182: (MXCHGDCL04) SEGWIDTH not changed from "string\nwrong"

Cause: SEGWIDTH requires one value for each dimension.

Action: Include values for each dimension of the specified object.

ORA-34183: (MXCHGDCL22) Partition number already exists.

Cause: User attempted to ADD a partition that already existed to a partitioned variable.

Action: None required - the partition already exists.

ORA-34184: (MXCHGDCL05) string is not a valid segment width.

ORA-34185: (MXCHGDCL23) Only dimension composites can have optional inversions. workspace object is not a dimension composite.

ORA-34186: (MXCHGDCL06) You cannot change workspace object to a dimension composite, because it is used as the type of a PROGRAM, RELATION or VALUESET.

ORA-34188: (MXCHGDCL07) Only conjoint dimensions can be redefined as composites. workspace object is not a conjoint dimension.

ORA-34190: (MXCHGDCL08) You cannot convert the conjoint dimension workspace object to a composite because it has the NOHASH attribute.

ORA-34192: (MXCHGDCL09) workspace object is a dimension composite and its definition cannot be changed to NOHASH.

ORA-34194: (MXCHGDCL10) You cannot change workspace object to a composite while there are permissions applied to it.

Cause: Permissions for composites must be applied through its base dimensions.

Action: Remove the permissions, change the dimension to a composite, and then apply permissions to the base dimensions.

ORA-34196: (MXCHGDCL11) Only dimension composites can be redefined as DIMENSIONs. workspace object is not a dimension composite.

ORA-34198: (MXCHGDCL12) You cannot change workspace object to a composite because its dimension list has one or more duplications.

ORA-34200: (MXCHGDCL13) You cannot change workspace object to a dimension composite because there are one or more formulas dimensioned by it.

ORA-34202: (MXCHGDCL14) workspace object is not a time dimension.

ORA-34204: (MXCHGDCL15) workspace object is not the kind of object to which SEGWIDTH can be applied.

ORA-34206: (MXCHGDCL16) You cannot change workspace object to a dimension composite because there are one or more relations dimensioned by it.

Cause: Relations can be dimensioned by conjoint dimensions, but not by composite dimensions.

Action: Do not change the dimension.

ORA-34208: (MXCHGDCL17) You cannot change workspace object to a dimension composite because it is used in one or more concat dimensions.

Cause: The specified dimension was used as a base in a concat dimension.

Action: Delete the concat dimension.

ORA-34210: (MXCHGDCL18) You cannot change workspace object to a dimension composite because one or more surrogates has been defined for it.

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.

ORA-34212: (MXCLASS01) An expression was specified where a DIMENSION or a VALUESET was expected.

ORA-34214: (MXCLASS02) workspace object is not a dimension.

ORA-34216: (MXCOMP001) workspace object cannot be compiled because it is not a PROGRAM, MODEL, AGGMAP, or FORMULA.

ORA-34218: (MXCTX01) workspace object cannot be in a CONTEXT because it is not a scalar variable.

ORA-34220: (MXCTX02) workspace object cannot be in a CONTEXT because it is not data.

ORA-34222: (MXCTX03) workspace object cannot be in a CONTEXT because it is a dimension composite.

ORA-34224: (MXDCL01) Analytic workspace string is not attached.

ORA-34226: (MXDCL02) REUSE can only be specified for SIMPLE, COMPOSITE, and CONJOINT dimensions.

ORA-34228: (MXDCL03) Only dimensions can have time periods.

Cause: 'day week month quarter year' syntax is only for dimensions.

Action: Use the dimension keyword before this syntax.

ORA-34230: (MXDCL04) You provided an invalid time period.

ORA-34232: (MXDCL05) A DAY dimension cannot be phased with a BEGINNING or ENDING phrase.

ORA-34234: (MXDCL06) The beginning date translates to an invalid end date.

Cause: The end date may not exceed year 9999.

Action: Fix the begin date.

ORA-34236: (MXDCL07) REUSE cannot be specified in AWs that have not been upgraded to version 12.

ORA-34238: (MXDCL08) A dimension cannot have a data type of DATE.

ORA-34240: (MXDCL09) You cannot specify EXPTEMP as an analytic workspace.

ORA-34242: (MXDCL10) You cannot specify an analytic workspace in this command.

ORA-34243: (MXDCL11) You can only use the string keyword when defining a COMPOSITE.

Cause: User supplied the COMPRESSED keyword when defining an object that was not a COMPOSITE.

Action: If the intent is to create a compressed composite, make sure that the object type is COMPOSITE. Otherwise, remove the COMPRESSED keyword from the command string and rerun.

ORA-34246: (MXDCL18) You cannot define an object with a recursive SPARSE dimension list.

Cause: A SPARSE dimension was specified that included a SPARSE dimension as one of its base dimensions.

Action: Define the sparse dimension using the base dimensions of the nested SPARSE dimensions rather than using the existing SPARSE dimension.

ORA-34248: (MXDCL19) You cannot specify a dimension list for the workspace object dimension.

ORA-34250: (MXDCL20) The workspace object dimension is in the wrong analytic workspace to be used in this DEFINE command.

ORA-34252: (MXDCL21) You have specified the wrong number of dimensions for workspace object.

ORA-34254: (MXDCL22) workspace object does not belong in the dimension list for composite workspace object, or it is in the wrong position.

ORA-34256: (MXDCL23) You must specify a dimension list for string workspace object when using it in a definition.

ORA-34258: (MXDCL24) Dimension composite number does not exist.

ORA-34260: (MXDCL25) You cannot use number to dimension a string because it is, or involves, a dimension composite. Use the composite's bases instead.

Cause: The user attempted to use a COMPOSITE in the dimension list of an object that does not allow for such dimensions.

Action: Use the base dimensions of the COMPOSITE in the dimension list.

ORA-34262: (MXDCL26) The object name string!string can only be defined in analytic workspace string, not in the EXPRESS analytic workspace.

ORA-34264: (MXDCL27) The object name string!string can only be defined in analytic workspace string, not in analytic workspace string.

ORA-34268: (MXDCL29) string objects must be type DIMENSION.

ORA-34270: (MXDCL30) You cannot specify a data type when defining a dimension alias.

ORA-34272: (MXDCL31) You cannot specify a dimension list when defining a dimension string.

ORA-34274: (MXDCL32) You cannot specify a width when defining a dimension alias.

ORA-34276: (MXDCL33) (Precision, Scale) arguments can only be used with a NUMBER variable or dimension.

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 data type is not allowed at all.

Action: Use the NUMBER type without specifying a precision or scale. If a NUMBER data type is not allowed at all, this fix will only change the exception message to something more specific.

ORA-34279: (MXDCL37) CONCAT can only be used when defining a DIMENSION.

Cause: The CONCAT keyword was used incorrectly.

Action: Retry the command without the CONCAT keyword.

ORA-34280: (MXDCL38) PARTITION BY can only be used when defining a PARTITION TEMPLATE.

ORA-34281: (MXDCL39) A (precision code) argument can only be used with DATETIME or TIMESTAMP dimensions.

ORA-34284: (MXDCL52) A SPARSE dimension cannot be specified in this context.

ORA-34286: (MXDCL53) workspace object cannot be used in this context because it is a string.

Cause: User specified a dimension composite, conjoint, or partition template in a place where that kind of dimension is not allowed. For instance, a relation cannot be dimensioned by a composite, and only a variable can dimensioned by a partition template.

Action: Usually, the offending dimension can be replaced with its bases. For instance, a relation cannot be dimensioned by a a composite of PRODUCT and GEOG, but it can be dimensioned by both PRODUCT and GEOG instead.

ORA-34298: (MXDCLEQ01) workspace object was not defined as a formula, so you cannot use the EQ command to give it a value.

ORA-34300: (MXDCLEQ02) workspace object is not a time dimension, so you cannot define a VNF formatting string for it.

ORA-34302: (MXDCLEQ03) workspace object is not a DATETIME or TIMESTAMP dimension, formula, program, or variable, so you cannot define a DATE_FORMAT formatting string for it.

ORA-34304: (MXDCLILP01) There is no current program definition. Define a program or use the CONSIDER command before using the PROGRAM command.

ORA-34306: (MXDCLILP02) workspace object was not defined as a program.

Cause: An attempt was made to use the PROGRAM command on an object that was not defined as a program. The PROGRAM command only works for objects defined as programs.

Action: Specify the name of a valid program with the PROGRAM command.

ORA-34308: (MXDCLILP03) Since you have no current program definition, your PROGRAM entries will be discarded. Type END to return to command level.

ORA-34310: (MXDCLILP04) The workspace object program cannot be redefined while it is executing.

ORA-34312: (MXDCLMOD01) There is no current model definition. Define a model or use the CONSIDER command before using the MODEL command.

ORA-34314: (MXDCLMOD02) workspace object was not defined as a model.

ORA-34316: (MXDCLMOD03) Since there is no current model definition, the MODEL statements will be discarded. Type END to return to the command line.

ORA-34318: (MXDCLAGR01) There is no current aggmap definition. Define an aggmap or use the CONSIDER command before using the AGGMAP command.

ORA-34320: (MXDELETE00) The object workspace object is not in the string analytic workspace.

ORA-34324: (MXFETCH01) The ACROSS and DOWN keywords cannot be set to NONE at the same time.

ORA-34336: (MXGO00) The string keyword can only be used for a model.

ORA-34338: (MXDIMEN01) An object cannot have more than number dimensions.

ORA-34340: (MXDINSRT01) An object named number already exists in analytic workspace string.

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.

Cause: This is an informational message that reminds you that you may not save changes to the specified analytic workspace.

Action: None, unless it was desired to save changes to the analytic workspace. In that case, detach and reattach the analytic workspace read-write.

ORA-34344: (MXDSS03) Analytic workspace string is not attached.

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.

ORA-34346: (MXDSS04) The string analytic workspace cannot be detached.

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.

ORA-34348: (MXDSS05) string is used only for internal purposes and cannot be accessed as an analytic workspace.

Cause: The command attempted to operate on an internal analytic workspace used by the system.

Action: Specify a different analytic workspace.

ORA-34350: (MXDSS06) string is an open analytic workspace.

Cause: The specified analytic workspace was in use.

Action: The AW DELETE, AW RENAME, AW TRUNCATE, and AW CREATE commands require an analytic workspace that is not currently in use.

ORA-34356: (MXDSS09) Analytic workspace string is attached in read-only mode, therefore you cannot change its string.

Cause: The analytic workspace was attached in read-only mode because of which it could not be changed.

Action: Detach the analytic workspace and then re-attach it to enable the read/write mode.

ORA-34357: (MXDSS10) string is not an alias of analytic workspace string.

Cause: User attempted to use AW UNALIAS on a nonexistent alias.

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

ORA-34358: (MXDSS14) number other users reading

Cause: Used for AW LIST output formatting when %d > 1

Action: None

ORA-34359: (MXDSS11) string appears twice in the alias list.

Cause: The user included the same name twice in the alias list of an AW ALIAS or AW UNALIAS command.

Action: Remove the duplicate name, and retry the operation.

ORA-34360: (MXDSS15) number other users writing

Cause: Used for AW LIST output formatting when %d > 1

Action: None

ORA-34362: (MXDSS16) Program number does not exist.

Cause: The specified program name could not be found.

Action: Change the name to a program that exists.

ORA-34364: (MXDSS17) The read/write status of analytic workspace string has not been changed. To change it, detach and re-attach the analytic workspace.

ORA-34370: (MXDSS21) Permission to attach analytic workspace string denied by a PERMIT program.

Cause: Access to the analytic workspace was denied by the Analytic Workplace's (AW) PERMIT_READ program (when the AW was attaching for read) or PERMIT_WRITE program (when the AW was attaching for write).

Action: The owner of the analytic workspace must adjust the appropriate PERMIT program to allow access.

ORA-34371: (MXDSS22) Schema name "string" contains characters that are not allowed in an analytic workspace name.

Cause: The specified or default schema name contained characters that can occur only in quoted identifiers, which are not supported in OLAP DML.

Action: Specify a schema name containing only characters that can appear in a nonquoted identifer.

ORA-34372: (MXDSS26) An analytic workspace named string is already attached.

Cause: The attempt to attach the named analytic workspace failed because there was already an analyitc workspace with that name attached.

Action: Only one analytic workspace of a given name may be attached at a time. The currently attached analytic workspace must be detached before you can attach the new analytic workspace.

ORA-34373: schema name contains unsupported characters

Cause: The specified or default schema name, contained characters that can occur only in quoted identifiers, which are not supported in OLAP DML.

Action: Specify a schema name containing only characters that can appear in a nonquoted identifier.

ORA-34376: (MXDSS28) string is not a valid analytic workspace name. Analytic workspace names must be number characters or less, can contain only letters, digits, underscores, and dollar signs, and cannot begin with a digit or dollar sign.

Cause: The specified analytic workspace or ALIAS name was too long or contained invalid characters.

Action: Ensure that the analytic workspace name meets the specified criteria.

ORA-34378: (MXDSS29) string is a reserved word and cannot be used as an analytic workspace name.

Cause: An attempt was made to create an analytic workspace using a reserved word.

Action: Choose a different name for the analytic workspace.

ORA-34380: (MXEXPORT00) You can only export one worksheet to a spreadsheet file.

ORA-34382: (MXEXPORT01) Worksheets are the only objects you can export to spreadsheet files. workspace object is not a worksheet.

ORA-34384: (MXFILEIO01) The string option of FILESET is not supported.

ORA-34386: (MXFILEIO02) No more than 9 arguments can be supplied to FILESET.

ORA-34388: (MXFILERD01) The format of the FILEREAD command is:\n FILEREAD unit [STOPAFTER n] [STRUCTURED | CSV | RULED] [fieldlist]

ORA-34390: (MXFILERD02) The format of the FILEVIEW command is:\n FILEVIEW unit [STRUCTURED | RULED] [fieldlist]

ORA-34392: (MXFORCAS00) You cannot calculate a forecast for an expression with no dimensions.

ORA-34394: (MXFORCAS01) You cannot calculate a forecast with an STSEASONAL expression with no dimensions.

ORA-34396: (MXFORCAS02) The expression to be forecast is not dimensioned by workspace object.

ORA-34398: (MXFORCAS03) The STSEASONAL expression must be dimensioned by only one dimension.

ORA-34400: (MXFORCAS04) time-series

ORA-34402: (MXFORCAS05) When you specify the forecast LENGTH, you must also specify an FCNAME.

ORA-34404: (MXFORCAS06) When you specify METHOD WINTERS, you must also specify the PERIODICITY.

ORA-34406: (MXFORCAS07) When STSMOOTHED, STTREND, or STSEASONAL is specified, they must all be specified.

ORA-34408: (MXFORCAS08) You specified a forecast phrase that is valid only when METHOD WINTERS is specified.

ORA-34410: (MXFORCAS09) The arguments to FCNAME, FCSMOOTHED, FCTREND, and FCSEASONAL must be numeric. workspace object is not numeric.

ORA-34412: (MXFORCAS10) FCNAME, FCSMOOTHED, FCTREND, and FCSEASONAL variables must be dimensioned by time dimension workspace object. workspace object is not.

ORA-34414: (MXGETFLD01) Your FILEREAD or FILEVIEW statement specifies no width for a string string field. There is no default width for this data type.

ORA-34416: (MXGETFLD02) string data cannot be read as a string value.

ORA-34418: (MXGETFLD03) A STRUCTURED or CSV record cannot contain string data.

ORA-34420: (MXGETFLD04) The string option of FILEREAD or FILEVIEW cannot be specified for string data.

ORA-34422: (MXGETFLD05) The SCALE option of FILEREAD or FILEVIEW cannot be specified for BINARY data other than INTEGER.

ORA-34424: (MXGETFLD06) The string option of FILEREAD or FILEVIEW cannot be specified for string string data.

ORA-34426: (MXGETFLD07) Values read into the relation workspace object must be INTEGER position numbers of its conjoint value dimension.

ORA-34428: (MXGETFLD08) Values read into conjoint dimension workspace object must be either INTEGER position numbers or a bracketed list of base dimension values.

ORA-34430: (MXGETFLD09) No data type was specified for one or more of the base dimensions of conjoint dimension workspace object.

ORA-34432: (MXGETFLD10) workspace object cannot be assigned time dimension data.

ORA-34434: (MXGETFLD11) You cannot read values of a dimension composite directly. You can specify a bracketed list of base dimension values.

ORA-34436: (MXGETFLD12) No data type was specified for one or more of the base dimensions of a dimension composite.

ORA-34438: (MXGETSVN01) A value of the workspace object dimension must be a single expression without surrounding angle brackets .

ORA-34440: (MXGETSVN02) A value of the workspace object dimension must be a combination of number base dimension values surrounded by angle brackets .

ORA-34442: (MXGETSVN03) You cannot use a Qualified Object Name as a value of the NAME dimension.

ORA-34444: (MXGETSVN04) Dimension workspace object is not a concatenated dimension.

ORA-34446: (MXGETSVN05) Dimension workspace object is not a base of concatenated dimension workspace object.

ORA-34448: (MXGOTO01) string is not defined as a label.

ORA-34450: (MXIFERR) The IF keyword must be followed by a BOOLEAN expression. The expression starting with string is string.

ORA-34452: (MXIMPORT01) string is a reserved keyword that cannot be used in this context.

ORA-34454: (MXIMPORT02) When importing a spreadsheet, CSV file, or PRN file, the target must be a worksheet. workspace object is not a worksheet.

ORA-34456: (MXIMPORT03) The STOPAFTER specification cannot be NA.

ORA-34458: (MXIMPORT04) The RULER expression cannot be missing or NA.

Cause: The RULER expression was missing.

Action: Add a RULER expression.

ORA-34460: (MXIMPORT05) The expression identifying the file cannot be NA.

ORA-34462: (MXIMPORT06) The STOPAFTER specification cannot be less than one. The value was number.

ORA-34464: (MXIMPORT07) TEXTSTART and TEXTEND are supported only for STRUCTURED PRN files. DELIMITER is supported for STRUCTURED PRN and CSV files.

ORA-34466: (MXIMPORT08) Target workspace object is not in analytic workspace string.

ORA-34468: (MXIMPORT09) workspace object is not a valid target name. You cannot use a Qualified Object Name to specify a target in an EIF import.

ORA-34476: (MXINFO01) The first argument to the string function must be FORECAST, PARSE, REGRESS, SEASADJ, or MODEL.

ORA-34478: (MXLOG01) Disk file string cannot be opened; it is in use.

ORA-34480: (MXMAINT01) You cannot string values of conjoint dimension workspace object.

ORA-34481: (MXMAINT07) You cannot string values of PARTITION TEMPLATE workspace object.

Cause: User attempted to use the MAINTAIN command with some keyword other than ADD or DELETE on a partition template.

Action: It is not possible to MAINTAIN a partition template, except to add or delete values of a partition list.

ORA-34482: (MXMAINT02) You cannot string values of time dimension workspace object.

ORA-34484: (MXMAINT03) You cannot string values of dimension composite workspace object.

ORA-34486: (MXMAINT04) You cannot maintain dimension alias workspace object.

Cause: Dimension aliases cannot be maintained.

Action: Maintain the base dimension.

ORA-34487: (MXMAINT08) You cannot string values of non-unique concat dimension workspace object.

Cause: The specified MAINTAIN operation can only be applied to UNQUE concats.

Action: Use the CHGDFN command to change the concat dimension to UNIQUE and retry.

ORA-34488: (MXMAINT05) You cannot string values of concat dimension workspace object.

ORA-34489: (MXMAINT06) You cannot maintain workspace object because it is a SURROGATE.

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.

ORA-34490: (MXMOVE00) You cannot use Qualified Object Names in the MOVE command except as part of an expression.

ORA-34492: (MXMSERR00) Analytic workspace object workspace object does not exist.

Cause: The referenced object did not exist in an attached analytic workspace.

Action: Specify an object name from one of the attached analytic workspaces.

ORA-34494: (MXMSERR01) Analytic Workspace string does not contain an object named workspace object.

Cause: The object name was not in the specified Analytic Workspace (AW).

Action: Use the DESCRIBE command to find out whether the object is in another Analytic Workspace (AW).

ORA-34496: (MXNAME01) The NAME dimension is available only when you have an active analytic workspace.

ORA-34498: (MXNAME02) You cannot use the NAME dimension in this context.

ORA-34500: (MXNAME03) string is a reserved keyword that cannot be used in this context.

ORA-34502: (MXNAME03A) number is a reserved keyword that cannot be used in this context.

Cause: A reserved keyword was specified as the name of the object or analytic workspace. Reserved keywords cannot be used as the names for objects or analytic workspaces.

Action: Specify another name other than a reserved keyword for the object or analytic workspace.

ORA-34504: (MXNAME04) You have no current analytic workspace.

ORA-34506: (MXNAME05) string is a local variable that cannot be used in this context.

Cause: This context required the name of a defined object.

Action: You may need to define an object with this name or rename your local variable if has the same name as a defined object.

ORA-34508: (MXNAME06) You cannot qualify references to the NAME dimension.

ORA-34512: (MXNEGERR) The NOT operator can only be used with BOOLEAN expressions. The expression at string is string.

ORA-34514: (MXOPERR) You cannot string string data in the expression that begins with 'string'.

Cause: The user attempted an invalid operation.

Action: n/a

ORA-34516: (MXPROPER01) A property name cannot be NA.

ORA-34518: (MXPROPER02) A property named string does not exist.

ORA-34520: (MXPROPER03) A property name cannot be a multi-line text.

ORA-34522: (MXPROPER04) A property name must be between number and number bytes long. You supplied a name of number bytes.

ORA-34524: (MXPROPER05) The object properties in this analytic workspace cannot be read, because they were created by an incompatible version of string.

ORA-34526: (MXPSHPOP01) You cannot string workspace object because it is not a scalar variable.

ORA-34528: (MXPSHPOP02) You cannot string workspace object because it is not data.

ORA-34530: (MXPSHPOP03) You cannot string workspace object because it is a string.

ORA-34534: (MXPUTQDR01) A FILEREAD attribute list is not valid in this context.

ORA-34538: (MXRECAP01) The format of the RECAP command is:\n RECAP [ALL|n] [string] [FILE pathname]

ORA-34540: (MXRECAP02) RECAP does not support multi-line strings.

ORA-34542: (MXRECAP03) There are no entries in the command log.

ORA-34544: (MXRECAP04) No matching commands were found.

ORA-34546: (MXRECAP05) The format of the REDO command is:\n REDO [n] [oldtext newtext [option]]

ORA-34548: (MXRECAP06) There is no occurrence number of 'number' in the command.

ORA-34550: (MXRECAP07) Command number number is not available.

ORA-34552: (MXRECAP08) Multi-line strings cannot be used in editing the command.

ORA-34554: (MXRECAP09) The string 'number' does not occur in the command.

Cause: A search string was specified in the REDO or REEDIT command that could not be found in the command to be modified.

Action: Check the command string to make sure that it contains at least one occurrence of the search string.

ORA-34556: (MXRECAP10) Substituting number for number would cause the command to exceed the maximum command length (number).

ORA-34558: (MXRECAP11) The format of the REEDIT command is:\n REEDIT [n] oldtext newtext [option]

ORA-34560: (MXRECAP12) The string command cannot be saved in the command log by REDO or REEDIT or executed by REDO.

Cause: The command was one of a small set of commands that could not be logged, including RECAP, REEDIT, REDO, and empty strings.

Action: Do not attempt REDO or REEDIT on this command.

ORA-34562: (MXRENAME02) An object named number already exists in analytic workspace string.

ORA-34564: (MXRENAME03) The SPARSE keyword changes a named composite to unnamed. You cannot apply it to an unnamed composite.

ORA-34566: (MXRENAME04) Only integer dimensions can be named string.

ORA-34568: (MXRENAME05) You cannot rename workspace object because you do not have PERMIT rights to do it or it is readonly.

ORA-34570: (MXRENAME06) The dimension composite workspace object is not in analytic workspace string.

ORA-34572: (MXRENAME07) cannot change workspace object to an unnamed composite because it is not a composite

Cause: The specified object could not be renamed to SPARSE because it was not a composite.

Action: None

ORA-34574: (MXRENAME08) You cannot change workspace object to an unnamed composite because it has permissions attached.

ORA-34576: (MXRENAME09) You cannot change workspace object to an unnamed composite because there are pushed statuses associated with it.

ORA-34578: (MXRENAME10) You cannot change workspace object to an unnamed composite because there are no objects dimensioned by it.

ORA-34580: (MXRENAME11) You cannot change workspace object to an unnamed composite because there are properties associated with it.

ORA-34582: (MXRENAME12) You cannot change workspace object to an unnamed composite, because there is already an unnamed composite with the same base dimensions.

ORA-34584: (MXRENAME13) You cannot change workspace object to an unnamed composite, because it appears in the dimension list of unnamed composite workspace object.

ORA-34586: (MXRENAME14) You cannot change workspace object to an unnamed composite, because unnamed composite workspace object appears in its dimension list.

ORA-34588: (MXRENAME15) The object workspace object is not in analytic workspace string.

ORA-34592: (MXRENAME17) You cannot change workspace object to an unnamed composite, because it would cause the dependent object workspace object to exceed the limit for the number of named dimensions.

ORA-34594: (MXROLLUP01) workspace object is not a data variable.

ORA-34596: (MXROLLUP02) The data type (string) of workspace object is not INTEGER, DECIMAL, or SHORTDECIMAL.

ORA-34598: (MXROLLUP03) workspace object is not related to itself.

ORA-34600: (MXROLLUP04) workspace object is not dimensioned by workspace object.

Cause: The ROLLUP variable was not dimensioned by the ROLLUP dimension.

Action: Specify a correct base dimension to ROLLUP.

ORA-34602: (MXROLLUP05) You must specify which dimension to roll up, since workspace object has more than one dimension.

ORA-34604: (MXROLLUP06) workspace object is not a relationship array.

ORA-34606: (MXROLLUP07) workspace object does not yield values of workspace object.

ORA-34608: (MXROLLUP08) workspace object is not dimensioned by workspace object.

ORA-34610: (MXROLLUP09) The relationship array workspace object shares the workspace object dimension with workspace object. It can only share the rollup dimension itself.

ORA-34612: (MXSHELL01) Your program or expression uses too much execution space. Eliminate recursion or reduce the levels of nesting.

ORA-34614: (MXSHOWCD00) No command was given. There is nothing to show.

ORA-34616: (MXSHOWCD01) No code is generated for the string command.

ORA-34618: (MXSHOWCD02) The compiled code for workspace object cannot be displayed because the program has been hidden.

ORA-34620: (MXSHOWCD03) No compiled code exists for string workspace object.

ORA-34622: (MXSHOWCD04) No text exists for string workspace object.

ORA-34624: (MXSORT01) Sort criterion number is not dimensioned by workspace object.

ORA-34626: (MXSORT02) You must convert WORKSHEET values to a simple data type before using them as a sort criterion.

Cause: The data type used for the sort criterion was not one data type.

Action: Use the CONVERT function to cast he sort criterion to a single data type.

ORA-34628: (MXSQL99) The SQL "string" command can only be used in a program, and it must be compiled before it can be executed.

ORA-34630: (MXSQL00) The format of the SQL DECLARE command is:\n SQL DECLARE cursor-name CURSOR FOR select-command

ORA-34632: (MXSQL01) The format of the SQL OPEN command is:\n SQL OPEN cursor-name

ORA-34634: (MXSQL02) The format of the SQL CLOSE command is:\n SQL CLOSE cursor-name

ORA-34636: (MXSQL03) The format of the SQL FETCH command is:\n SQL FETCH cursor-name [LOOP [count]] INTO :host-var [:host-var ...] [THEN filereadactions]

ORA-34637: (MXSQL11) The format of the SQL IMPORT command is:\n SQL IMPORT cursor-name INTO :host-var [:host-var ...]\n [THEN filereadactions]

ORA-34638: (MXSQL04) The format of the SQL CLEANUP command is:\n SQL CLEANUP

ORA-34639: (MXSQL05) The format of the SQL SELECT command is:\n SQL SELECT rest of select statement INTO :host-var [:host-var ...] [THEN filereadactions]

ORA-34642: (MXSQL08) The format of the SQL PREPARE command is:\n SQL PREPARE statement-name FROM non-select-command

ORA-34644: (MXSQL09) The format of the SQL EXECUTE command is:\n SQL EXECUTE statement-name

ORA-34646: (MXSQL10) The format of the SQL PROCEDURE command is:\n SQL PROCEDURE procedure-name [ ( parameter {, parameter} ) ]

ORA-34647: (MXSQL18) The text expression in a CURSOR FOR TEXT declaration cannot be NA.

Cause: The text for the SELECT expression in a CURSOR FOR TEXT declaration was evaluated at compile time as NA.

Action: Specify a text expression that is not NA at the time the program containing the SQL DECLARE is compiled.

ORA-34648: (MXSQL19) The SQL command is incomplete.

ORA-34650: (MXSQL20) The SELECT command is not supported by string. You must declare a cursor to retrieve SQL data.

ORA-34652: (MXSQL21) The SQL command contains a syntax error.

ORA-34654: (MXSQL23) Host variable expected; use :: to escape a colon.

ORA-34656: (MXSQL24) Additional WHERE clause conditions with CURRENT OF cursor name syntax

Cause: A SQL UPDATE or DELETE statement tried to use the CURRENT of cursor name syntax with a WHERE clause containing multiple conditions.

Action: When using the CURRENT OF cursor name syntax make sure it is the only condition in the WHERE clause.

ORA-34658: (MXSQL25) The words CURSOR FOR TEXT must be followed by a compile-time text expression specifying a SELECT command.

Cause: A SQL DECLARE csr CURSOR FOR TEXT command lacked a text expression, or the expression was otherwise invalid.

Action: Specify a single text expression that can be evaluated at compile time to yield a SELECT statement

ORA-34660: (MXSQL26) SQL cursor string has already been declared in this compilation.

ORA-34662: (MXSQL27) SQL statement string has already been prepared in this compilation.

ORA-34665: (MXSQL30) Concat dimension workspace object cannot be used as a target host variable. You must specify one of its leaves, and then set the concat's status from that leaf.

ORA-34666: (MXSWITCH01) Only one DEFAULT label is allowed in a SWITCH.

ORA-34668: (MXSWITCH02) The format of a DEFAULT label statement is:\n DEFAULT:

ORA-34670: (MXSWITCH03) Invalid syntax in case label expression

ORA-34672: (MXSWITCH04) The format of a CASE label statement is:\n CASE case-expression:

ORA-34674: (MXTRACE01) There is no trace in effect.

ORA-34676: (MXTRAP01) string is not defined as a label.

ORA-34680: (MXUPDATE03) Analytic workspace string is read-only. Therefore, the UPDATE command will not save changes.

Cause: The specified analytic workspace was attached read-only when the OLAP UPDATE command was issued. Any unsaved changes will be lost.

Action: The analytic workspace will need to be attached read-write and the changes made again before they can be saved.

ORA-34682: (MXUPDATE04) You have no attached analytic workspaces.

Cause: The OLAP AW UPDATE command was executed without any analytic workspaces attached for write operations.

Action: Attach an analytic workspace for write, redo the changes, and retry the AW UPDATE command.

ORA-34684: (MXUPDATE05) All of your attached analytic workspaces are read-only. Therefore, the UPDATE command will not save changes.

Cause: The AW UPDATE command did not find an analytic workspace that is attached for write.

Action: Attach the analytic workspace that needs changes for write make the desired changes, and issue the AW UPDATE command again.

ORA-34686: (MXVAR02) string is not a valid data type for a declarative statement.

ORA-34688: (MXVAR03) workspace object cannot be used as a variable or argument type because it is the name of a dimension composite.

ORA-34690: (MXWATCH01) There are no watchpoints set.

ORA-34691: (MXXEQ00A) The value value is greater than the specified precision (number, number) for workspace object.

Cause: A numeric value was entered that exceeded the precision defined for this object. For example, for an object defined to be NUMBER(3,2), the precision or the maximum number of significant decimal digits is 3. The scale or the number of digits from the decimal point to the least significant digit is 2. In this case, a value of 123.89 will cause the error because the precision allows a maximum of 3 digits and 2 of them must be to the right of the decimal point. A value of 3.89 will not cause the error.

Action: Enter a value that complies with the precision defined for the object.

ORA-34692: (MXXEQ01) A division by zero was attempted. Set DIVIDEBYZERO to YES if you want NA to be returned as the result of division by zero.

ORA-34693: (MXXEQ00B) The value value is greater than the specified precision (number, number).

Cause: A numeric value was entered that exceeded the specified precision for this operation. For example, for a specified precision of NUMBER(3,2), the precision or the maximum number of significant decimal digits is 3. The scale or the number of digits from the decimal point to the least significant digit is 2. In this case, a value of 123.89 will cause the error because the precision allows a maximum of 3 digits and 2 of them must be to the right of the decimal point. A value of 3.89 will not cause the error.

Action: Enter a value that complies with the specified precision limit.

ORA-34694: (MXXEQ02) Unsupported conversion of RELATION data was attempted.

ORA-34696: (MXXEQ03A) "number" is not a number.

ORA-34698: (MXXEQ03B) "number" is not a Boolean.

ORA-34700: (MXXEQ05) Function calls are too deeply nested to be evaluated.

ORA-34702: (MXXEQ13) "number" is not a valid number format.

ORA-34704: (MXXEQ14) "number" does not match number format "number".

ORA-34706: (MXXEQ35) value is not a valid workspace object.

ORA-34708: (MXXEQ36) value does not exist.

ORA-34710: (MXXEQ37) Positions in the product of breakout dimensions of an aggregation function cannot exceed 2**63.

ORA-34712: (NAFILENAME) The expression identifying the file cannot be NA or blank.

ORA-34718: (NLSCHARSET02) number is not a valid, installed NLS character set.

ORA-34719: (NLSCHARSET03) Character data loss in NTEXT/TEXT conversion

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 set or set NLS_NCHAR_CONV_EXCP to be FALSE. Note: This message is the OLAP equivalent of ORA-12713.

ORA-34720: (NLSCHARSET04) An unknown character set conversion error occurred.

ORA-34722: (NLSCHARSET05) CAUTION: Character data loss in character set conversion from string to string

Cause: Some operation required a string to be converted into a different character set, but the string contained characters that didn't exist in the new character set.

Action: Choose different character sets.

ORA-34726: (NLSCHARSET06) CAUTION: String truncated during character set conversion from string to string

Cause: Some operation required a string to be converted into a different character set. The string required more bytes in the new encoding, and exceeded some byte limit on its allowable length, causing some characters to be removed from the end of the string.

Action: If the byte limit is due to using the ID datatype, consider using the CHAR datatype instead. If the byte limit is due to the limit of 4000 bytes per line of CHAR data, break the long line up into multiple lines.

ORA-34730: (NLSCHARSET08) CAUTION: During character set conversion, some of hidden program workspace object was truncated or could not be converted.

ORA-34731: (NLSSORT01) 'number' is not a valid NLS_SORT specification.

Cause: An unrecognized NLS_SORT value was specified in the SORT command or the SORT, SORTLINES or UNIQUELINES function.

Action: Specify a supported NLS_SORT value.

ORA-34732: (NOCONSIDER) You have no current definition. Define an object or use the CONSIDER command before using the string command.

ORA-34738: (NOUPDATE) A severe problem has been detected. Analytic workspace operations have been disabled.

Cause: A previous severe error marked the session so that it could not perform any updates.

Action: Use the EXPORT command to save your work, then start a new session.

ORA-34740: (NOUPDATEDB) Changes made to the string analytic workspace are not saved.

Cause: A previous, severe error marked the session so that it could not perform any UPDATEs.

Action: Use the EXPORT command to save your work, then start a new session.

ORA-34744: (NPV01) Time dimension workspace object has a range in status of number periods. The maximum range allowed for the NPV function is number periods.

ORA-34746: (NPV02) The interest rate in the NPV function is number. The value must be greater than -1.

ORA-34748: (NUMARGS1) You supplied number argument(s) to the string function. You must supply at least number.

ORA-34750: (NUMARGS2) The string function cannot have any arguments.

ORA-34752: (NUMARGS3) You supplied number arguments to the string function. It can have no more than number arguments.

ORA-34754: (NUMARGS4) You supplied number argument(s) to a function that requires at least number.

ORA-34756: (NUMARGS5) You supplied arguments to a function that does not take arguments.

ORA-34758: (NUMARGS6) You supplied number arguments to a function that can have no more than number arguments.

ORA-34760: (NXHANDLE01) Decimal overflow in context that is unprotected by the DECIMALOVERFLOW option. Contact Oracle OLAP technical support.

ORA-34761: (NXHANDLEALLO) A decimal overflow occurred during an ALLOCATE operation.

Cause: While performing an ALLOCATE operation, a decimal overflow occurred. This created unreliable results.

Action: Correct the data or use a higher precision data type.

ORA-34762: (NXHANDLE02) A decimal overflow has occurred. Set DECIMALOVERFLOW to YES if you want NA to be returned as the result of a decimal overflow.

ORA-34764: (NXHANDLE03) A decimal overflow occurred during a ROLLUP operation. The results are not reliable.

ORA-34766: (NXHANDLE04) A decimal overflow occurred during an AGGREGATE operation. The results are not reliable.

ORA-34768: (NXHANDLE05) A decimal overflow occurred while parsing the AGGMAP.

ORA-34770: (OBJENG02) The object name argument to the OBJ function cannot be NA.

ORA-34772: (OBJENG03) number contains more than one name.

ORA-34774: (OBJENG04) 'number' is not the name of a dimension or composite.

ORA-34776: (OBJENG05) Analytic workspace object number does not exist.

ORA-34778: (OBJENG06) You cannot use the OBJ function on objects in analytic workspace string.

Cause: The OBJ function was used against the EXPTEMP analytic workspace.

Action: Use the OBJ function on any analytic workspace other than EXPTEMP.

ORA-34780: (OBJLIST01) Analytic workspace 'string' is not attached.

ORA-34782: (OBJSAVE2) Analytic Workspace string already has the maximum number of objects (number).

Cause: The Analytic Workspace has too many objects.

Action: Redesign the Analytic Workspace to not exceed the maximum number of objects.

ORA-34786: (OCI02) The total length of all output variables cannot be more than number bytes.

ORA-34796: (OCI08) SQL host variable number cannot be bound.

Cause: The data type of the host variable is not supported.

Action: Specify only variables of supported types as host variable names.

ORA-34798: (OCI09) OLAP OCI operation canceled.

ORA-34800: (OCI10) OLAP OCI operation returned 'string'.

ORA-34802: (OCI11) OLAP OCI operation caused ROLLBACK past an UPDATE of an attached analytic workspace. Current operation canceled.

Cause: ROLLBACK past the UPDATE of one of the attached Analytic Workspaces was called. The current operation is aborted, and the Analytic Workspace detached.

Action: Change the called SQL procedure to avoid the ROLLBACK

ORA-34804: (OCI12) The value of SQL host variable number is too long. Use the WIDE keyword for columns that may exceed number bytes.

Cause: The host variable had a text value longer than the maximum SQL VARCHAR length

Action: Use the WIDE keyword in the host variable specification, e.g. :WIDE OLAP_object_name

ORA-34805: (OCI13) Statement number must have at least one host variable.

Cause: Statements prepared with DIRECT=YES must have at least one host variable.

Action: Add a host variable to the prepared statements declaration.

ORA-34806: (OCI14) Statement number can only be executed within an ACROSS command.

Cause: Statements prepared with DIRECT=YES must be executed in an ACROSS command.

Action: Execute the statement within an ACROSS command.

ORA-34830: (OFCENG02) The string function cannot be applied to the dimension composite workspace object.

Cause: The specified function could not be applied to the dimension composite. Dimension composites do not have status lists. Status is based on the status of the base dimensions.

Action: Do not apply status directly to a dimension composite.

ORA-34832: (OFCENG03) number is not the name of a dimension or valueset.

ORA-34833: (OFCENG04) The string function cannot be applied to the PARTITION TEMPLATE workspace object.

Cause: Partition templates did not have status lists.

Action: Do not try to apply status to a partition template.

ORA-34834: (OKUNDSS01) Analytic workspace string must remain current because the workspace object program is still executing in it.

ORA-34836: (OKUNDSS03) Analytic workspace string cannot be detached because a currently executing command depends upon an object (workspace object) it contains.

Cause: Analytic workspaces can only be detached when they are not being referenced by currently executing code. This error might occur when multiple queries are executed by the user code and one of those processes tries to detach the Analytic Workspace.

Action: Restructure the application so this condition does not occur.

ORA-34840: (OPCREATE01) The string option must be declared with datatype string.

Cause: An attempt was made to declare the option with the wrong datatype.

Action: Declare the option with the correct datatype.

ORA-34841: (OPCREATE02) The string option must be declared with the READONLY attribute.

Cause: An attempt was made to declare the option without the READONLY attribute.

Action: Declare the option READONLY.

ORA-34842: (OPTWIDTH) workspace object must be between number and number. It cannot be number. Its previous value was retained.

ORA-34844: (OPUTNA00) You cannot set an option to NA. The previous value of workspace object was retained.

ORA-34846: (OVERRIDE01) number

ORA-34848: (PARSE01) The text to be parsed is NA.

ORA-34852: (PHASTOVC00) Unsupported type

ORA-34854: (PMTSETUP00) Permission expression for workspace object is invalid and will be treated as FALSE.

ORA-34856: (PMTSETUP01) Permission for workspace object does not have proper dimensionality of the BY expression.

ORA-34858: (PMTUPDAT01) Permission expression for workspace object is invalid and will not be stored.

ORA-34859: (PMTUPDAT07) Permission condition for workspace object contains an expression longer than number bytes and cannot be stored.

Cause: One of the components of the PERMIT condition was too long.

Action: Rewrite the condition to shorten it.

ORA-34860: (PMTUPDAT02) You do not have PERMIT rights for workspace object.

ORA-34862: (PMTUPDAT03) workspace object is not a dimension, so you cannot give it MAINTAIN permission.

ORA-34864: (PMTUPDAT04) A BY clause cannot be given with string permission for workspace object.

ORA-34866: (PMTUPDAT05) You cannot apply permissions to dimension composite workspace object. Instead, you can apply permissions to its base dimensions.

ORA-34868: (PMTUPDAT06) You cannot apply permissions to dimension alias workspace object. Instead, you can apply permissions to the aliased dimension.

ORA-34870: (PERMIT01) You do not have permission to read this value of workspace object.

ORA-34871: (PERMIT06) Session-only value 'value' of workspace object has been deleted because a PERMIT change has revealed a duplicate value.

Cause: Execution of a PERMIT command revealed a permanent dimension or surrogate value having the same name as the SESSION value.

Action: If the SESSION value is still needed, add it with a different name.

ORA-34872: (PERMIT02) You do not have permission to write this value of workspace object.

ORA-34873: (PERMIT07) You cannot write this value of workspace object since it is readonly.

ORA-34874: (PERMIT03) You do not have permission to run workspace object.

ORA-34876: (PERMIT04) You do not have permission to read AGGMAP workspace object.

ORA-34877: (PERMIT05) You cannot apply permissions to concat dimension workspace object. Instead, you may apply permissions to its leaf dimension(s).

ORA-34880: (PPDTORDR00) DATEORDER must be YMD, YDM, MYD, MDY, DYM, or DMY.

ORA-34882: (PPENG00) The level name for string cannot be NA.

ORA-34884: (PPENG01) number does not match a PUSHLEVEL command.

Cause: The POPLEVEL command failed because the level name did not match an active PUSHLEVEL command.

Action: Look for redundant POP commands since this level may have already been popped.

ORA-34886: (PPENG02) The option workspace object is read-only. Since its value cannot be popped, it cannot be pushed.

ORA-34888: (PPENG03) The status list for workspace object is protected by the TEMPSTAT command.

ORA-34892: (PPESCCH01) The ESCAPECHAR option requires a single character.

ORA-34894: (PPESCCH02) The 'string' character is an invalid choice for the ESCAPECHAR option.

ORA-34896: (PPMONTHS00) At least 12 month names must be given. Only number were provided.

Cause: There must be at least one name for each month. Not enough names were provided.

Action: Provide at least 12 names.

ORA-34897: (PPMONTHS01) Blank lines are not allowed in the MONTHNAMES option.

Cause: There is at least one blank line in the string populating the MONTHNAMES option. We do not allow blank month names.

Action: Remove the blank line(s) from the string.

ORA-34900: (PPWKDAYS00) At least 7 day names must be given. Only number were provided.

Cause: There must be at least one name for each day. Not enough names were provided.

Action: Make sure there are at least 7 names in the string.

ORA-34901: (PPWKDAYS01) Blank lines are not allowed in the DAYNAMES option.

Cause: There is at least one blank line in the string populating the DAYNAMES option. We do not allow blank day names.

Action: Remove the blank line(s) from the string.

ORA-34902: (PPWKDNY01) The value of WEEKDAYSNEWYEAR must be a number between 1 and 7.

ORA-34904: (VCFMT001) must be multi-line

ORA-34908: (VCFMT003) missing arg

ORA-34910: (VCFMT004) duplicate

ORA-34912: (VCFMT005) error during %%p permutation

ORA-34914: (VCFMT006) non-numeric

ORA-34916: (PRMPINIT001) ->

ORA-34918: (PRMPINIT002) Continue>

ORA-34920: (PRMPINIT003) More>

ORA-34924: (PRMPINIT005) PRG>

ORA-34926: (PRMPINIT006) =>

ORA-34928: (PRMPINIT007) MDL>

ORA-34930: (PRMPINIT008) MDL>

ORA-34934: (PRMPINIT010) AGGMAP>

ORA-34936: (PRMPINIT011) AGGMAP>

ORA-34946: (PRMPINIT031) Press Enter to continue.

ORA-34956: (PRMPINIT200) exponentiate

ORA-34957: (PRMPINIT217) compare

ORA-34958: (PRMPINIT201) multiply

ORA-34959: (PRMPINIT218) compare

ORA-34960: (PRMPINIT202) divide

ORA-34962: (PRMPINIT203) add

ORA-34964: (PRMPINIT204) subtract

ORA-34966: (PRMPINIT205) compare

ORA-34968: (PRMPINIT206) compare

ORA-34970: (PRMPINIT207) compare

ORA-34972: (PRMPINIT208) compare

ORA-34974: (PRMPINIT209) compare

ORA-34976: (PRMPINIT210) compare

ORA-34978: (PRMPINIT211) compare

ORA-34980: (PRMPINIT212) compare

ORA-34982: (PRMPINIT213) AND

ORA-34984: (PRMPINIT214) OR

ORA-34986: (PRMPINIT215) NOT

ORA-34988: (PRMPINIT216) negate

ORA-34990: (PRNIMPRT01) CAUTION: number line(s) in a TEXT PRN file were too long. Each line was truncated to number bytes.

ORA-34992: (PRNIMPRT02) CAUTION: number field(s) in a STRUCTURED PRN or CSV file were too long. Each field was truncated to number bytes.

ORA-34994: (PRNIMPRT03) Unexpected EOF encountered in string while importing data.

ORA-34996: (PRNIMPRT04) Unexpected character 'character' at end of string.

ORA-35000: (PRNRULER01) The RULER specification does not have any valid field descriptions.

ORA-35002: (PRNRULER02) Zero is not a valid repeat count.

ORA-35004: (PRNRULER03) The repeat count number was not followed by a field type.

ORA-35006: (PRNRULER04) The character 'character' is not a valid field type. The valid types are A, S and T.

ORA-35008: (PRNRULER05) A field description (type character) does not include a field width.

Cause: The field width was missing.

Action: Add a field width.

ORA-35010: (PRNRULER06) The width (number) for an A or T field was too large. The limit is number.

ORA-35012: (PRNRULER07) Zero is not a valid width for an S field.

ORA-35014: (PRNRULER08) A repeat count or field width (string) was too large. The limit is number.

ORA-35016: (QFCHECK00) The analytic workspace and EIF file definitions of workspace object have a mismatched type.

Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB.

Action: Import the object into an Analytic Workspace that does not already contain an object with the same name.

ORA-35017: (QFCHECK06) The analytic workspace and EIF file definitions of workspace object have different partitioning methods.

Cause: Importing from an EIF file or LOB into an existing analytic workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB.

Action: Import the object into an analytic workspace that does not already contain an object with the same name.

ORA-35018: (QFCHECK01) The analytic workspace and EIF file definitions of workspace object have a mismatched data type.

Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB.

Action: Import the object into an Analytic Workspace that does not already contain an object with the same name.

ORA-35019: (QFCHECK07) The Analytic Workspace and EIF file definitions of workspace object have different partition dimensions.

Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB.

Action: Import the object into an Analytic Workspace that does not already contain an object with the same name.

ORA-35020: (QFCHECK02) The analytic workspace and EIF file definitions of workspace object have mismatched dimensioning.

Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB.

Action: Import the object into an Analytic Workspace that does not already contain an object with the same name.

ORA-35021: (QFCHECK08) The EIF file definition of workspace object has some partitions that are not present in the existing Analytic Workspace object.

Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB.

Action: Import the object into an Analytic Workspace that does not already contain an object with the same name.

ORA-35022: (QFCHECK03) The analytic workspace and EIF file definitions of workspace object have a mismatched relation.

Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB.

Action: Import the object into an Analytic Workspace that does not already contain an object with the same name.

ORA-35023: (QFCHECK09) The analytic workspace and EIF file definitions of workspace object have incompatible partition definitions.

Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB.

Action: Import the object into an Analytic Workspace that does not already contain an object with the same name.

ORA-35024: (QFCHECK04) The analytic workspace and EIF file definitions of workspace object have mismatched time dimension attributes.

Cause: Importing from an EIF file or LOB into an existing analytic workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB.

Action: Import the object into an analytic workspace that does not already contain an object with the same name.

ORA-35026: (QFCHECK05) The analytic workspace and EIF file definitions of workspace object have a mismatched ALIASOF dimension.

Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB.

Action: Import the object into an Analytic Workspace that does not already contain an object with the same name.

ORA-35028: (QFASCII00) The IMPORT command has terminated because of a defect in the EIF file.

ORA-35029: (QFPART00) The IMPORT command has terminated because of a defect in the EIF file.

ORA-35030: (QFDATA00) The IMPORT command has terminated because of a defect in the EIF file.

ORA-35031: (QFSVNS00) The IMPORT command has terminated because of a defect in the EIF file.

Cause: The EIF file contains a compressed composite with defective aggregation data.

Action: Re-create the EIF file using the NOAGGR keyword.

ORA-35032: The IMPORT command terminated because of a defect in the EIF file.

Cause: This was an unexpected error.

Action: Re-create the EIF file or restore it from a backup. If the problem persists, contact Oracle Support.

ORA-35036: (QFGETBUF00) The IMPORT command has terminated because of a defect in the EIF file.

ORA-35038: (QFGETHDR00) The IMPORT command has terminated because of a defect in the EIF file.

ORA-35040: The IMPORT command has terminated because of a defect in the EIF file.

Cause: This is an unexpected error.

Action: Re-create the EIF file or restore it from a backup. If the problem persists, contact Oracle Support.

ORA-35042: (QFOBJECT92) The IMPORT command has terminated because of a defect in the EIF file.

ORA-35044: The IMPORT command terminated because of a defect in the EIF file.

Cause: An unexpected error occurred because of a defect in the EIF file which caused the IMPORT command to terminate.

Action: Re-create the EIF file or restore it from a backup. If the problem persists, contact Oracle Support.

ORA-35046: The IMPORT command terminated because of a defect in the EIF file.

Cause: There was an unexpected error.

Action: Re-create the EIF file or restore it from a backup. If the problem persists, contact Oracle Support.

ORA-35048: (QFOBJECT97) The IMPORT command has terminated because of a defect in the EIF file.

ORA-35050: The IMPORT command terminated because of a defect in the EIF file.

Cause: There was an unexpected error.

Action: Re-create the EIF file or restore it from a backup. If the problem persists, contact Oracle Support.

ORA-35052: (QFPUTILP98) The IMPORT command has terminated because of a defect in the EIF file.

ORA-35054: The IMPORT command has terminated because of a defect in the EIF file.

Cause: This is an unexpected error.

Action: Re-create the EIF file or restore it from a backup. If the problem persists, contact Oracle Support.

ORA-35056: The IMPORT command terminated because of a defect in the EIF file.

Cause: This an unexpected error.

Action: Re-create the EIF file or restore it from a backup. If the problem persists, contact Oracle Support.

ORA-35058: The IMPORT command has terminated because of a defect in the Express Interchange File (EIF).

Cause: There is a defect in the EIF.

Action: Re-create the EIF or restore it from a backup. If the problem persists, contact Oracle Support.

ORA-35060: The IMPORT command has terminated because of a defect in the EIF file.

Cause: This is an unexpected error.

Action: Re-create the EIF file or restore it from a backup. If the problem persists, contact Oracle Support.

ORA-35062: (QFGET01) Duplicate files found for extension number number of EIF file string.

Cause: IMPORT searched the directories specified in EIFEXTENSIONPATH and found two EIF extension files with the same name (differing at most by the case used in the final name component.

Action: Delete, rename or move any files that are not to be read by IMPORT.

ORA-35066: (QFGET03) Extension number number is missing for EIF file string.

Cause: IMPORT searched the directories specified in EIFEXTENSIONPATH and could not find the appropriately numbered extension file.

Action: Move the missing file into one of the searched directories.

ORA-35070: (QFHEAD00) File string is not in EIF format.

Cause: This was not an EIF file. It could not be imported with the EIF specification.

Action: Unless this file has been damaged in some way and can be restored from backup, it is likely that this was never an EIF file.

ORA-35071: (QFHEAD06) EIF file string cannot be imported because analytic workspace string has not been upgraded to version string.

Cause: User attempted to import from an EIF file that was created by a newer version of the product into an AW that was created by a older version of the product.

Action: Make sure that the compatibility mode parameter in the init.ora of the importing instance specifies a version that is at least as high as the parameter was in the exporting instance. Then, convert the AW to the latest storage format and reexecute the import command. Alternatively, change the EIFVERSION option of the exporting instance to a lower number, recreate the EIF file, and import the new file.

ORA-35074: (QFHEAD02) EIF file string cannot be read by this version of string.

Cause: The EIF file was created with an internal version number indicating it may contain objects that are not compatible with the current Oracle OLAP version, or the EIF file is in an obsolete format.

Action: If possible, set EIFVERSION in the exporting instance to a lower number, recreate the EIF file, and import the new file.

ORA-35076: (QFHEAD04) CAUTION: The textual data in EIF file string is encoded in a character set that is not recognized by this version of string.

Cause: IMPORT could not recognize the character set specification in the EIF file.

Action: Check the imported text data. If it was not imported correctly, recreate the EIF file with a character set supported by the current Oracle version.

ORA-35078: (QFHEAD05) An EIF extension file header for string is not in the correct format.

Cause: An EIF extension file in multi-file IMPORT did not contain correct header information.

Action: Check to be sure that EIFEXTENSIONPATH is set correctly and that all the extension files for the current IMPORT were created by the same EXPORT command as the main EIF file.

ORA-35080: (QFOBJECT01) You cannot rename dimensions when you import them. The string dimension cannot be imported as string.

Cause: An attempt was made to rename a dimension during IMPORT. Renaming of dimension during IMPORT is not allowed.

Action: Do not attempt to rename the dimension during import.

ORA-35082: (QFOBJECT02) You cannot import changes to the workspace object program now, because it is currently executing.

ORA-35084: (QFOBJECT06) CAUTION: string is being imported. However, this is a reserved word, so you must rename the new object before you can use it.

ORA-35086: (QFOBJECT07) " number dimension values "

ORA-35087: (QFOBJECT09) number\nInvalid

ORA-35088: (QFOBJECT08) " number dimension value combinations "

ORA-35090: (QFPARSE00) The object string cannot be imported because it does not exist in the EIF file.

Cause: The requested object was not in the EIF file.

Action: To see the contents of the EIF file, run the IMPORT command with the LIST ONLY parameter.

ORA-35092: (QFPARSE01) You cannot import the object string into both string and string at the same time. To import an object into two different analytic workspaces, use two separate IMPORT commands with different INTO arguments.

ORA-35095: (QFSVNS01) One or more imported values of fixed-width dimension workspace object have been truncated.

Cause: The data in the EIF file was exported from a dimension with wider values than the target dimension will accommodate.

Action: Change the definition of the target dimension, or check to be sure that multiple values from the target dimension have not become identical during the import process. This could cause data loss as data from later dimension values overstores data imported earlier.

ORA-35096: (QUAFEOF) An unexpected end-of-file occurred in the EIF file. Check to make sure you have all the imported data that you expected.

ORA-35098: (RDPOW01) You cannot raise zero to a negative power.

ORA-35100: (RDPOW02) You cannot raise a negative number to a non-integer power.

ORA-35102: (READONLY00) The option workspace object is read-only. Its previous value was retained.

ORA-35104: (REALDTOK01) "string" is not a number.

ORA-35106: (REGRESS00) The regression was not calculated because of a linear relationship between your independent variables.

Cause: The values of the specified independent variables are not independent. For example, one may be a multiple of the other.

Action: Chose independent variables whose values are truly independent of one another.

ORA-35108: (REGRESS01) The number of non-NA observations with weights greater than zero (number) is too small to calculate a regression.

ORA-35110: (REGRESS02) The number of independent variables cannot exceed number.

ORA-35134: (RGACCUM01) A weighted regression cannot be calculated if any of the weights specified is less than zero.

ORA-35136: (RGINFO00) There is no saved regression information for the INFO function to retrieve.

ORA-35138: (RPACROSS01) You must specify dimension values if you use string in an ACROSS phrase.

ORA-35140: (RPACROSS02) ACROSS must be followed by the name of a dimension or an expression with one dimension.

ORA-35142: (RPCOLUMN01) Multiple ACROSS phrases specifying the same dimension (workspace object) cannot be given for the same column.

ORA-35144: (RPFORMAT01) The value of the string attribute in column number is NA.

ORA-35146: (RPFORMAT02) The value of the string attribute in column number is negative.

ORA-35148: (RPFORMAT03) The value of the string attribute in column number is zero.

ORA-35150: (RPFORMAT04) The INDENT value for column number equals or exceeds the WIDTH.

ORA-35152: (RPFORMAT05) Column number extends past the maximum length (number) of a report line.

ORA-35154: (RSEXECUT01) The string function can only be used in a ROW or REPORT command.

Cause: The COLVAL, RUNTOTAL, or SUBTOTAL functions were used outside of a ROW or REPORT command.

Action: Use the COLVAL, RUNTOTAL, and SUBTOTAL functions only in a ROW or REPORT command.

ORA-35158: (RSEXECUT03) Column index number in string is before the first or after the last report column.

Cause: COLVAL referenced a column that did not exist.

Action: Use a valid column number or use a negative index to go back from the current column.

ORA-35162: (RSEXECUT05) The column number (number) in string must be greater than zero.

Cause: The specified column number was less than or equal to zero.

Action: Specify column numbers that are greater than zero.

ORA-35164: (RSEXECUT06) An argument (number) to string must be zero or greater.

Cause: The value of a row command attribute was less than zero.

Action: Omit this attribute if you want the default value.

ORA-35166: (SIGENG01) string

ORA-35168: (SIGENG02) (number) Contact the administrator of your string application.

ORA-35170: (SIGENG03) The "errorname" argument to the SIGNAL command is NA.

ORA-35172: (SNCHILD01) Either there is duplicate information beginning at string, or this information conflicts with a keyword.

Cause: The syntax of the current command was invalid.

Action: Check Oracle OLAP documentation for the correct syntax, and retry.

ORA-35174: (SNSYN100) The word string must be followed by a name.

Cause: The name of an Online Analytical Processing (OLAP) object was expected after the specified word in the command.

Action: Supply the name of an OLAP object and retry.

ORA-35176: (SNSYN101) The format of the AGGMAPINFO function is:\n \n AGGMAPINFO(aggmap-name { RELATIONS | NUMRELS | AGGINDEX | STORE | SHARE | FCACHE | MAPTYPE | { RELATION | PRECOMPUTE | STATUS } expression})

Cause: The syntax of the AGGMAPINFO function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35178: (SNSYN102) The format of the INFILE command is:\n \n INFILE {EOF | filename} [NOW] [NLS_CHARSET name] [TABEXPAND expression]

Cause: The syntax of the INFILE function was invalid.

Action: Check the error message or Oracle documentation for the correct syntax.

ORA-35180: (SNSYN103) The format of the OUTFILE command is:\n \n OUTFILE [APPEND] {EOF | TRACEFILE | filename [NOCACHE] [NLS_CHARSET name]}

Cause: The syntax of the OUTFILE command was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35182: (SNSYN104) The format of the WKSDATA function is:\n \n WKSDATA(worksheetname)

Cause: The syntax of the specified WKSDATA function was invalid.

Action: Check Oracle documentation for the correct syntax.

ORA-35184: (SNSYN105) The dimension name (string) must be followed by one of these keywords: TO, KEEP, ADD, REMOVE, COMPLEMENT, SORT, or INSERT.

Cause: The syntax of the LIMIT command or function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35186: (SNSYN106) The word string must be followed by an argument such as a dimension value.

ORA-35188: (SNSYN107) The word string must be followed by an expression.

Cause: A required expression was missing at the indicated location.

Action: Check Oracle documentation for the correct syntax and retry.

ORA-35190: (SNSYN108) The TOP or BOTTOM value (string) must be followed by the keyword BASEDON or PERCENTOF and an expression.

Cause: A BASEDON or PERCENTOF specification, required when generating a list of TOP or BOTTOM dimension values, was missing from the command.

Action: Supply a BASEDON or PERCENTOF specification. For the correct syntax, see the Oracle documentation.

ORA-35192: (SNSYN109) The dimension name must be followed by a sort order (A or D) and a sort criterion expression.

Cause: The syntax of the SORT command or function was invalid.

Action: Check the error message text. Check the Oracle documentation for the correct syntax.

ORA-35194: (SNSYN110) The format of the INFO function is:\n \n INFO({FORECAST|PARSE|REGRESS|MODEL} choice [index1 [index2 ...]])

Cause: The syntax of the INFO function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35196: (SNSYN111) The format of the CHARLIST function is:\n \n CHARLIST(expression [dimension1 [dimension2 ...]])

ORA-35198: (SNSYN112) The dimension name (string) must be followed by one of these keywords: ADD, BULKRENAME, DELETE, MERGE, MOVE, or RENAME.

Cause: The syntax of the MAINTAIN command was invalid.

Action: Check the error message text or refer to Oracle Database documentation for the correct syntax.

ORA-35200: (SNSYN113) An angle bracket (>) is missing after string.

Cause: The final angle bracket was missing from a list of dimensions or dimension values.

Action: Supply the missing angle bracket. For more information, consult the Oracle documentation.

ORA-35202: (SNSYN114) A right parenthesis or an operator is expected after string.

Cause: The expression could not be interpreted because a closing parenthesis or further expression operator was missing.

Action: For the correct expression syntax, consult the Oracle OLAP documentation.

ORA-35204: (SNSYN115) A label is missing after string.

Cause: The name of PROGRAM label was not found at the indicated location.

Action: Provide the missing label name. For more information, see Oracle OLAP documentation.

ORA-35206: (SNSYN116) The word UNION must be followed by a parenthesized list of LIST clauses.

ORA-35208: (SNSYN117) An expression, SKIP, <, or ACROSS must follow 'string', or this expression conflicts with a keyword.

Cause: The syntax was invalid at the indicated location.

Action: Check the error message text or Oracle documentation for the correct syntax of the command or function where the error occurred.

ORA-35210: (SNSYN118) A colon (:) is required after an ACROSS phrase.

ORA-35212: (SNSYN119) The format of the UNRAVEL function is:\n \n UNRAVEL(expression [dimension1 [dimension2 ...]])

Cause: The syntax of the UNRAVEL function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35214: (SNSYN120) The format of the COMPILE command is:\n \n COMPILE name [NOWARN]

Cause: The syntax of the COMPILE command was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35216: (SNSYN121) The file unit number (string) must be followed by an attribute (such as DATE) and a new value for the attribute.

Cause: The syntax of the FILESET command was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35218: (SNSYN122) The format of LEAD and the LAG functions is:\n \n function(time-series nperiods time-dimension [STATUS|NOSTATUS])

Cause: The syntax of the LAG or LEAD function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35220: (SNSYN123) The format of the EXISTS function is:\n \n EXISTS(text-expression)

Cause: The syntax of the EXISTS function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35222: (SNSYN135) The format of the EXTCHARS function is:\n \n EXTCHARS(text-expression [start [length]])

Cause: The syntax of the EXTCHARS function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35224: (SNSYN136) The format of the EXTLINES function is:\n \n EXTLINES(text-expression [start [length]])

Cause: The syntax of the EXTLINES function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35226: (SNSYN137) The format of the FINDCHARS function is:\n \n FINDCHARS(search-text find-text [start [LINENUM]])

Cause: The syntax of the FINDCHARS function was invalid.

Action: Check the error message text or refer to Oracle documentation for the correct syntax.

ORA-35228: (SNSYN138) The format of the FINDLINES function is:\n \n FINDLINES(search-text find-text)

Cause: The syntax of the FINDLINES function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35230: (SNSYN139) The format of the JOINCHARS function is:\n \n JOINCHARS(text-expression1 text-expression2 ...)

Cause: The syntax of the JOINLINES function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35232: (SNSYN140) The format of the JOINLINES function is:\n \n JOINLINES(text-expression1 text-expression2 ...)

Cause: The syntax of the JOINLINES function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35234: (SNSYN141) The format of the NUMCHARS function is:\n \n NUMCHARS(text-expression)

ORA-35236: (SNSYN142) The format of the NUMLINES function is:\n \n NUMLINES(text-expression)

ORA-35238: (SNSYN143) The format of the UPCASE function is:\n \n UPCASE(text-expression)

Cause: The syntax of the UPCASE function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35240: (SNSYN144) The format of the TEXTFILL function is:\n \n TEXTFILL(text-expression width)

Cause: The syntax of the TEXTFILL function was invalid.

Action: Check the error message text or refer to Oracle documentation for the correct syntax.

ORA-35242: (SNSYN145) The format of the INSCHARS function is:\n \n INSCHARS(text-expression characters [after-position])

Cause: The syntax of the INSCHARS function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35244: (SNSYN146) The format of the INSLINES function is:\n \n INSLINES(text-expression newtext [after-expression])

Cause: The syntax of the INSLINES function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35246: (SNSYN147) The format of the REMCHARS function is:\n \n REMCHARS(text-expression start [length])

Cause: The syntax of the REMCHARS function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35248: (SNSYN148) The format of the REMLINES function is:\n \n REMLINES(text-expression start [length])

Cause: The syntax of the REMLINES function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35250: (SNSYN149) The format of the REPLCHARS function is:\n \n REPLCHARS(text-expression characters [start-position])

Cause: The syntax of the REPLCHARS function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35252: (SNSYN150) The format of the REPLLINES function is:\n \n REPLLINES(text-expression newtext [start-line]).

Cause: The syntax of the REPLLINES function was invalid.

Action: Check the error message text. Use the Oracle documentation for the correct syntax.

ORA-35254: (SNSYN151) The format of the SORTLINES function is:\n \n SORTLINES(text-expression [A|D] [nls_sort [sort-exp]])

Cause: The syntax of the SORTLINES function was invalid.

Action: Check the error message text or refer to Oracle documentation for the correct syntax.

ORA-35256: (SNSYN152) The format of the INLIST function is:\n \n INLIST(text-master text-sublist)

ORA-35258: (SNSYN153) The format of the BLANKSTRIP function is:\n \n BLANKSTRIP(text-expression [LEADING|TRAILING|BOTH])

Cause: The syntax of the BLANKSTRIP function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35260: (SNSYN154) The format of the ARG function is:\n \n ARG(n)\nwhere "n" specifies the number of the argument to be returned.

Cause: The syntax of the ARG function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35262: (SNSYN155) The format of the QUAL function is:\n \n QUAL(expression dimension1 dimvalue [dimension2 dimvalue ...])

Cause: The syntax of the QUAL function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35264: (SNSYN156) The format of the ARGFR function is:\n \n ARGFR(start-arg-no)

Cause: The syntax of the ARGFR function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35266: (SNSYN157) The format of the CONVERT function is:\n \n CONVERT(expression data-type [options])

Cause: The syntax of the CONVERT function was invalid.

Action: Check the error message text or refer to Oracle Database documentation for the correct syntax.

ORA-35268: (SNSYN158) The format of the OBJ function is:\n \n OBJ(choice ['name']) or OBJ(choice [text-expression])

Cause: The syntax of the specified OBJ function was invalid.

Action: Consult the Oracle documentation for syntax and available arguments for the OBJ function.

ORA-35270: (SNSYN159) The format for this type of aggregation function is:\n \n function(expression [[STATUS] dimensions])

Cause: The syntax of the aggregation function was invalid.

Action: Check the Oracle documentation for the correct syntax of the function.

ORA-35272: (SNSYN161) The ROWTOTALS attribute must immediately precede an ACROSS keyword.

ORA-35274: (SNSYN162) The first argument to GET must be a data type or the name of a dimension optionally preceded by the word NEW or VALID.

ORA-35276: (SNSYN163) The format of the ALLOCATE command is:\n \n ALLOCATE varname [SOURCE svarname] [BASIS bvarname [ACROSS dimname]] [TARGET tvarname [TARGETLOG logvarname]] [USING aggmap]

Cause: The syntax of the ALLOCATE command was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax and retry.

ORA-35278: (SNSYN164) A right parenthesis [)] is missing after "string".

ORA-35280: (SNSYN165) The format of the AGGREGATE command is:\n \n AGGREGATE varname1 [varname2 varname3 ...] [USING aggmap-name] [COUNTVAR intvar-name1 [intvar-name2 intvar-name3 ...]] [FUNCDATA] [FORCEORDER] [PARALLEL #] [{FROM|FROMVAR} fromname [, fromname2 ...]]

Cause: The user used incorrect syntax for the AGGREGATE command.

Action: Correct the calling syntax.

ORA-35282: (SNSYN166) The format of the AGGREGATE function is:\n \n AGGREGATE(varname [USING aggmap-name] [COUNTVAR intvar-name] [FORCECALC] [FORCEORDER] [{FROM|FROMVAR} fromname [, fromname2 ...]])

Cause: The user used incorrect syntax for the AGGREGATE function.

Action: Correct the calling syntax.

ORA-35284: (SNSYN167) The format of the IRR function is:\n \n IRR(cashflows time-dimension)

Cause: The syntax of the IRR function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35286: (SNSYN168) The format of the NPV function is:\n \n NPV(cashflows discount-rate time-dimension)

Cause: The syntax of the NPV function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35288: (SNSYN169) The format of a moving function is:\n \n function(expression, start, stop, stepsize, dimension)

Cause: The syntax of the MOVINGAVERAGE, MOVINGTOTAL, MOVINGMIN, or MOVINGMAX function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35290: (SNSYN170) The format of the CUMSUM function is:\n \n CUMSUM(expression [STATUS] dimension [resetdimension])

Cause: The syntax of the CUMSUM function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35292: (SNSYN171) The format of the ISVALUE function is:\n \n ISVALUE(dimension expression)

Cause: The syntax of the ISVALUE function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35294: (SNSYN173) The format of the STATLEN function is:\n \n STATLEN(dimension)

Cause: The syntax of the STATLEN function was invalid.

Action: Check the error message text or refer to Oracle Database documentation for the correct syntax.

ORA-35296: (SNSYN174) The format of the STATLIST function is:\n \n STATLIST(dimension [INTEGER] [width])

Cause: The syntax of the STATLIST function was invalid.

Action: Check the error message text or refer to Oracle documentation for the correct syntax.

ORA-35298: (SNSYN175) The format of the STATFIRST function is:\n \n STATFIRST(dimension)

ORA-35300: (SNSYN176) The format of the STATLAST function is:\n \n STATLAST(dimension)

Cause: The syntax of the STATLAST function was invalid.

Action: Check the error message text or refer to Oracle Database documentation for the correct syntax.

ORA-35302: (SNSYN177) The format of the STATMIN function is:\n \n STATMIN(dimension)

Cause: The syntax of the STATMIN function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35304: (SNSYN178) The format of the STATMAX function is:\n \n STATMAX(dimension)

Cause: The syntax of the STATMAX function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35306: (SNSYN179) The format of the STATVAL function is:\n \n STATVAL(dimension nth-value-to-find [INTEGER])

ORA-35308: (SNSYN180) The format of the STATRANK function is:\n \n STATRANK(dimension [dimension-value])

Cause: The syntax of the STATRANK function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35310: (SNSYN181) The format of the INSTAT function is:\n \n INSTAT(dimension dimension-value)

Cause: The syntax of the INSTAT function was invalid.

Action: Check the error message text and correct the format of the INSTAT function or refer to Oracle documentation for the correct syntax.

ORA-35312: (SNSYN182) The format of the COLVAL function is:\n \n COLVAL(column-number)

Cause: The syntax of the COLVAL function was invalid.

Action: Check the error message text or refer to Oracle documentation for the correct syntax.

ORA-35314: (SNSYN183) The format of the RUNTOTAL function is:\n \n RUNTOTAL(subtotal-number)

Cause: The syntax of the RUNTOTAL function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35316: (SNSYN184) The format of the SUBTOTAL function is:\n \n SUBTOTAL(subtotal-number)

Cause: The syntax of the SUBTOTAL function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35318: (SNSYN185) The format of the INTPART function is:\n \n INTPART(expression)

ORA-35320: (SNSYN186) The format of the SQRT function is:\n \n SQRT(expression).

Cause: The syntax of the SQRT function was invalid.

Action: Check the error message text. Use the Oracle documentation for the correct syntax.

ORA-35322: (SNSYN187) The format of the LOG function is:\n \n LOG(expression)

Cause: The syntax of the LOG function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35324: (SNSYN188) The format of the LOG10 function is:\n \n LOG10(expression)

ORA-35326: (SNSYN189) The format of the ABS function is:\n \n ABS(expression)

Cause: The syntax of the ABS function was invalid.

Action: Check the error message text and correct the syntax, or refer to Oracle documentation for the correct syntax.

ORA-35328: (SNSYN190) The format of the REM function is:\n \n REM(expression1 expression2)

Cause: The syntax of the REM function was invalid.

Action: Check the error message text or refer to Oracle documentation for the correct syntax.

ORA-35330: (SNSYN191) The format of the MIN function is \n \n MIN(expression1 expression2)

Cause: The syntax of the MIN function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35332: (SNSYN192) The format of the MAX function is:\n \n MAX(expression1 expression2)

Cause: The syntax of the MAX function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35336: (SNSYN195) The format of the FILEOPEN function is:\n \n FILEOPEN(filename-expression {READ | WRITE | APPEND} [BINARY] [NLS_CHARSET name])

Cause: The syntax of the FILEOPEN function was invalid.

Action: Check the error message text or refer to Oracle Database documentation for the correct syntax.

ORA-35338: (SNSYN196) The format of the FILEGET function is:\n \n FILEGET(fileunit [LENGTH n])

Cause: The syntax of the FILEGET function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35340: (SNSYN197) The format of the FILEQUERY function is:\n \n FILEQUERY({fileunit-number | filename-expression} attribute)

ORA-35342: (SNSYN198) The format of the SYSVAR function is:\n \n SYSVAR(system-variable-name)

Cause: The syntax of the SYSVAR function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35344: (SNSYN199) The format of the VALUES function is:\n \n VALUES(dimension [STATUS|NOSTATUS] [INTEGER])

Cause: The syntax of the VALUES function was invalid.

Action: Check the error message text, or refer to Oracle documentation for the correct syntax.

ORA-35346: (SNSYN201) The format of the LOWCASE function is:\n \n LOWCASE(text-expression)

Cause: The syntax of the LOWCASE function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35348: (SNSYN202) Invalid format for the FORECAST command.

ORA-35349: (SNSYN203) The format of the BASEVAL function is:\n \n BASEVAL(concat-dimension)

ORA-35350: (SNSYN206) The format of the KEY function is:\n \n KEY(conjoint-dimension, base-dimension)

Cause: The syntax of the KEY function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35351: (SNSYN204) The format of the BASEDIM function is:\n \n BASEDIM(concat-dimension [LEAF])

ORA-35353: (SNSYN205) The format of the MDQUERY function is:\n \n MDQUERY(object-type, schema-name, object-name [, refresh|norefresh])

Cause: The syntax of the MDQUERY function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35355: (SNSYN209) Invalid format for the AW command.

ORA-35356: (SNSYN210) The format of the NUMTODSINTERVAL function is:\n \n NUMTODSINTERVAL(number, day|hour|minute|second)

ORA-35357: (SNSYN211) The format of the NUMTOYMINTERVAL function is:\n \n NUMTOYMINTERVAL(number, year|month)

Cause: The syntax of the NUMTOYMINTERVAL function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35358: (SNSYN214) The format of the NAFILL function is:\n \n NAFILL( source-exp, fill-exp )

Cause: The syntax of the NAFILL function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35360: (SNSYN215) The format of the FILENEXT function is:\n \n FILENEXT(fileunit)

Cause: The syntax of the FILENEXT function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35362: (SNSYN216) The format of the RECNO function is:\n \n RECNO(fileunit)

Cause: The syntax of the RECNO function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35364: (SNSYN217) The format of the ROUND function is:\n \n ROUND(expression1 [, expression2])

Cause: The syntax of the ROUND function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35366: (SNSYN218) The format for exporting an expression is "expression AS name" or "SCATTER AS namevar [ TYPE typevar ]".

ORA-35368: (SNSYN219) The format of the ROW function is:\n \n ROW(list-of-column-descriptions)

Cause: The syntax of the ROW function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35370: (SNSYN220) The format of the AW function is:\n \n AW(subfunction [, analytic workspace-name-expression])

Cause: The syntax of the analytic workspace (AW) function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35372: (SNSYN221) The format of the OBJLIST function is:\n \n OBJLIST[(analytic workspace-list-expression)]

Cause: The syntax of the OBJLIST function was invalid.

Action: Check the error message text or Oracle documentation for the correct syntax.

ORA-35374: (SNSYN222) Invalid UNIQUELINES function syntax.

Cause: The format of the UNIQUELINES function was invalid.

Action: Correct the syntax and try again. The format of the UNIQUELINES function is 'UNIQUELINES(text-expression [nls_sort [sort-exp]])'. For more information, consult Oracle documentation.

ORA-35376: (SNSYN223) invalid JOINCOLS function syntax

Cause: The syntax of the JOINCOLS function was invalid.

Action: Correct the syntax and try again. The format of the JOINCOLS function is 'JOINCOLS(text-expression1 [, text-expression2 ... ])'. For more information, consult Oracle documentation.

ORA-35378: (SNSYN224) The format of the EXTCOLS function is:\n \n EXTCOLS(text-expression [start [length]])

ORA-35380: (SNSYN225) The format of the REMCOLS function is:\n \n REMCOLS(text-expression, start [, length])

ORA-35382: (SNSYN226) Invalid REPLCOLS function syntax.

Cause: The format of the REPLCOLS function was incorrect.

Action: Correct the syntax and try again. The format of the REPLCOLS function is REPLCOLS(text-expression, overlay-expression [, start-position]). For more information, consult Oracle documentation.

ORA-35384: (SNSYN227) The format of the INSCOLS function is:\n \n INSCOLS(text-expression, insert-expression [, after-position])

ORA-35386: (SNSYN228) The format of MCALC is:\n \n MCALC(expression [ALWAYS] [SCREENBY expr] \n [method [OF] member-expr [WEIGHTBY expr]] ...)

ORA-35388: (SNSYN229) Invalid DDOF function syntax.

Cause: The format of the DDOF function was incorrect.

Action: Correct the syntax and try again. The format of the DDOF function is DDOF(expression). For more information, consult Oracle documentation.

ORA-35390: (SNSYN230) Invalid MMOF function syntax.

Cause: The format of the MMOF function was incorrect.

Action: Correct the syntax and try again. The format of the MMOF function is MMOF(expression). For more information, consult Oracle documentation.

ORA-35392: (SNSYN231) Invalid YYOF function syntax.

Cause: The format of the YYOF function was incorrect.

Action: Correct the syntax and try again. The format of the YYOF function is YYOF(expression). For more information, consult Oracle documentation.

ORA-35394: (SNSYN232) The DAYOF function syntax is invalid.

Cause: The format of the DAYOF function was invalid.

Action: Correct the syntax and try again. The format of the DAYOF function is DAYOF(expression). For more information, consult Oracle Database documentation.

ORA-35396: (SNSYN233) Invalid SIN function syntax.

Cause: The format of the SIN function was incorrect.

Action: Correct the syntax and try again. The format of the SIN function is SIN(expression). For more information, consult Oracle documentation.

ORA-35398: (SNSYN234) Invalid COS function syntax.

Cause: The format of the COS function was invalid.

Action: Correct the syntax and try again. The format of the COS function is COS(expression). For more information, consult Oracle documentation.

ORA-35400: (SNSYN235) Invalid MAKEDATE function syntax.

Cause: The format of the MAKEDATE function was invalid.

Action: Correct the syntax and try again. The format of the MAKEDATE function is MAKEDATE(year month day). For more information, consult Oracle documentation.

ORA-35402: (SNSYN236) Invalid ANTILOG function syntax.

Cause: The format of the ANTILOG function was invalid.

Action: Correct the syntax and try again. The format of the ANTILOG function is ANTILOG(expression). For more information, consult Oracle documentation.

ORA-35404: (SNSYN237) Invalid ANTILOG10 function syntax.

Cause: The format of the ANTILOG10 function was invalid.

Action: Correct the syntax and try again. The format of the ANTILOG10 function is ANTILOG10(expression). For more information, consult Oracle documentation.

ORA-35406: (SNSYN238) Invalid ROLLUP command syntax.

Cause: The format of the ROLLUP command was invalid.

Action: Correct the syntax and try again. The format of the ROLLUP command is ROLLUP variable [OVER dimension] [USING relationship]. For more information, consult Oracle documentation.

ORA-35408: (SNSYN239) Invalid STARTOF function syntax.

Cause: The format of the STARTOF function was invalid.

Action: Correct the syntax and try again. The format of the STARTOF function is STARTOF(expression). For more information, consult Oracle documentation.

ORA-35410: (SNSYN240) Invalid ENDOF function syntax.

Cause: The format of the ENDOF function was invalid.

Action: Correct the syntax and try again. The format of the ENDOF function is ENDOF(expression). For more information, consult Oracle documentation.

ORA-35412: (SNSYN241) Invalid BEGINDATE function syntax.

Cause: The format of the BEGINDATE function was incorrect.

Action: Correct the syntax and try again. The format of the BEGINDATE function is BEGINDATE(time-dimension-value). For more information, consult Oracle documentation.

ORA-35414: (SNSYN242) Invalid ENDDATE function syntax.

Cause: The format of the ENDDATE function was invalid.

Action: Correct the syntax and try again. The format of the ENDDATE function is ENDDATE(time-dimension-value). For more information, consult Oracle documentation.

ORA-35416: (SNSYN243) Invalid TCONVERT function syntax.

Cause: The format of the TCONVERT function was invalid.

Action: Correct the syntax and try again. The format of the TCONVERT function is TCONVERT(expression time-dimension method [method]). For more information, consult Oracle documentation.

ORA-35418: (SNSYN244) Invalid FILEERROR function syntax.

Cause: The format of the FILEERROR function was incorrect.

Action: Correct the syntax and try again. The format of the FILEERROR function is FILEERROR(TYPE | POSITION | WIDTH | VALUE | DIMENSION | RESET). For more information, consult Oracle documentation.

ORA-35420: (SNSYN245) Invalid payment or interest function syntax.

Cause: The format of an Oracle OLAP payment or interest function was invalid.

Action: Correct the syntax and try again. The format of a payment or interest function is FUNCTION-NAME(principal, rate, num-payments [time-dimension]). For more information, consult Oracle documentation.

ORA-35422: (SNSYN246) Invalid DEPRSL function syntax.

Cause: The format of the DEPRSL function was invalid.

Action: Correct the syntax and try again. The format of the DEPRSL function is DEPRSL(beg-val, end-val, num-pds, [FULL | HALF | exp, [time-dim]]). For more information, consult Oracle documentation.

ORA-35424: (SNSYN247) Invalid DEPRDECL function syntax.

Cause: The format of the DEPRDECL function was invalid.

Action: Correct the syntax and try again. The format of the DEPRDECL function is DEPRDECL(beg, end, n-pds, [decl-factor, [FULL | HALF | exp, [time dim]]]). For more information, consult Oracle documentation.

ORA-35426: (SNSYN248) Invalid DEPRSOYD function syntax.

Cause: The format of the DEPRSOYD function was invalid.

Action: Correct the syntax and try again. The format of the DEPRSOYD function is DEPRSOYD(beg-val, end-val, num-pds, [FULL | HALF | exp, [time- dim]]). For more information, consult Oracle documentation.

ORA-35428: (SNSYN249) Invalid GROWRATE function syntax.

Cause: The format of the GROWRATE function was invalid.

Action: 4688 // *Action: Correct the syntax and try again. The format of the GROWRATE function is GROWRATE(expression [time dim]). For more information, consult Oracle documentation.

ORA-35430: (SNSYN250) Invalid NORMAL function syntax.

Cause: The format of the NORMAL function was invalid.

Action: Correct the syntax and try again. The format of the NORMAL function is NORMAL(mean, standard-deviation). For more information, consult Oracle documentation.

ORA-35432: (SNSYN251) Invalid DEPRDECLSW function syntax.

Cause: The format of the DEPRDECLSW function was invalid.

Action: Correct the syntax and try again. The format of DEPRDECLSW is DEPRDECLSW(beg-val, end-val, num-pds, [decl-factor, FULL|HALF|exp, [sw-pd, [time dim]]]]). For more information, consult Oracle documentation.

ORA-35434: (SNSYN265) Invalid format for CHGDFN command.

ORA-35436: (SNSYN267) Invalid WEEKOF function syntax.

Cause: The format of the WEEKOF function was invalid.

Action: Correct the syntax and try again. The format of the WEEKOF function is WEEKOF(expression). For more information, consult Oracle documentation.

ORA-35438: (SNSYN268) Invalid PERMIT command syntax.

Cause: The format of the PERMIT command was invalid.

Action: Correct the syntax and try again. The format of the PERMIT command is PERMIT READ|WRITE|MAINTAIN|PERMIT WHEN bool-exp [BY bool-exp]]. For more information, consult Oracle documentation.

ORA-35442: (SNSYN270) invalid PROPERTY command syntax

Cause: The format of the PROPERTY command was incorrect.

Action: Correct the syntax and try again. The format of the PROPERTY command is: PROPERTY {prop-name [,] value} | {DELETE {ALL | prop-name}} For more information, consult Oracle documentation.

ORA-35444: (SNSYN271) invalid TRANSLATEBYTES function syntax

Cause: The format of the TRANSLATEBYTES function was incorrect.

Action: Correct the syntax and try again. The format of the TRANSLATEBYTES function is: TRANSLATEBYTES(text 256-char-table). For more information, consult Oracle documentation.

ORA-35446: (SNSYN274) invalid LIMIT function syntax

Cause: The format of the LIMIT function was invalid.

Action: Correct the syntax and try again. The format of the LIMIT function is: LIMIT(limit arguments) For more information, consult Oracle documentation.

ORA-35448: (SNSYN276) The keyword USING must be followed by a dimension list in angle brackets .

ORA-35450: (SNSYN277) invalid CHANGECHARS function syntax

Cause: The format of the CHANGECHARS function was invalid.

Action: Correct the syntax and try again. The format of the CHANGECHARS function is: CHANGECHARS(text-expr old-text new-text [num-to-change] [UPCASE]) For more information, consult Oracle documentation.

ORA-35456: (SNSYN281) The word string must be followed by an unsigned number.

ORA-35458: (SNSYN282) invalid ARCSIN function syntax

Cause: The format of the ARCSIN function was incorrect.

Action: Correct the syntax and try again. The format of the ARCSIN function is: ARCSIN(expression). For more information, consult the Oracle documentation.

ORA-35460: (SNSYN283) invalid ARCTAN function syntax

Cause: The format of the ARCTAN function was incorrect.

Action: Correct the syntax and try again. The format of the ARCTAN function is: ARCTAN(expression). For more information, consult Oracle documentation.

ORA-35462: (SNSYN284) invalid COSH function syntax

Cause: The format of the COSH function was incorrect.

Action: Correct the syntax and try again. The format of the COSH function is: COSH(expression). For more information, consult Oracle documentation.

ORA-35464: (SNSYN285) Invalid SINH function syntax.

Cause: The format of the SINH function was incorrect.

Action: Correct the syntax and try again. The format of the SINH function is SINH(expression). For more information, consult Oracle documentation.

ORA-35466: (SNSYN286) The format of the TANH function is:\n \n TANH(expression)

ORA-35468: (SNSYN287) Invalid TAN function syntax.

Cause: The format of the TAN function was incorrect.

Action: Correct the syntax and try again. The format of the TAN function is TAN(expression). For more information, consult Oracle documentation.

ORA-35470: (SNSYN288) Invalid ARCCOS function syntax.

Cause: The format of the ARCCOS function was incorrect.

Action: The format of the ARCCOS function is: ARCCOS(expression). Correct the syntax and retry.

ORA-35472: (SNSYN301) invalid MAXCHARS function syntax

Cause: The format of the MAXCHARS function was incorrect.

Action: Correct the syntax and try again. The format of the MAXCHARS function is MAXCHARS(text-expression). Refer to Oracle Database documentation for additional information.

ORA-35474: (SNSYN305) The format of the STATALL function is:\n \n STATALL(dimension)

ORA-35476: (SNSYN306) invalid EXTBYTES function syntax

Cause: The format of the EXTBYTES function was invalid.

Action: Correct the syntax and try again. The format of the EXTBYTES function is: EXTBYTES(text-expression [start [length]]). For more information, consult Oracle documentation.

ORA-35478: (SNSYN307) The format of the FINDBYTES function is:\n \n FINDBYTES(search-text find-text [start [LINENUM]])

ORA-35480: (SNSYN308) The format of the JOINBYTES function is:\n \n JOINBYTES(text-expression1 text-expression2 ...)

ORA-35482: (SNSYN309) The format of the NUMBYTES function is:\n \n NUMBYTES(text-expression)

ORA-35484: (SNSYN310) The format of the INSBYTES function is:\n \n INSBYTES(text-expression bytes [after-position])

ORA-35486: (SNSYN311) The format of the REMBYTES function is:\n \n REMBYTES(text-expression start [length])

ORA-35488: (SNSYN312) The format of the REPLBYTES function is:\n \n REPLBYTES(text-expression bytes [start-position])

ORA-35490: (SNSYN313) The format of the CHANGEBYTES function is:\n \n CHANGEBYTES(text-expression oldtext newtext [number-to-change])

ORA-35492: (SNSYN314) invalid MAXBYTES function syntax

Cause: The format of the MAXBYTES function was invalid.

Action: Correct the syntax and try again. The format of the MAXBYTES function is: MAXBYTES(text-expression). For more information, consult the Oracle documentation.

ORA-35494: (SNSYN315) The word ACROSS must be followed by a dimension name.

ORA-35496: (SNSYN316) The format of the FILTERLINES function is:\n \n FILTERLINES(source-exp, filter-exp)

ORA-35498: (SNSYN318) The format of the DBGOUTFILE command is:\n \n DBGOUTFILE [APPEND] {EOF | filename [NOCACHE]}

ORA-35500: (SNSYN319) The format of the OBSCURE function is:\n \n OBSCURE ({HASH | HIDE | UNHIDE | ENCRYPT} [, TEXT],\n seed-text, input-text)

ORA-35502: (SNSYN324) INSERT must be followed by FIRST, LAST, BEFORE dimension-value, or AFTER dimension-value.

ORA-35504: (SNSYN325) Invalid IMPORT command syntax.

Cause: There was an error in the syntax of the IMPORT command.

Action: Check Oracle documentation for command syntax and retry.

ORA-35508: (SNSYN329) invalid SYSINFO function syntax

Cause: The syntax of the SYSINFO function was incorrect.

Action: Correct the syntax and try again. The format of the SYSINFO function is 'SYSINFO(user|uid|roles|profiles|hostname|termname|pid| progname|osuser|chostname|cosuser|instname)'

ORA-35510: (SNSYN330) The format of the CATEGORIZE function is:\n \n CATEGORIZE(expression {group literal list | group expression})

ORA-35512: (SNSYN331) The format of the CORRELATION function is:\n \n CORRELATION(expression1, expression2, method, [BASEDON dimension1 [dimension2 ...]])

ORA-35514: (SNSYN332) The format of the MODE function is:\n \n MODE(expression, BASEDON dimension)

ORA-35516: (SNSYN333) The format of the PERCENTAGE function is:\n \n PERCENTAGE(expression [BASEDON dimension1 [dimension2 ...]])

ORA-35518: (SNSYN334) The format of the RANK function is:\n \n RANK(expression, method, BASEDON dimension)

ORA-35520: (SNSYN335) The format of the SMOOTH function is:\n \n SMOOTH(expression, method, parameters [BASEDON dimension1 [dimension2 ...]])

ORA-35522: (SNSYN336) The format of the NLSITEMS function is:\n \n NLSITEMS({LANGUAGE | TERRITORY})

ORA-35524: (SNSYN337) The format of the NLSAVAIL function is:\n \n NLSAVAIL({LANGUAGE | TERRITORY} itemname)

ORA-35526: (SORTENG10A) The expression for TOP or BOTTOM has a value of NA.

ORA-35528: (SORTENG10B) negative number of dimension values (number) requested in the TOP or BOTTOM phrase

Cause: There was a negative number of dimension values requested in the TOP or BOTTOM phrase. The TOP or BOTTOM phrase only support positive dimension values.

Action: Change your TOP or BOTTOM phrase to only use positive dimension values.

ORA-35529: (SORTENG10D) You cannot sort more than 2**31 - 1 values.

Cause: The product of the status lengths of the base dimensions exceeded the maximum integer value.

Action: Use fewer base dimensions or reduce the status lengths of the base dimensions.

ORA-35530: (SORTENG10C) Cannot specify a percentage greater than 100 or less than 0. Percentage number requested.

Cause: A percentage greater than 100 or less than 0 was specified.

Action: Percent must be a number between 0 and 100.

ORA-35532: (SPSFILE1) The file you specified is not in string format.

ORA-35534: (SPSFILE2) string files require worksheets with only two dimensions.

ORA-35536: (SPSFILE3) PRN files require worksheets with only two dimensions.

ORA-35538: (SPSIDIF01) A record (string) that was not in DIF format was read while importing file string.

ORA-35540: (SPSIWKS1) An unexpected end-of-file occurred in spreadsheet file string. Check your data to make sure you imported all you expected.

ORA-35542: (SPSRREC01) An unexpected end-of-file occurred while importing file string. Check your data to make sure you imported all you expected.

ORA-35544: (SQA03) The SQL data in column number of your fetch statement cannot be converted to type string.

ORA-35548: (SQCGEXE01) SQL statement-name 'string' has not been prepared in the current program.

ORA-35550: (SQCGOPN01) SQL cursor 'string' has not been declared in the current program.

ORA-35554: (SQCSRNAM00) SQL cursor name 'number' has an invalid length of number. A cursor name must have a length of 1 to 18 bytes, inclusive.

ORA-35556: (SQCSRNAM01) SQL cursor name 'number' has an invalid first character. Use a-z, @, # or $.

ORA-35558: (SQCSRNAM02) SQL cursor name 'number' contains an invalid character. Use a-z, 0-9, @, #, $ and _.

ORA-35559: (SQCSRNAM03) SQL cursor name cannot be INTO.

ORA-35560: (SQGETCD01) Conjoint dimension workspace object cannot be an input host variable. You can use the current values of its bases via the KEY function.

ORA-35561: (XSRWLD01) Object workspace object is not a valid target.

Cause: An invalid object was specified as a target.

Action: Choose a valid object as a target.

ORA-35562: (SQLIMP01) The SQL IMPORT command will produce number columns of output, but you have provided number host variables in your INTO clause.

Cause: The expression is the source query do not match the targets in the INTO clause.

Action: Make sure the the expressions in the source query match the targets in the INTO clause.

ORA-35563: (XSRWLD17) Multiple values exist for an attribute of this dimension member.

Cause: Multiple source table rows containing different values for a dimension attribute were found. Only the first of the multiple rows has been loaded.

Action: Fix the mapping or remove the rows with conflicting attribute values.

ORA-35564: (XSRWLD02) Cannot convert from the string type to the string type.

Cause: Conversion from source to target is not allowed

Action: Choose a different target datatype

ORA-35565: (XSRWLD03) For object workspace object only APPEND, MATCH or ASSIGN may be used.

Cause: An incorrect setting was applied to the target

Action: For DIMENSIONs use APPEND or MATCH, for SURROGATEs use ASSIGN.

ORA-35566: (XSRWLD04) Object workspace object cannot be used with QDRs

Cause: A QDR was placed on a target dimension

Action: Remove the QDR on the target dimension

ORA-35568: (SQLIMP03) The datatype of variable number should be INTEGER, LONGINTEGER or SHORTINTEGER.

Cause: The target variable was not INTEGER, LONGINTEGER or SHORTINTEGER.

Action: The target variable must be INTEGER, LONGINTEGER or SHORTINTEGER.

ORA-35569: (XSRWLD05) An error was encountered in converting data string to string in column number.

Cause: The data could not be converted to the target datatype.

Action: Ensure the source data is valid for the target datatype.

ORA-35570: (XSRWLD06) A column value is not a valid member of its target dimension.

Cause: The source value for a dimension is not an existing member of the dimension.

Action: Ensure the column value is an existing member of its target dimension.

ORA-35571: (XSRWLD07) The maximum number of load errors has occurred. No changes from this step were committed to the database.

Cause: The number of load errors exceeded the specified maximum.

Action: Fix the load errors, or increase the maximum number allowed and rerun the load.

ORA-35572: (XSRWLD08) A column value is not a valid member of its related dimension.

Cause: The source data for a relation is not a member of the related dimension.

Action: Ensure the source data is a valid member of the related dimension.

ORA-35573: (XSRWLD09) An incoming dimension value is null.

Cause: A source value for a dimension is null.

Action: Ensure the source data for the dimension is not null.

ORA-35574: (SQLOUT02) SQL cursor 'number' is not known in the current logical unit of work.

ORA-35575: (SQLOUT04) The string command will produce number columns of output, but you have provided number host variables in your INTO clause.

ORA-35576: (SQLOUT09) SQL cursor 'number' is not open.

ORA-35577: (SQLOUT10) SQL cursor 'number' has already been declared with a different SELECT statement.

ORA-35578: (SQLOUT11) SQL cursor 'number' cannot be used with CURRENT OF cursor name syntax

Cause: The CURRENT OF cursor syntax in the WHERE clause tried to use a cursor that was not declared with the FOR UPDATE [ of column name ] SQL syntax.

Action: Add the FOR UPDATE [ OF column name ] SQL syntax to the cursor specified.

ORA-35579: (SQLOUT12) SQL cursor 'number' has already been opened.

ORA-35580: (XSRWLD10) An incoming column contains a data type mismatch.

Cause: The data could not be converted to the target datatype.

Action: Ensure the source data is valid for the target datatype.

ORA-35581: (XSRWLD11) You do not have permission to write this value of the target.

Cause: You do not have sufficient permissions to write to the specified target.

Action: Ask the owner of the schema or OLAP DBA to grant you sufficient permissions.

ORA-35582: (XSRWLD12) Cannot change the level of dimension member "number" from "number" to "number" within a single load.

Cause: A dimension member is mapped to more than one level.

Action: Change the mapping so that each dimension member is mapped to only one level.

ORA-35583: (XSRWLD13) Cannot change the level of a dimension member within a single load.

Cause: A dimension member is mapped to more than one level.

Action: Change the mapping so that each dimension member is mapped to only one level.

ORA-35584: (SQLOUT17) The string procedure requires number parameters.

ORA-35585: (XSRWLD14) This SQL query generated rejected records.

Cause: Rejected records were generated by this query.

Action: Locate the records that were rejected and resolve the rejection (for example, data, mapping, and so on).

ORA-35586: (SQLOUT19) The parameter list passed to the procedure is syntactically incorrect.

ORA-35587: (SQLOUT20) The nesting of table functions and SQL commands has exceeded the maximum of number levels.

Cause: The nesting of table functions with the PREDMLCMD token populated with an OLAP DML expression that use the embedded SQL support to access another table function which contains a table functions with the PREDMLCMD token filled in with an OLAP DML expression that uses the embedded SQL support.

Action: Reduce the level of nesting between table functions and OLAP DML embedded SQL support.

ORA-35588: (XSRWLD15) Cannot change the parent of existing dimension member "number" from "number" to "number" in LOAD RETAIN mode.

Cause: An attempt was made to change the parent of an existing dimension member in LOAD RETAIN mode.

Action: Fix the mapping or use LOAD [NO] SYNCH mode.

ORA-35589: (XSRWLD16) Cannot change the parent of an existing dimension member in LOAD RETAIN mode.

Cause: An attempt was made to change the parent of an existing dimension member in LOAD RETAIN mode.

Action: Fix the mapping or use LOAD [NO] SYNCH mode.

ORA-35590: (SQPHRASE01) The host variable expression has invalid syntax.

ORA-35592: (SQRT00) The argument to SQRT is negative. Set ROOTOFNEGATIVE to YES if you want NA to be returned for the root of a negative number.

ORA-35594: (SSCGEXP01) The LIMIT criterion expression must be dimensioned by workspace object.

Cause: The LIMIT criterion did not have the dimension that LIMIT requires.

Action: If the target is a VALUESET, check its VALUESET attribute.

ORA-35596: (SSCGEXP02) The LIMIT criterion expression must be dimensioned by workspace object, which is a component of workspace object.

Cause: The LIMIT criterion expression was not a dimension of all the base dimensions of the composite.

Action: Use a LIMIT criterion that is dimensioned by all the base dimensions of the composite.

ORA-35600: (SSCGLIMT01) The IFNONE label is not allowed when you specify NULL status.

Cause: The LIMIT to NULL IFNONE label was specified which is not allowed.

Action: Use GOTO, if that is the desired behavior.

ORA-35602: (SSCGLIMT02) You cannot limit dimension composite workspace object.

Cause: The LIMIT of composite dimensions was specified which is not allowed.

Action: If a limit is required, then specify the limit in the base dimensions // of the composite dimension.

ORA-35603: (SSCGLIMT03) You cannot limit PARTITION TEMPLATE workspace object.

ORA-35604: (SSCGNULL01) The phrase "IFNONE label" can only be used when the LIMIT command executes in a program.

Cause: This specified command was not used in a program.

Action: Use this command in a program to intercept NULL status.

ORA-35606: (SSCGNULL02) string is not defined as a label.

Cause: The IFNONE label did not exist.

Action: Change the program to add the label or correct its spelling.

ORA-35610: (SSCGREL01) workspace object and workspace object are not related.

Cause: The target and source dimensions were not related.

Action: Choose a related dimension.

ORA-35612: (SSCGREL02) Related dimension values are not allowed when you specify a scalar or multi-dimensional relationship array.

ORA-35614: (SSCGREL03) workspace object is not a relationship involving workspace object.

ORA-35622: (SSCGREL07) workspace object is not a relation of workspace object.

Cause: The RELATION argument to LIMIT was not valid.

Action: Find a relation with the correct RELATION attribute.

ORA-35623: (XSSCLLEV07) workspace object is not a VALUESET of workspace object.

Cause: LEVELREL expected a VALUESET of the dimension argument.

Action: Use a VALUESET of the target dimension.

ORA-35624: (SSCGREL08) workspace object is not dimensioned by workspace object.

Cause: This relation was not a valid self relation for the target dimension.

Action: Find or create a valid self relation.

ORA-35625: (XSSCLLEV08) workspace object is not dimensioned by workspace object.

Cause: The relation was not a valid LEVELREL for target dimension.

Action: Use a valid LEVELREL.

ORA-35626: (SSCGREL09) workspace object is not related to itself.

ORA-35627: (XSSCLEV09) workspace object is not a relationship array.

Cause: LIMIT or SORT expected a RELATION name.

Action: Fix the RELATION argument to LIMIT or SORT.

ORA-35628: (SSCGREL10) workspace object is not a dimension of relation workspace object.

Cause: A dimension of the relation or its relation dimension was expected.

Action: Describe the relation and choose the one of its dimensions.

ORA-35629: (XSBASLIM00) workspace object does not have base dimensions.

ORA-35630: (SSCGREL11) While limiting dimension workspace object, it was used to qualify relation workspace object.

Cause: The target dimension was used to qualify a relation while it was being limited.

Action: Remove this clause from the LIMIT command.

ORA-35632: (SSCGREL12) While limiting an alias of workspace object, it was used to qualify relation workspace object.

Cause: The target dimension was used to qualify a relation.

Action: Remove this clause from the LIMIT command.

ORA-35633: (STATEQ01) Both arguments to STATEQUAL must be status lists of the same dimension.

Cause: The arguments are status lists of different dimensions.

Action: Use two status lists of the same dimension.

ORA-35634: (SSCGVALS01) The format of a related dimension list is:\n related-dimension [valuelist] | relationship-array-name

Cause: Incorrect syntax was used to specify a relate-dimension list.

Action: Consult Oracle Documentation for correct syntax of related- dimension lists.

ORA-35636: (SSCGVALS02) workspace object is a dimension composite and its position numbers cannot be used in LIMIT NOCONVERT.

ORA-35640: (SSEXECUT03) You cannot MAINTAIN ADD workspace object while it is being LIMITed.

ORA-35642: (SSEXECUT07A) The expression for the beginning of the dimension range has a value of NA.

Cause: The values for the beginning and ending of a dimensions range need to be non-NA values.

Action: Fix the caller to check for NA values.

ORA-35644: (SSEXECUT07B) The expression for the end of the dimension range has a value of NA.

Cause: The values for the beginning and ending of a dimensions range must be non-NA values.

Action: Fix the caller to check for NA values.

ORA-35646: (SSEXECUT08) The expression for BEFORE or AFTER has a value of NA.

Cause: The BEFORE or AFTER value is NA.

Action: Fix the caller to supply a correct value.

ORA-35648: (SSEXECUT09) The expression for FIRST or LAST has a value of NA.

Cause: LIMIT did not allow NA values for FIRST or LAST.

Action: Either test the value before using LIMIT or fix the expression to exclude NA values.

ORA-35650: (SSEXECUT15) The expression for BEFORE or AFTER is not in current status.

Cause: BEFORE and AFTER must be followed by a value in current status.

Action: Fix the BEFORE or AFTER expression.

ORA-35652: (SSFRLST01) In the FIRST or LAST phrase, you requested a negative number of dimension values (number).

ORA-35654: (SSNULL) The status of the workspace object dimension cannot be set to null.

ORA-35656: (STATCHK00) workspace object has no values in status.

ORA-35658: (STATLIST01) The data width argument to the STATLIST function must be greater than zero.

ORA-35660: (STATVAL03) The workspace object dimension does not have a status value numbered number.

ORA-35662: (STKTOINF01) The width argument to the CONVERT(... INFILE) function was number. The limit is number.

ORA-35664: (STKTOINF02) Conversion to INFILE would produce a value number bytes wide, exceeding the maximum input line length number.

ORA-35666: (STRBYT01) NTEXT arguments to the BYTE functions must be converted to TEXT. Use CONVERT(value TEXT NOTRANSLATE) to avoid translation.

ORA-35668: (STRCHG01) The oldtext and newtext arguments must be single-line text values.

ORA-35670: (STRCHG02) The oldtext argument must contain at least one character.

ORA-35672: (STRCHG03) The number-to-change argument must be greater than 0.

ORA-35674: (STRDEL01) The position of the first character to remove must be at least 1.

ORA-35676: (STRDEL02) You must remove at least one character. You cannot remove number characters.

ORA-35678: (STREXTR01) The position of the first character to extract must be greater than zero. You cannot start extracting at position number.

ORA-35680: (STREXTR02) You must extract at least one character. You cannot extract number characters.

ORA-35682: (STRFIND01) The start argument must be at least 1.

ORA-35684: (STRINS01) Insertion must begin after a character position of zero or greater.

ORA-35686: (STRINS02) The length of one line of a text value cannot exceed number characters. You attempted to create a line with number characters.

ORA-35688: (STRREP01) The position of the first character to replace must be at least 1.

ORA-35690: (SUBGONE00) You have requested a feature or used a command that is not supported in this release.

ORA-35692: (TDENDPT00) Dimension workspace object is empty.

ORA-35694: (TDINCNUM00) You attempted to work with a date outside of the allowable range.

ORA-35696: (TEXTFENG01) The data width argument to the TEXTFILL function must be greater than zero.

ORA-35698: (TFGROUP01) Dimension workspace object appears in more than one GROUP phrase, either directly or via a dimension composite or conjoint dimension.

ORA-35700: (TFGROUP02) An expression used in a GROUP phrase must have exactly one dimension.

ORA-35702: (TFPARSE01) Dimension workspace object appears in both the DOWN phrase and a GROUP phrase, either directly or via a conjoint dimension or composite.

ORA-35704: (TFPARSE02) Dimension workspace object appears in both the DOWN phrase and an ACROSS phrase, either directly or via a conjoint dimension or composite.

ORA-35706: (TFPARSE03) Dimension workspace object appears both inside and outside an ACROSS loop.

ORA-35708: (TFPARSE04) The expressions used in the DOWN phrase must all have the same single dimension.

ORA-35710: (TFPARSE05) The DOWN phrase must be a single expression or a list of expressions enclosed in angle brackets .

ORA-35712: (TFPARSE07) Dimension workspace object appears in both an ACROSS phrase and a GROUP phrase, either directly or via a conjoint dimension or composite.

ORA-35716: (TRIGGER00) NA trigger calls exceed the maximum allowable depth of number.

ORA-35718: (TRIGGER01) The NA trigger expression for variable workspace object contains a format error.

ORA-35720: (TRIGGER02) The NA trigger for workspace object could not be executed recursively because the RECURSIVE option is set to NO.

ORA-35726: (TSFENG01) The starting point (number) for a moving function must be less than or equal to the stopping point (number).

ORA-35728: (TSFENG02) The step value (number) for a moving function must be greater than zero.

ORA-35730: (TSFENG03) The starting point, stopping point, and step value for a moving function cannot be NA.

ORA-35732: (UNITCHEK01) number is an invalid file unit number.

ORA-35734: (UNITCHEK02) File unit number is not open.

ORA-35736: (VALNAME01) You cannot define NAME. NAME is a special reserved dimension used to organize your analytic workspace dictionary.

ORA-35738: (VCLEX01) "number" is not a valid dimension value because it contains invalid characters or blanks, but it is not enclosed in single quotes.

ORA-35740: (VCLEX02) string is too large to be an integer.

ORA-35742: (VCLEX06) number already exists in the string analytic workspace.

ORA-35744: (VCLEX07) "number" is not a valid name because it contains invalid characters or blanks.

ORA-35746: (VCLEX08) string is too large to be a short integer.

ORA-35748: (VCOVRFLW01) A text value cannot be more than number characters long. Your value is number characters long.

ORA-35749: (VCHEX01) 'character' is not a valid hexadecimal digit.

Cause: The text being converted contains an invalid hexadecimal digit.

Action: Replace the character with a digit in the range 0-9 or A-F.

ORA-35750: (VCTOBOOL01) A multiline text value cannot be converted to a BOOLEAN.

ORA-35752: (VCTODT00) 'string' is not a valid date order. Valid orders are YMD, YDM, MYD, MDY, DMY, and DYM.

ORA-35754: (VCTODT01) 'number' is not a valid date because number is out of range for a month.

ORA-35756: (VCTODT02) 'number' is not a valid date because number is out of range for a year.

Cause: n'%1p'

Action: n/a

ORA-35758: (VCTODT03) 'number' is not a valid date because number is out of range for a day of the month.

Cause: The numeric value of day was invalid for this year and month.

Action: Specify a valid numeric value in day for the specified year and month. Then, retry the operation.

ORA-35760: (VCTODT04) 'number' is not a valid date because it is ambiguous.

ORA-35762: (VCTODT05) 'number' is not a valid packed numeric date.

ORA-35764: (VCTODT06) 'number' is not a valid date.

ORA-35766: (VCTODT07) 'number' is not a valid date or name for the workspace object dimension.

ORA-35768: (VCTODT08) 'number' is not a valid name for workspace object, because the period number is out of range.

Cause: The wrong number days, weeks or months in a year was specified.

Action: Correct the first word in this error to be a valid date.

ORA-35770: (VCTODT15) 'number' is not a valid date. The numeric field 'string' cannot be interpreted.

ORA-35772: (VCTODT16) 'number' is not a valid date. 'string' is the second year field encountered.

Cause: Two year fields were entered.

Action: Remove the second year field.

ORA-35774: (VCTODT17) 'number' is not a valid date. A second alphabetic field, 'string', is not allowed.

Cause: The date contains two values for month.

Action: Enter a single valid date.

ORA-35776: (VCTODT18) 'number' is not a valid date. A date cannot end with a separation character.

ORA-35778: (VCTODT19) 'number' is not a valid date. Input after 'string' is extra.

ORA-35780: (VCTODT20) A date cannot be an empty string.

ORA-35782: (VCTODT21) 'number' is not a valid date because it is incomplete.

ORA-35784: (VCTODT22) 'number' is not a valid date. Packed numeric notation must be 6 or 8 digits long.

ORA-35786: (VCTODT23) 'number' is not a valid date. 'string' cannot be recognized as a month name.

Cause: An invalid month name was specified.

Action: Specify a valid month name.

ORA-35788: (VCTODT24) 'number' is not a valid date. There are too many leading zeros beginning at 'string'.

ORA-35790: (VCTODT25) 'number' is not a valid date. A date cannot begin with 'string'.

Cause: The date was invalid. Valid dates cannot begin with the specified characters.

Action: Use a correct date value.

ORA-35792: (VCTODT27) 'number' is not a valid date. 'string' is not a valid character.

ORA-35794: (VCTORD01) A multiline text value cannot be converted to a number.

ORA-35796: (VERFAIL01) Your response does not meet the requirements for this item.

ORA-35798: (VERFAIL02) string

ORA-35800: (VSDOKAY01) Discarding compiled code for workspace object, because number now resolves to a value of workspace object. Previously, it resolved to a value of workspace object.

ORA-35802: (VSDOKAY02) Discarding compiled code for workspace object, because number is no longer a value of workspace object.

ORA-35804: (WATCHXEQ01) Watch point number: number is true in workspace object at statement:

ORA-35810: (XSINPUTERR) The command has requested more input than was supplied in the command string.

Cause: The command required input that was not supplied in the string.

Action: Reexecute the command with the required input.

ORA-35812: (XSACROSS01) The string command cannot be executed by ACROSS.

ORA-35818: (XSCAT01) Group definition values cannot be NA.

ORA-35820: (XSCAT02) Each group definition value must be greater than its predecessor.

ORA-35822: (XSCGCAT01) The source expression must be numeric.

ORA-35824: (XSCGCAT02) The group expression must be numeric.

ORA-35826: (XSCGCAT03) The group expression must be one-dimensional.

ORA-35828: (XSCGCORR01) Data expressions must be numeric.

ORA-35830: (XSCGCORR02) BASEDON names must be dimensions.

ORA-35832: (XSCGCORR03) BASEDON names must be dimensions of both data expressions.

ORA-35834: (XSCGCORR04) You have named duplicate BASEDON dimensions.

ORA-35836: (XSCGCORR05) The two expressions must have at least one common dimension.

ORA-35838: (XSCGMODE01) The data expression must be numeric.

ORA-35840: (XSCGMODE02) BASEDON names must be dimensions.

ORA-35842: (XSCGMODE03) BASEDON names must be dimensions of the data expression.

ORA-35844: (XSCGMODE04) You have named duplicate BASEDON dimensions.

ORA-35846: (XSCGPCTAGE01) The data expression must be numeric.

Cause: The data expression was not numeric.

Action: Correct the data expression to be numeric.

ORA-35848: (XSCGPCTAGE02) BASEDON names must be dimensions.

ORA-35850: (XSCGPCTAGE03) BASEDON names must be dimensions of the data expression.

ORA-35852: (XSCGPCTAGE04) You have named duplicate BASEDON dimensions.

ORA-35854: (XSCGRANK01) The data expression must be numeric.

ORA-35856: (XSCGRANK02) BASEDON names must be dimensions.

Cause: BASEDON was not followed by the name of a dimension.

Action: Use a dimension name.

ORA-35858: (XSCGRANK03) BASEDON names must be dimensions of the data expression.

ORA-35860: (XSCGRANK04) You have named duplicate BASEDON dimensions.

ORA-35862: (XSCGSMOOTH01) The data expression must be numeric.

ORA-35864: (XSCGSMOOTH02) You have not supplied enough smoothing parameters.

ORA-35866: (XSCGSMOOTH03) The smoothing parameters must be numeric.

ORA-35868: (XSCGSMOOTH04) BASEDON names must be dimensions.

Cause: BASEDON must be followed by the name of a dimension.

Action: Use a dimension name.

ORA-35870: (XSCGSMOOTH05) BASEDON names must be dimensions of the data expression.

ORA-35872: (XSCGSMOOTH06) You have named duplicate BASEDON dimensions.

ORA-35874: (XSFCAST01) The string forecasting option cannot be set.

ORA-35876: (XSFCAST02) You must use an INTO phrase to specify an output location for the forecast results.

ORA-35878: (XSFCAST03) The string forecasting option cannot be queried.

ORA-35880: (XSFCAST04) You cannot specify a trial number when querying the string forecasting option.

ORA-35882: (XSFCAST05) You must specify a trial number when querying the string forecasting option.

ORA-35884: (XSFCAST06) The forecasting context handle cannot be NA.

ORA-35886: (XSFCAST07) The time dimension workspace object has number values in status. The limit is number.

ORA-35888: (XSFCAST08) The time dimension workspace object has no values in status.

ORA-35890: (XSFCAST09) The time dimension workspace object has only number values in status. You cannot specify number historical periods.

ORA-35892: (XSFCAST10) The string target variable must also be dimensioned by string.

ORA-35894: (XSFCAST11) string must be less than or equal to string. The current values are number and number, respectively.

ORA-35896: (XSFCAST12) The value of string must evenly divide the difference between MIN and MAX values. The current values are number, number, and number.

ORA-35898: (XSFCAST13) The trial number for querying string cannot be NA.

ORA-35900: (XSFCAST14) number is not the handle of an open forecasting context.

ORA-35902: (XSFCAST15) You cannot specify an NA value for string.

ORA-35904: (XSFCAST16) Values of string must be between number and number. You specified number.

ORA-35906: (XSFCAST17) Values of string must be between number and number. You specified number.

ORA-35908: (XSFCAST18) 'number' is not a recognized value of string.

ORA-35910: (XSFCAST19) The forecasting context number has been invalidated because one or more of the extra dimensions of the time-series expression is no longer available.

ORA-35912: (XSFCAST20) A forecasting context identified by the text 'string' already exists. Its handle is number.

ORA-35914: (XSFCAST21) Values of the TRADINGDAYS expression cannot be less than or equal to zero.

ORA-35916: (XSHIDE01) workspace object is not a program or model.

ORA-35917: (XSHIDE05) Cannot HIDE model workspace object because the analytic workspace in which it is defined has not been upgraded to version string.

Cause: An attempt was made to apply the HIDE command to a model in an analytic workspace that was not upgraded to the necessary compatibility level.

Action: Ensure that the database is running in the appropriate compatibility mode, and upgrade the analytic workspace.

ORA-35918: (XSHIDE02) You do not have access to workspace object.

Cause: Permission to read the text of the named object was not granted.

Action: Acquire the necessary READ permission on the object and retry the command.

ORA-35919: (XSHIDE06) The encryption seed text for string must be at least number characters in length.

Cause: Seed text shorter than the minimum required length was specified.

Action: Specify seed text that is at least as long as the length specified.

ORA-35920: (XSHIDE03) The encryption seed for HIDE and UNHIDE must be a non-empty, one-line TEXT value.

ORA-35922: (XSHIDE04) workspace object is already hidden.

ORA-35924: (XSMOOTH01) Smoothing parameters cannot be NA.

ORA-35926: (XSMOOTH02) Smoothing constants must be between 0 and 1.

ORA-35928: (XSMOOTH03) Cannot compute valuespace offset

ORA-35930: (XSPCTAGE01) Cannot compute valuespace offset

ORA-35932: (XSPGFTCH01) Analytic workspace string is not attached.

ORA-35934: (XSPGFTCH02) No fetch analytic workspace specified

ORA-35950: (OBSCURE01) The seed expression argument to OBSCURE cannot be NA.

ORA-35951: (OBSCURE02) The ENCRYPT option of OBSCURE is not supported at the current compatibility level.

Cause: An attempt was made to use the ENCRYPT option of the OBSCURE function, which is not supported for a compatibility level earlier than 12.2.0.2.

Action: Raise the compatibility level or choose a different OBSCURE option.

ORA-35952: (XSSPFC01) The string dimension workspace object and the string dimension workspace object must have the same number of values in status for SPFCEXEC method number.

Cause: This method requires the named dimensions to have the same number of values in status, but the user provided statuses of different lengths.

Action: Relimit the dimensions so that their status lengths are the same.

ORA-35958: (XSPGREPORT01) Of number allocated pages number are currently in use, number are available for use, number are hard-locked, and number are soft-locked.

ORA-35964: (COPYDFN01) You must have a current analytic workspace to perform a COPYDFN.

ORA-35966: (COPYDFN02) The format of the COPYDFN command is:\n\n COPYDFN newname oldname.

ORA-35968: (COPYDFN03) Analytic workspace object %1 does not exist.

ORA-35970: (COPYDFN05) You cannot copy the definition of an OPTION.

ORA-35972: (COPYDFN06) %1 is an invalid name for an analytic workspace object.

ORA-35974: (DBDESC00) There are no objects in this analytic workspace.

ORA-35976: (DBDESC01) Last updated: %1 Time: %2

ORA-35980: (DBDESC03) %1 contains:

ORA-35986: (DBDESC06) Description of %1 objects

ORA-35988: (DBDESC07) Description of PROGRAM %1

ORA-35990: (DBDESC08) Description of MODEL %1

ORA-35992: (DBDESC09) (Cont'd)

ORA-35994: (DBDESC10) Page

ORA-35996: (DBDESC11) Analytic Workspace:

ORA-35998: (DBDESC12) Updated:

ORA-36000: (DBDESC13) At:

ORA-36004: (DBDESC15) TYPE

ORA-36006: (DBDESC16) DESCRIPTION

ORA-36008: (DBDESC17) Analytic Workspace Listing

ORA-36010: (DBDESC18) Page

ORA-36017: (XSHIERCK10) The definition of hierarchy workspace object over number in level number is not star consistent. The collision parents include number.

Cause: The definition of the hierarchy was not star consistent.

Action: Change the definition of the hierarchy.

ORA-36018: (XSHIERCK02) The format of the HIERCHECK command is:\n\n HIERCHECK relation [STATUS|NOSTATUS|valueset] [MULTIPATH] [CONSISTENT] [{BALANCED|STAR_CONSISTENT} levelrelation] \nOr\n HIERCHECK aggmap [MULTIPATH] [CONSISTENT]

Cause: The wrong object type was specified.

Action: Change the object to a RELATION or AGGMAP.

ORA-36019: (XSHIERCK11) The format of the HIERSHAPE function is:\n\n HIERSHAPE(relation[(qdr)] {level|ragged|skiplevel|regular} USING levelrel [INHIERARCHY inhvs] LEVELORDER levelvs)

Cause: The wrong object type or the wrong object definition was specified.

Action: Change the object type or use the correct object definition.

ORA-36020: (XSHIERCK03) The definition of hierarchy workspace object over number is inconsistent.

Cause: The definition of the hierarchy was inconsistent.

Action: Change the definition of the hierarchy.

ORA-36021: (XSHIERCK12) The format of the HIERCHECK function is:\n\n HIERCHECK(relation [STATUS|NOSTATUS|valueset] [MULTIPATH] [CONSISTENT] [{BALANCED|STAR_CONSISTENT} levelrelation]) \nOr\n HIERCHECK(aggmap [MULTIPATH] [CONSISTENT])

Cause: The wrong object type was specified.

Action: Change the object to a RELATION or AGGMAP.

ORA-36022: (XSHIERCK04) Valuesets specified in the HIERCHECK command must be scalar. workspace object is dimensioned.

Cause: The HIERCHECK command specified a dimensioned valueset.

Action: Specify a scalar valueset in its place.

ORA-36024: (XSHIERCK05) Valueset workspace object must contain values of one of the extra dimensions of relation workspace object.

Cause: The HIERCHECK command specified a valueset over an invalid dimension.

Action: Specify a valueset containing values of one of the self-relation's extra dimensions (the dimensions in the relation's dimension list, minus the self-related dimension itself).

ORA-36025: (XSHIERCK06) The level dimension of the level relation workspace object is the same as the relation dimension workspace object.

Cause: The level dimension was the same as the relation dimension.

Action: Change the definition of the level relation.

ORA-36026: (XSHIERCK07) Level relation workspace object is not dimensioned by relation dimension workspace object.

Cause: The level relation was not dimensioned by the relation dimension.

Action: Change the definition of the level relation.

ORA-36027: (XSHIERCK08) Hierarchy workspace object is not balanced.

Cause: The current hierarchy was not balanced.

Action: Change the hierarchy to balanced.

ORA-36028: (XSHIERCK09) Hierarchy workspace object has multiple paths from number to number.

Cause: The current hierarchy had multiple paths.

Action: Remove multiple paths from the hierarchy.

ORA-36034: (XSMHIERCK00) One or more loops have been detected in relationship workspace object over workspace object. The last number of the items are number.

Cause: A relation was used that contained loops. There were more items involved than could be reported.

Action: Correct the relation so that it does not contain loops.

ORA-36035: (XSMHIERCKREL) One or more loops have been detected in workspace object. number items involved are number.

Cause: A relation was used that had loops in it.

Action: Correct the relation so that it does not contain loops.

ORA-36036: (XSMHIERCK01) One or more loops have been detected in relationship workspace object over workspace object. The number items involved are number.

Cause: A relation was used that contained loops.

Action: Correct the relation so that it does not contain loops.

ORA-36038: (INTL00) No application code specified

ORA-36040: (INTL01) IMPORTANT: The length of the following phrase(s) exceeds %1. They will be truncated.

ORA-36042: (INTL02A) The %1 language analytic workspace for %2 could not be attached, and there is no English-language analytic workspace for this application.

ORA-36044: (INTL02B) Neither the %1 language analytic workspace nor the %2 language analytic workspace could be attached for %3, and there is no English-language analytic workspace for this application.

ORA-36050: (INTL06) Invalid option specified. Option must be either OSM, CA, or blank.

ORA-36052: (LISTBY00) LISTBY cannot be called as a function returning a value.

ORA-36054: (LISTBY01) You must have a current analytic workspace to use the LISTBY command.

ORA-36056: (LISTBY02) The syntax of the LISTBY command is:\n LISTBY dimension [dimension ...]\nDimension composites can also be named.

ORA-36058: (LISTBY03) %1 does not exist in any attached analytic workspace.

ORA-36060: (LISTBY04) %1 is not a dimension or composite.

ORA-36062: (LISTBY05) %1 is in a different analytic workspace from previously specified object(s) "%2".

ORA-36064: (LISTBY06) The syntax for specifying an unnamed composite is:\n SPARSEdimension-list\nwhere 'dimension-list' is a list of simple or conjoint dimensions or named composites.

ORA-36066: (LISTBY07) %1 objects dimensioned by or related to %2 in analytic workspace %3

ORA-36068: (LISTNAMES00) Analytic workspace %1 is not attached.

ORA-36070: (LISTNAMES01) There are no objects in the analytic workspace of the following types:\n%1

ORA-36072: (LISTNAMES02) There are no objects in the analytic workspace.

ORA-36074: (LISTNAMES03) There are no objects in the analytic workspace that match '%1'.

ORA-36076: (LISTNAMES04) %1 is not a valid keyword for LISTNAMES.\nValid keywords are:\nALL, SORT or UNSORT, AW workspace-name\n%2

ORA-36078: (MODEL00) Specify the name of a model for the report.

ORA-36080: (MODEL01) %1 does not exist.

ORA-36082: (MODEL02) %1 is not a model.

ORA-36084: (MODEL03) Model %1 has not been compiled.

ORA-36086: (MODEL04) Information is not available for model %1.

ORA-36088: (MODEL05) Model %1 is not the most-recently executed model.

ORA-36090: (MODEL06) Solution status:

ORA-36092: (MODEL07) Model options in use:

ORA-36094: (MODEL08) Solution status:

ORA-36098: (MODEL10) Divergent statement

ORA-36100: (MODEL11) Model: %1

ORA-36102: (MODEL12) Statement %1%2

ORA-36104: (STATUS00) You must have a current analytic workspace to use the STATUS command.

ORA-36106: (STATUS01) There are no dimensions in your current analytic workspace.

ORA-36108: (STATUS02) There are no dimensions in analytic workspace %1.

ORA-36110: (STATUS03) %1 has no dimensions.

ORA-36112: (STATUS04) The current status of %1 is:

ORA-36114: (STDHDR00) Page

ORA-36116: (TRACKREPORT00) Program name

ORA-36118: (TRACKREPORT01) Exclusive cost

ORA-36120: (TRACKREPORT02) Inclusive cost

ORA-36122: (TRACKREPORT03) Number of calls

ORA-36124: (XLIST00) %1 exceptions found.

ORA-36126: (XLIST01) %1 already exists.

ORA-36128: (XLIST03) The exception criterion must be a single expression.

ORA-36130: (XLIST04) The exception criterion must be a BOOLEAN expression.

ORA-36132: (XLIST05) The exception criterion must be dimensioned.

ORA-36134: (XLIST06) %1 is not an exception list.

ORA-36136: (XLIST07) There is no current exception list. You can use the NAMEXL command to specify one.

ORA-36138: (XLIST08) %1 has been deleted.

ORA-36142: (XREF01) Referenced By:

ORA-36145: (SETPROP01) The property "%1" cannot be set for measure "%2".

Cause: A property name was given that is not one of the allowed properties to be set.

Action: Specify one of the legal property names.

ORA-36146: (READSIZE01) The string expression cannot be missing or NA.

ORA-36148: (READSIZE02) The minimum value for string is number. You specified a value of number.

ORA-36152: (READSIZE04) The maximum value for string is number. You specified a value of number.

ORA-36154: (XSMXAGGR01) workspace object is not a data variable.

Cause: An object was specified on the Aggregate command line that was not a variable

Action: Specify a variable instead

ORA-36155: (XSMXAGGRFROM) workspace object must be a variable or formula of a similar data type to workspace object to be used with FROM, or a TEXT variable or formula to be used with FROMVAR.

Cause: The user specified an illegal variable for use with FROM or FROMVAR on the AGGREGATE command line

Action: Specify a legal variable instead

ORA-36156: (XSMXAGGR02) When using the BOOLEAN or FORMULA WEIGHT workspace object, WNAFILL is the only valid option.

ORA-36158: (XSMXAGGR03) workspace object must be an AGGMAP object.

ORA-36160: (XSMXAGGR04) You cannot use string on scalar VARIABLE workspace object.

Cause: The user tried to run the AGGREGATE or AGGCOUNT command or function on a scalar variable.

Action: Specify a dimensioned variable instead

ORA-36161: (XSAGGRRUVCV) Aggregation variable workspace object cannot have itself as a COUNTVAR.

Cause: The user specified the same variable as both an aggregation variable and a COUNTVAR

Action: Specify a different COUNTVAR

ORA-36162: (XSMXAGGR05) COUNTVAR variable workspace object must be of type INTEGER, not string.

Cause: The user specified a non-INTEGER variable as a COUNTVAR for aggregation

Action: Redefine the COUNTVAR to be an INTEGER

ORA-36164: (XSMXAGGR07) When using the COUNTVAR clause, the number of variables to be aggregated (number) must match the number of COUNTVAR variables (number).

Cause: The user specified a COUNTVAR clause to the AGGREGATE command, but the number of COUNTVAR variables specified did not match the number of variables to be aggregated

Action: Specify a separate COUNTVAR for each variable

ORA-36165: (XSAGGCNTPROP) Variable workspace object cannot have both an AGGCOUNT and the $COUNTVAR property.

Cause: An attempt was made to add the $COUNTVAR property to a variable which already had an AGGCOUNT, or vice versa.

Action: Delete the already existing $COUNTVAR property or AGGCOUNT first.

ORA-36166: (XSMXAGGR08) workspace object is not a VARIABLE.

Cause: An attempt was made to perform an AGGREGATE or other action on an object which is not a variable.

Action: Specify a variable instead.

ORA-36167: (XSAGGRFORM) workspace object is not a valid AGGMAP for aggregating a FORMULA.

Cause: The user attempted to aggregate a FORMULA using an AGGMAP that is not valid for aggregating FORMULAs. The AGGMAP must specify PRECOMPUTE(NA) for all relation lines and must not specify any caching.

Action: Correct the AGGMAP so that it is valid for aggregating a FORMULA.

ORA-36168: (XSMXAGGR10) COUNTVAR variable workspace object must have the same dimensionality as workspace object

Cause: The user specified a COUNTVAR variable which is missing at least one dimension of the aggregation variable

Action: Specify a COUNTVAR variable which has at least as many base dimensions as the aggregation variable

ORA-36170: (XSMXAGGR12) The data type of the WEIGHT workspace object must be numeric or BOOLEAN, not string.

Cause: The user specified a WEIGHT variable or formula which wasn't numeric or boolean

Action: Specify a numerical or boolean weight instead

ORA-36172: (XSMXAGGR18) WEIGHT option WNOAGG cannot be used with the WSTORE, WVARPRIORITY, or WAGGPRIORITY options on WEIGHT workspace object.

ORA-36174: (XSMXAGGR23) workspace object must be either a VARIABLE, a RELATION or a FORMULA.

Cause: The user specified something that was not a variable, a relation or a formula as a weight for AGGREGATE

Action: Specify a valid variable, relation or formula instead

ORA-36176: (XSMXAGGR25) Relation workspace object must be a one-dimensional self-relation to be used as a weight for AGGREGATE.

Cause: The user specified an illegal relation as a weight. The relation might have been multidimensional, not a self-relation, or not a relation over one of the bases of the aggregation variable.

Action: Specify a valid self relation over one of the bases of the aggregation variable.

ORA-36178: (XSAGGR01) To be used with AGGREGATE, AGGMAP workspace object must be declared with the AGGMAP command.

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.

ORA-36179: (XSNOAGM) No AGGMAP was specified for VARIABLE workspace object.

Cause: The user used the AGGREGATE command without specifying an AGGMAP on the command line, with a variable which had no $AGGMAP property.

Action: Specify an AGGMAP on the AGGREGATE command line, or add the $AGGMAP property to the variable in question.

ORA-36180: (XSAGGR08) AGGREGATE cannot function because there is a permission clause associated with variable workspace object.

Cause: When using AGGREGATE, only simple permissions and permissions on base dimensions are valid.

Action: Remove the permissions clause from the variable causing problems.

ORA-36181: A VARIABLE cannot have both the $AGGREGATE_FROM and $AGGREGATE_FROMVAR properties applied to it.

Cause: The user attempted to add both the $AGGREGATE_FROM and $AGGREGATE_FROMVAR properties to a single variable.

Action: Remove the existing property before applying the new one.

ORA-36182: (XSAGGR09) Could not locate a value for variable number in measure dimension workspace object.

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.

ORA-36184: (XSAGGR10) You do not have sufficient permissions for the variable workspace object.

Cause: The user lacked the permissions necessary for the aggregation variable.

Action: Remove the restricting permissions from the variable or base dimension.

ORA-36185: (XSAGGR11) workspace object does not have any AGGCOUNT information.

Cause: User attempted an operation (such as the AVERAGE aggregation operator or the AGGCOUNT function) that requires a variable to have AGGCOUNT information on a variable that does not.

Action: Define the variable using the WITH AGGCOUNT clause, or use the CHGDFN ADD AGGCOUNT command to enable AGGCOUNT for the variable.

ORA-36186: (XSAGGR12) You must use a COUNTVAR when aggregating with AVERAGE.

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 problem in AGGREGATE. If no one has modified the values in this COUNTVAR, contact Oracle customer support.

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 OLAP technical support.

ORA-36190: (XSAGGR26) workspace object is of type string. The numerical calculation string requires INTEGER, DECIMAL or SHORTDECIMAL data.

ORA-36192: (XSAGGR27) workspace object is of type string. The boolean calculation string requires BOOLEAN data.

ORA-36194: (XSAGGR28) workspace object is of type string. The requested operation requires INTEGER, DECIMAL, SHORTDECIMAL or BOOLEAN data.

ORA-36196: (XSAGGR32) 'number' is an invalid argument specifier for AGGREGATE.

ORA-36198: (XSAGGR33) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object because the operator variable with more than 1 line dimensions is not supported for bases of a COMPRESSED COMPOSITE.

Cause: The user specified an aggregation the operator variable with more than 1 line dimensions that is not supported by COMPRESSED COMPOSITES.

Action: Use a MODEL for the calculation, or use an uncompressed COMPOSITE.

ORA-36200: (XSAGGR34) AGGREGATE operator string requires a WEIGHTBY clause, but ARGS variable workspace object did not specify one.

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.

ORA-36201: (XSAGGR35) Cannot aggregate workspace object(partition workspace object) because the subpartition is itself partitioned.

Cause: Attempted to aggregate an intermediate partition of a variable with nested partitioning.

Action: rerun the aggregate command seperately for each ultimate partition or just for the variable as a whole

ORA-36202: (XSAGOP01) 'number' is not a valid aggregation operator.

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.

ORA-36204: (XSAGOP04N) In AGGMAP workspace object, the NAOPERATOR string must be HFIRST, HLAST or HEVEN.

Cause: An invalid NAOPERATOR was specified.

Action: Specify HFIRST, HLAST or HEVEN.

ORA-36206: (XSAGOP04R) In AGGMAP workspace object, REMOPERATOR string must be MIN, MAX, FIRST, LAST, HFIRST or HLAST.

Cause: An invalid REMOPERATOR was specified.

Action: Specify one of the legal operators.

ORA-36208: (XSAGOP05N) In AGGMAP workspace object, you can only specify NAOPERATOR string with the PROPORTIONAL or EVEN operators, not string.

Cause: The user specified an NAOPERATOR when you were not using PROPORTIONAL or EVEN.

Action: Remove the NAOPERATOR clause from the RELATION line.

ORA-36210: (XSAGOP05R) In AGGMAP workspace object, you can only specify the REMOPERATOR string with the PROPORTIONAL, EVEN, or HEVEN operators, not string.

Cause: The user specified a REMOPERATOR without using PROPORTIONAL, EVEN, or HEVEN.

Action: Remove the REMOPERATOR clause from the RELATION line.

ORA-36212: (XSAGOP06) In AGGMAP workspace object, you can only specify the MIN, MAX, FLOOR, and CEILING arguments while using the PROPORTIONAL operator, not string.

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.

ORA-36216: (XSOPARM01) A DIMENSION must have a data type (ID, TEXT, or INTEGER), a time period, or a list of bases for a conjoint dimension.

ORA-36220: (XSLPDSC01) All dimensions in LIST number are also in the IGNORE clause.

Cause: One of the dimension lists in the dimension loop descriptor had no base dimensions except those in the IGNORE list. This leaves no dimensions for looping over.

Action: Fix the dimension loop descriptor.

ORA-36221: (XSLPDSC02) LIST number and LIST number have different base dimensions.

Cause: The base dimensions of the dimension lists given in the loop descriptor do not match.

Action: Ensure that each dimension list has the same set of looping base dimensions. If necessary, use IGNORE within a lists to discard base dimensions that should not be looped.

ORA-36222: (XSLPDSC03) duplicate IGNORE or DENSE information for dimension workspace object

Cause: An IGNORE or DENSE list in a dimension loop descriptor included the dimension twice, included two different valuesets of the dimension, or includes the dimension and a valueset of the dimension.

Action: Only use the dimension or a valueset of the dimension once in an IGNORE or DENSE list.

ORA-36223: (XSLPDSC04) object workspace object in IGNORE or DENSE list has illegal type

Cause: An IGNORE or DENSE list in a dimension loop descriptor included and object that was not a dimension or a valueset, was a conjoint dimension, or was a dimensioned valueset.

Action: Only use simple dimensions and undimensioned valuesets in the IGNORE or DENSE list.

ORA-36224: (XSLPDSC05) workspace object is not a loop dimension

Cause: An IGNORE or DENSE list in a dimension loop descriptor referenced a dimension (or a valueset of a dimension) that was not a base dimension of the loop dimension list.

Action: Remove the dimension or valueset from the IGNORE or DENSE list.

ORA-36225: (XSLPDSC06) A LOOP AGGMAP list must contain an aggmap object, followed by one or more variables and/or dimensions.

Cause: An invalid AGGMAP list was specified. Either to few objects were specified, or an incorrect type of object was used.

Action: Specify a valid AGGMAP list consisting of an aggmap object, followed by one or more variables and/or dimensions.

ORA-36226: (XSLPDSC07) The syntax of the $LOOP property on formula workspace object is incorrect.

Cause: Unrecognized contents in the $LOOP property of a formula in the table function measure list.

Action: Restrict the contents of the $LOOP property to valid elements (other than OPTIMIZED and MEASURES) of the table function LOOP directive.

ORA-36230: (XSANALYZ00) object workspace object cannot be used in the ANALYZE command

Cause: An object that cannot be analyzed was used in the ANALYZE command.

Action: Analyze VARIABLES, RELATIONS, DIMENSIONS, or SURROGATES.

ORA-36231: (XSANALYZ01) object workspace object cannot be used in the INHIERARCHY clause

Cause: An invalid INHIERARCHY object was referenced.

Action: Use either a VALUESET or boolean VARIABLE.

ORA-36232: (XSANALYZ02) a level list was specified when a language dimension was present

Cause: A level list dimension was specified when a language dimension was present.

Action: Remove the USING clause.

ORA-36233: (XSANALYZ03) the dimensionality of object workspace object does not match the ANALYZE command

Cause: The dimensionality of the object did not match the ANALYZE command syntax used.

Action: Match the ANALYZE syntax to the dimensionality of the specified object.

ORA-36234: (XSANALYZ04) all objects in the current status of the NAME dimension must have the same dimensionality when used with the ANALYZE command

Cause: The dimensionality of at least one of the objects listed in the NAME dimension does not match the rest of the objects.