Answer / guest

Cause: There was an error originating from this materialized
view log. One possible cause is that schema redefinition has
occurred on the master table and one or more columns in the
log is now a different type than corresponding master
column(s). Another possible cause is that there is a problem
accessing the underlying materialized view log table.

Action: Check further error messages in stack for more
detail about the cause. If there has been schema
redefinition, drop the materialized view log and recreate it.

Please add more information about this Error

ORA-14019: partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE

1 Answers  

---

LPX-00215: processing instruction did not end in "?>"

1 Answers  

---

PCC-00020: Unable to obtain define variables at line number in file string

1 Answers  

---

ORA-16622: Two or more broker database objects resolve to one physical database.

1 Answers  

---

ORA-08265: create_ora_addr: cannot open nameserver

1 Answers  

---

ORA-36270: (XSCGMDLAGG03) The right-hand side of the AGGREGATION function includes duplicate values.

1 Answers  

---

ORA-12595: TNS:no confirmation

1 Answers  

---

ORA-00234: error in identifying or opening snapshot or copy controlfile

1 Answers  

---

ORA-23417: unknown materialized view type: string

1 Answers  

---

TNS-00138: Failed to find ORACLE executable directory

1 Answers  

---

ORA-14070: option may be specified only for partitioned indices or with REBUILD

1 Answers  

---

QSM-02170: tables must be identical across the UNION operator

1 Answers  

---