RE: Trigger not firing!!!!!!!!!!(URGENT)

Ahhhh, I see now. You tried to use the ORA_ variable interactively, but it's only populated during the event as per the docs.

Rich

-----Original Message-----

From: Jesse, Rich=20
Sent: Thursday, June 09, 2005 3:20 PM
To: Oracle-L (E-mail)
Subject: RE: Trigger not firing!!!!!!!!!!(URGENT)

Hey Mark,

You're example wrapped (could never get used to that in SQL*Plus) -- which one isn't populated? I'm hoping it's SYS_CONTEXT because Ch 16 of the "Oracle9i Application Developer's Guide - Fundamentals" manual says ORA_CLIENT_IP_ADDRESS is for an AFTER LOGON event (table 16-3).

Thx!
Rich

-----Original Message-----

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Powell, Mark D Sent: Thursday, June 09, 2005 3:07 PM
To: Oracle-L (E-mail)
Subject: RE: Trigger not firing!!!!!!!!!!(URGENT)

The initial post was about the fact the event trigger public variables like ORA_CLIENT_IP_ADDRESS were not producing results.

Test on 9.2.0.6
UT1 > select ORA_CLIENT_IP_ADDRESS, sys_context('USERENV','IP_ADDRESS') ip_addr
  2 from sys.dual
  3 /

ORA_CLIENT_IP_ADDRESS

xxx.103.x.141

While some of the event variables can be used in a select from dual and always seem to be populated others are populated only after certain events take place so where a sys_context or v$session.column exists I think it may be, at present, a better choice.

IMHO -- Mark D Powell --

--
http://www.freelists.org/webpage/oracle-l