QSM-02150: select lists must be identical across the UNION
operator
Answer Posted / guest
Cause: You have specified a materialized view using the
UNION operator and the respective queries on each side of
the UNION operator do not have the same select list. The
RELATED_NAME column shows the alias of the first different
select list item. The RELATED_NUM column shows the offset
from the SELECT keyword to the start of this select list item.
Action: Restructure the materialized view query such that
the respective sides of the UNION operator have identical
select lists.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
ORA-16626: failed to enable specified object
ORA-26084: direct path context already finished
IMP-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier
[ERROR] [main 11:01:20] (JCLLoggerAdapter.java:error:454) Unsuccessful: alter table user.CEN_USER_MASTER add constraint FKF4EDEDC3D0BAAE75 foreign key (ROLE_ID) references user.CEN_ROLE_MASTER [ERROR] [main 11:01:20] (JCLLoggerAdapter.java:error:454) ORA-02275: such a referential constraint already exists in the table
ORA-26029: index string.string partition string initially in unusable state
ORA-26079: file "string" is not part of table string.string
When i am connect database through toad,one error occured. ORA-12514: TNS:listener does not currently know of service requested in connect descriptor. plz help me thanks advance.............
NZE-28868: Peer certificate chain check failed.
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity
ORA-26095: unprocessed stream data exists
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
ORA-26032: index string.string loading aborted after string keys
IMP-00070: Lob definitions in dump file are inconsistent with database.
ORA-26030: index string.string had string partitions made unusable due to:
ORA-16627: No standby databases support the overall protection mode.