Answer / guest

Cause: There was a failure to communicate with the ASM
instance, most likely because the connection went down.

Action: Check the accompanying error messages for more
information on the reason for the failure. Note that
database instances will always return this error when the
ASM instance is terminated abnormally.

Please add more information about this Error

NNL-01005: UNKNOWN TYPE responses received: number

1 Answers  

---

ORA-16614: object has an ancestor that is disabled

1 Answers  

---

ORA-13787: missing SQL profile for statement object "string" for tuning task "string"

1 Answers  

---

LSX-00148: annotation must come first in "~S"

1 Answers  

---

PCC-02385: CHAR_MAP disallowed when using NLS_CHAR and NLS_LOCAL=TRUE

1 Answers  

---

ORA-22306: type "string"."string" already exists

1 Answers  

---

RMAN-08511: piece handle=string tag=string

1 Answers  

---

ORA-29894: base or varray datatype does not exist

1 Answers  

---

ORA-29271: not connected

1 Answers  

---

ORA-12921: database is not in force logging mode

1 Answers  

---

ORA-08101: index key does not exist file string: (root string, node string) blocks (string)

1 Answers  

---

DRG-50864: number assignment failed

1 Answers  

---