KUP-04090: big endian byte order mark found when little
endian expected in string
- 1 Answers
- 2107 Views
- I also Faced
- E-Mail Answers
Answer / 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
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-27477: "string.string" already exists
ORA-09322: slpdtb: unable to convert packed decimal to binary
ORA-31055: A null XMLType element cannot be inserted into RESOURCE_VIEW
ORA-02362: error closing file: string
QSM-01065: materialized view, string, cannot compute measure, string, in the query
ORA-12843: pdml lock not held properly on the table
NNL-00001: request argument "string" is invalid
ORA-37011: (XSACQUIRE_LOCKED) Object workspace object is locked by another user.
EXP-00090: cannot pin type "string"."string"
ORA-16130: supplemental log information is missing from log stream
ORA-06610: LU6.2 Driver: Failed during deallocation
PLS-00606: cursor subquery is not supported on client side in this release
Oracle Errors 
