Answer Posted / guest

Cause: An instance in the cluster crashed making instance
recovery necessary.

Action: None. This error should not normally be seen by an
ASM client. ASM will trap this error and retry the operation
after doing instance recovery automatically.

Please add more information about this Error

IMP-00070: Lob definitions in dump file are inconsistent with database.

1743

---

ORA-26094: stream format error: input column overflow

2798

---

ORA-26079: file "string" is not part of table string.string

1958

---

NZE-28890: Entrust Login Failed

1879

---

ORA-26082: load of overlapping segments on table string.string is not allowed

1768

---

ORA-16627: No standby databases support the overall protection mode.

3989

---

ORA-16516: The current state is invalid for the attempted operation.

8818

---

IMP-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier

3155

---

When i am connect database through toad,one error occured. ORA-12514: TNS:listener does not currently know of service requested in connect descriptor. plz help me thanks advance.............

2800

---

when i ran any workflow or session, getting below error: seesion task instance[s_xxx]: Execution terminated unexpecterdly

2230

---

IMP-00064: Definition of LOB was truncated by export

6413

---

ORA-26030: index string.string had string partitions made unusable due to:

1941

---

ORA-26029: index string.string partition string initially in unusable state

2155

---

ORA-26084: direct path context already finished

1949

---

ORA-07497: sdpri: cannot create trace file 'string'; errno = string.

2801

---