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
- 2917 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-02728: osnfop: access error on oracle executable
ORA-06440: ssaio: the asynchronous read returned incorrect number of bytes
PCB-00003: Value of DBMS option invalid with given value of MODE option
ORA-08237: smsget: SGA region not yet created
DRG-50804: failed to exec cursor
ORA-16642: db_unique_name mismatch
DRG-11845: No Partial Update
PLS-00384: type mismatch found at 'string' in UPDATE's SET clause
ORA-14306: List value 'string' specified twice in partitions 'string', 'string'
DRG-12005: Please give name of file to save in:
ORA-13622: The recommendation annotation string is invalid.
ORA-37116: OLAP API table function error: (string)
Oracle Errors 
