What you're saying doesn't make sense.
If ID_SUPPR_LICENSE is the primary key and the NEXTVAL of the sequence is returning a value that is larger than any value stored in the table, you would not get a constraint violation error. Either IS_SUPPR_LICENSE is not the primary key or NEXTVAL is not returning the value you say it is or there is actually a duplicate row in the table.
If you are confident that your statements are all accurate, then you've encountered a bug that you need to report to Oracle Support and get a patchset for. Of course, it is wildly more likely that you have made a mistake than that Oracle has introduced a fatal bug in a very basic piece of functionality that was able to go uncaught through all the testing Oracle does and through all the systems that others build
I agree that it does not make sens.
now i now that the problem doesn't come from the sequence. I inserted a random values of 295468256 in the primary key and still have the same error.
Select max(id_suppr_licence) from TheTable five me value of 58015 , the same as an ORDER BY id_suppr_licence DESC.
There are a few possiblle explanations for this.
First of all, please post the DDL for the sequence.
Next, you say: The Value of the NEXTVAL est 59015 at the moment. How do you know that? Are you looking in the data dictionary? Do you understand that sequences can be cached? Do you understand the implications of that cacheing in a RAC environment?
I suspect that your program is not getting 59015 when it pulls a value from the sequence.
How many rows does the select in your insert-select return? You're reusing the same sequence number for all of them. I suggest to change the insert to
insert into EXPLOIT.SUPPR_LIC_INFO_LICENCE