Answer / guest

Cause: One or both of the workload tables are missing. The
two workload tables which should be present in the user's
schema are V_192216243_F_5_E_14_8_1 and
V_192216243_F_5_E_15_8_1; the former is mapped to
WORK$_IDEAL_MVIEW and the latter to WORK$_MVIEW_USAGE. The
workload tables are created by the Oracle Trace Formatter
when the data-collection-file (oraclesm.dat) is formatted by
the user.

Action: Check whether the Formatter succeeded in formatting
the data collection. Sometimes the V_192216243_F_5_E_14_8_1
(i.e WORK$_IDEAL_MVIEW) may not be created whereas the other
table is created. The most likely cause of this is the
init.ora parameters needed to invoke mview-rewrite are not
enabled. Check your

Please add more information about this Error

ORA-19755: could not open change tracking file

1 Answers  

---

EXP-00007: dictionary shows no columns for string.string

1 Answers  

---

ORA-19853: error preparing auxiliary instance string (error string)

1 Answers  

---

ORA-12211: TNS:needs PREFERRED_CMANAGERS entry in TNSNAV.ORA

1 Answers  

---

ORA-27366: job "string.string" is not running

1 Answers  

---

ORA-27365: job has been notified to stop, but failed to do so immediately

1 Answers  

---

ORA-00360: not a logfile member: string

1 Answers  

---

ORA-31059: Cannot insert root XML document node if it already exists

1 Answers  

---

ORA-27367: program "string.string" associated with this job is disabled

1 Answers  

---

ORA-09743: smscre: could not attach shared memory.

1 Answers  

---

ORA-27011: skgfrd: cannot read from file opened for write

1 Answers  

---

ORA-12058: materialized view cannot use prebuilt table

1 Answers  

---