Interested to Buy Any Domain ? << Click Here >> for more details...
PLS-00216: NUMBER precision constraint must be in range (1
.. 38)
- 1 Answers
- 6843 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: A NUMBER variable was declared with a precision that
is outside the legal range. Declarations such as N
NUMBER(800) or N NUMBER(123,10) are not supported.
Action: Change the illegal NUMBER precision constraint,
making sure that it lies in the range 1 .. 38.
Please add more information about this Error
| Is This Answer Correct ? | 3 Yes | 3 No |
ORA-36692: (XSRELTBL00) The format of the HIERHEIGHT command is: HIERHEIGHT relation1[(dimension dimvalue, ...)] into relation2 [using relation3 | a | d] [inhierarchy {variable | valueset}].
ORA-24005: must use DBMS_AQADM.DROP_QUEUE_TABLE to drop queue tables
ORA-01577: cannot add log file 'string' - file already part of database
RMAN-04012: auxiliary database Password:
SQL*Loader-00428: count for field string not stored in character or integer field
DRG-12219: section name missing
IMP-00066: Missing NLS_CHARACTERSET in props$
ORA-13833: SQL profile named string doesn't exist
QSM-01021: materialized view, string, not found in the hint list
ORA-06300: IPA: Disconnect failure
KUP-04091: little endian byte order mark found when big endian expected in string
ORA-19017: Attributes can only be simple scalars
Oracle Errors 
