Answer Posted / guest

Cause: A detail table has been truncated and no materialized
view supports fast refersh after a detail table has been
truncated

Action: Use REFRESH COMPLETE. Note: you can determine why
your materialized view does not support fast refresh after
TRUNCATE using the DBMS_MVIEW.EXPLAIN_MVIEW() API.

Please add more information about this Error

ORA-26079: file "string" is not part of table string.string

1934

---

IMP-00064: Definition of LOB was truncated by export

6396

---

ORA-16627: No standby databases support the overall protection mode.

3963

---

ORA-26032: index string.string loading aborted after string keys

2089

---

ORA-26030: index string.string had string partitions made unusable due to:

1926

---

ORA-07497: sdpri: cannot create trace file 'string'; errno = string.

2778

---

ORA-26029: index string.string partition string initially in unusable state

2140

---

NZE-28868: Peer certificate chain check failed.

2787

---

ORA-26028: index string.string initially in unusable state

3848

---

ORA-26076: cannot set or reset value after direct path structure is allocated

1951

---

ORA-26082: load of overlapping segments on table string.string is not allowed

1755

---

NZE-28890: Entrust Login Failed

1863

---

How to resolve QSM-01108 error. I have no OR conditions in my query, but do have 9 IN conditions. The error says the max limit is 2 while I have 257 number of disjuncts. However, if I remove even a single IN condition, the query is rewritten. I cannot change my query. How can I resolve this issue?

2705

---

In my project I am using star schema and only diimension tables are loaded and not fact tables any one can help me why it is happening? Plase guide me.

2862

---

IMP-00070: Lob definitions in dump file are inconsistent with database.

1732

---