ORA-31469: cannot enable Change Data Capture for change set
string
Answer Posted / guest
Cause: The change set has reached the specified limit that
was set up by the CREATE_CHANGE_SET command.
Action: Check the alert log to find out whether capture,
apply or both reached the limit. Once apply reaches its
limit, the change set is permanently disabled. Create a new
change set with new limits to continue capturing data.
Please add more information about this Error
Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
ORA-26084: direct path context already finished
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-16516: The current state is invalid for the attempted operation.
ORA-26095: unprocessed stream data exists
IMP-00064: Definition of LOB was truncated by export
ORA-26082: load of overlapping segments on table string.string is not allowed
ORA-26030: index string.string had string partitions made unusable due to:
IMG-02003: 2FF03 - incorrect color histogram feature specification
ORA-16626: failed to enable specified object
IMP-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier
NZE-28868: Peer certificate chain check failed.
[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
IMP-00070: Lob definitions in dump file are inconsistent with database.
ORA-26027: unique index string.string partition string initially in unusable state