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.
- 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.
- 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
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-33012: (XSAGDNGL05) AGGMAP workspace object contains invalid syntax.
-
Cause: A line in the AGGMAP contains invalid 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.
- 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.
- 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.
- 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.
- ORA-33024: (XSAGDNGL11) AGGMAP workspace object contains duplicate information.
-
Cause: The aggmap contains multiple instances of a clause that can only be specified once.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-33036: (XSAGDNGL17) ARGS option workspace object must be a TEXT variable.
-
Cause: An ARGS value had a non-text data type.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-33046: (XSAGDNGL22) In AGGMAP workspace object, you can specify only one SCREENBY clause.
-
Cause: The AGGMAP contained multiple SCREENBY clauses.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-33084: (XSAGDNGL42) In AGGMAP workspace object, you cannot qualify the dimensioned valueset workspace object.
-
Cause: The VALUESET line referred to a dimensioned valueset.
- ORA-33086: (XSAGINIT01) AGGMAP workspace object cannot be dimensioned by a conjoint dimension.
-
Cause: The specified AGGMAP was dimensioned by a conjoint 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-33116: (APMSTYPE00) MODSIMULTYPE must be either AITKENS or GAUSS.
-
Cause: An invalid value was specified for the MODSIMULTYPE option.
- 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.
- 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.
- 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.
- ORA-33124: (APMITERS00) MODMAXITERS must be a whole number greater than zero.
-
Cause: An invalid value was specified for the MODMAXITERS option.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-33138: (APSPARSX02) The value 'number' is not valid for SPARSEINDEX.
-
Cause: An invalid value was specified for the SPARSEINDEX option.
- 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.
- ORA-33141: (XSAWFREEZE1) The analytic workspace string is already frozen.
-
Cause: An attempt was made to freeze an analytic workspace that was already frozen.
- ORA-33142: (BADSYN00) The format of the string command is incorrect.
-
Cause: There was an error in the syntax of the indicated command.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-33154: (CFINDVAL01) The workspace object dimension does not have identifiers.
-
- ORA-33156: (CFINDVAL02) exceeds 2**63.
-
Cause: This dimension is too large.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-33214: (CINSERT02) The workspace object dimension is too large.
-
Cause: The dimension has too many values.
- 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.
- 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.
- 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).
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-33269: error while operating on 'string'
-
Cause: Creation of an analytic workspace for the specified object failed.
- ORA-33270: (DBERR05) Analytic workspace string already exists.
-
Cause: The AW CREATE command was passed the name of an analytic workspace that already exists
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-33287: This DDL operation is not allowed on table "string"."string"
-
Cause: A DDL operation was attempted on an analytic workspace table.
- 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.
- 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.
- 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
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-33338: (DSSEXIST05) You cannot specify the EXPTEMP analytic workspace.
-
Cause: The command requires a permanent analytic workspace to operate on.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-33736: (ILPPUT02) The workspace object program contains unmatched DO or DOEND statements.
-
Cause: The program has a compiler error.
- 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.
- 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.
- 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.
- 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.
- ORA-33746: (ILPPUT08) number must be preceded by an IF clause.
-
Cause: There was a compiler error.
- ORA-33748: (ILPPUT09) number must be preceded by a THEN clause.
-
Cause: There was a compiler error.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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).
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-34182: (MXCHGDCL04) SEGWIDTH not changed from "string\nwrong"
-
Cause: SEGWIDTH requires one value for each dimension.
- ORA-34183: (MXCHGDCL22) Partition number already exists.
-
Cause: User attempted to ADD a partition that already existed to a partitioned variable.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-34279: (MXDCL37) CONCAT can only be used when defining a DIMENSION.
-
Cause: The CONCAT keyword was used incorrectly.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-34350: (MXDSS06) string is an open analytic workspace.
-
Cause: The specified analytic workspace was 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.
- ORA-34357: (MXDSS10) string is not an alias of analytic workspace string.
-
Cause: User attempted to use AW UNALIAS on a nonexistent alias.
- ORA-34358: (MXDSS14) number other users reading
-
Cause: Used for AW LIST output formatting when %d > 1
- 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.
- ORA-34360: (MXDSS15) number other users writing
-
Cause: Used for AW LIST output formatting when %d > 1
- ORA-34362: (MXDSS16) Program number does not exist.
-
Cause: The specified program name could not be found.
- 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).
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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).
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-35032: The IMPORT command terminated because of a defect in the EIF file.
-
Cause: This was an unexpected error.
- 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.
- 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.
- ORA-35046: The IMPORT command terminated because of a defect in the EIF file.
-
Cause: There was an unexpected error.
- 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.
- 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.
- ORA-35056: The IMPORT command terminated because of a defect in the EIF file.
-
Cause: This an unexpected error.
- 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.
- ORA-35060: The IMPORT command has terminated because of a defect in the EIF file.
-
Cause: This is an unexpected error.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-35182: (SNSYN104) The format of the WKSDATA function is:\n \n WKSDATA(worksheetname)
-
Cause: The syntax of the specified WKSDATA function was invalid.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-35204: (SNSYN115) A label is missing after string.
-
Cause: The name of PROGRAM label was not found at the indicated location.
- 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.
- 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.
- ORA-35214: (SNSYN120) The format of the COMPILE command is:\n \n COMPILE name [NOWARN]
-
Cause: The syntax of the COMPILE command was invalid.
- 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.
- 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.
- ORA-35220: (SNSYN123) The format of the EXISTS function is:\n \n EXISTS(text-expression)
-
Cause: The syntax of the EXISTS function was invalid.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-35292: (SNSYN171) The format of the ISVALUE function is:\n \n ISVALUE(dimension expression)
-
Cause: The syntax of the ISVALUE function was invalid.
- ORA-35294: (SNSYN173) The format of the STATLEN function is:\n \n STATLEN(dimension)
-
Cause: The syntax of the STATLEN function was invalid.
- 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.
- 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.
- ORA-35302: (SNSYN177) The format of the STATMIN function is:\n \n STATMIN(dimension)
-
Cause: The syntax of the STATMIN function was invalid.
- ORA-35304: (SNSYN178) The format of the STATMAX function is:\n \n STATMAX(dimension)
-
Cause: The syntax of the STATMAX function was invalid.
- 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.
- 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.
- ORA-35312: (SNSYN182) The format of the COLVAL function is:\n \n COLVAL(column-number)
-
Cause: The syntax of the COLVAL function was invalid.
- ORA-35314: (SNSYN183) The format of the RUNTOTAL function is:\n \n RUNTOTAL(subtotal-number)
-
Cause: The syntax of the RUNTOTAL function was invalid.
- ORA-35316: (SNSYN184) The format of the SUBTOTAL function is:\n \n SUBTOTAL(subtotal-number)
-
Cause: The syntax of the SUBTOTAL function was invalid.
- 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.
- ORA-35322: (SNSYN187) The format of the LOG function is:\n \n LOG(expression)
-
Cause: The syntax of the LOG function was invalid.
- 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.
- ORA-35328: (SNSYN190) The format of the REM function is:\n \n REM(expression1 expression2)
-
Cause: The syntax of the REM function was invalid.
- ORA-35330: (SNSYN191) The format of the MIN function is \n \n MIN(expression1 expression2)
-
Cause: The syntax of the MIN function was invalid.
- ORA-35332: (SNSYN192) The format of the MAX function is:\n \n MAX(expression1 expression2)
-
Cause: The syntax of the MAX function was invalid.
- 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.
- 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.
- 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.
- 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.
- ORA-35346: (SNSYN201) The format of the LOWCASE function is:\n \n LOWCASE(text-expression)
-
Cause: The syntax of the LOWCASE function was invalid.
- 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.
- 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.
- 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.
- 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.
- ORA-35360: (SNSYN215) The format of the FILENEXT function is:\n \n FILENEXT(fileunit)
-
Cause: The syntax of the FILENEXT function was invalid.
- ORA-35362: (SNSYN216) The format of the RECNO function is:\n \n RECNO(fileunit)
-
Cause: The syntax of the RECNO function was invalid.
- ORA-35364: (SNSYN217) The format of the ROUND function is:\n \n ROUND(expression1 [, expression2])
-
Cause: The syntax of the ROUND function was invalid.
- 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.
- 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.
- 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.
- ORA-35374: (SNSYN222) Invalid UNIQUELINES function syntax.
-
Cause: The format of the UNIQUELINES function was invalid.
- ORA-35376: (SNSYN223) invalid JOINCOLS function syntax
-
Cause: The syntax of the JOINCOLS function was invalid.
- 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.
- 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.
- ORA-35390: (SNSYN230) Invalid MMOF function syntax.
-
Cause: The format of the MMOF function was incorrect.
- ORA-35392: (SNSYN231) Invalid YYOF function syntax.
-
Cause: The format of the YYOF function was incorrect.
- ORA-35394: (SNSYN232) The DAYOF function syntax is invalid.
-
Cause: The format of the DAYOF function was invalid.
- ORA-35396: (SNSYN233) Invalid SIN function syntax.
-
Cause: The format of the SIN function was incorrect.
- ORA-35398: (SNSYN234) Invalid COS function syntax.
-
Cause: The format of the COS function was invalid.
- ORA-35400: (SNSYN235) Invalid MAKEDATE function syntax.
-
Cause: The format of the MAKEDATE function was invalid.
- ORA-35402: (SNSYN236) Invalid ANTILOG function syntax.
-
Cause: The format of the ANTILOG function was invalid.
- ORA-35404: (SNSYN237) Invalid ANTILOG10 function syntax.
-
Cause: The format of the ANTILOG10 function was invalid.
- ORA-35406: (SNSYN238) Invalid ROLLUP command syntax.
-
Cause: The format of the ROLLUP command was invalid.
- ORA-35408: (SNSYN239) Invalid STARTOF function syntax.
-
Cause: The format of the STARTOF function was invalid.
- ORA-35410: (SNSYN240) Invalid ENDOF function syntax.
-
Cause: The format of the ENDOF function was invalid.
- ORA-35412: (SNSYN241) Invalid BEGINDATE function syntax.
-
Cause: The format of the BEGINDATE function was incorrect.
- ORA-35414: (SNSYN242) Invalid ENDDATE function syntax.
-
Cause: The format of the ENDDATE function was invalid.
- ORA-35416: (SNSYN243) Invalid TCONVERT function syntax.
-
Cause: The format of the TCONVERT function was invalid.
- ORA-35418: (SNSYN244) Invalid FILEERROR function syntax.
-
Cause: The format of the FILEERROR function was incorrect.
- ORA-35420: (SNSYN245) Invalid payment or interest function syntax.
-
Cause: The format of an Oracle OLAP payment or interest function was invalid.
- ORA-35422: (SNSYN246) Invalid DEPRSL function syntax.
-
Cause: The format of the DEPRSL function was invalid.
- ORA-35424: (SNSYN247) Invalid DEPRDECL function syntax.
-
Cause: The format of the DEPRDECL function was invalid.
- ORA-35426: (SNSYN248) Invalid DEPRSOYD function syntax.
-
Cause: The format of the DEPRSOYD function was invalid.
- ORA-35428: (SNSYN249) Invalid GROWRATE function syntax.
-
Cause: The format of the GROWRATE function was invalid.
- ORA-35430: (SNSYN250) Invalid NORMAL function syntax.
-
Cause: The format of the NORMAL function was invalid.
- ORA-35432: (SNSYN251) Invalid DEPRDECLSW function syntax.
-
Cause: The format of the DEPRDECLSW function was invalid.
- ORA-35434: (SNSYN265) Invalid format for CHGDFN command.
-
- ORA-35436: (SNSYN267) Invalid WEEKOF function syntax.
-
Cause: The format of the WEEKOF function was invalid.
- ORA-35438: (SNSYN268) Invalid PERMIT command syntax.
-
Cause: The format of the PERMIT command was invalid.
- ORA-35442: (SNSYN270) invalid PROPERTY command syntax
-
Cause: The format of the PROPERTY command was incorrect.
- ORA-35444: (SNSYN271) invalid TRANSLATEBYTES function syntax
-
Cause: The format of the TRANSLATEBYTES function was incorrect.
- ORA-35446: (SNSYN274) invalid LIMIT function syntax
-
Cause: The format of the LIMIT function was invalid.
- 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.
- 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.
- ORA-35460: (SNSYN283) invalid ARCTAN function syntax
-
Cause: The format of the ARCTAN function was incorrect.
- ORA-35462: (SNSYN284) invalid COSH function syntax
-
Cause: The format of the COSH function was incorrect.
- ORA-35464: (SNSYN285) Invalid SINH function syntax.
-
Cause: The format of the SINH function was incorrect.
- 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.
- ORA-35470: (SNSYN288) Invalid ARCCOS function syntax.
-
Cause: The format of the ARCCOS function was incorrect.
- ORA-35472: (SNSYN301) invalid MAXCHARS function syntax
-
Cause: The format of the MAXCHARS function was incorrect.
- 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.
- 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.
- 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.
- ORA-35508: (SNSYN329) invalid SYSINFO function syntax
-
Cause: The syntax of the SYSINFO function was incorrect.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-35564: (XSRWLD02) Cannot convert from the string type to the string type.
-
Cause: Conversion from source to target is not allowed
- ORA-35565: (XSRWLD03) For object workspace object only APPEND, MATCH or ASSIGN may be used.
-
Cause: An incorrect setting was applied to the target
- ORA-35566: (XSRWLD04) Object workspace object cannot be used with QDRs
-
Cause: A QDR was placed on a 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.
- 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.
- 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.
- 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.
- 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.
- ORA-35573: (XSRWLD09) An incoming dimension value is null.
-
Cause: A source value for a dimension is 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-35602: (SSCGLIMT02) You cannot limit dimension composite workspace object.
-
Cause: The LIMIT of composite dimensions was specified which is not allowed.
- 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.
- ORA-35606: (SSCGNULL02) string is not defined as a label.
-
Cause: The IFNONE label did not exist.
- ORA-35610: (SSCGREL01) workspace object and workspace object are not related.
-
Cause: The target and source dimensions were not related.
- 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.
- ORA-35623: (XSSCLLEV07) workspace object is not a VALUESET of workspace object.
-
Cause: LEVELREL expected a VALUESET of the dimension argument.
- ORA-35624: (SSCGREL08) workspace object is not dimensioned by workspace object.
-
Cause: This relation was not a valid self relation for the target dimension.
- ORA-35625: (XSSCLLEV08) workspace object is not dimensioned by workspace object.
-
Cause: The relation was not a valid LEVELREL for target dimension.
- 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.
- 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.
- 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.
- 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.
- ORA-35633: (STATEQ01) Both arguments to STATEQUAL must be status lists of the same dimension.
-
Cause: The arguments are status lists of different dimensions.
- 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.
- 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.
- 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.
- ORA-35646: (SSEXECUT08) The expression for BEFORE or AFTER has a value of NA.
-
Cause: The BEFORE or AFTER value is NA.
- 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.
- 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.
- 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.
- 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'
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-35918: (XSHIDE02) You do not have access to workspace object.
-
Cause: Permission to read the text of the named object was not granted.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-36020: (XSHIERCK03) The definition of hierarchy workspace object over number is inconsistent.
-
Cause: The definition of the hierarchy was inconsistent.
- 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.
- ORA-36022: (XSHIERCK04) Valuesets specified in the HIERCHECK command must be scalar. workspace object is dimensioned.
-
Cause: The HIERCHECK command specified a dimensioned valueset.
- 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.
- 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.
- 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.
- ORA-36027: (XSHIERCK08) Hierarchy workspace object is not balanced.
-
Cause: The current hierarchy was not balanced.
- ORA-36028: (XSHIERCK09) Hierarchy workspace object has multiple paths from number to number.
-
Cause: The current hierarchy had multiple paths.
- 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.
- 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.
- 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.
- 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.
- 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
- 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
- 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.
- 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
- 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
- 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
- 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.
- 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.
- 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.
- 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
- 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
- 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
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-36202: (XSAGOP01) 'number' is not a valid aggregation operator.
-
Cause: An invalid string was provided for an aggregation operator.
- ORA-36204: (XSAGOP04N) In AGGMAP workspace object, the NAOPERATOR string must be HFIRST, HLAST or HEVEN.
-
Cause: An invalid NAOPERATOR was specified.
- ORA-36206: (XSAGOP04R) In AGGMAP workspace object, REMOPERATOR string must be MIN, MAX, FIRST, LAST, HFIRST or HLAST.
-
Cause: An invalid REMOPERATOR was specified.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-36231: (XSANALYZ01) object workspace object cannot be used in the INHIERARCHY clause
-
Cause: An invalid INHIERARCHY object was referenced.
- 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.
- 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.
- 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.
- ORA-36236: (XSANALYZ06) the AW format must be 11.0.0.0 or higher to use the ANALYZE command
-
Cause: The AW version is less than 11.0.0.0
- ORA-36237: (XSANALYZ07) analytic workspace string.string must be attached RW or EXCLUSIVE mode
-
Cause: The analytic workspace was already attached RO or MULTI mode.
- ORA-36238: (XSANALYZ08) object string.string does not exist
-
Cause: The object name does not exist
- ORA-36258: (XSAGINFO00) When the AGGMAPINFO function is called, workspace object must be an AGGMAP.
-
Cause: The AGGMAPINFO function was called with an object that is not an AGGMAP.
- ORA-36260: (XSAGHIERPART00) Aggregating from partition %J to partition %J over hierarchy workspace object creates an increase in sparsity.
-
Cause: In the partition creation / aggmap creation a situation developed such that when aggregating over a particular dimension of the aggmap a partition boundary was crossed such that the sparsity of the target partition included dimensions that were not in the sparsity of the source partition. Since the process of aggregation always densifies rather than sparsifying this is an extremely suboptimal design and it is not supported by the aggregate system.
- ORA-36261: (XSAGPARTDEP00) Can not Aggregate PARTITION TEMPLATE %J because the path of aggregation would recursively enter partition %J.
-
Cause: The partitioning scheme was such that while aggregating there exists a cell (m) such that both one of its descendants and one of its ancestors are both in the referenced partition, while (m) is in a different partition.
- ORA-36262: (XSAGREMOD00) MODEL workspace object was not attached to the AGGMAP.
-
- ORA-36264: (XSAGREMOD01) Removed MODEL: number
-
- ORA-36266: (XSCGMDLAGG00) Invalid context for the AGGREGATION function
-
Cause: The AGGREGATION function was used outside of the MODEL context.
- ORA-36267: (XSCGMDLAGG09) workspace object has no dimensions, so it cannot have a qualified data reference.
-
Cause: A dimension qualification was specified for a valueset with no dimensions.
- ORA-36268: (XSCGMDLAGG01) 'string' is not a valid dimension value.
-
Cause: The AGGREGATION parameter list included a value that does not exist in the MODEL dimension that contains the target of the AGGREGATION
- ORA-36269: (XSCGMDLAGG10) 'workspace object' does not exist or is not a dimension.
-
Cause: A nonexistent or invalid object was specified as a QDR dimension.
- ORA-36270: (XSCGMDLAGG03) The parameter list for the AGGREGATION function includes duplicate values.
-
Cause: One or more duplicate values appeared in the AGGREGATION parameter list.
- ORA-36271: (XSCGMDLAGG11) workspace object is not in the dimension list of valueset workspace object.
-
Cause: A QDR dimension was specified that does not appear in the valueset's dimension list.
- ORA-36272: (XSCGMDLAGG04) 'workspace object' is not a valid operator for the AGGREGATION function.
-
Cause: An invalid AGGREGATION operator was specified.
- ORA-36273: (XSCGMDLAGG12) Dimension workspace object appears more than once in the QDR.
-
Cause: A dimension was specified more than once in the QDR.
- ORA-36274: (XSCGMDLAGG05) The operator used in this equation needs a weight variable.
-
Cause: An invalid weight variable was specified.
- ORA-36275: (XSCGMDLAGG13) string is not a valid workspace object.
-
Cause: A value was specified that does not exist in the QDR dimension.
- ORA-36276: (XSCGMDLAGG06) The current operator does not need a weight variable.
-
Cause: A weight variable was specified in a context that does not support it.
- ORA-36278: (XSCGMDLAGG07) workspace object does not exist or is not valueset.
-
Cause: A nonexistent or invalid object was specified where a valueset is required.
- ORA-36280: (XSCGMDLAGG08) Valueset workspace object does not contain values of any dimension of the current model.
-
Cause: AGGREGATION specified a valueset of a dimension not listed in a DIMENSION statement for the current model.
- ORA-36282: (DNAMELEN01) Object name string is longer than number bytes.
-
- ORA-36286: (EIFMAKEF12) The EXPORT command terminated because there is not enough disk space in path string to contain a complete extension file.
-
Cause: There was insufficient disk space at the specified location.
- ORA-36290: (EIFMAKEF14) You cannot export object workspace object, because EIFVERSION is set to number. That version does not support string strings.
-
Cause: Tried to export a NUMBER dimension to an EIF file with the EIFVERSION option set to a number less than 80000. Versions before 80000 do not support NUMBER dimensions.
- ORA-36300: (XSCGTERM01) The command is too long or complex to compile.
-
Cause: In a PROGRAM or a MODEL, expressions exceeded the limit of 32765 bytes of stack memory.
- ORA-36302: (MXCLASS03) You cannot reference an analytic workspace NAME dimension using a QON. You can only access the NAME dimension of the current analytic workspace.
-
Cause: An attempt was made to access the NAME dimension of a non-current analytic workspace by using a qualified object name (QON).
- ORA-36304: (MXDCLAGR02) workspace object was not defined as an AGGMAP.
-
- ORA-36306: (MXDCLAGR03) Since there is no current aggmap definition, the AGGMAP statements will be discarded. Type END to return to the command line.
-
- ORA-36308: (MXDCLAGR04) The object workspace object has been defined as an AGGMAP, and it cannot be redefined as an ALLOCMAP.
-
- ORA-36310: (MXDCLAGR05) The object workspace object has been defined an ALLOCMAP, and it cannot be redefined as an AGGMAP.
-
- ORA-36312: (PHYS00) workspace object must be a dimension, dimensioned variable, or relation.
-
Cause: An invalid Oracle OLAP object was specified while attempting to use the PHYSICAL function.
- ORA-36313: (PHYS03) The VALUE option of the PHYSICAL clause cannot be applied to a variable.
-
Cause: A VALUE option of the PHYSICAL clause was specified for a variable.
- ORA-36314: (PHYS01) workspace object must be a dimension, relation or variable.
-
Cause: An invalid OLAP object was specified while attempting to use the PHYSICAL command.
- ORA-36315: (PHYS04) You must specify the VALUE option for scalar relation workspace object.
-
Cause: The VALUE argument to PHYSICAL was omitted for a scalar relation
- ORA-36316: (PHYS02) Relation workspace object must be a single-dimensional relation that relates one INTEGER dimension to another.
-
Cause: An invalid relation was specified while attempting to use the PHYSICAL command.
- ORA-36320: (PPENG05) No more than number push levels are allowed.
-
Cause: An attempt was made to use the PUSH command more times than allowed.
- ORA-36322: (PPENG06) workspace object cannot be pushed more than number times.
-
Cause: The specified PUSH command did not have a matching POP command.
- ORA-36324: (PPNLSOPT00) 'number' is not a legal value for the string option. The previous value was retained.
-
- ORA-36330: (SNSYN124) The format of the PHYSICAL command is:\n \n PHYSICAL [dimension|relation]
-
- ORA-36332: (SNSYN125) The format of the PHYSICAL function is:\n \n PHYSICAL(dimension|variable|{relation [VALUE]})
-
- ORA-36334: (SNSYN126) The format of the TO_DATE function is:\n \n TO_DATE(value [format] [{option optionvalue}...])
-
- ORA-36336: (SNSYN127) The format of the TO_CHAR function is:\n \n TO_CHAR(value [format] [{option optionvalue}...])
-
- ORA-36338: (SNSYN128) invalid TO_NUMBER function syntax
-
Cause: The format of the TO_NUMBER function was incorrect.
- ORA-36339: (SNSYN129) The format of the TO_NCHAR function is:\n \n TO_NCHAR(value [format] [{option optionvalue}...])
-
- ORA-36340: (SNSYN130) The format of the PARTITIONCHECK function is:\n \n PARTITIONCHECK(aggmap, partition_template)
-
Cause: Bad syntax
- ORA-36341: (SNSYN131) The format of the TO_TIMESTAMP function is:\n \n TO_TIMESTAMP(value [format] [{option optionvalue}...])
-
- ORA-36342: (SNSYN200) Invalid CLEAR command syntax.
-
Cause: The format of the CLEAR command was incorrect.
- ORA-36344: (SNSYN272) invalid AGGREGATION function syntax
-
Cause: The format of the AGGREGATION function syntax was invalid.
- ORA-36346: (SNSYN338) invalid TRUNC function syntax
-
Cause: The format of the TRUNC function syntax was invalid.
- ORA-36348: (SNSYN339) invalid CEIL function syntax
-
Cause: The format of the CEIL function was invalid.
- ORA-36350: (SNSYN340) invalid FLOOR function syntax
-
Cause: The format of the FLOOR function syntax was invalid.
- ORA-36352: (SNSYN341) Invalid ADD_MONTHS function syntax.
-
Cause: The format of the ADD_MONTHS function was incorrect.
- ORA-36354: (SNSYN342) Invalid LAST_DAY function syntax.
-
Cause: The format of the LAST_DAY function was incorrect.
- ORA-36356: (SNSYN343) Invalid MONTHS_BETWEEN function syntax.
-
Cause: The format of the MONTHS_BETWEEN function was incorrect.
- ORA-36358: (SNSYN344) invalid NEW_TIME function syntax
-
Cause: The format of the NEW_TIME function was invalid.
- ORA-36360: (SNSYN345) The format of the NEXT_DAY function is:\n \n NEXT_DAY(date, day name)
-
- ORA-36376: (XSAGZERO) AGGREGATE attempted to divide by zero. Set DIVIDEBYZERO to YES if you want NA to be returned as the result of a division by zero.
-
Cause: A calculation in the current AGGREGATE command attempted to divide by zero as a result of an AVERAGE, WAVERAGE, HAVERAGE or HWAVERAGE operation.
- ORA-36387: (XSPARTCHECK00) Object workspace object must be an AGGMAP.
-
- ORA-36388: (XSPARTCHECK01) Object workspace object must be a PARTITION TEMPLATE.
-
- ORA-36389: (XSAGPARTDEP01) Can not aggregate from PARTITION number into PARTITION number due to increasing sparsity along DIMENSION %J.
-
Cause: The user is attempting to use partitions as a means of sparsity control, however they have set up their partitions in a manner that simply makes no sense. It is a simple fact that during aggregation data becomes more dense, not less dense, and yet their partitions indicate the opposite.
- ORA-36392: (XSMXCLEA02) When using CLEAR with the PRECOMPUTES or NONPRECOMPUTES options, you must specify an AGGMAP.
-
Cause: The user didn't specify an AGGMAP with the CLEAR command.
- ORA-36393: (XSMXCLEA03) When using the AGGREGATES, CHANGES or CACHE options, specify the ALL keyword.
-
Cause: The ALL keyword was not specified when using the AGGREGATES, CHANGES or CACHE options.
- ORA-36394: (XSMXCLEA04) When using CLEAR on the AGGMAP workspace object, CACHE is the only valid directive.
-
Cause: An attempted was made to CLEAR an AGGMAP using a directive other than CACHE.
- ORA-36395: (XSMXCLEA05) To CLEAR ALL AGGREGATES from workspace object, specify an AGGMAP.
-
Cause: The CLEAR command could not determine how the variable was aggregated because the variable was not dimensioned by a compressed composite.
- ORA-36397: (XSSPROPNA) The value of property string cannot be NA.
-
Cause: The user tried to set a system-reserved property on an OLAP object to NA
- ORA-36398: (XSSPROP01) Property name 'number' is invalid because only system-reserved property names can begin with '$'.
-
Cause: The user attempted to add a property which starts with $ but is not a reserved property name
- ORA-36399: (XSSPROPDTYPE) The data type of property string must be string.
-
Cause: The user tried to set a system-reserved property on an OLAP object to a value with an illegal datatype
- ORA-36400: (XSSPROP02) workspace object is not a valid variable name.
-
Cause: Not a valid variable name
- ORA-36401: (XSSPROPOTYPE) Property string may only be applied to objects of type string.
-
Cause: The user applied a reserved property name to an incorrect object type
- ORA-36402: (XSSPROP03) The property '$string' requires a leading "$" because it is a system-reserved property name.
-
Cause: The user tried to specify a property name which is reserved, but did not use a leading $
- ORA-36403: (XSBADSPROP) number is an illegal value for system-reserved property string on workspace object.
-
Cause: The user tried to specify an illegal value for a special property
- ORA-36404: (XSSPROP04) Property string cannot be applied to an undimensioned (scalar) TEMPORARY variable.
-
Cause: The user applied a reserved property name to an incorrect object type
- ORA-36405: (XSSPROP05) Property ignored for object workspace object:
-
Cause: A property was ignored during import.
- ORA-36406: (VCACHE00) 'number' is an invalid value for the VARCACHE option. The only permissible values are 'SESSION', 'VARIABLE', and 'NONE'.
-
Cause: The user tried to assign an invalid value to the VARCACHE option
- ORA-36410: (VCACHE03) 'number' is an invalid value for the $VARCACHE property. The only permissible values are 'DEFAULT', 'SESSION', 'VARIABLE', and 'NONE'.
-
Cause: The user tried to assign an invalid value to the $VARCACHE property on a variable
- ORA-36608: (XSAGHOVERFLOW) The depth of the hierarchies encountered while processing a composite dimension in AGGREGATE caused a counter overflow.
-
Cause: The depth of the hierarchies that are part of a composite exceeded 4 billion levels during the merge.
- ORA-36610: (XSLMS00) Unable to locate a message file for Online Analytical Processing (OLAP) message value.
-
Cause: An internal OLAP program in the EXPRESS Analytic Workspace failed to retrieve a user message.
- ORA-36612: (XSLMS01) invalid OLAP message number: value
-
Cause: An internal OLAP DML program in the EXPRESS Analytic Workspace attempted to retrieve a non-existent message.
- ORA-36616: (XSAGMODHIER01) There is a cycle formed by MODEL workspace object and other embedded or containing models with the same dimension, workspace object.
-
Cause: Inclusion of a dynamic model formed a cycle in the named dimension.
- ORA-36617: (XSAGMODHIER02) There is a self-cycle equation in MODEL workspace object.
-
Cause: The model for relation modification included a self-cycle equation.
- ORA-36618: (XSAGMODDIM00) workspace object is not a valid dynamic model for AGGMAP.
-
Cause: The model failed one of the following tests: 1) only one dimension (aside from LAG/LEAD dimensions); 2) assignment to dimension values only; 3) a single simple solution block; 4) no time-series functions with variable step values.
- ORA-36620: (XSAGMODDIM01) MODEL workspace object cannot find the matching embedded model.
-
Cause: AGGMAP ADD model could not find the matching embedded model.
- ORA-36621: (XSAGMODDIM02) You cannot AGGREGATE the individual partition using static model workspace object because a partition dimension or its deriver workspace object appears in the equation of the step or simultaneous block.
-
Cause: An attempt was made to AGGREGATE the individual partition using the static model with the partition dimension in the equation of the step or simultaneous block.
- ORA-36622: (XSAGMODLIST00) workspace object cannot be added to the AGGMAP workspace object because it is not a valid MODEL.
-
Cause: An object specified in AGGMAP ADD was not a model.
- ORA-36626: (XSAGMODLIST02) MODEL workspace object was skipped because there is already a MODEL by that name attached to AGGMAP workspace object.
-
Cause: An attempt was made to add the same model to the AGGMAP twice.
- ORA-36628: (XSAGMODLIST03) MODEL workspace object could not be added to AGGMAP workspace object.
-
Cause: The dimension of the model did not match a hierarchy of the aggmap.
- ORA-36630: (XSDUNION00) An empty base dimension list was specified in the concat dimension definition.
-
Cause: An empty concat dimension list was specified.
- ORA-36632: (XSDUNION01) The concat dimension workspace object is not currently defined as UNIQUE.
-
Cause: An attempt was made to CHGDFN a concat dimension, which was already non-unique, to NOT UNIQUE.
- ORA-36634: (XSDUNION02) INTEGER dimension workspace object cannot be used as a concat dimension base.
-
Cause: The user cannot specify INTEGER base dimensions when defining a concat dimension.
- ORA-36635: (XSDUNION03) The base dimension workspace object has an invalid datatype for use in a UNIQUE concat definition.
-
Cause: Base dimensions of a unique concat must have TEXT or ID datatypes.
- ORA-36636: (XSDUNION04) The unique concat dimension workspace object cannot be changed to NOT UNIQUE, because it is a base of at least one other unique concat dimension.
-
Cause: A non-unique concat dimension could not be used as a base of a dependent unique concat.
- ORA-36637: (XSDUNION05) The concat dimension cannot be defined as UNIQUE because it has a non-unique concat base dimension workspace object.
-
Cause: A non-unique concat dimension could not be used as a base for a dependent unique concat.
- ORA-36638: (XSDUNION17) Concat dimension workspace object cannot be changed to UNIQUE because it has a non-unique concat base dimension workspace object.
-
Cause: A non-unique concat dimension was used as a base for a dependent unique concat.
- ORA-36639: (XSDUNION18) UNIQUE cannot be applied to this concat dimension because LEAVES workspace object and workspace object share the value number.
-
Cause: The UNIQUE concat base dimensions contained duplicate values.
- ORA-36640: (XSDUNION19) Concat dimension workspace object cannot be changed to UNIQUE because base dimension workspace object does not have a TEXT or ID datatype.
-
Cause: Base dimensions of a unique concat must have TEXT or ID datatypes.
- ORA-36641: (XSDUNION20) The concat dimension must be defined as UNIQUE because base dimension workspace object contains custom member values.
-
Cause: The UNIQUE keyword was not specified in the concat dimension definition and is required if any of the base dimensions contain custom member values.
- ORA-36642: (XSDUNION06) Concat dimension list contains duplicate leaf dimension workspace object.
-
Cause: Duplicate concat leaf dimensions were found.
- ORA-36643: (XSDUNION21) Concat dimension workspace object cannot be changed to NOT UNIQUE because it contains custom member values.
-
Cause: Only UNIQUE concat dimensions can have custom member values or base dimensions which contain custom member values.
- ORA-36646: (XSDUNION08) Only concat dimensions can be redefined as UNIQUE. workspace object is not a concat dimension.
-
Cause: The UNIQUE keyword was used with an invalid object.
- ORA-36648: (XSDUNION09) Concat dimension workspace object is already defined as UNIQUE.
-
Cause: The concat dimension could not be changed to UNIQUE because it was already UNIQUE.
- ORA-36650: (XSDUNION10) Concat dimension workspace object cannot be changed to UNIQUE. Leaves workspace object and workspace object share the value number.
-
Cause: The concat dimension could not be changed to UNIQUE because of one or more duplicate values among its bases.
- ORA-36652: (XSDUNION11) workspace object is not a string type dimension.
-
Cause: The CHGDFN BASE ADD command was applied to an object that is not a concat dimensions.
- ORA-36654: (XSDUNION12) workspace object cannot be added to workspace object because it conflicts with the dimensions of object workspace object.
-
Cause: The dimension could not be added using CHGDFN because it was already one the bases of the concat dimension.
- ORA-36656: (XSDUNION13) workspace object is already a member of workspace object and cannot be added.
-
- ORA-36660: (XSDUENG00) The first argument to the string function must be an expression yielding a dimension value.
-
Cause: The user supplied an expression to BASEVAL or BASEDIM that did not yield a valid dimension value.
- ORA-36662: (XSDUENG01) You cannot apply the string function to workspace object because it is not a concat dimension.
-
Cause: You tried to use the BASEVAL or BASEDIM function with an object that is not a concat dimension.
- ORA-36663: (XSDPART01) specify a dimension list when defining a PARTITION TEMPLATE
-
Cause: The PARTITION TEMPLATE specification did not contain a dimension list.
- ORA-36664: (XSDPART02) defined a PARTITION TEMPLATE without a PARTITION BY clause
-
Cause: An attempt was made to define a PARTITION TEMPLATE without a PARTITION BY clause.
- ORA-36665: (XSDPART03) workspace object is not in the dimension list of the partition template.
-
Cause: While defining a partition template, an attempt was made to specify a partition dimension that was not a dimension of the partition template itself.
- ORA-36666: (XSDPART04) workspace object is not a concat dimension.
-
Cause: An attempt was made to define a partition template with PARTITION BY CONCAT(... dim ...) command where dim is not a concat dimension.
- ORA-36667: (XSDPART05) string is not a valid CONCAT partition.
-
Cause: An attempt was made to use RANGE or LIST syntax in defining a CONCAT partition template.
- ORA-36668: (XSDPART06) string is not a legal RANGE partition.
-
Cause: User attempted to use CONCAT or LIST syntax in defining a RANGE partition template.
- ORA-36669: (XSDPART07) string is not a legal LIST partition.
-
Cause: User attempted to use RANGE or CONCAT syntax in defining a LIST partition template.
- ORA-36670: (XSDPART08) workspace object is an INTEGER or NTEXT dimension, or contains an INTEGER or NTEXT dimension. INTEGER and NTEXT dimensions cannot be used as partition dimensions.
-
Cause: User attempted to define a partition template partitioned by an INTEGER or NTEXT dimension or a concat containing an NTEXT leaf.
- ORA-36671: (XSDPART09) Leaves of workspace object have different datatypes. A partition dimension cannot have more than one datatype when RANGE partitioning is used.
-
Cause: User attempted to define a range partition template with a concat partition dimension, and the concat had two leaf dimensions with different datatypes.
- ORA-36672: (XSDPART10) A RANGE or LIST PARTITION TEMPLATE can only have a single partition dimension.
-
Cause: User attempted to define a RANGE or LIST partition template with more than one partition dimension.
- ORA-36673: (XSDPART11) Use simple leaf values to identify concat dimension values in a VALUES LESS THAN clause, rather than the <LEAF: VALUE> format.
-
Cause: While defining a RANGE partition template with a concat dimension for the partition dimension, an attempt was made to define a range using the <LEAF: VALUE> format of a concat dimension value.
- ORA-36674: (XSDPART12) Invalid dimension value starting at string.
-
Cause: When defining a RANGE or LIST partition template, the user specified an invalid value in a VALUES LESS THAN or VALUES clause. An "invalid value" can be one of two things: a value whose datatype does not match the partition dimension's datatype, or a non-constant value.
- ORA-36675: (XSDPART13) A RANGE or LIST PARTITION TEMPLATE cannot have a conjoint for its partition dimension.
-
- ORA-36676: (XSDPART14) Missing dimension list for string.
-
Cause: User attempted to define a CONCAT partition template, and didn't supply a list of dimensions for one of the partition definitions.
- ORA-36677: (XSDPART15) Duplicate value in value lists of number and number.
-
Cause: In a LIST PARTITION TEMPLATE definition, a value appeared in more than one value list, or more than once within a single value list.
- ORA-36678: (XSDPART16) workspace object is missing from one or more partition dimension lists.
-
Cause: In the definition of a partition template, one of the partitions had a dimension list that did not contain all the dimensions of the partition template.
- ORA-36679: (XSDPART17) workspace object contains a leaf (workspace object) that is not part of the partition dimension workspace object.
-
Cause: In the definition of a CONCAT partition template, one of the partitions was dimensioned by a dimension that was concat-related to a partition dimension. For example, it shared some leaves with the partition dimension, but it also contained some leaves that were not in the partition dimension.
- ORA-36680: (XSDPART18) workspace object is not a dimension of the PARTITION TEMPLATE.
-
Cause: In the definition of a partition template, one of the partitions was dimensioned by a dimension that was not given in the dimension list of the partition template.
- ORA-36681: (XSDPART19) Partitions string and string are out of order.
-
Cause: In the definition of a range partition template, a partition with a lower range boundary was listed after a partition with a higher range boundary.
- ORA-36682: (XSDPART20) Partition name string appears more than once.
-
Cause: A list of analytic workspace partitions was specified in which the partition name appeared more than once.
- ORA-36683: (XSDPART21) Partition string dimensioned by more than one composite.
-
Cause: It is illegal to define a partition template in which one of the partitions is dimensioned by more than one composite.
- ORA-36684: (XSDPART22) cannot rename values of DIMENSION workspace object because it is the partition dimension of RANGE PARTITION TEMPLATE workspace object
-
Cause: An attempt was made to rename the value of a dimension that serves as the partition dimension of some RANGE or LIST partition template.
- ORA-36685: (XSDPART23) Only CONCAT partition templates can be subpartitioned.
-
Cause: User attempted to define a RANGE or LIST partition template with one or more partitions dimensioned by another partition template.
- ORA-36686: (XSDPART24) Value number is not in partition number.
-
Cause: User attempted to reorganize a list partition template by removing a value from some partition's list, but the value was not in the list.
- ORA-36687: (XSDPART25) You cannot use compressed composite workspace object to dimension multiple partitions of the partition template, because its dimension list includes the PARTITION BY dimension workspace object.
-
Cause: The specified PARTITION BY dimension also occurred in the dimension list of a compressed composite used to dimension multiple partitions.
- ORA-36688: (NTEXTCNV00) Error during conversion from TEXT to NTEXT.
-
Cause: An unknown character set conversion error occurred when converting a TEXT value to an NTEXT value.
- ORA-36691: (NTEXTCNV02) invalid escape sequence in argument to UNISTR function: string
-
Cause: The UNISTR function was called on a string that had an invalid escape sequence. The only valid escape sequences in UNISTR are - An escape-escape sequence. - An escape, followed by exactly four hexadecimal digits.
- ORA-36692: (XSRELGID24) A level relation must be specified for the GROUPSET and ROLLUP options of GROUPINGID.
-
Cause: level relation was not specified.
- ORA-36693: (XSRELGID25) INHIERARCHY cannot be specified with the GROUPSET and ROLLUP options of GROUPINGID.
-
Cause: INHIERARCHY option was specified.
- ORA-36694: (XSRELTBL01) The value cannot be added to dimension workspace object.
-
Cause: Unknown.
- ORA-36695: (XSRELGID26) The length of GID dimension status is number. The length of LEVEL dimension status is number.
-
Cause: GID dimension status did not match LEVEL dimension status.
- ORA-36696: (XSRELTBL02) QDR dimension workspace object should not be the related dimension of the relation.
-
Cause: An ineligible dimension was specified in the Qualified Data Reference
- ORA-36698: (XSRELTBL03) QDR dimension workspace object is not in the dimension list that dimensions the relation.
-
Cause: The specified qualified data reference (QDR) dimension was not in the dimension list of the relation.
- ORA-36700: (XSRELTBL04) Dimension workspace object cannot be qualified more than once.
-
Cause: The same dimension was specified more than once in the qualified data reference.
- ORA-36702: (XSRELTBL05) The format of the HIERHEIGHT function is: \n HIERHEIGHT(relation [,] level)\n level >= 1.
-
Cause: The HIERHEIGHT function was specified incorrectly.
- ORA-36704: (XSRELTBL06) workspace object should be dimensioned by workspace object.
-
Cause: The level relation is not dimensioned by the source relation dimension.
- ORA-36706: (XSRELTBL07) workspace object should be dimensioned by workspace object and one level dimension.
-
Cause: The destination relation has the wrong definition.
- ORA-36708: (XSMXALLOC00) Variable workspace object must be dimensioned to be used by the ALLOCATE command.
-
Cause: The user supplied an undimensioned (scalar) variable to the ALLOCATE command.
- ORA-36710: (XSMXALLOC01) TARGETLOG variable workspace object must be dimensioned identically to TARGET variable workspace object.
-
Cause: The user attempted to execute ALLOCATE with mismatched TARGET and TARGETLOG variables
- ORA-36712: (XSMXALLOC02) Relation workspace object must be a one-dimensional self-relation to be used as a SOURCE or BASIS with ALLOCATE.
-
Cause: The user specified an invalid source or basis relation on the ALLOCATE command line.
- ORA-36714: (XSMXALLOC03) TARGETLOG variable workspace object must have the same data type as TARGET variable workspace object.
-
Cause: The user specified a TARGETLOG variable that had a different data type from the TARGET variable.
- ORA-36718: (XSALLOC00) You do not have the necessary permissions to use AGGMAP workspace object.
-
Cause: The user did not have sufficient permissions to run the ALLOCATE command
- ORA-36720: (XSALLOC01) To be used with ALLOCATE, your AGGMAP workspace object must be defined with the ALLOCMAP command.
-
Cause: The user used the AGGMAP command to define the AGGMAP, so either the AGGMAP can only be used with the AGGREGATE command, or the AGGMAP has no contents attached to it.
- ORA-36722: (XSALLOC02) In AGGMAP workspace object, you specified an NA or ZERO sourceval but supplied formula workspace object as your source for ALLOCATE.
-
Cause: The user requested that source values be modified during the allocation, but that is not possible when using a formula source.
- ORA-36724: (XSALLOC03) workspace object cannot include more dimensions than the source variable.
-
- ORA-36726: (XSALERR00) The character 'character' is not a valid format specifier for the ALLOCATE error log.
-
Cause: The user specified an invalid formatter in the ALLOCERRLOGHEADER or ALLOCERRLOGFORMAT options.
- ORA-36728: (XSALERR01) While performing the ALLOCATE command with AGGMAP workspace object, the error logging limit of number was exceeded.
-
Cause: The user specified an ERRORLOG MAX value in the ALLOCMAP, but more errors were encountered while performing the allocation.
- ORA-36730: A deadlock occurred allocating data.
-
- ORA-36731: An NA basis parent cell was encountered.
-
- ORA-36732: A value was less than the FLOOR specification.
-
- ORA-36733: A value exceeded the CEILING specification.
-
- ORA-36734: A value was less than the MIN specification.
-
- ORA-36735: A value exceeded the MAX specification
-
Cause: .
- ORA-36736: Renormalizing data
-
- ORA-36737: The logging limit was exceeded.
-
- ORA-36738: Falling back to NAOPERATOR after deadlock.
-
- ORA-36739: Redistributing remainder with REMOPERATOR.
-
- ORA-36740: A CHILDLOCK was detected in your valueset
-
Cause: .
- ORA-36741: A source was OVER ALLOCATED to its children
-
- ORA-36761: (XSLANGDM01) Analytic workspace string already contains a dimension (%J) with the string property.
-
Cause: An attempt was made to apply this property to more than one dimension in the analytic workspace.
- ORA-36762: (XSLANGDM02) Cannot modify the string property of %J because analytic workspace string is attached in multiwriter mode.
-
Cause: An attempt was made to add or delete a $DEFAULT_LANGUAGE property in an analytic workspace (AW) attached in multiwriter mode.
- ORA-36763: (XSAGGCNTMOVE01) Aggregation variable workspace object cannot have itself as an AGGCOUNT.
-
Cause: An attempt was made to turn a variable into its own AGGCOUNT.
- ORA-36764: (XSAGGCNTMOVE02) AGGCOUNT variable workspace object must be of type INTEGER, not string.
-
Cause: An attempt was made to create an AGGCOUNT variable that was not an INTEGER type.
- ORA-36765: (XSAGGCNTMOVE03) A string aggregation variable cannot have a string AGGCOUNT.
-
Cause: The specified AGGCOUNT variable did not have the same TEMPORARY or PERMANENT attribute as the aggregation variable.
- ORA-36766: (XSAGGCNTMOVE04) workspace object cannot be used as an AGGCOUNT because it has an AGGCOUNT.
-
Cause: The specified AGGCOUNT variable had its own AGGCOUNT
- ORA-36767: (XSAGGCNTMOVE05) workspace object cannot be used as an AGGCOUNT while there are permissions applied to it.
-
Cause: The specified AGGCOUNT variable permissions were distinct from those on the aggregation variable.
- ORA-36768: (XSAGGCNTMOVE06) An aggregation variable and its AGGCOUNT must have the same base dimensions.
-
Cause: An AGGCOUNT variable was specified with different base dimensions than the aggregation variable.
- ORA-36777: Unable to allocate string bytes for the OLAP page pool.
-
Cause: Insufficient memory was available to allocate the needed memory for the online analytical processing (OLAP) page pool. One cause is the value of the OLAP_PAGE_POOL_SIZE initialization parameter.
- ORA-36778: (XSPGTRLOW) The amount of available temporary storage is still low. Free some temporary storage immediately. You can do so, for example, by UPDATING or DETACHING an analytic workspace.
-
Cause: Ran out of temporary tablespace storage.
- ORA-36779: invalid parameter value specified for OLAP_PAGE_POOL_SIZE
-
Cause: The specified value for the OLAP_PAGE_POOL_SIZE initialization parameter was out of range. The OLAP_PAGE_POOL_SIZE initialization parameter must be between 2,097,152 (2MB) and 2,147,483,647, and it must be less than 90% of the PGA_AGGREGATE_LIMIT initialization parameter. Furthermore, you cannot set a fixed-size OLAP page pool with multiple tablespace block sizes. The OLAP_PAGE_POOL_SIZE initialization parameter remains unmodified.
- ORA-36780: (IOSEC01) Current Directory Alias is not set. Cannot complete string.
-
- ORA-36782: (IOSEC02) Directory Alias used in string does not exist, or you do not have sufficient privileges to access it.
-
- ORA-36783: Directory alias used in string does not exist, or there are insufficient access privileges.
-
Cause: The directory alias did not exist, or there were insufficient access privileges.
- ORA-36784: (IOSEC03) string is an invalid directory or file name.
-
Cause: The supplied value could not be interpreted as a directory or a file name.
- ORA-36785: Invalid directory or file name string.
-
- ORA-36786: (IOSEC04) File string does not exist or cannot be accessed.
-
- ORA-36792: (IOSEC07) Error accessing file string.
-
- ORA-36793: Error accessing file string.
-
- ORA-36802: (XSTBLFUNC01) The OLAP_TABLE function must contain a DATAMAP that executes a FETCH command or a LIMITMAP.
-
Cause: There is no limitmap on the table function and either the datamap does not contain a fetch, or it errored before the fetch was called.
- ORA-36804: (XSTBLFUNC02) The OLAP_TABLE function encountered an error while parsing the LIMITMAP.
-
Cause: Invalid LIMITMAP syntax, or the name resolution failure of an ANALYTIC WORSKPACE OBJECT.
- ORA-36806: (XSTBLFUNC03) The OLAP_TABLE function refers to an invalid ADT attribute: string.
-
Cause: The limitmap refers to a matching of ADT attribute to AW object, but the ADT attribute is not an element of the specified ADT table. Most commonly this is a typo.
- ORA-36808: (XSTBLFUNC04) The OLAP_TABLE function LEVELREL clause cannot declare number ADT fields from number AW fields.
-
Cause: The limitmap has a levelrel clause which has a different number of values in the list to the right of the FROM than it has to the left.
- ORA-36810: (XSTBLFUNC05) Analytic workspace object number does not exist.
-
Cause: The limitmap refers to a non-existent aw object.
- ORA-36814: (XSTBLFUNC07) The datatype of the column used in the ROW2CELL clause of a LIMITMAP must be RAW(16).
-
Cause: Datatype of column used in ROW2CELL clause of a LIMITMAP is not RAW(16).
- ORA-36815: (XSTBLFUNC08) The OLAP_TABLE has attempted to use an AW single row function with the aw_attach parameter set to DURATION QUERY.
-
Cause: The OLAP_TABLE aw_attach parameter was set to DURATION QUERY.
- ORA-36816: (XSTBLFUNC09) The workspace object dimension is of datatype string which does not support custom member upserts.
-
Cause: Custom members were attempted to be added via an upsert to a dimension that does not support them
- ORA-36817: (XSTBLFUNC10) The LIMITMAP LOOP clause specifies an invalid type of object. workspace object must be a DIMENSION or COMPOSITE.
-
Cause: An invalid type of object was specified in the LOOP clause.
- ORA-36818: (XSTBLFUNC11) A LIMITMAP DIMENSION clause specifies an invalid type of object. workspace object must be a DIMENSION.
-
Cause: An invalid type of object was specified in the DIMENSION clause.
- ORA-36819: (XSTBLFUNC12) workspace object cannot be used in a LIMITMAP string clause.
-
Cause: An invalid type of object was specified in a LIMITMAP clause.
- ORA-36820: (XSLMINFO00) The LIMITMAPINFO function encountered an error while parsing the LIMITMAP.
-
Cause: Invalid LIMITMAP syntax.
- ORA-36825: (XSTBLFUNC13) An error occurred expanding the cube_name argument in the OLAP table function
-
Cause: Incorrect metadata or invalid cube name
- ORA-36826: (XSTBLFUNC14) OLAP C Looper is disabled by event 37395
-
Cause: init.ora event 37395 includes level 8 which disables the OLAP C looper
- ORA-36831: (XSLMGEN01) View token cannot be NA
-
Cause: A NA was passed as the view token
- ORA-36832: (XSLMGEN02) View token cannot be greater than 4000 bytes
-
Cause: A view token was greater than 4000 bytes
- ORA-36833: (XSLMGEN03) View token cannot be blank
-
Cause: A blank was passed as the view token
- ORA-36834: (XSLMGEN04) Column tag is greater than 30 bytes
-
Cause: A value greater than 30 bytes was passed as the column tag
- ORA-36835: (XSLMGEN05) Dimension string.string hierarchy string level string is missing a COLUMNNAME property value
-
Cause: The COLUMNNAME property has no value
- ORA-36836: (XSLMGEN06) The dimensionality of object string.string is different than the view token
-
Cause: The dimensionality of the cube does not match the view token
- ORA-36837: (XSLMGEN07) Object owner string is different than string
-
Cause: The object owners are different
- ORA-36838: (XSLMGEN08) Dimension string.string attribute string is missing a COLUMNNAME property value
-
Cause: The COLUMNNAME property has no value
- ORA-36839: (XSLMGEN09) Cube string.string measure string is missing a COLUMNNAME property value
-
Cause: The COLUMNNAME property has no value
- ORA-36840: (XSLMGEN10) Cube string.string has no measures
-
Cause: The cube has no measures
- ORA-36841: (XSLMGEN11) Dimension string.string was not found
-
Cause: The view token referenced a dimension that does not exist
- ORA-36842: (XSLMGEN12) Hierarchy string.string.string was not found
-
Cause: The view token referenced a hierarchy that does not exist
- ORA-36843: (XSLMGEN13) Dimension string.string hierarchy string is missing a PHYSICALNAME property value
-
Cause: The property PHYSICALNAME has no value
- ORA-36844: (XSLMGEN14) Dimension string.string is missing a string property value
-
Cause: The dimension is missing a required property
- ORA-36845: (XSLMGEN15) Owner is greater than 30 bytes
-
Cause: The owner passed is greater than 30 bytes
- ORA-36846: (XSLMGEN16) AW name is greater than 30 bytes
-
Cause: The AW name passed is greater than 30 bytes
- ORA-36847: (XSLMGEN17) AW name is blank
-
Cause: The AW name passed is blank
- ORA-36848: (XSLMGEN18) Object name string is different than string
-
Cause: The object names are different
- ORA-36849: (XSLMGEN19) AW owner does not match View token owner
-
Cause: The AW owner does not match the View token owner
- ORA-36850: (XSLMGEN20) View token string is not correct
-
Cause: The view token is not correct
- ORA-36861: (XSTFRC01) SQL Cache ID parameter is invalid or missing.
-
Cause: SQL Cache ID parameter is required to identify SQL cache to query
- ORA-36862: (XSTFRC02) Column number for this SQL Cache must be between 1 and number. Specified column number number is invalid.
-
Cause: Column Map references a column number that is greater than the maximum column number in SQL Cache
- ORA-36871: (XSFTDSC01) Object string cannot be used to define a column in a LIMITMAP.
-
Cause: The object cannot define a column in LIMITMAP most likely because it is of a wrong type such as, for example, a Worksheet.
- ORA-36872: (XSTFDSC02) Column type specifier cannot be used when the table function data type is specified.
-
Cause: Column type can only be used with implicitly-specified table functions
- ORA-36874: (XSTFDSC04) Expression string cannot be used to define a column in a LIMITMAP.
-
Cause: The expression cannot define a column in LIMITMAP most likely because it is of a wrong type such as, for example, a Worksheet.
- ORA-36875: (XSTFDSC05) LIMITMAP is missing or is not a string literal.
-
Cause: Table functions that have an automatic ADT require LIMITMAP to be a string literal.
- ORA-36876: (XSTFDSC06) The column datatype string is not supported in OLAP table functions.
-
Cause: The object type layer does not support column datatype.
- ORA-36881: (XSSRF00) The OLAP DML ROW2CELL function can only be used in a LIMITMAP.
-
Cause: Using the ROW2CELL function outside of the LIMITMAP.
- ORA-36882: (XSSRF01) The second parameter of an AW single row function cannot be NULL.
-
Cause: The second parameter of the AW single row function was NULL
- ORA-36883: (XSSRF02) The first parameter of an AW single row function cannot be NULL.
-
Cause: The first parameter of the AW single row function was NULL
- ORA-36884: (XSSRF03) The value of the first parameter of the AW single row function is incorrect.
-
Cause: The column specified in the LIMITMAP ROW2CELL clause was not the first parameter of the AW single row function.
- ORA-36885: (XSSRF04) Error rewriting OLAP DML expression. Column name too big
-
Cause: The column name specified in the OLAP DML expression was larger than 30 bytes.
- ORA-36886: (XSSRF05) Error rewritting OLAP DML expression. Rewritten expression is greater than number bytes
-
Cause: The rewritten OLAP DML expression was larger than the output buffer.
- ORA-36887: (XSSRF06) Error rewriting OLAP DML expression. Column name string is not a valid ADT column.
-
Cause: The column name passes does not exist.
- ORA-36902: (XSAGDNGL43) In AGGMAP workspace object, the MODEL workspace object is not a model over a base dimension of the AGGMAP.
-
Cause: Model may include equations others than dimension values, or blocks other than simple blocks.
- ORA-36904: (XSAGDNGL44) In AGGMAP workspace object, RELATION workspace object occurs after a dynamic model. The dynamic model must be the last calculation within the AGGMAP.
-
Cause: Before the current relation, dynamic model exists.
- ORA-36910: (XSAGDNGL47) In AGGMAP workspace object, DYNAMIC MODEL workspace object can only edit the top level of its matching relation hierarchy.
-
Cause: The model attempted to edit a child node in the relation hierarchy.
- ORA-36912: (XSAGDNGL48) In AGGMAP workspace object, MODEL workspace object cannot be simultaneous.
-
Cause: The aggmap contained a simultaneous model.
- ORA-36913: (XSAGDNGL49) In AGGMAP workspace object, LOAD_STATUS object workspace object must be an undimensioned VALUESET over the relation dimension.
-
Cause: The object refered to by the LOAD_STATUS clause of the aggmap wasn't an undimensioned valueset over the related dimension
- ORA-36914: (XSAGDNGL50) In AGGMAP workspace object, LOAD_STATUS valueset workspace object contains both a child and its ancestor.
-
Cause: The LOAD_STATUS valueset is not allowed to contain both a dimension value and an ancestor of that value.
- ORA-36920: (XSVPMVTOPART01) workspace object cannot become anonymous because it has properties.
-
Cause: The OLAP DML command would result in a named object becoming an anonymous object, but the object had one or more properties associated with it.
- ORA-36921: (XSVPMVTOPART02) workspace object and workspace object are not in the same analytic workspace.
-
Cause: The OLAP DML command requires certain objects to be in the same analytic workspace, and the command string specified objects from two different analytic workspaces.
- ORA-36922: (XSVPMVTOPART03) workspace object is the target of an external partition of a partitioned variable.
-
Cause: An attempt was made to perform some prohibited operation on a variable which is itself a partition of some other variable.
- ORA-36923: (XSVPMVTOPART04) workspace object is not a LIST or RANGE PARTITION TEMPLATE.
-
Cause: The user ran a command that only operates on a LIST or RANGE partition template (or a variable dimensioned by a LIST or RANGE partition template) on some other kind of analytic workspace object.
- ORA-36924: (XSVPMVTOPART05) workspace object is not in a COMPOSITE.
-
Cause: The OLAP DML command expected that the variable would be dimensioned by a composite containing the specified dimension, the specified dimension within a composite.
- ORA-36925: (XSVPMVTOPART06) Partition number has some values that are not in workspace object.
-
- ORA-36930: Cannot start a recursive call to Oracle OLAP because a ROLLBACK past an UPDATE to an attached analytic workspace has been performed.
-
Cause: ROLLBACK past the UPDATE of one of the attached Analytic Workspaces was called. A recursive Oracle OLAP call cannot be made until the control returns to the initial OLAP call and the affected Analytic Workspaces detached.
- ORA-36940: (XSDPENG00) The PARTITION function cannot be applied to workspace object because it is not a partition template.
-
Cause: An attempt was made to apply the PARTITION function to an object that was not a partition template.
- ORA-36950: (XSFCAST22) The list of string values cannot have more than number members. number were supplied.
-
Cause: More than the maximum number of OFFSET or PERIODICITY values were specified.
- ORA-36951: (XSFCAST28) The ALLOCLAST parameter cannot be set to YES unless PERIODICITY specifies more than one cycle.
-
Cause: The ALLOCLAST parameter was set to YES when the PERIODICITY parameter specified a single value rather than a list of nested cycles.
- ORA-36952: (XSFCAST23) cannot specify a cycle number when querying the string forecasting option
-
Cause: A cycle number was specified in a call to the FCQUERY function to retrieve forecast data not related to a cycle.
- ORA-36954: (XSFCAST24) The cycle number must be between 1 and number. You specified number.
-
Cause: A cycle number less than 1 or greater than the maximum value was specified in a call to FCQUERY.
- ORA-36956: (XSFCAST25) There are only number PERIODICITY values. You cannot specify more OFFSET values.
-
Cause: More OFFSET values were specified than PERIODICITY values.
- ORA-36958: (XSFCAST26) The OFFSET value for cycle number cannot be greater than the cycle's PERIODICITY, which is number. You specified number.
-
Cause: The OFFSET for a cycle exceeded the PERIODICITY for that cycle.
- ORA-36960: (XSFCAST27) The value of the string expression must be an odd number. You specified number.
-
Cause: An even number was given for an option that requires an odd number.
- ORA-36961: Oracle OLAP is not available.
-
Cause: An attempt was made to utilize functionality found only in Oracle OLAP, but Oracle OLAP was not enabled in the executable.
- ORA-36962: (XSRELTBL08) string is not a valid workspace object.
-
Cause: The specified value did not exist in the dimension.
- ORA-36963: (XSRELTBL16) INHIERARCHY object workspace object should be a valid valueset or boolean variable.
-
Cause: Invalid valueset or variable was specified.
- ORA-36964: (XSRELTBL09) workspace object is not a valid level relation.
-
Cause: The specified level relation was not consistent with the parentage hierarchy.
- ORA-36965: (XSRELTBL17) Invalid LEVELORDER valueset workspace object.
-
Cause: Invalid LEVELORDER valueset was specified.
- ORA-36966: (XSRELTBL10) workspace object must be a dimension.
-
Cause: The qualified object must be a dimensions.
- ORA-36967: (XSRELTBL18) invalid INHIERARCHY valueset workspace object
-
Cause: An invalid valueset was specified for the INHIERARCHY parameter.
- ORA-36968: (XSRELTBL11) Invalid relation workspace object.
-
Cause: Non-object or an object other than a RELATION was specified as source or destination.
- ORA-36969: (XSRELTBL19) Merged family relation cannot take INHIERARCHY option.
-
Cause: INHIERARCHY option was specified.
- ORA-36970: (XSRELTBL12) workspace object must be a self-relation.
-
Cause: The specified source relation was not a self-relation.
- ORA-36971: (XSRELTBL20) Merged family relation cannot take LEVELORDER option.
-
Cause: LEVELORDER option was specified.
- ORA-36972: (XSRELTBL13) Relation workspace object must be dimensioned by workspace object.
-
Cause: Destination relation is not dimensioned by source relation dimension.
- ORA-36974: (XSRELTBL14) workspace object is not a BOOLEAN variable dimensioned by all the dimensions of the hierarchy.
-
Cause: The named variable had either the wrong data type or the wrong dimensions.
- ORA-36975: (XSRELTBL15) The USING clause did not name a relation with the same level dimension as LEVELORDER valueset workspace object.
-
Cause: Either the USING clause was omitted from the HIERHEIGHT command, or specified a relation that contained values of a different dimension other than the LEVELORDER valueset.
- ORA-36976: (XSRELGID00) Invlid GROUPINGID destination relation or variable workspace object.
-
Cause: Non-Object or invalid relation or invlid variable.
- ORA-36977: (XSRELGID17) The GROUPINGID command does not support hierarchies with more than 126 levels.
-
Cause: A hierarchy was specified with more than 126 levels.
- ORA-36978: (XSRELGID01) workspace object must be a self-relation.
-
Cause: Source relation is not a self-relation.
- ORA-36979: (XSRELGID18) Property number can only be set by the GROUPINGID command.
-
Cause: You tried to set the $GID_DEPTH property.
- ORA-36980: (XSRELGID02) Variable workspace object must have a numeric data type.
-
Cause: The destination variable does not have a numeric data type.
- ORA-36981: (XSRELGID19) The format of the GROUPINGID function is:\n \n GROUPINGID(gidrel1 [gidrel2]...)
-
Cause: Bad syntax
- ORA-36982: (XSRELGID03) The destination variable/relation workspace object must be dimensioned by all dimensions of the source relation workspace object that have more than one value in status.
-
Cause: Destination variable/relation does not have enough dimensionality to hold the result from the multi-dimensional source relation.
- ORA-36983: (XSRELGID20) The groupingid relation workspace object repeats.
-
Cause: The groupingid relation repeated.
- ORA-36984: (XSRELGID04) A value cannot be inserted into dimension workspace object.
-
Cause: An error occurred that prevented a value from being added to the named dimension.
- ORA-36985: (XSRELGID21) The source relation can be omitted only when using both surrogate GID and level order valueset.
-
Cause: Source relation was not specified.
- ORA-36986: (XSRELGID05) Relation workspace object must be dimensioned by workspace object.
-
Cause: The destination relation was not dimensioned by the dimension of the source relation.
- ORA-36988: (XSRELGID06) The related dimension of relation workspace object must be of type NUMBER.
-
Cause: The related dimension of the destination relation has the wrong data type.
- ORA-36989: (XSRELGID23) GROUPSET and ROLLUP options in GROUPINGID require the destination relation.
-
Cause: Either variable or surrrogate dimension was specified as destination.
- ORA-36990: (XSRELGID07) The level relation workspace object should be dimensioned by a level dimension.
-
Cause: The level relation was not dimensioned by a level dimension.
- ORA-36991: (XSRELGID08) The level relation and level order valueset provide inconsistent level mappings.
-
Cause: There is a conflict between the hierarchy/level relation and the level order valueset.
- ORA-36992: (XSRELGID09) A level relation is needed to produce a surrogate dimension gid.
-
Cause: A level relation was not specified.
- ORA-36993: (XSRELGID10) OBJECT workspace object must be a SURROGATE DIMENSION based on the level dimension workspace object.
-
Cause: The object specified was not a surrogate dimension based on the level dimension.
- ORA-36994: (XSRELGID11) The SURROGATE DIMENSION workspace object must be numeric.
-
Cause: The surrogate dimension is not numeric
- ORA-36995: (XSRELGID12) There are duplicate values in the surrogate dimension gid. Use the levelorder option to resolve the ambiguity.
-
Cause: more than 1 hierarchies in the current computing scope.
- ORA-36996: (XSRELGID13) Valueset workspace object should be defined over dimension workspace object.
-
Cause: The specified INHIERARCHY valueset did not contain values of the hierarchy dimension.
- ORA-36997: (XSRELGID14) For variable or relation grouping ids, a level relation is needed when a level order valueset is specified.
-
Cause: no level relation exists with level order valueset.
- ORA-36998: (XSRELGID15) LEVELORDER valueset workspace object and level relation workspace object do not have the same level dimension.
-
Cause: A mismatch was detected between the level dimension of the LEVELORDER valueset and that of the level relation specified in the USING clause.
- ORA-36999: (XSRELGID16) OBJECT workspace object is not a surrogate dimension, a source relation must be specified when creating any non-surrogate grouping id.
-
Cause: use variable/relation gid without providing the source relation
- ORA-37000: (NOTALIAS00) workspace object is not an ALIAS DIMENSION of workspace object.
-
Cause: The user specified an object which is not alias dimension of the first dimension
- ORA-37001: You have one or more attached but unupdated analytic workspaces.
-
Cause: The user has attempted to shut down OLAP, but they have active analytic workspaces whose changes have not been saved.
- ORA-37003: (AWLISTALL01) number readers
-
Cause: Used in AW(LISTALL) output formatting when %d is 0.
- ORA-37010: (XSACQUIRE_DIFFAW) When using the CONSISTENT WITH clause, all objects must come from the same analytic workspace.
-
Cause: The ACQUIRE command cannot keep objects from several workspaces consistent with each other
- ORA-37011: (XSACQUIRE_LOCKED) Object workspace object is locked by another user.
-
Cause: Could not acquire (or acquire consistent) the object, since it is locked by another user
- ORA-37012: (XSACQUIRE_TIMEOUT) Object workspace object is locked by another user and the WAIT timed out.
-
Cause: Could not acquire (or acquire consistent) the object for a while, since it is locked by another user
- ORA-37013: (XSACQUIRE_DEADLOCK) Cannot wait to acquire object workspace object, since doing so would cause a deadlock.
-
Cause: Waiting to acquire the object would cause a deadlock
- ORA-37014: (XSACQUIRE_ACQUIRED) Object workspace object is already acquired.
-
Cause: The object is already acquired
- ORA-37015: (XSACQUIRE_YNRESYNC) Object workspace object is ambiguously listed to be acquired both with and without RESYNC.
-
Cause: The object is listed in with resync list and no resync list. Such usage is ambiguous as to the user's intent on preserving or not preserving private changes.
- ORA-37016: (XSACQUIRE01) You must specify objects to acquire for the ACQUIRE command.
-
Cause: A list of objects to acquire with or without resync is missing
- ORA-37018: (XSACQUIRE03) Multiwriter operations are not supported for object workspace object.
-
Cause: Multiwriter presently does not work for this object type
- ORA-37020: (XSMULTI01) Analytic workspace string is not in MULTI mode.
-
Cause: The workspace for an object is not in multiwriter mode. Hence, no multiwriter operations are allowed on the objects in the workspace
- ORA-37021: (XSMULTI02) Object workspace object is not acquired.
-
Cause: The object must be acquired for this multiwriter operation
- ORA-37023: (XSMLTUPD01) Object workspace object cannot be updated without dimension workspace object.
-
Cause: One cannot update an object if it is dimensioned by a maintained dimension without updating that dimension or if the object is a relation and the dimension is its target.
- ORA-37026: (XSMLTRESYNC01) Object workspace object cannot be resynced without dimension workspace object.
-
Cause: One cannot resync an object if it is dimensioned by a maintained dimension without updating that dimension or if the object is a relation and the dimension is its target.
- ORA-37027: (XSMLTRESYNC02) Object workspace object cannot be resynced without modified object workspace object because they share a modified composite dimension.
-
Cause: When one resyncs an object that is dimensioned by a composite dimension, the composite dimension is resynced automatically, dropping all new tuples. This cannot be done, however, if the automatic resync of the composite dimension might cause data in an object that shares the composite dimension to become NA.
- ORA-37028: (XSMLTRESYNC03) Object workspace object cannot be resynced without modified object workspace object because they share a modified dimension map.
-
Cause: When one resyncs an object that is dimensioned by a dimension map, the dimension map is resynced automatically, dropping all changes. This cannot be done, however, if the automatic resync of the dimension map might cause data in an object that shares the dimension map to become NA.
- ORA-37030: (XSMLTMAINT01) You cannot maintain workspace object because it is not ACQUIRED.
-
Cause: One cannot maintain a dimension in a multiwriter AW if it is not acquired.
- ORA-37031: (XSMLTMAINT02) You cannot DELETE values of dimension workspace object in MULTI mode.
-
Cause: DELETE is allowed in multiwriter mode only for SESSION dimension members
- ORA-37032: (XSMLTMAINT03) cannot MAINTAIN partition template workspace object in MULTI mode
-
Cause: An attempt was made to add or remove values from LIST partition template lists while the analytic workspace containing the partition template was attached in multiwriter mode.
- ORA-37035: (XSMLTDCL01) You can only DEFINE SESSION objects in analytic workspace string because it is attached in MULTI mode.
-
Cause: Persistent object definition in multiwriter mode is not allowed.
- ORA-37036: (XSMLTDCL02) You cannot DELETE objects in analytic workspace string because it is attached in MULTI mode.
-
Cause: One cannot delete objects in an analytic workspace attached in MULTI mode.
- ORA-37037: (XSMLTDCL03) You cannot RENAME objects in analytic workspace string because it is attached in MULTI mode.
-
Cause: One cannot rename objects in an analytic workspace attached in MULTI mode.
- ORA-37038: (XSMLTDCL04) You cannot change definitions of objects in analytic workspace string because it is attached in MULTI mode.
-
Cause: One cannot used CHGDFN command on objects in an analytic workspace attached in MULTI mode.
- ORA-37039: (XSMLTDCL05) You cannot maintain triggers in analytic workspace string because it is attached in MULTI mode.
-
Cause: One cannot use TRIGGER command on objects in an analytic workspace attached in MULTI mode.
- ORA-37040: (XSACQUIRE_DEP_LOCKED) Composite, concat, dimension map, or internal partition workspace object is locked by another user.
-
Cause: Some object required locking a composite, concat, dimension map, or internal partition, which is locked by another user
- ORA-37041: (XSACQUIRE_DEP_TIMEOUT) Composite, concat, dimension map, or internal partition workspace object is locked by another user and the WAIT timed out.
-
Cause: Some object required locking a composite, concat, dimension map, or internal partition, which could not be locked for a while, since it is locked by another user
- ORA-37042: (XSACQUIRE_DEP_DEADLOCK) Cannot wait to acquire composite, concat, dimension map, or internal partition workspace object, since doing so would cause a deadlock.
-
Cause: Some object required locking a composite, concat, dimension map, or internal partition, which would cause a deadlock
- ORA-37043: (XSACQUIRE_DEP_OLDGEN) Composite, concat, dimension map, or internal partition workspace object cannot be locked, since another user has committed a new one already.
-
Cause: Some object required locking a composite, concat, dimension map, or internal partition in the present generation, which is not possible, since a newer generation already exists.
- ORA-37044: (XSACQUIRE_OLDGEN) Cannot acquire object workspace object without resync.
-
Cause: Could not acquire the object without resync because another user has committed a newer version of it already.
- ORA-37050: (XSMLTDCL06) You cannot use the RELATION command with workspace object because analytic workspace string is attached in MULTI mode.
-
Cause: One cannot use the RELATION command on objects in an analytic workspace attached in MULTI mode.
- ORA-37051: (XSAWRESREV01) You cannot RESYNC or REVERT analytic workspace string because one or more objects have been defined in it during this session.
-
- ORA-37052: (XSAWRESREV02) You cannot RESYNC or REVERT analytic workspace string because one or more objects have been deleted from it during this session.
-
- ORA-37053: (XSAWRESREV03) You cannot RESYNC or REVERT analytic workspace string because one or more of its objects have had their definitions changed during this session.
-
- ORA-37054: (XSAWRESREV04) You cannot RESYNC or REVERT analytic workspace string because it contains one or more unnamed composites renamed during this session.
-
- ORA-37055: (XSAWRESREV05) You cannot RESYNC analytic workspace string because another session has changed the definitions of one or more objects it contains.
-
- ORA-37056: (XSAWRESREV06) You cannot RESYNC or REVERT analytic workspace string because one or more SESSION dimensions or composites are based on workspace object.
-
- ORA-37072: (XSMCSESS00) Object workspace object has the wrong type.
-
Cause: The object is not of the object type specified in the APPLY clause
- ORA-37073: (XSMCSESS01) Applied relation workspace object must be dimensioned by dimension workspace object.
-
Cause: Applied relation has the different dimension from the dimension currently being maintained
- ORA-37074: (XSMCSESS02) Variable workspace object has no default aggmap.
-
Cause: The applied variable has no default aggmap
- ORA-37075: (XSMCSESS03) You cannot rename a session-only dimension value.
-
Cause: The user tried to apply MAINTAIN RENAME to a SESSION value.
- ORA-37076: (XSMCSESS04) workspace object is not the type of dimension that can have session-only values. Valid types are TEXT, NTEXT, ID, NUMBER, and CONCAT with the UNIQUE attribute.
-
Cause: The user tried to add a SESSION value to a dimension type that does not support SESSION values.
- ORA-37077: (XSMCSESS05) Object workspace object is specified more than once.
-
Cause: The same object name was given more than once in the apply clause or in the step dimension list.
- ORA-37078: (XSMCSESS06) The dimension being maintained (workspace object) cannot also be used as a step dimension.
-
Cause: The dimension being maintained was named as a step dimension.
- ORA-37079: (XSMCSESS07) Aggmap workspace object cannot be used for AGGREGATE.
-
Cause: The current aggmap may be for ALLOCATE
- ORA-37080: Advice requested for hierarchy with too many levels
-
Cause: A request was made for advice on a hierarchy with more levels than are supported.
- ORA-37082: invalid percent specified for pre-computation
-
Cause: Advice was requested for an invalid percent value for pre-computation.
- ORA-37083: advice requested for invalid object string
-
Cause: Advice was requested for an invalid object name.
- ORA-37084: Output valueset string must match string's dimensionality
-
Cause: A request was made for advice for a relation with different dimensionality from the output valueset.
- ORA-37086: string is not a valueset
-
Cause: An operation was attempted that supports only valuesets as precompute expressions in an aggmap, yet a different kind of precompute expression was used.
- ORA-37093: (XSOBJORG_BAD_CUBE) invalid property "string" specified for cube "string.string"
-
Cause: Either the specified cube did not have an analytic workspace (AW) organization or the specified property did not apply to cubes.
- ORA-37094: (XSOBJORG_BAD_DIM) invalid property "string" specified for dimension "string.string"
-
Cause: Either the specified dimension did not have an analytic workspace (AW) organization, or the specified property did not apply to dimensions.
- ORA-37095: (XSOBJORG_BAD_MEAS) invalid property "string" specified for measure "string.string.string"
-
Cause: Either the specified measure did not have an analytic workspace organization, or the specified property did not apply to measures.
- ORA-37096: (XSOBJORG_BAD_ATTR) invalid property "string" specified for base attribute "string.string.string"
-
Cause: Either the specified base attribute did not have an analytic workspace (AW) organization, or the specified property did not apply to the base attribute.
- ORA-37097: (XSOBJORG_BAD_DIM_LEVEL) invalid property "string" specified for dimension level "string.string.string"
-
Cause: Either the specified dimension level did not have an analytic workspace (AW) organization or the specified property did not apply to dimension levels.
- ORA-37098: (XSOBJORG_BAD_MODEL) invalid property "string" specified for dimension calculation model "string.string.string"
-
Cause: Either the specified dimension calculation model did not have an analytic workspace (AW) organization, or the specified property did not apply to the dimension calculation models.
- ORA-37099: (XSOBJORG_BAD_DIMALITY) invalid property "string" specified for dimensionality "string.string.string"
-
Cause: Either the specified dimensionality did not have an analytic workspace organization, or the specified property did not apply to dimensionalities.
- ORA-37100: (XSUNCOMMITTED) You have one or more updated but uncommitted analytic workspaces.
-
Cause: The user has attempted to shut down OLAP, but they have active analytic workspaces whose changes have not been saved.
- ORA-37101: (XSVPART01) Partitioning information can only be given for variables dimensioned by a PARTITION TEMPLATE.
-
Cause: User attempted to define or reference an AW object with the "all internal" phrase or internal / external partition list, but the object was not a variable, was not dimensioned by a partition template, or was an already existing target of an external partition.
- ORA-37102: (XSVPART02) Invalid partition name string.
-
Cause: The user gave an invalid partition name. When defining a partitioned variable, this message indicates that the partition name does not exist in the partition template. In any other context, it indicates that the partitioned variable or partition template does not have a partition with the given name.
- ORA-37103: (XSVPART03) The dimensionality or datatype of workspace object does not match the dimensionality or datatype of the partition.
-
Cause: User attempted to define a partitioned variable with an external partition, but the target of the external partition had incorrect dimensionality or datatype.
- ORA-37104: (XSVPART04) A partitioned variable must be dimensioned by a single partition template only.
-
Cause: User attempted to define a partitioned variable with more than one partition templates, or a partition template and one or more other dimensions, in the dimension list.
- ORA-37105: (XSVPART05) Only variables dimensioned by a CONCAT PARTITION TEMPLATE can have string partitions.
-
Cause: Attempted to create an external partition on a partitioned variable, but variable was dimensioned by a RANGE or LIST partition template.
- ORA-37106: (XSVPART06) Invalid partition name number.
-
Cause: The user gave an invalid partition name.
- ORA-37107: (XSVPART07) Attempt to write to non-existent partition of workspace object.
-
Cause: Some action attempted to write data to a partitioned variable, but the variable didn't have a partition for that data. This can result from a partition template that does not assign all possible dimension values to some subcube, or from a partitioned variable that does not have a partition for one of the partitions defined by the partition template.
- ORA-37108: (XSVPART08) workspace object has an AGGCOUNT, but workspace object does not.
-
Cause: An attempt was made to add a partition to a partitioned variable. Either the partition was defined WITH AGGCOUNT and the partitioned variable was not, or the partitioned variable was defined WITH AGGCOUNT and the partition was not.
- ORA-37109: (XSVPART09) Partition workspace object and its parent variable workspace object cannot both be specified.
-
Cause: Partition and its parent partition were operated upon together.
- ORA-37111: unable to load the OLAP API sharable library: (string)
-
Cause: This could happen if: - The online analytical processing (OLAP) API sharable library was missing. - The sharable library upon which the OLAP API sharable library depends was missing. - The OLAP API sharable library was the wrong version.
- ORA-37113: OLAP API initialization error: (string)
-
Cause: OLAP API initialization failed.
- ORA-37114: Online Analytical Processing (OLAP) API bootstrap error: (string)
-
Cause: OLAP API bootstrapping failed.
- ORA-37115: New OLAP API history is not allowed
-
Cause: If there are active OLAP API sessions, it is not allowed to start a new OLAP API history by setting _olapi_history_retention parameter to true.
- ORA-37116: OLAP API table function error: (string)
-
Cause: OLAP API table function failed.
- ORA-37117: olapi history retention has been disabled
-
Cause: Under certain circumstances, for example, when the database is read only, olapi history retention is not possible because it requires updating persistent tables from time to time. If olapi history retention has been disabled, setting _olapi_history_retention parameter to true has no effect.
- ORA-37118: The Online Analytical Processing (OLAP) API library was not preloaded.
-
Cause: In shared-server mode, the OLAP API library must be loaded during process initialization to ensure that the C++ virtual table addresses are identical in all shared server processes. The OLAP API session was executing in a process in which the library had not been loaded.
- ORA-37119: Incompatible Online Analytical Processing (OLAP) application programming interface (API) library load address.
-
Cause: The OLAP API session was executing in a process in which the OLAP API sharable library was loaded which was at a different address than the process in which the OLAP API session originated.
- ORA-37120: expression string is null
-
Cause: expression parser received a null string for syntax analysis.
- ORA-37121: AW Spreadsheet invalidated
-
Cause: While this cursor was open, a command was issued that changed the underlying data to become inconsistent.
- ORA-37122: AW Session cache disabled
-
Cause: A SQL Spreadsheet was attempted while the AW Session cache was disabled.
- ORA-37123: (XSCCOMP17) Can not AGGREGATE workspace object(partition number) because it depends on unaggregated compressed partition number.
-
Cause: attempted to use a feature not supported by CC's in the current AW format
- ORA-37124: (XSCCOMP16) COMPRESSED COMPOSITES with string are not supported in analytic workspace string because it has not been upgraded to version string.
-
Cause: attempted to use a feature not supported by CC's in the current AW format
- ORA-37126: (XSCCOMP01) The COMPRESSED COMPOSITE workspace object can only be used as the base of a single variable.
-
Cause: An attempt was made to DEFINE a variable dimensioned by a COMPRESSED COMPOSITE, but that COMPRESSED COMPOSITE was already being used by another VARIABLE.
- ORA-37127: (XSCCOMP02) The compressed composite workspace object must be last in the dimension list.
-
Cause: An attempt was made to DEFINE a variable dimensioned by a compressed composite, but a slower varying dimension was specified in the dimension list.
- ORA-37128: (XSCCOMP20) The partition template workspace object has already used the COMPRESSED COMPOSITE workspace object.
-
Cause: The COMPRESSED COMPOSITE specified for either a variable or partition template was already in use in another partition template.
- ORA-37129: (XSCCOMP04) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object. All static MODEL statements must precede all RELATION statements over the bases of the COMPRESSED COMPOSITE.
-
Cause: The AGGMAP was defined with a MODEL statement after a RELATION statement over a base of the COMPRESSED COMPOSITE.
- ORA-37130: (XSCCOMP05) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object because you must specify AGGINDEX OFF when there is a PRECOMPUTE clause on a RELATION over base workspace object.
-
Cause: A PRECOMPUTE clause was specified in the AGGMAP for a RELATION over a base of a COMPRESSED COMPOSITE, but AGGINDEX was ON.
- ORA-37132: (XSCCOMP07) Incremental aggregation over the dense DIMENSION workspace object is not supported when aggregating a VARIABLE dimensioned by a COMPRESSED COMPOSITE.
-
Cause: The status of the specified dimension did not include all detail cells.
- ORA-37133: (XSCCOMP08) cannot write into an aggregated VARIABLE dimensioned by a COMPRESSED COMPOSITE
-
Cause: An attempt was made to store a value into to an aggregated variable dimensioned by a COMPRESSED COMPOSITE. Once the AGGREGATE command is run on a variable dimensioned by a COMPRESSED COMPOSITE, it becomes read-only until the computed values are removed with the CLEAR command.
- ORA-37134: (XSCCOMP09) cannot add new values to workspace object because it includes positions for precomputed aggregate values
-
Cause: An attempt was made to create a new position in a compressed composite, either directly (using MAINTAIN MERGE or MAINTAIN ADD) or by storing a value in the variable dimensioned by the compressed composite. This is not allowed when the variable has been precomputed using the AGGREGATE command. Once the AGGREGATE command is run on a variable dimensioned by a compressed composite, the compressed composite becomes read-only until the computed values are removed with the CLEAR command.
- ORA-37135: (XSCCOMP19) The compressed composite workspace object in the current defined partition template should be unique or global.
-
Cause: The compressed composite was neither unique nor global. Unique subpartitions should have different compressed composites. Global subpartitions should use the same compressed composite if they use any compressed composite at all.
- ORA-37136: (XSCCOMP11) Cannot ROLLUP dimension workspace object which is a base of COMPRESSED COMPOSITE workspace object. Use AGGREGATE instead.
-
Cause: An attempt was made to run ROLLUP on a variable dimensioned by a COMPRESSED COMPOSITE.
- ORA-37137: (XSCCOMP12) cannot CHGDFN workspace object because it is a compressed composite
-
Cause: An attempt was made to process the CHGDFN function on a compressed composite.
- ORA-37138: (XSCCOMP13) You cannot delete values from workspace object because it is an aggregated compressed composite.
-
Cause: The MAINTAIN DELETE statement was specified for an aggregated compressed composite.
- ORA-37139: (XSCCOMP14) Cannot AGGREGATE workspace object using aggmap workspace object because you cannot AGGREGATE a variable dimensioned by a COMPRESSED COMPOSITE using an aggmap with a PROTECT clause.
-
Cause: An attempt was made to AGGREGATE a variable dimensioned by a COMPRESSED COMPOSITE with an aggmap that included a PROTECT clause.
- ORA-37140: (XSCCOMP15) Cannot AGGREGATE partitioned variable workspace object using AGGMAP workspace object because you cannot use the base of a COMPRESSED COMPOSITE as a partition dimension.
-
Cause: The user tried to run aggregate on a partitioned variable with a partition dimension that is a base of a COMPRESSED COMPOSITE.
- ORA-37141: (XSSQLMDQ01) Invalid host variable syntax for MDQUERY procedure.
-
Cause: The schema and analytic workspace name for the MDQUERY cursor declaration were incorrectly specified.
- ORA-37142: (XSSQLMDQ02) Invalid host variable data type for MDQUERY procedure: string expected.
-
Cause: The user specified a host variable that was not of the correct type.
- ORA-37143: (XSSQLMDQ03) string is not a valid analytic workspace name.
-
Cause: The user specified an analytic workspace name not qualified by a schema name, or one or both components of the name exceed the maximum length
- ORA-37144: (MDQUERY01) string is not a valid metadata object type for MDQUERY.
-
Cause: The first argument to MDQUERY was not recognized.
- ORA-37145: (XSTTS_PLAT) cannot transport analytic workspace across platforms
-
Cause: An attempt was made to transport a tablespace containing an analytic workspace from one platform to another.
- ORA-37146: (XSCCOMP18) The variable workspace object is already dimensioned by the compressed composite workspace object.
-
Cause: An attempt was made to define the partition template dimensioned by the compressed composite that had dimensioned the variable.
- ORA-37147: (XSCCOMP21) The variable workspace object must be in the current operation group of the COMPRESSED COMPOSITE workspace object.
-
Cause: The variable dimensioned by the COMPRESSED COMPOSITE was not in the object list of the current operation group. For AGGREGATE, all variables dimensioned by the same COMPRESSED COMPOSITE also must use the same aggmap
- ORA-37149: (XSCCOMP23) Individual partitions of the variable dimensioned by workspace object cannot be aggregated separately.
-
Cause: An attempt was made to aggregate partitions of a variable dimensioned by a global COMPRESSED COMPOSITE partition template.
- ORA-37150: line string, column string, string
-
Cause: A syntax error was found in the expression query string.
- ORA-37151: expression parser initialization error
-
Cause: expression parser initialization failed
- ORA-37152: MDX query error: (string)
-
Cause: An exception occurred while the Multidimensional Expressions (MDX) query was being processed.
- ORA-37154: OLAP API initialization error: (case string)
-
Cause: OLAP API initialization failed.
- ORA-37155: OLAP API bootstrap error: (case string)
-
Cause: OLAP API bootstraping failed.
- ORA-37156: (string)
-
Cause: An unexpected error occurred while the Oracle Online Analytical Processing (Oracle OLAP) Java API (OLAPI) command was being processed.
- ORA-37157: Error text is missing for the expression syntax error.
-
Cause: A syntax error occurred in the expression, but the message file containing the error text could not be found.
- ORA-37158: Bad clob or varray IN-args: (case string)
-
Cause: When in clob or varray mode, the PL/SQL mappings of OLAP API's IDL interface methods were executed blindly with null clob/varray or non-null clob/varray containing garbages.
- ORA-37159: OLAPI operations cannot be performed because OLAPI C++ virtual table addresses have become invalid.
-
Cause: Session migration in shared server mode caused Oracle Online Analytical Processing (Oracle OLAP) Java API (OLAPI) C++ virtual table addresses to become invalid. This was most likely due to the use of Exec Shield.
- ORA-37161: invalid privilege specified for OLAP object
-
Cause: An attempt was made to grant or revoke an invalid privilege on an OLAP object.
- ORA-37162: OLAP error
-
Cause: An exception was raised by OLAP code.
- ORA-37163: An analytic workspace with dependent CUBES or CUBE DIMENSIONS cannot be deleted or truncated.
-
Cause: An attempt was made to delete or truncate an analytic workspace that currently had a CUBE or CUBE DIMENSION defined over it.
- ORA-37164: The current SQL statement does not support this OLAP object
-
Cause: The OLAP object is not supported in the current SQL statement.
- ORA-37166: (XSOQ_BAD_OBJ) OLAP object "string.string" does not exist
-
Cause: A nonexistent OLAP object was specified.
- ORA-37167: (XSOQ_BAD_SUBOBJ) OLAP object "string.string.string" does not exist
-
Cause: A nonexistent OLAP object was specified.
- ORA-37168: (XSOBJORG_UNSUPP_OBJ) unsupported OLAP object "string.string" for OBJORG function
-
Cause: The specified OLAP object was a type that is not supported by the OBJORG function.
- ORA-37169: (XSOBJORG_UNSUPP_SUBOBJ) unsupported OLAP object "string.string.string" for OBJORG function
-
Cause: The specified OLAP object was of a type not supported by the OBJORG function.
- ORA-37170: (XSOBJORG_NA) The top-level object name argument to the OBJORG function cannot be NA.
-
Cause: An attempt was made to pass NA as the second argument to the OBJORG function.
- ORA-37171: dimension sources not specified
-
Cause: The user passed an empty or null collection to DBMS_AW.ADVISE_SPARSITY
- ORA-37172: invalid dimension type
-
Cause: An invalid number was specified for the DIMTYPE field in the dimension sources argument.
- ORA-37173: null dimension source data
-
Cause: The user specified NULL for one of the members of the dimension sources argument
- ORA-37174: source SQL must be a SELECT statement
-
Cause: The user specified an INSERT, UPDATE, DELETE or other type of SQL statement
- ORA-37175: column string is not a column of source data
-
Cause: A dimension column was specified which did not exist in the input data
- ORA-37176: argument string is not valid for the sparsity advisor
-
Cause: An invalid argument was passed to the advisor
- ORA-37177: column string does not have any leaf values
-
Cause: The specified dimension column or fact table did not contain any leaf values
- ORA-37178: column string has no values
-
Cause: The specified dimension column did not contain any values
- ORA-37179: expected at least one column for dimension string, got string
-
Cause: Not enough columns were specified for the dimension
- ORA-37180: expected exactly one column for dimension string, got string
-
Cause: Expected a single source column for the dimension. Either none or more than one was specified.
- ORA-37181: expected exactly string columns for dimension string, got string
-
Cause: Expected a certain number of source columns for the dimension. Either none or the wrong number of columns was specified.
- ORA-37182: you may only specify one dimension to partition
-
Cause: The user passed a DIMENSION_SOURCE_T to ADVISE_SPARSITY which specified partitioning on more than one dimension
- ORA-37183: invalid value string for PARTBY
-
Cause: A value other than PARTBY_DEFAULT, PARTBY_NONE or PARTBY_FORCE was passed to the DBMS_AW.ADVISE_SPARSITY PL/SQL package.
- ORA-37184: invalid value string for ADVMODE
-
Cause: A value other than ADVICE_DEFAULT, ADVICE_FAST or ADVICE_FULL was passed to the DBMS_AW.ADVISE_SPARSITY PL/SQL package.
- ORA-37185: length of string (string) exceeds maximum (string)
-
Cause: The specified value exceeded the maximum length allowed.
- ORA-37186: null child value for parent (string) found in parent-child hierarchy
-
Cause: While reading values for a parent-child hierarchy, a NULL child value was found for a non-NULL parent
- ORA-37187: null parent and child pair found in parent-child hierarchy
-
Cause: While reading values for a parent-child hierarchy, a row was retrieved which had both null child and parent values.
- ORA-37188: unexpected null result while querying string
-
Cause: While querying the input fact table, the sparsity advisor unexpectedly got no results, possibly due to changes being made during operation.
- ORA-37400: analytic workspace does not exist
-
Cause: The user attempted to create an OLAP MV or Table on an AW that does not exist.
- ORA-37401: you may not perform this operation on a system analytic workspace
-
Cause: The user attempted to create a CUBE MV or Table on a system-created AW.
- ORA-37402: analytic workspace object does not exist
-
Cause: The user attempted to create a CUBE MV or Table mapping to an object that does not exist in the AW.
- ORA-37403: invalid analytic workspace object type
-
Cause: The user attempted to create a CUBE MV or Table mapping to an object that is not the correct type.
- ORA-37404: Create table as select disallowed for CUBE ORGANIZED tables
-
Cause: User attempted to create a CUBE ORGANIZED table by doing a create table as select.
- ORA-37405: unknown ORGANIZATION CUBE keyword
-
Cause: An unknown keyword was encountered while parsing the ORGANIZATION CUBE clause
- ORA-37406: invalid option for a CUBE ORGANIZED table
-
Cause: An attempt to specify one or more options for a CUBE ORGANIZED table such as: [NO]CACHE, NO LOGGING, CLUSTER, (NO)COMPRESS
- ORA-37407: invalid column type for a CUBE ORGANIZED table
-
Cause: A illegal column type is specified in a CUBE ORGANIZED table.
- ORA-37409: Cannot delete or truncate analytic workspace used by CUBE ORGANIZED table.
-
Cause: User attempted to delete or truncate an analytic workspace (AW) which had a CUBE ORGANIZED table or materialized view defined over it.
- ORA-37410: cannot delete or modify AW object referenced by CUBE ORGANIZED table
-
Cause: User attempted to delete, chgdfn, or otherwise modify an object referenced by a CUBE ORGANIZED table or MV
- ORA-37411: invalid object type
-
Cause: User referenced an invalid object type
- ORA-37412: column not mapped by ORGANIZATION CUBE clause
-
Cause: Not all columns in the table or MV definition were mapped in the ORGANIZATION CUBE clause
- ORA-37413: column referenced multiple times in ORGANIZATION CUBE clause
-
Cause: The same column name was referenced multiple times inside of the ORGANIZATION CUBE clause
- ORA-37414: dimension without mapping or hierarchy in ORGANIZATION CUBE clause
-
Cause: A dimension was listed in the ORGANIZATION CUBE clause but no mapping information was supplied
- ORA-37415: AW schema must match TABLE or MATERIALIZED VIEW schema
-
Cause: An ORGANIZATION CUBE table or MV on top of an existing AW must be created in the same schema as the AW
- ORA-37416: multiple GROUPING IDs found for ORGANIZATION CUBE
-
Cause: Multiple GROUPING IDs for the ORGANIZATION CUBE TABLE or MATERIALIZED VIEW
- ORA-37417: variable does not have an AGGCOUNT
-
Cause: A COUNT clause was specified in the ORGANIZATION CUBE description for a variable that does not have an AGGCOUNT
- ORA-37418: detail query cannot be derived
-
Cause: If an ORANIZATION CUBE MV is to automatically derive its loading clause, then its definition query cannot contain set operators (eg UNION ALL), a HAVING clause, START WITH or a SQL MODEL clause. The definition query contains these or other unsupported syntax.
- ORA-37419: ORGANIZATION CUBE clause not allowed in explain mview
-
Cause: User tries to explain mview on a CREATE MATERIALIZED VIEW statement that contains a ORGANIZATION CUBE clause.
- ORA-37420: unsupported feature with CUBE ORGANIZED materialized view
-
Cause: User attempts operations such as creating a mv log on an CUBE ORGANIZED MATERIALIZED VIEW.
- ORA-37421: specified pseudocolumn is not supported by CUBE ORGANIZED tables
-
Cause: An unsupported pseudocolumn was referenced with a CUBE ORGANIZED table.
- ORA-37422: illegal attempt to write to a calculated column
-
Cause: An attempt was made to write to a calculated column which could not be written to.
- ORA-37423: operation not supported on CUBE ORGANIZED tables
-
Cause: The attempted operation was not supported with CUBE ORGANIZED tables.
- ORA-37424: alter materialized view (MV) on a primary cube organized MV failed to find secondary cube MV table
-
Cause: The operation failed due to the missing secondary cube materialized view (MV) table in alter MV.
- ORA-37521: (HASHSCAN00) Dimension string contains duplicate values. Please contact Oracle OLAP Technical Support.
-
Cause: The named dimension contains duplicate values.
- ORA-37522: (HASHSCAN01) You must specify the name of an existing TEXT or NTEXT dimension.
-
Cause: the _HASHSCAN program was invoked with an invalid argument
- ORA-37527: (XSCHGDFN01) SESSION values of dimension string are being automatically deleted.
-
Cause: When using CHGDFN to rebuild the hash index of a TEXT or NTEXT dimension, SESSION values were encountered.
- ORA-37528: (XSOBJORG_BAD_HIER) invalid property "string" specified for hierarchy "string.string.string"
-
Cause: Either the specified hierarchy did not have an analytic workspace organization, or the specified property did not apply to hierarchies.
- ORA-37530: (XSCCLOAD01) When aggregating between compressed partitions the base dimensions of workspace object did not match the base dimensions of workspace object.
-
Cause: When aggregating a partitioned variable the dimensionality of any compressed partitions should be identical.
- ORA-37531: (XSCCLOAD02) When aggregating between compressed partitions the source partitions were aggregated with a different AGGMAP, or the RELATIONS have changed since the source partitions were aggregated.
-
Cause: When aggregation crosses partition boundaries within a compressed variable the individual partitions must all be aggregated using a similar aggmap over the same unaltered relations.
- ORA-37541: Hierarchy element DIMENSION_MEMBER can aggregate into element MEMBER_ANCESTOR through multiple paths.
-
Cause: When a low level hierarchy element can reach an aggregate element by more than one path through the hierarchy, it is said to have multiple paths. The danger is that the value of the low level hierarchy element will have its value counted multiple times (once per path) in the total of the aggregate element.
- ORA-37542: DIMENSION_MEMBER makes hierarchy HIERARCHY1 unbalanced.
-
Cause: A hierarchy is balanced if: 1) All members of a level are at the same depth from the root of the hierarchy and 2) All the members in different levels are at different depths from the root of the hierarchy.
- ORA-37543: Hierarchy member DIMENSION_MEMBER is inconsistent across HIERARCHY1 and HIERARCHY2.
-
Cause: Two hierarchies are inconsistent when members that appear in both hierarchies have different ultimate leaves.
- ORA-37544: Dimension members DIMENSION_MEMBER and MEMBER_ANCESTOR make this dimension star inconsistent.
-
Cause: A dimension is "star consistent" when it can be represented in a star schema table. This requires that a hierarchy level map to a single underlying column. If a level is shared across one or more hierarchies, it must have the same set of members in each hierarchy (to share a column).
- ORA-37545: DIMENSION_MEMBER is part of a hierarchy loop.
-
Cause: A hierarchy has loops when the ancestor of a dimension member uses that member as its parent. Note that some loops are created across hierarchies. For example, in hierarchy 1, dimension member A is the parent of B, B is the parent of C and in hierarchy 2, C is that parent of A forms a hierarchy loop.
- ORA-37546: (XSHIERSP00) Levelorder valueset is empty.
-
Cause: An empty levelorder valueset was specified for the HIERSHAPE function.
- ORA-37547: (XSHIERSP01) DIMENSION_MEMBER has no level associated with it.
-
Cause: DIMENSION_MEMBER did not have an associated level. Level based hierarchies must have a level for every dimension member.
- ORA-37548: (XSHIERSP02) DIMENSION_MEMBER is not specified as a member of HIERARCHY1.
-
Cause: When a dimension member is part of a hierarchy, it appears in the INHIER valueset associated with the hierarchy. This dimension member is missing from this value set and thus should not be part of this hierarchy.
- ORA-37549: (XSHIERSP03) The level of DIMENSION_MEMBER is not lower than the level of MEMBER_ANCESTOR.
-
Cause: A dimension member has a parent that is lower or on the same level as this member according to the levelorder valueset.
- ORA-37550: (XSHIERSP04) The level of MEMBER_ANCESTOR is not one level above DIMENSION_MEMBER.
-
Cause: A dimension member had a parent that was not one level above the level of this member according to the LEVELORDER valueset.
- ORA-37551: (XSHIERSP05) Leaf value DIMENSION_MEMBER is not on the same level as the rest of leaf dimension values.
-
Cause: The detail or leaf values of this hierarchy must all have the same level. This member is on a different level than most of the leaf values.
- ORA-37552: (XSHIERSP06) DIMENSION_MEMBER is associated with a level not found in the levelorder valueset.
-
Cause: DIMENSION_MEMBER must have an associated level that is found in the levelorder valueset so that we can figure out DIMENSION_MEMBER's level depth.
- ORA-37553: A cycle between number and number has been detected in relation workspace object over workspace object.
-
Cause: A relation was used that had loops in it.
- ORA-37554: A cycle between number and number has been detected in relation workspace object.
-
Cause: A relation was used that contained loops.
- ORA-37560: lob locator invalid for specified log target
-
Cause: A lob locator was passed as a target to DBMS_CUBE_LOG.ENABLE, but the log_target was not DBMS_CUBE_LOG.TARGET_LOB
- ORA-37561: unknown logging type
-
Cause: An invalid log_type was specified
- ORA-37562: unknown logging target
-
Cause: An invalid log_target was specified
- ORA-37563: invalid log verbosity
-
Cause: An invalid log_verbosity was specified
- ORA-37564: unknown log table version
-
Cause: Could not determine the version of the specified logging table
- ORA-37565: invalid parameter for specified log type
-
Cause: The log_type specified does not support the specified parameter, for instance, DBMS_CUBE_LOG.MAX_ERRORS is not valid for
- ORA-37566: invalid log location
-
Cause: The specified log location is in an invalid format. For file targets it must be of the form 'directory_alias/filename'
- ORA-37567: log location not specified
-
Cause: The log location was not specified for a log target which requires one
- ORA-37568: invalid log parameter
-
Cause: An invalid log_param was passed to dbms_cube_log.set_parameter or get_parameter
- ORA-37569: invalid log parameter value
-
Cause: An invalid value was passed to dbms_cube_log.set_parameter
- ORA-37570: invalid log specification
-
Cause: An invalid logging specification was supplied to DBMS_CUBE_LOG.SET_LOG_SPEC
- ORA-37571: invalid SQL ID
-
Cause: Either the SQL ID supplied was invalid or no associated logging information was captured.
- ORA-37572: invalid ID
-
Cause: An invalid ID was supplied for the given SQL ID.
- ORA-37573: no limits logged
-
Cause: There were no corresponding OLAP filters to the supplied information.
- ORA-37574: error logging to table "string.string"
-
Cause: An error occurerd attempting to write log records to the named table.
- ORA-37575: Invalid cube operations log component, "string".
-
Cause: Invalid cube operations log component value.
- ORA-37576: Invalid cube operations log handle id.
-
Cause: An invalid cube operations log handle id was specified. No oplog handle found for oplogHandleId parameter.
- ORA-37577: Invalid cube operations log message name.
-
Cause: Cube operations log message name value is NULL.
- ORA-37578: Invalid cube operations log operation value.
-
Cause: Cube operation log operations value is NULL.
- ORA-37580: The EXPRESS AW does not exist.
-
Cause: The EXPRESS AW does not exist.
- ORA-37581: The EXPRESS AW has not been properly installed.
-
Cause: The EXPRESS AW has not been properly installed.
- ORA-37582: The EXPRESS AW version string is different than the Oracle version string.
-
Cause: The EXPRESS AW version does not match the current Oracle version.
- ORA-37600: (XSPGERRPERMDETACH) ran out of tablespace storage while updating analytic workspace string
-
Cause: There was not enough space in the large object (LOB) segment to complete the UPDATE operation.
- ORA-37601: (XSPGERRTEMP) Ran out of temporary storage while writing to analytic workspace with ID=number.
-
Cause: Ran out of temporary tablespace storage.
- ORA-37602: (XSPGERRTEMPUSER) Ran out of temporary storage while writing to analytic workspace string. Free some temporary storage by detaching an analytic workspace.
-
Cause: There was insufficient temporary tablespace storage for the analytic workspace.
- ORA-37603: (XSPGERRTEMPSYSTEM) Ran out of temporary storage while writing to a system temporary analytic workspace. Free some temporary storage immediately by DETACHING an analytic workspace.
-
Cause: The amount of temporary tablespace storage was insufficient.
- ORA-37604: (XSPGERRPQUPD) Parallel updating analytic workspace string failed.
-
Cause: An unexpected error occurred to the parallel update servers.
- ORA-37605: error during OLAP AW UPDATE
-
Cause: An error occurred during the OLAP AW UPDATE process.
- ORA-37606: Oracle OLAP failed to initialize at string.
-
Cause: A severe error occurred while initializing Oracle OLAP.
- ORA-37999: Serious Oracle OLAP error: string.
-
Cause: Something unexpected occurred in the Oracle Online Analytical Processing (Oracle OLAP) system.