Answer / guest

Cause: Not enough servers are running to handle the current
system load, and a large backlog of commands has
accumulated; perhaps no servers are running. This message
could also indicate an internal error where one of the
servers has crashed trying to process a given request

Action: Check that enough servers are running, and that they
are processing commands of the correct type. For instance, a
DDL command might timeout if all the servers are setup to
exclusively process query commands. Also, check the server
log files.

Please add more information about this Error

ORA-12716: Cannot ALTER DATABASE CHARACTER SET when CLOB data exists

1 Answers  

---

ORA-12234: TNS:Redirect to destination

1 Answers  

---

ORA-26040: Data block was loaded using the NOLOGGING option

1 Answers  

---

ORA-15192: invalid ASM disk header [string] [string] [string] [string] [string]

1 Answers  

---

ORA-16212: number processes specified for APPLY is too great

1 Answers  

---

---

ORA-19816: WARNING: Files may exist in string that are not known to database.

1 Answers  

---

RMAN-06065: The backup operand [string] conflicts with another specified operand.

1 Answers  

---

ORA-29365: parameters string and string cannot both be set

1 Answers  

---

if the lengths of two wires are same and the area of cross sections is 4:7 then what will be the ratio of current passing through these wires

0 Answers   Wipro,

---

ORA-01879: the hh25 field must be between 0 and 24

1 Answers  

---

ORA-01978: Missing sequence number

1 Answers  

---

IMG-00832: fail queue is full

1 Answers  

---