Answer Posted / guest

Cause: After a subtype was defined as NOT NULL, it was used
as the base type for another subtype defined as NULL. That
is not allowed. For example, the code might look like
DECLARE SUBTYPE Weekday IS INTEGER NOT NULL; SUBTYPE Weekend
IS Weekday NULL; -- illegal instead of DECLARE SUBTYPE
Weekday IS INTEGER NOT NULL; SUBTYPE Weekend IS Weekday;

Action: Revise the subtype definitions to eliminate the
conflict.

Please add more information about this Error

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

1900

---

IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created

1562

---

ORA-26079: file "string" is not part of table string.string

1895

---

ORA-26095: unprocessed stream data exists

3512

---

RMAN-05017: no copy of datafile number found to recover

2346

---

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

1652

---

ORA-26082: load of overlapping segments on table string.string is not allowed

1716

---

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

8758

---

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

1698

---

ORA-26094: stream format error: input column overflow

2738

---

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

2056

---

IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier

2686

---

IMP-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier

3103

---

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.

2800

---

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

2742

---