Answer / guest

Cause: The number begin copied or assigned had too many
digits to the left of the decimal and did not fit into its
destination. In other words, there is a number precision
mismatch. This error may also occur if, for example, an
attempt is made to assign a character string to a number, as
demonstrated below. a varchar2(4); b number(1,1); a :=
'10.1'; b := a;

Action: First, check explicit number precision value
mismatches. If none are found, then consider implicit
conversions of other types to numbers, including conversions
performed during binds.

Please add more information about this Error

ORA-01109: database not open

1 Answers  

---

ORA-27212: some entrypoints in Media Management Library are missing

1 Answers  

---

ORA-24048: cannot create QUEUE_TABLE, user does not have access to AQ object types

1 Answers  

---

ORA-35276: (SNSYN163) The format of the ALLOCATE command is: ALLOCATE varname [SOURCE svarname] [BASIS bvarname [ACROSS dimname]] [TARGET tvarname [TARGETLOG logvarname]] [ USING aggmap ]

1 Answers  

---

ORA-23497: repgroup name cannot be null

1 Answers  

---

LSX-00103: duplicate group "~S"

1 Answers  

---

NZE-28824: invalid encryption/decryption/signature state passed

1 Answers  

---

ORA-02451: duplicate HASHKEYS specification

1 Answers  

---

DRG-13006: sub lexer for this language is not defined

1 Answers  

---

KUP-03999: error occurred while processing a date format: ORA-number: string

1 Answers  

---

IMP-00077: Could not convert to server national character set's handle

1 Answers  

---

ORA-03241: Invalid unit size

1 Answers  

---