Question

This is my code:

CREATE OR REPLACE TRIGGER unsuccessful_logins
    AFTER INSERT OR UPDATE
    ON temp_logins
    for each row

DECLARE

        CURSOR c_unsuccessful_attempts 
        IS
        SELECT * from temp_attempts
         and user_id= :new.user_id;

    max_fails EXCEPTION;


    BEGIN
         FOR r_unsuccessful_attempts in c_unsuccessful_attempts  
         LOOP

             if(:new.user_id = r_unsuccessful_attempts.user_id) then
                 if (r_unsuccessful_attempts.locked = 'Y') then
                    raise max_fails;
                end if;
            else
                null;
            end if;

        END LOOP;       

EXCEPTION  
    WHEN max_fails THEN  
        RAISE_APPLICATION_ERROR (-20300,'User '''||:new.login_name||''' has reached maximum failed logins. Please contact your system administrator ');    

   END unsuccessful_logins;

The error I am getting in my oracle apps screen is:

APP-01564: ORACLE error 20300 in fdssgn
cause: fdssgn failed due to ORA-20300: You have reached maximum failed logins. Please contact your system administrator.
    ORA-06512: at "APPS.UNSUCCESSFUL_LOGINS",line 24
    ORA-04088: error during excution of trigger 'APPS.UNSUCCESSFUL_LOGINS'.

The SQL statement being executed at the time of the error was:
INSERT INTO TEMP_LOGINS (USER_ID, ATTEMPT_TIME,TERMINAL_ID,LOGIN_NAME)
values(:user_id, sysdate,:erminal_id,:login_name)

I just want to display ORA-20300: You have reached maximum failed logins. Please contact your system administrator part.

And want to omit:

    ORA-06512: at "APPS.UNSUCCESSFUL_LOGINS",line 24
    ORA-04088: error during excution of trigger 'APPS.UNSUCCESSFUL_LOGINS'.
  The SQL statement being executed at the time of the error was: 
INSERT INTO TEMP_LOGINS (USER_ID, ATTEMPT_TIME,TERMINAL_ID,LOGIN_NAME)
values(:user_id, sysdate,:erminal_id,:login_name)

How can I get rid off these extra messages on the screen?

Answer 1

I’m not sure exactly what you mean by ‘oracle apps’, but this link may help; it has a section on exception handling.

As I suggested in an earlier comment, I suspect you need something in your application code to catch and gracefully handle the exception raised by the trigger, so some kind of wrapper around the insert statement. The link is specifically talking about handling an exception in Forms, which (as is probably quite clear) I’m not familiar with, but the principal is likely to be the same if you’re using something related.

Adapting their example slightly, something like this might fit what I think you’re trying to do:

DECLARE
    too_many_attempts EXCEPTION;
    PRAGMA EXCEPTION_INIT(too_many_attempts, -20300);
BEGIN
    INSERT INTO TEMP_LOGINS (USER_ID, ATTEMPT_TIME,TERMINAL_ID,LOGIN_NAME)
    values(:user_id, sysdate,:erminal_id,:login_name);
EXCEPTION
    WHEN too_many_attempts THEN
       fnd_message.set_string(SQLERRM);
       fnd_message.error;
       RAISE FORM_TRIGGER_FAILURE;
END;