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

ORA-24056: internal inconsistency for QUEUE string and destination string

1 Answers  

---

ORA-00324: log file 'string' translated name 'string' too long, string characters exceeds string limit

1 Answers  

---

ORA-02052: remote transaction failure at string

1 Answers  

---

ORA-14275: cannot reuse lower-bound partition as resulting partition

1 Answers  

---

ORA-27036: translation error, unable to expand file name

1 Answers  

---

ORA-00335: online log string: No log with this number, log does not exist

1 Answers  

---

PLS-00960: RPCs cannot use variables with schema level user-defined types in this release

1 Answers  

---

ORA-14054: invalid ALTER TABLE TRUNCATE PARTITION option

1 Answers  

---

ORA-09753: spwat: invalid process number.

1 Answers  

---

ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

1 Answers  

---

SQL*Loader-00282: Unable to locate character set handle for character set ID (number).

2 Answers  

---

IMP-00054: must be connected 'AS SYSDBA' to do Point-in-time Recovery or Transportable Tablespace import

1 Answers  

---