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

ORA-00064: object is too large to allocate on this O/S (string,string)

1 Answers  

---

ORA-03123: operation would block

1 Answers  

---

ORA-25126: Invalid name specified for BUFFER_POOL

1 Answers  

---

TNS-12583: TNS:no reader

1 Answers  

---

NNL-01063: Statistic counters next reset in: string

1 Answers  

---

PLS-00361: IN cursor 'string' cannot be OPEN'ed

1 Answers  

---

ORA-33000: (AGOPEN00) AGGMAP workspace object cannot be accessed because it was compiled by a more recent version of string.

1 Answers  

---

ORA-12821: invalid value for INSTANCES

1 Answers  

---

TNS-12235: TNS:Failure to redirect to destination

1 Answers  

---

PLS-00418: array bind type must match PL/SQL table row type

1 Answers  

---

ORA-12914: Cannot migrate tablespace to dictionary managed type

2 Answers  

---

ORA-02097: parameter cannot be modified because specified value is invalid

1 Answers  

---