1. Categories >> ERRORS >> Database Errors >> Oracle Errors
  2. Suggest New Category

ORA-29327: unsupported client compatibility mode used when
talking to the server

Question Posted / guest

Answer Posted / guest

Cause: The client compatibility mode is higher than the
version of the server.

Action: Using SET COMPATIBILITY command, specify the same
release number as the server.

Please add more information about this Error

Is This Answer Correct ?    0 Yes 0 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity

2982

ORA-26032: index string.string loading aborted after string keys

1739

ORA-07497: sdpri: cannot create trace file 'string'; errno = string.

2427

How to resolve QSM-01108 error. I have no OR conditions in my query, but do have 9 IN conditions. The error says the max limit is 2 while I have 257 number of disjuncts. However, if I remove even a single IN condition, the query is rewritten. I cannot change my query. How can I resolve this issue?

2401

ORA-26076: cannot set or reset value after direct path structure is allocated

1573




IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier

2400

ORA-26095: unprocessed stream data exists

3051

ORA-26084: direct path context already finished

1589

ORA-26028: index string.string initially in unusable state

3534

ORA-26079: file "string" is not part of table string.string

1604

In my project I am using star schema and only diimension tables are loaded and not fact tables any one can help me why it is happening? Plase guide me.

2438

[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

2407

ORA-16627: No standby databases support the overall protection mode.

3648

ORA-26082: load of overlapping segments on table string.string is not allowed

1447

ORA-26029: index string.string partition string initially in unusable state

1816