Answer / guest

Cause: The max_commit_propagation_delay INIT.ORA parameter
is inconsistent with those in other instances.

Action: Make sure all instances have the same
max_commit_propagation_delay.

Please add more information about this Error

ORA-31468: cannot process DDL change record

1 Answers  

---

ORA-34183: (MXCHGDCL22) Partition number already exists.

1 Answers  

---

ORA-19589: %s is not a snapshot or backup controlfile

1 Answers  

---

NNF-01001: ds_initialize: workspace initialization failed

1 Answers  

---

ORA-30071: conversion between datetime/interval and string fail

1 Answers  

---

ORA-02396: exceeded maximum idle time, please connect again

1 Answers  

---

ORA-26017: global indexes not allowed for direct path load of table partition string

1 Answers  

---

ORA-16503: site ID allocation failure

1 Answers  

---

ORA-24032: object string exists, index could not be created for queue table string

1 Answers  

---

ORA-01681: max # extents (string) reached in LOB segment in tablespace string

1 Answers  

---

ORA-13380: network not found

1 Answers  

---

ORA-01512: error renaming log file string - new file string not found

1 Answers  

---