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-04086: trigger description too long, move comments into triggering code

1 Answers  

---

PLS-00532: Target of REF must be a complete or incomplete object type.

1 Answers  

---

RMAN-06609: AS COPY can be configured only for disk device

1 Answers  

---

RMAN-08534: channel string: controlfile restore from autobackup complete

1 Answers  

---

ORA-19002: Missing XMLSchema URL

1 Answers  

---

TNS-00252: Unable to handle route request: string

1 Answers  

---

ORA-02242: no options specified for ALTER INDEX

1 Answers  

---

ORA-33278: (DBERR09) Analytic workspace string cannot be attached in RW or EXCLUSIVE mode until the changes made and updated in MULTI mode are committed or rolled back.

1 Answers  

---

DRG-10756: neither text indexing nor theme indexing has been selected

1 Answers  

---

QSM-02073: non-primary key RepAPI mv is not fast refreshable

1 Answers  

---

ORA-09262: spdde: error terminating detached (background) process

1 Answers  

---

PLS-00603: GROUPING function supported only with GROUP BY CUBE or ROLLUP

1 Answers  

---