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-01757: Must specify an object number

1 Answers  

---

ORA-28272: Domain policy restricts password based GLOBAL user authentication.

1 Answers  

---

PCC-00027: Redeclared SQL Identifier "string" at line number in file string

1 Answers  

---

TNS-00255: Closing down log, stopping Navigator

1 Answers  

---

EXP-00074: rounding VOLSIZE down, new value is string

1 Answers  

---

RMAN-08059: media recovery failed

1 Answers  

---

RMAN-06190: PL/SQL package string.string version string in string database is not current

1 Answers  

---

ORA-01621: cannot rename member of current log if database is open

1 Answers  

---

ORA-24303: call not supported in non-deferred linkage

1 Answers  

---

ORA-23394: duplicate propagator

1 Answers  

---

ORA-27014: skgfqpini: translation error while expanding SS_UDMPDIR

1 Answers  

---

O2U-00203: Type to be declared must be an object type or a named collection type

1 Answers  

---