i am facing a problem when i run a shell script to load a table.the error is
Record 1: Rejected - Error on table TRENDS."SHP_CUST_ORD_ITM".
ORA-14400: inserted partition key is beyond highest legal partition key
Record 2: Rejected - Error on table TRENDS."SHP_CUST_ORD_ITM", column PROD_NBR.
ORA-01722: invalid number
MAXIMUM ERROR COUNT EXCEEDED - Above statistics reflect partial run.
Table TRENDS."SHP_CUST_ORD_ITM":
0 Rows successfully loaded.
2 Rows not loaded due to data errors.
0 Rows not loaded because all WHEN clauses were failed.
0 Rows not loaded because all fields were null.
Space allocated for bind array: 51968 bytes(64 rows)
Space allocated for memory besides bind array: 0 bytes
Total logical records skipped: 0
Total logical records read: 6
Total logical records rejected: 2
Total logical records discarded: 0
Run began on Fri Mar 11 03:25:15 2005
Run ended on Fri Mar 11 03:25:18 2005
Elapsed time was: 00:00:02.73
CPU time was: 00:00:00.45
Your shell script is running sqlldr -- which is what wrote the error.... The second record has a data problem, specifically you are inserting non-number data into a number-only field.
for record 1:
you have a partitioned table by date. You are attempting to load a date-value into the table that is higher than your highest dated-partition.
example:
My table partitions highest value is March 12, 2005
If I attempt to enter a date larger than March 11, 2005 I will get this error.
The partition only handles anything LESS than the date specified.
...therefore, have your DBA add a partition that either accomodates the higher range value or a partition speficying MAXVALUE to represent a virtual infinite value.
Since the two errors occurred on the same column, it is likely that the data is wrong and nonsensical with respect to the partition key. In which case, the record rejection is the correct response. These are also the first two records in the table so review the data and the sqlldr control file.