Is this a bug in Oracle 10g ?

Question

I've been trying to port my SQL from 9.2.0.6 to 10g recently and noticed a problem using the sequence operator NEXTVAL from within a trigger, when inserting rows into another tables.
For example, the following code works ok on 9.2.0.6 but when run on 10g the KPIIDD.NEXTVAL is inserted as NULL.
<< This is part of a Trigger on PDRTEM table >>
INSERT INTO LSTKPI (KPIIDD, PRMNME, KPISUP, TEMIDD1)
VALUES (KPIIDD.NEXTVAL, NEXTPRM.PRMNME, NEXTSTA.STANAM, PDRTEM_PKG_1.rids(i));
In order to fix the problem i had to add a +0 to the NEXTVAL clause, as demonstrated in the following example which works in 9.2.0.6 and 10g
INSERT INTO LSTKPI (KPIIDD, PRMNME, KPISUP, TEMIDD1)
VALUES (KPIIDD.NEXTVAL+0, NEXTPRM.PRMNME, NEXTSTA.STANAM, PDRTEM_PKG_1.rids(i));
NOTE: If the insert is outside of a Trigger then it's fine - just when within the Trigger it's a problem.

Answer 1

Do your sequence and column have the same name? In your code sample, it looks like they do:
INSERT INTO LSTKPI (KPIIDD, PRMNME, KPISUP, TEMIDD1)
VALUES (KPIIDD.NEXTVAL, NEXTPRM.PRMNME, NEXTSTA.STANAM, PDRTEM_PKG_1.rids(i));
Maybe that has confused the parser.
As Oracle moves forward, you can expect more object-oriented functionality. That could mean that columns could have their own attributes or methods. If so, how is the parser to know whether in this code the value KPIIDD.NEXTVAL refers to the (external) sequence or a column attribute?
As a suggestion, try renaming the sequence.
create sequence KPIIDD_SEQ start with ... ;
INSERT INTO LSTKPI (KPIIDD, PRMNME, KPISUP, TEMIDD1)
VALUES (KPIIDD_SEQ.NEXTVAL, NEXTPRM.PRMNME, NEXTSTA.STANAM, PDRTEM_PKG_1.rids(i));
HTH,
- Doug