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

PCC-02045: CMD-LINE: Option is not unique:

1 Answers  

---

ORA-12001: cannot create log: table 'string' already has a trigger

1 Answers  

---

ORA-12524: TNS:listener could not resolve HANDLER_NAME given in connect descriptor

1 Answers  

---

ORA-32147: Environment not specified

1 Answers  

---

ORA-00129: listener address validation failed 'string'

1 Answers  

---

PLS-00380: functions and procedures are not included in this release of PL/SQL

1 Answers  

---

PCB-00575: PLS-number: string

1 Answers  

---

ORA-28670: mapping table cannot be dropped due to an existing bitmap index

1 Answers  

---

ORA-01292: no log file has been specified for the current LogMiner session

2 Answers  

---

ORA-30183: invalid field width specifier

1 Answers  

---

TNS-00114: Internal error- Allocation of addresses not performed

1 Answers  

---

ORA-01721: USERENV(COMMITSCN) invoked more than once in a transaction

1 Answers   ABC,

---