Answer / guest

Cause: The maximum number of concurrent persistent LogMiner
sessions allowed is limited by
LOGMNR_MAX_PERSISTENT_SESSIONS parameter. Not enough memory
has been set aside at instance startup to allocate the new
LogMiner session.

Action: Increase LOGMNR_MAX_PERSISTENT_SESSIONS and restart
instance.

Please add more information about this Error

QSM-01041: materialized view, string, does not match with a measure in the query

1 Answers  

---

ORA-22973: size of object identifier exceeds maximum size allowed

1 Answers  

---

ORA-12923: tablespace string is in force logging mode

1 Answers  

---

IMP-00066: Missing NLS_CHARACTERSET in props$

1 Answers  

---

ORA-23312: not the masterdef according to string

1 Answers  

---

---

ORA-30991: cannot use DOM to add special attribute to schema-based parent

1 Answers  

---

ORA-25408: can not safely replay call

2 Answers  

---

ORA-12152: TNS:unable to send break message

1 Answers  

---

PLS-01419: Subquery must have either '*' or exactly one column in its select list

1 Answers  

---

ORA-33302: (DBVALID01) SEVERE ERROR: Record number multiply used.

1 Answers  

---

RMAN-06502: skipping archive log file string; already backed on string

1 Answers  

---

ORA-06770: TLI Driver: error sending version

1 Answers  

---