Answer / guest

Cause: A parenthesized list of values separated by commas
(that is, an aggregate) was used in the wrong context. For
example, the following usage is invalid: WHERE (col1, col2)
> (SELECT col3, col4 FROM my_table ...) However, an equal
sign can take a list of values and a subquery as left- and
right-hand-side arguments, respectively. So, the following
usage is valid: WHERE (col1, col2) = (SELECT col3, col4 FROM
my_table ...)

Action: Rewrite the expression. For example, the clause
WHERE (col1, col2) > (SELECT col3, col4 FROM my_table ...)
can be rewritten as WHERE col1 > (SELECT col3 FROM my_table
...) AND col2 > (SELECT col4 FROM my_table ...)

Please add more information about this Error

RMAN-06709: No scripts in recovery catalog

1 Answers  

---

NNO-00305: trace level changed from number to number

1 Answers  

---

NID-00302: Datafile string - dbid changed

1 Answers  

---

ORA-29807: specified operator does not exist

1 Answers  

---

ORA-30341: dropped level has references

1 Answers  

---

RMAN-08011: including current controlfile in backupset

1 Answers  

---

ORA-14630: subpartition resides in offlined tablespace

1 Answers  

---

ORA-12215: TNS:poorly formed PREFERRED_NAVIGATORS Addresses in TNSNAV.ORA

1 Answers  

---

ORA-06923: CMX: illegal break condition

1 Answers  

---

ORA-12834: Instance group name, 'string', too long, must be less than string characters

1 Answers  

---

ORA-25279: dequeue as select not supported before 8.2

1 Answers  

---

ORA-12681: Login failed: the SecurID card does not have a pincode yet

1 Answers  

---