We have an application designed for an old oracle version which issues some sql which is no more supported in todays database version.
We want to use the application unchanged with a new database server.
The application issues an
ALTER SESSION SET OPTIMIZER_GOAL = FIRST_ROWS ;
which results in ORA-01986 and the application dies.
We would like to hide the error 01986 from the application using a trigger:
create or replace
if (ora_is_servererror (1986)) then
null; -- what to do here? we want clear the ora-01986 from the error stack
How to handle the error, so that the alter session set ...
statement is just ignored and no error code is returned to the application?
Edited by: jjaeckel on Dec 11, 2010 12:58 AM
Edited by: jjaeckel on Dec 12, 2010 2:16 AM
Edited by: jjaeckel on 13.12.2010 02:00