Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-34296: (MXDCL36) A NUMBER dimension must be defined with
a fixed precision and scale, using the form
NUMBER(precision) or NUMBER(precision, scale).
- 1 Answers
- 2995 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: The user attempted to define a NUMBER dimension
without specifying a precision. The proper format for
declaring a number dimension is NUMBER(Precision) or
NUMBER(Precision, Scale). NUMBER with no precision or scale
is not allowed.
Action: Use NUMBER(Precision) or NUMBER(Precision, Scale) to
specify the datatype of a NUMBER dimension.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-30676: socket read or write failed
ORA-00381: cannot use both new and old parameters for buffer cache size specification
ORA-13609: The specified task string must be executing to be cancelled or interrupted.
QSM-02117: missing GROUPING_ID or GROUPING functions on GROUP BY column(s)
ORA-36680: (XSDPART18) workspace object is not a dimension of the PARTITION TEMPLATE.
ORA-01202: wrong incarnation of this file - wrong creation time
ORA-31068: updateXML expected data format [string] instead of [string]
ORA-31410: change set string is not an existing change set
NNL-01067: Trace level: number
NNL-00806: Queries received, type RELATED-INFO: number
AMD-00103: %s "string" does not have a string
ORA-39059: dump file set is incomplete
Oracle Errors 
