Answer Posted / guest
Cause: Logical Standby does not support this type of DDL in
this version, so the DDL is skipped.
Action: The DBA may apply the DDL explicitly at a later time
or a procedure to handle this type of DDL can be created.
see DBMS_LOGSTDBY.SKIP procedure for details.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
IMP-00064: Definition of LOB was truncated by export
ORA-26029: index string.string partition string initially in unusable state
ORA-26076: cannot set or reset value after direct path structure is allocated
RMAN-05017: no copy of datafile number found to recover
ORA-26079: file "string" is not part of table string.string
[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-26094: stream format error: input column overflow
IMG-02003: 2FF03 - incorrect color histogram feature specification
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity
ORA-26084: direct path context already finished
ORA-16626: failed to enable specified object
ORA-26032: index string.string loading aborted after string keys
IMP-00070: Lob definitions in dump file are inconsistent with database.
when i ran any workflow or session, getting below error: seesion task instance[s_xxx]: Execution terminated unexpecterdly
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.