Answer / guest

Cause: A SQL string has been associated with both a column
object and one of its attributes in the control file.
Because the SQL string of the column object will replace the
entire column object in the VALUE clause of the INSERT
statement, the SQL string of the attribute is ignored. This
could cause unexpected or incorrect values to be loaded.

Action: Correct the control file so that only the column
object or its attribute has a SQL string, but not both.

Please add more information about this Error

ORA-16205: DDL skipped due to skip setting

1 Answers  

---

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

1 Answers  

---

ORA-27453: %s is an invalid job or program argument name.

1 Answers  

---

ORA-14112: RECOVERABLE/UNRECOVERABLE may not be specified for a partition or subpartition

1 Answers  

---

ORA-02470: TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression.

1 Answers  

---

ORA-16171: RECOVER...FINISH not allowed due to gap for thr string, seq string-string

1 Answers  

---

RMAN-06725: database not open: sort area size too small

1 Answers  

---

NZE-28781: No data for the access method is specified in the parameter.

1 Answers  

---

RMAN-06161: error when inspecting auxiliary filename: string

1 Answers  

---

RMAN-08100: channel string: starting proxy validation

1 Answers  

---

ORA-36774: (XSPGERRTEMPUSER) Ran out of temporary storage while writing to analytic workspace string. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.

1 Answers  

---

NZE-29155: continuous key pair consistency check self-test failure

1 Answers  

---