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-13861: Statistics aggregation for client identifier string is already enabled

1 Answers  

---

ORA-28154: Proxy user may not act as client 'string'

1 Answers  

---

ORA-36666: (XSDPART04) workspace object is not a concat dimension.

1 Answers  

---

ORA-09807: Conversion of label from string to binary failed.

1 Answers  

---

ORA-12163: TNS:connect descriptor is too long

1 Answers  

---

ORA-32310: object materialized views must select from an object table

1 Answers  

---

ORA-00109: invalid value for attribute string: string

1 Answers  

---

PLS-00539: subprogram 'string' is declared in an object type body and must be defined in the object type specification

1 Answers  

---

DRG-11729: phrase does not have any narrower terms of this type

1 Answers  

---

ORA-07591: spdde: $GETJPIW failure

1 Answers  

---

NZE-28855: Unsupported SSL operation

1 Answers  

---

SQL*Loader-00411: Only a direct path load may be continued

1 Answers  

---