Different result executing by EXEC and by job

Question

Greetings!
I've got simple procedure:
CREATE OR REPLACE PROCEDURE alertlog.check_log IS
IP_ADDRESS VARCHAR2(16);
BEGIN
SELECT sys_context('USERENV','IP_ADDRESS') INTO IP_ADDRESS FROM sys.dual;
FOR alert_conn IN (SELECT alert_date,alert_text FROM alert_log WHERE alert_date > SYSDATE - 20/1440 and REGEXP_LIKE(alert_text,'ORA-'))
LOOP
     INSERT INTO ALERT_LOG_CONT@EMGRID VALUES (IP_ADDRESS,alert_conn.alert_date,alert_conn.alert_text);
END LOOP;
UPDATE SID_LIST@EMGRID SET LAST_UPLOAD=SYSDATE WHERE IPADDR=IP_ADDRESS;
COMMIT;
END;
And Job
BEGIN
sys.dbms_scheduler.create_job(
job_name => '"ALERTLOG"."CHECK_LOG_JOB"',
job_type => 'PLSQL_BLOCK',
job_action => 'begin
alertlog.check_log;
end;',
repeat_interval => 'FREQ=MINUTELY;INTERVAL=15;BYDAY=MON,TUE,WED,THU,FRI,SAT,SUN;BYHOUR=0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23',
start_date => to_timestamp_tz('2010-12-01 13:09:57 Europe/Moscow', 'YYYY-MM-DD HH24:MI:SS TZR'),
job_class => '"DEFAULT_JOB_CLASS"',
auto_drop => FALSE,
enabled => FALSE);
sys.dbms_scheduler.set_attribute( name => '"ALERTLOG"."FFF"', attribute => 'logging_level', value => DBMS_SCHEDULER.LOGGING_OFF);
sys.dbms_scheduler.set_attribute( name => '"ALERTLOG"."FFF"', attribute => 'job_weight', value => 1);
sys.dbms_scheduler.enable( '"ALERTLOG"."FFF"' );
END;
When I run EXEC alertlog.check_log in sqlplus the result is good:
IPADDR     EVENT_DATE     ERROR_LINE
10.20.17.38     2010-12-01 13:19:01.0     ORA-TEST
But when it is being run by job - it doesn't get an ip address:
IPADDR     EVENT_DATE     ERROR_LINE
     2010-12-01 13:19:01.0     ORA-TEST
What am I doing wrong?
Update:
And it also doesn't update SID_LIST@EMGRID by
UPDATE SID_LIST@EMGRID SET LAST_UPLOAD=SYSDATE WHERE IPADDR=IP_ADDRESS;
Edited by: Skalny on 01.12.2010 13:41

Answer 1

Herald ten Dam wrote:
SELECT sys_context('USERENV','IP_ADDRESS') INTO IP_ADDRESS FROM sys.dual;In a job this will give no value back, because a job is run inside the database and has no client connection, so IP_ADDRESS will be null. That's why your update doesn't work.
For a job you can use UTL_INADDR.GET_HOST_ADDRESS.Thank you for explanation.