KUP-04091: little endian byte order mark found when big
endian expected in string
- 1 Answers
- 2418 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: A little endian byte order mark was found at the
beginning of the specified file and either the access
parameters specified the data was in big endian order or the
byte order mark for a previous file was big 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 little endian.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
PCC-02321: only subtraction between two pointers is permitted
ORA-32154: Anydata context not specified
ORA-09291: sksachk: invalid device specified for archive destination
ORA-24281: invalid access past the maximum size of LOB parameter string
PLS-00115: this PRAGMA must follow the declaration of 'string'
ORA-13025: polygon does not close
TNS-12623: TNS:operation is illegal in this state
ORA-21602: operation does not support the specified typecode
ORA-33625: (FRASSIGN02) You cannot use the APPEND keyword with concat dimension workspace object.
ORA-22286: insufficient privileges on file or directory to perform string operation
TNS-00249: Unable to read network configuration data from file string with error: string
ORA-32311: materialized view definition query selects an unsupported user-defined type
Oracle Errors 
