Thank you for the additional information regarding the refererencing clause.

Thank you for reproducing the error on 11.2.0.1.

Anyone running Oracle Database 9i (or 8i) that can test the script?

Thank you for confirming the results on Oracle Database 10.2.0.5.

I would prefer to say that I was intending to alias “NEW” as something else due to a potential naming conflict:
http://download.oracle.com/docs/cd/E14072_01/appdev.112/e10472/triggers.htm#LNPLS749

As my sample code is written, there is no point in the “REFERENCING NEW AS NEW” phrase in the trigger code (I think that this is what you are implying).

I assume that the person in the forum thread was attempting to do something like the following, just without realizing that a sequence must be created to generate the sequential numbers:

DROP TABLE T1 PURGE;
DROP TABLE T2 PURGE;
CREATE SEQUENCE T2_C2;

CREATE TABLE T1(C1 DATE, C2 NUMBER);

CREATE TABLE T2(C1 DATE, C2 NUMBER);

CREATE OR REPLACE TRIGGER T1_AFTER_INSERT AFTER INSERT ON T1
REFERENCING NEW AS NEW
FOR EACH ROW
BEGIN
  INSERT INTO T2 VALUES (:NEW.C1,T2_C2.NEXTVAL);
END T1_AFTER_INSERT;
/

INSERT INTO T1 VALUES(SYSDATE-10,-10);

INSERT INTO
  T1
SELECT
  SYSDATE+ROWNUM,
  ROWNUM
FROM
  DUAL
CONNECT BY
  LEVEL<=10;

INSERT INTO T1 VALUES(SYSDATE-ROWNUM,ROWNUM);

SELECT * FROM T2;

The output of the above follows (note that this is similar to Answer B above):

SQL> SELECT * FROM T2;
 
C1                C2
--------- ----------
24-MAY-11          1
04-JUN-11          2
05-JUN-11          3
06-JUN-11          4
07-JUN-11          5
08-JUN-11          6
09-JUN-11          7
10-JUN-11          8
11-JUN-11          9
12-JUN-11         10
13-JUN-11         11
 
11 rows selected.

As demonstrated below, the “REFERENCING NEW AS NEW” clause is not necessary:

DROP SEQUENCE T2_C2;
DROP TABLE T1 PURGE;
DROP TABLE T2 PURGE;
CREATE SEQUENCE T2_C2;

CREATE TABLE T1(C1 DATE, C2 NUMBER);

CREATE TABLE T2(C1 DATE, C2 NUMBER);

CREATE OR REPLACE TRIGGER T1_AFTER_INSERT AFTER INSERT ON T1
FOR EACH ROW
BEGIN
  INSERT INTO T2 VALUES (:NEW.C1,T2_C2.NEXTVAL);
END T1_AFTER_INSERT;
/

INSERT INTO T1 VALUES(SYSDATE-10,-10);

INSERT INTO
  T1
SELECT
  SYSDATE+ROWNUM,
  ROWNUM
FROM
  DUAL
CONNECT BY
  LEVEL<=10;

INSERT INTO T1 VALUES(SYSDATE-ROWNUM,ROWNUM);

SELECT * FROM T2;

SQL> SELECT * FROM T2;

C1                C2
--------- ----------
24-MAY-11          1
04-JUN-11          2
05-JUN-11          3
06-JUN-11          4
07-JUN-11          5
08-JUN-11          6
09-JUN-11          7
10-JUN-11          8
11-JUN-11          9
12-JUN-11         10
13-JUN-11         11

11 rows selected.

Of course if we have a name collision with the word “NEW”, we can specify the “REFERENCING NEW AS” clause:

DROP SEQUENCE T2_C2;
DROP TABLE T1 PURGE;
DROP TABLE T2 PURGE;
CREATE SEQUENCE T2_C2;

CREATE TABLE T1(C1 DATE, C2 NUMBER);

CREATE TABLE T2(C1 DATE, C2 NUMBER);

CREATE OR REPLACE TRIGGER T1_AFTER_INSERT AFTER INSERT ON T1
REFERENCING NEW AS NEW_NO_NAME_COLLISION
FOR EACH ROW
BEGIN
  INSERT INTO T2 VALUES (:NEW_NO_NAME_COLLISION.C1,T2_C2.NEXTVAL);
END T1_AFTER_INSERT;
/

INSERT INTO T1 VALUES(SYSDATE-10,-10);

INSERT INTO
  T1
SELECT
  SYSDATE+ROWNUM,
  ROWNUM
FROM
  DUAL
CONNECT BY
  LEVEL<=10;

INSERT INTO T1 VALUES(SYSDATE-ROWNUM,ROWNUM);

SELECT * FROM T2;

SQL> SELECT * FROM T2;

C1                C2
--------- ----------
24-MAY-11          1
04-JUN-11          2
05-JUN-11          3
06-JUN-11          4
07-JUN-11          5
08-JUN-11          6
09-JUN-11          7
10-JUN-11          8
11-JUN-11          9
12-JUN-11         10
13-JUN-11         11

11 rows selected.

I have reproduced the same behaviour in 11.2.0.1.0 (don’t be disturbed by the error displayed in french)

mhouri@mhouri> select * from v$version;

BANNER
——————————————————————————
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 – Production
PL/SQL Release 11.2.0.1.0 – Production
CORE 11.2.0.1.0 Production
TNS for 32-bit Windows: Version 11.2.0.1.0 – Production
NLSRTL Version 11.2.0.1.0 – Production

mhouri@mhouri> INSERT INTO
2 T1
3 SELECT
4 SYSDATE+ROWNUM,
5 ROWNUM
6 FROM
7 DUAL
8 CONNECT BY
9 LEVEL<=10;
T1
*
ERREUR Ó la ligne 2 :
ORA-00976: Pseudo-colonne ou opÚrateur indiquÚ non autorisÚ ici.
ORA-06512: Ó "MHOURI.T1_AFTER_INSERT", ligne 2
ORA-04088: erreur lors d'exÚcution du dÚclencheur 'MHOURI.T1_AFTER_INSERT'

Best regards

14:46:20 SQL> CREATE TABLE T1(C1 DATE, C2 NUMBER);

Table created.

Elapsed: 00:00:00.07
16:50:33 SQL> 16:50:33 SQL> CREATE TABLE T2(C1 DATE, C2 NUMBER);

Table created.

Elapsed: 00:00:00.04
16:50:37 SQL> CREATE OR REPLACE TRIGGER T1_AFTER_INSERT AFTER INSERT ON T1
REFERENCING NEW AS NEW
FOR EACH ROW
BEGIN
INSERT INTO T2 VALUES (SYSDATE,ROWNUM);
END T1_AFTER_INSERT;
/
16:50:42 2 16:50:42 3 16:50:42 4 16:50:42 5 16:50:42 6 16:50:42 7
Trigger created.

Elapsed: 00:00:00.15
16:50:42 SQL> INSERT INTO T1 VALUES(SYSDATE-10,-10);

1 row created.

Elapsed: 00:00:00.04
16:50:46 SQL> INSERT INTO
T1
SELECT
SYSDATE+ROWNUM,
ROWNUM
FROM
DUAL
CONNECT BY
LEVEL INSERT INTO T1 VALUES(SYSDATE-ROWNUM,ROWNUM);

1 row created.

Elapsed: 00:00:00.00
16:50:54 SQL>
16:51:01 SQL>
16:51:01 SQL>
16:51:01 SQL>
16:51:01 SQL>
16:51:02 SQL>
16:51:02 SQL> select * from t2;

C1 C2
——— ———-
02-JUN-11 0
02-JUN-11 0
02-JUN-11 0
02-JUN-11 0
02-JUN-11 0
02-JUN-11 0
02-JUN-11 0
02-JUN-11 0
02-JUN-11 0
02-JUN-11 0
02-JUN-11 0

C1 C2
——— ———-
02-JUN-11 0

12 rows selected.

Elapsed: 00:00:00.01
16:51:07 SQL>

Thats a good point and it’s indeed seems to be a bug.

Thanks,
Jay