Cause: The dictionary file is produced by a database that is different fro

ORA-01295: DB_ID mismatch between dictionary string and logfiles

Question Posted / guest

1 Answers
7977 Views
I also Faced
E-Mail Answers

Answer Posted / guest

Cause: The dictionary file is produced by a database that is
different from that produced the logfiles.

Action: Specify a compatible dictionary file.

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

IMG-02003: 2FF03 - incorrect color histogram feature specification

1760

ORA-16626: failed to enable specified object

2272

NZE-28890: Entrust Login Failed

1922

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

3912

IMP-00070: Lob definitions in dump file are inconsistent with database.

1796

ORA-26030: index string.string had string partitions made unusable due to:

1986

ORA-26084: direct path context already finished

1995

ORA-16516: The current state is invalid for the attempted operation.

8875

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

4036

ORA-26095: unprocessed stream data exists

3638

[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

2772

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

2032

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.

2945

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

2857

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

2177