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-07638: smsget: SGA pad area not large enough for created SGA

1 Answers  

---

PROT-00018: Failed to open file

1 Answers  

---

ORA-34897: (PPMONTHS01) Blank lines are not allowed in the MONTHNAMES option.

1 Answers  

---

QSM-02050: subquery using the ALL clause in mv

1 Answers  

---

ORA-27159: failure setting process scheduling priority

1 Answers  

---

ORA-02063: preceding stringstring from stringstring

1 Answers  

---

DRG-11858: Gopher Server Replies

1 Answers  

---

ORA-01909: REUSE keyword expected

1 Answers  

---

ORA-12983: cannot drop all columns in a table

1 Answers  

---

NNO-00317: statistic counter reset interval changed to number seconds

1 Answers  

---

ORA-36976: (XSRELGID00) The format of the GROUPINGID command is: GROUPINGID [relation1] INTO {variable | relation2 | surrogate} [USING levelrelation] [INHIERARCHY {inhvariable | valueset}] [LEVELORDER levelordervs] The source relation can be omitted only when using both surrogate gid and level order valueset.

1 Answers  

---

SQL*Loader-00421: error converting data

1 Answers  

---