Answer / guest

Cause: A callback from within a user's 3GL routine resulted
in the invocation of another external procedure.

Action: Make sure that the SQL code executed in a callback
does not directly call another external procedure, or
indirectly results in another external procedure, such as
triggers calling external procedures, PL/SQL procedures
calling external procedures, etc.

Please add more information about this Error

ORA-21500: internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]

1 Answers  

---

TNS-00282: Connection Manager: Failed to force log, logging is off

1 Answers  

---

ORA-01538: failed to acquire any rollback segment

1 Answers  

---

ORA-01155: the database is being opened, closed, mounted or dismounted

1 Answers  

---

NNO-00600: warning: forwarder count number exceeds maximum of number, first number will be loaded

1 Answers  

---

RMAN-20000: abnormal termination of job step

1 Answers   Nokia,

---

TNS-00229: Error in call: unable to deliver message :string: string string string

1 Answers  

---

ORA-14025: PARTITION may not be specified for a materialized view or a materialized view log

1 Answers  

---

QSM-02078: mv log must have new values

1 Answers  

---

ORA-32108: max column or parameter size not specified

1 Answers  

---

IMG-00902: VIR signature free failed

1 Answers  

---

ORA-16502: the Data Guard broker operation succeeded with warnings

1 Answers  

---