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
- 2886 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-12922: concurrent ALTER DATABASE [NO] FORCE LOGGING command is running
ORA-27193: sbtinfo2 did not return volume label
ORA-14016: underlying table of a LOCAL partitioned index must be partitioned
UDI-00013: internal impdp error.
RMAN-06021: FROM DATAFILECCOPY/BACKUPSET may not be specified with archive logs
ORA-30104: 'string' is not a legal integer for 'string'
TNS-12645: Parameter does not exist.
ORA-02447: cannot defer a constraint that is not deferrable
RMAN-06484: changed controlfile copy expired
PCC-00002: Invalid syntax at column number in line number of file string
ORA-32025: %s.string is not a table or view object.
ORA-39005: inconsistent arguments
Oracle Errors 
