ORA-34286: (MXDCL53) workspace object cannot be used in this
context because it is a string.
Answer Posted / guest
Cause: User specified a dimension composite, conjoint, or
partition template in a place where that kind of dimension
is not allowed. For instance, a relation cannot be
dimensioned by a composite, and only a variable can
dimensioned by a partition template.
Action: Usually, the offending dimension can be replaced
with its bases. For instance, a relation cannot be
dimensioned by a a composite of PRODUCT and GEOG, but it can
be dimensioned by both PRODUCT and GEOG instead.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
ORA-26095: unprocessed stream data exists
ORA-16626: failed to enable specified object
[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-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier
ORA-26030: index string.string had string partitions made unusable due to:
ORA-26094: stream format error: input column overflow
ORA-26082: load of overlapping segments on table string.string is not allowed
IMP-00064: Definition of LOB was truncated by export
ORA-16627: No standby databases support the overall protection mode.
NZE-28868: Peer certificate chain check failed.
IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
ORA-26076: cannot set or reset value after direct path structure is allocated
ORA-26028: index string.string initially in unusable state
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.
IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier