don't you need
Thanks for your reply.
I have now tried what you suggest and receive the same error ("Invalid column index").
I have also tried using the default text that SQL Developer puts into the validation, i.e.:
-- Please raise an exception if the validation fails.
-- For example:
SELECT count(*) INTO l_count FROM dual;
IF l_count = 0
Using this I also receive the same error ("Invalid column index").
Interestingly, running the same unit test using SQL Developer 126.96.36.199 works. Some problem specific to the latest version of SQL Developer therefore perhaps?
Any other thoughts very gratefully received!
Perhaps. I'd open an SR with MOS.
For anyone finding this thread, this is confirmed by Oracle Support as a bug. No resolution exists as at 8-Jun-2017.
Bug 25973908 : UT: USING 'USER PL/SQL CODE' IN 'PROCESS VALIDATION' FAILS: INVALID COLUMN INDEX