Answer Posted / guest

Cause: A big endian byte order mark was found at the
beginning of the specified file and either the access
parameters specified the data was in little endian order or
the byte order mark for a previous file was little endian.

Action: The file needs to be loaded separately. If a byte
order was specified in the access parameters, make sure it
is changed to be big endian.

Please add more information about this Error

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

2309

---

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.

2321

---

IMP-00064: Definition of LOB was truncated by export

5878

---

ORA-26028: index string.string initially in unusable state

3395

---

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

1196

---

---

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

1233

---

when i ran any workflow or session, getting below error: seesion task instance[s_xxx]: Execution terminated unexpecterdly

1746

---

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

1514

---

if the lengths of two wires are same and the area of cross sections is 4:7 then what will be the ratio of current passing through these wires

2228

---

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

1368

---

ORA-26094: stream format error: input column overflow

2244

---

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

1283

---

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

8057

---

NZE-28890: Entrust Login Failed

1402

---

ORA-26095: unprocessed stream data exists

2794

---