Interested to Buy Any Domain ? << Click Here >> for more details...
SQL*Loader-03121: Maximum record length of [number] exceeded
for bad or discard file
- 1 Answers
- 3900 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: There is a limit on the maximum size of the record
which can be written to the bad or discard file. SQL*Loader
encountered a record that exceeded this limit.
Action: See the next message which follows this message to
know which record exceeded the limit. Modify that record, if
necessary, and try to load again.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-30118: syntax error at 'string' at the end of input
ORA-10922: Temporary tablespace group is empty
ORA-13019: coordinates out of bounds
ORA-14276: EXCHANGE SUBPARTITION requires a non-partitioned, non-clustered table
ORA-36904: (XSAGDNGL44) In AGGMAP workspace object, RELATION workspace object occurs after a dynamic model. The dynamic model must be the last calculation within the AGGMAP.
ORA-02492: missing required file block increment size in NEXT clause
DRG-12422: write to client failed
SQL*Loader-00264: File mode token string parsed but ignored
IMP-00040: FILESIZE does not match the value used for export: string
RMAN-06028: duplicate operand specified in restore specification: string
ORA-08452: specification of E in picture mask is unsupported
ORA-07846: sllfop: string byte record too big for string byte user buffer
Oracle Errors 
