We help IT Professionals succeed at work.

ORA-14400: Inserted partition key does not map to any partition

Nakuru1234
Nakuru1234 asked
on
Hi,

What advice can you give me about this error message?: "ORA-14400: Inserted partition key does not map to any partition."

TIA,
N.
Comment
Watch Question

Senior Software Engineer
CERTIFIED EXPERT
Commented:
According to this URL: http://ora-14400.ora-code.com/ ,
seems that you have a partitioned table, were you have possibly defined certain values for the partition key, but when inserting the data, you are not respecting this set of values.
The solution should be use the appropriated values.
There are other interpretations that could fit in your case as well.
Walter RitzelSenior Software Engineer
CERTIFIED EXPERT
Commented:

Author

Commented:
Hi,

Your answer is straight from the internet website...

TIA,
N.
Walter RitzelSenior Software Engineer
CERTIFIED EXPERT

Commented:
Yes, it is because your problem is a documented one. Did you check to see if this solves your issue?
awking00Information Technology Specialist
CERTIFIED EXPERT

Commented:
Is this occurring doing an insert from another table or from running sqlloader or some other instance? What is the code you're using that generated this error?

Author

Commented:
It is occuring when doing an insert from another table. I was using a select statement.

TIA,
N.
awking00Information Technology Specialist
CERTIFIED EXPERT
Commented:
You can compare the max(high_value) from user_tab_partitions where table_name = 'YOURTARGETTABLE' to the max(column_value) from your source table where the column_value represents the value going into your partition key. If the column_value is greater, then you need to add a new partition to your target table. Can you post the relevant two table structures to include the partition key fields in both?
Walter RitzelSenior Software Engineer
CERTIFIED EXPERT
Commented:
Nakuru1234,
please do as requested by Awking00. His point is exactly same as mine. If you look into the last link I've provided, you will have enough explanation to understand your problem.

Also, if the problem is the one reported on that link, your solution would be:
1) change the partition to support more values;
2) restrict the field causing issue to receive only the values allowed (depending on the situation, a simple constraint will help).

Author

Commented:
I used exp / imp to go around the problem and that worked ok. Thank you for your help!

TIA,
N
awking00Information Technology Specialist
CERTIFIED EXPERT

Commented:
That raises a couple of questions. Was your source table partitioned? If not, then your new target table is not. Does it need to be or should be partitioned?

Author

Commented:
Thank you!