Answer Posted / guest
Cause: The CHANGE ARCHIVED LOG VALIDATE command found that
the archived log still matches its data in the recovery catalog.
Action: None - this is an informational message.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
ORA-26032: index string.string loading aborted after string keys
ORA-26095: unprocessed stream data exists
IMP-00070: Lob definitions in dump file are inconsistent with database.
ORA-26029: index string.string partition string initially in unusable state
ORA-16627: No standby databases support the overall protection mode.
RMAN-05017: no copy of datafile number found to recover
ORA-26084: direct path context already finished
[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-26082: load of overlapping segments on table string.string is not allowed
ORA-26076: cannot set or reset value after direct path structure is allocated
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
ORA-26094: stream format error: input column overflow
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.
ORA-26027: unique index string.string partition string initially in unusable state
