Answer / guest

Cause: While advancing a change set, an CDC attempted to
query the LogMiner dictionary system tables to obtain the
columns from the source table. The query returned no rows.
This may be because none of the redo logs contains a
catalog, or it may be an internal error.

Action: First, verify that the source system contains the
source table. execute dbms_logmnr_d.build procedure to
populate the redos log with logminer dictionary information.
If this has been done and the problem persists, then contact
Oracle Corporation

Please add more information about this Error

SQL*Loader-00460: Column (string), form of use (number) does not match char set id of (number)

1 Answers  

---

ORA-04022: nowait requested, but had to wait to lock dictionary object

2 Answers   Oracle,

---

ORA-19013: Cannot create VARRAY columns containing XMLType

1 Answers  

---

ORA-00133: value of string is too long

1 Answers  

---

ORA-36706: (XSRELTBL07) workspace object should be dimensioned by workspace object and one level dimension.

1 Answers  

---

ORA-23435: cannot create an updatable ROWID materialized view with LOB columns

1 Answers  

---

TNS-00083: (USER or ADMIN) in the argument field

1 Answers  

---

ORA-01239: database must be in ARCHIVELOG mode to use external cache

1 Answers  

---

ORA-03236: max # extents (string) reached in index string.string subpartition string

1 Answers  

---

ORA-01154: database busy. Open, close, mount, and dismount not allowed now

1 Answers  

---

ORA-32842: value for property string cannot be altered

1 Answers  

---

TNS-00515: Connect failed because target host or object does not exist

1 Answers  

---