Trace users by after logon trigger

Hi.
I have to trace some users application to find the source of problems.
Oracle8i Enterprise Edition Release 8.1.7.0.0
connect system/manager@testdb
create or replace trigger login_trigger
after logon on database
begin
if (USER in ('BLAKE','SCOTT')) then
execute immediate
'ALTER SESSION SET EVENTS ''10046 TRACE NAME CONTEXT FOREVER, LEVEL 12''';
end if;
end;
show error;
SQL> connect scott/tiger@testdb
ERROR:
ORA-00604: error occurred at recursive SQL level 1
ORA-01031: insufficient privileges
ORA-06512: at line 3
OK, I'll grant a priv.
SQL> connect system/manager@testdb
SQL> GRANT administer DATABASE TRIGGER TO "SCOTT";
SQL> connect scott/tiger@testdb
Connected.
Good, only *.trc file is empty after that and there is no trace information for analyse.
Could you please give me a solution?
Mikhail

can't find any *.trc & alert files relevant current time 20080329:20.34
only this
29.03.2008 18:20 72 583 nmuALRT.LOG
25.03.2008 22:22 600 nmuARC0.TRC
but the last connection I've made
20080329:20.34
SQL> connect SCOTT/[email protected]
ERROR:
ORA-00604: error occurred at recursive SQL level 1
ORA-01031: insufficient privileges
ORA-06512: at line 3
this is the files
---nmuALRT.LOG---
Dump file C:\oracle\admin\nmu\bdump\nmuALRT.LOG
Sat Mar 22 17:58:46 2008
ORACLE V8.1.7.0.0 - Production vsnsta=0
vsnsql=e vsnxtr=3
Windows 2000 Version 5.1 Service Pack 2, CPU type 586
Starting up ORACLE RDBMS Version: 8.1.7.0.0.
System parameters with non-default values:
processes = 150
shared_pool_size = 52428800
large_pool_size = 614400
java_pool_size = 20971520
control_files = C:\oracle\oradata\nmu\control01.ctl, C:\oracle\oradata\nmu\control02.ctl, C:\oracle\oradata\nmu\control03.ctl
db_block_buffers = 19200
db_block_size = 8192
compatible = 8.1.0
log_buffer = 32768
log_checkpoint_interval = 10000
log_checkpoint_timeout = 1800
db_files = 1024
db_file_multiblock_read_count= 8
max_enabled_roles = 30
remote_login_passwordfile= EXCLUSIVE
global_names = TRUE
distributed_transactions = 500
instance_name = nmu
service_names = nmu
mts_dispatchers = (PROTOCOL=TCP)(PRE=oracle.aurora.server.SGiopServer)
open_links = 4
sort_area_size = 65536
sort_area_retained_size = 65536
db_name = nmu
open_cursors = 300
os_authent_prefix =
job_queue_processes = 0
job_queue_interval = 10
parallel_max_servers = 5
background_dump_dest = C:\oracle\admin\nmu\bdump
user_dump_dest = C:\oracle\admin\nmu\udump
max_dump_file_size = 10240
oracle_trace_collection_name=
Sat Mar 29 18:20:39 2008
Errors in file C:\oracle\admin\nmu\udump\ORA02288.TRC:
ORA-00604: error occurred at recursive SQL level 1
ORA-01031: insufficient privileges
ORA-06512: at line 3
---nmuARC0.TRC-----------------------------------------
Dump file C:\oracle\admin\nmu\bdump\nmuARC0.TRC
Tue Mar 25 22:22:38 2008
ORACLE V8.1.7.0.0 - Production vsnsta=0
vsnsql=e vsnxtr=3
Windows 2000 Version 5.1 Service Pack 2, CPU type 586
Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
Windows 2000 Version 5.1 Service Pack 2, CPU type 586
Instance name: nmu
Redo thread mounted by this instance: 0 <none>
Oracle process number: 14
Windows thread id: 2592, image: ORACLE.EXE
*** SESSION ID:(11.1) 2008-03-25 22:22:38.428
*** 2008-03-25 22:22:38.428

Similar Messages

Insufficient privileges using execute immediate in after logon trigger

I have an after logon trigger that executes a package/procedure in the schema it was created in.
One of the procedures runs the following:
EXECUTE IMMEDIATE 'AUDIT INSERT TABLE, UPDATE TABLE, DELETE TABLE, EXECUTE PROCEDURE BY ' || USER;
The procedure is throwing an insufficient privileges error when executing this.
However - the schema owner has audit any and audit system privileges and - the statement works fine independently.
When I login as another user this issue arises. The package/procedure are created with definers rights... So - i'm not sure why this is happenening.
Any help is appreciated.

privileges acquired via ROLE do NOT apply within named PL/SQL procedures.
SQL> SET ROLE NONE
SQL> --issue AUDIT again now

Closing DBA session in AFTER LOGON trigger

Hello *,
this is my first question here and my first piece of code in oracle so please don't laugh ;-)
I'm trying to create an AFTER LOGON trigger which disconnects a user if he/she tries to log in from an incorrect host.
What should happen?
User tries to connect.
If he/she is permitted, a record is added to a table.
If not, a record is added to another table and the user is disconnected using RAISE_APPLICATION_ERROR().
After a number of issues I've got it working, except ... I have the feeling that RAISE_APPLICATION_ERROR() doesn't effect users with DBA privileges.
Finally, I'm testing it with one ordinary user - DEF.
The main idea is to disallow connections from user ABC which has DBA privileges.
Tests using DEF are successful but when ABC tries to log in from an incorrect host, a record is added in pcbaudit_failed_logins but the user is not disconnected.
The database is 9.2.0.8.0 and I'm prepared to post RDA report if it is required.
Thank you for your help in advance - I hope I was kind enough :P
Here's the code for the trigger:
DROP TABLE pcbaudit_users;
CREATE TABLE pcbaudit_users (username VARCHAR2(32) NOT NULL, host VARCHAR2(64) NOT NULL);
CREATE INDEX idx_pcbaudit_users_username ON pcbaudit_users(username);
CREATE INDEX idx_pcbaudit_users_host ON pcbaudit_users(host);
DROP TABLE pcbaudit_logins;
CREATE TABLE pcbaudit_logins (username VARCHAR2(32), ip_address VARCHAR2(15), host VARCHAR2(64), ts DATE);
DROP TABLE pcbaudit_failed_logins;
CREATE TABLE pcbaudit_failed_logins (username VARCHAR2(32), ip_address VARCHAR2(15), host VARCHAR2(64), ts DATE);
CREATE OR REPLACE PUBLIC SYNONYM pcbaudit_users FOR sys.pcbaudit_users;
CREATE OR REPLACE PUBLIC SYNONYM pcbaudit_logins FOR sys.pcbaudit_logins;
CREATE OR REPLACE PUBLIC SYNONYM pcbaudit_failed_logins FOR sys.pcbaudit_failed_logins;
GRANT SELECT ON sys.pcbaudit_users TO public;
GRANT INSERT ON sys.pcbaudit_logins TO public;
GRANT INSERT ON sys.pcbaudit_failed_logins TO public;
INSERT INTO pcbaudit_users VALUES ('SYS', '%');
INSERT INTO pcbaudit_users VALUES ('SYSTEM', '%');
INSERT INTO pcbaudit_users VALUES ('ABC', '%');
INSERT INTO pcbaudit_users VALUES ('DEF', '%');
COMMIT;
CREATE OR REPLACE
TRIGGER logon_pcbaudit_trigger AFTER LOGON ON DATABASE
DECLARE
     v_username     VARCHAR2(32); /* variable that will hold current username */
     v_host          VARCHAR2(4000); /* variable that will hold current host */
     v_allowed     NUMBER(1) := 0;
     PRAGMA          AUTONOMOUS_TRANSACTION;
BEGIN
     SELECT     UPPER(USER), /* current user */
          UPPER(SYS_CONTEXT('USERENV', 'HOST')) /* current user host */
     INTO     v_username,
          v_host
     FROM     dual;
     /* debug */
--     DBMS_OUTPUT.PUT_LINE(v_username || '@' || v_host);
     SELECT     1
     INTO     v_allowed
     FROM     pcbaudit_users
     WHERE     UPPER(username) = v_username
AND (
               UPPER(REPLACE(v_host, CHR(0), '')) LIKE UPPER(host) ESCAPE '!' /* fuck that shit! Something appends CHR(0) to its host... */
               OR
               v_host IS NULL /* fuck that shit! Some hosts are NULLs! */
/* write log (user has logged in!) */
INSERT
INTO pcbaudit_logins
(username, ip_address, host, ts)
VALUES
(v_username, SYS_CONTEXT('USERENV', 'IP_ADDRESS'), v_host, SYSDATE);
COMMIT;
EXCEPTION
     WHEN     NO_DATA_FOUND     THEN /* occurs when no matches were found; i.e. current username is not permitted to login from the current host */
          /* log the failed attempt */
          INSERT
          INTO     pcbaudit_failed_logins
          (username, ip_address, host, ts)
          VALUES
          (v_username, SYS_CONTEXT('USERENV', 'IP_ADDRESS'), v_host, SYSDATE);
COMMIT;
          /* disconnect user */
          RAISE_APPLICATION_ERROR(-20001, v_username || '@' || v_host || ' is not allowed to connect.');
     WHEN     OTHERS THEN
          NULL; /* in this case, NULL is better than an error - if an error occurs, user will not be able to login. */
END;

Thank you for your reply!
The situation is quite complicated.
I am aware that a user with DBA privileges can drop the trigger, modify it, etc.
There's an application on top of it and (i don't know why) it requires dba privileges. The point is, there are developers with access to the production database and my task is to stop them from logging in with this username.
Since I'm creating a trigger, I've obviously have no other choice. I can't change the user's password because of number of reasons, I can't deny developers' IP addresses using sqlnet.ora because they need read-only access and so on.
I realize that this is not the way that things are being done (development cycle), but I have no other choice.
So, is there any other way?

Error In After Logon Trigger

Hi,
    I am using Release 11.2.0.3.0 of oracle.
I have created a trigger for restricting specific users(logging from specific program and having specific OSUSER) from loging into the database.
I created below trigger in SYS schema.
CREATE OR REPLACE TRIGGER t1
AFTER
LOGON
ON DATABASE
DECLARE
trg_program varchar2(4000);
trg_user varchar2(4000);
trg_osuser varchar2(4000);
v_killsession VARCHAR2(4000);
v_sid   VARCHAR2(4000);
v_serial   VARCHAR2(4000);
BEGIN
SELECT UPPER (program), UPPER (USERNAME), UPPER (OSUSER),SID,serial#
INTO trg_program, trg_user, trg_osuser,v_sid,v_serial
FROM v$session
WHERE audsid = SYS_CONTEXT ('USERENV', 'SESSIONID') AND ROWNUM = 1;
IF trg_program IN ('SQLPLUS.EXE','SQLPLUSW.EXE','TOAD.EXE')
    AND trg_user in ('USER1','USER2')--,'SYS','SYSTEM')
    --AND trg_osuser not in ('O12345')
THEN
       raise_application_error(-20001,'You are not authorized to connect to this schema directly!!');
END IF;
END;
when i am logging into USER1 through sqlplus/toad it works fine, i am getting required message which is mentioned as 'raise application error'
but when i am compiling the trigger by uncommenting extra condition for OSUSER i.e trg_osuser not in ('O12345') in the trigger code, so that it wont affect the highly provileged user(i.e OSUSER O12345).During logging in to user USER1 i am getting below error
ERROR:
ORA-04045: errors during recompilation/revalidation of
XIGNCMN.RESTRICT_UNAUTH_ACCESS
ORA-01031: insufficient privileges
it should alow me to login because i am OSUSER 'O12345', so why its not working?

Thanks John.
Actually currently we are having database server installed in each of the developers machine so having DBA privilege and having business data, thats why i am planning to configure common database to which all will connect and i wont allow them to connect to the database directly through the functional schema(2 schemas). Now i am planning to restrict the developers access to only 'SELECT+DMLS' for the functional schema and i will do that by creating another user through which they will get connected to the actual functional schema with restricted privilege.
But here the issue is that, for JAVA application, they are having local source code in each of their machine and will also need the connection string/password for the functional schema, so they will know the password for the functional schema, but i want to restrict their access through all the program except 'Jdbc thin client' so i thought of above trigger.
kindly suggest if any other way out?

Calling set_context() outside after logon trigger?

Hello all
I'm trying out and learning on using the application context so I tried out the tutorials from: Oracle® Database Security Guide 11g Release 1 (11.1) B28531-06 document (well, very similar examples that is)
I made a procedure which should retreive the employee_id based on the provided user_name (a logical user_name stored in a table) and set an (attribute, value) pair using the dbms_session.set_context()...
select employee_id into emp_id from user_pswd_table where user_name like p_user_name;
DBMS_SESSION.SET_CONTEXT('employee_id_ctx', 'employee_id', emp_id);
and (the tester) the call of the procedure looked like something like this:
declare usernm varchar2(30);
begin
usernm :='user_name_which_will_be_provided';
set_employee_id_pck.set_employee_id_ctx(usernm);
end;
but as it seams like it is only working if the call is made from the after logon on database trigger...if that's the case after the next log on I have the needed information retrieved with select sys_context(...) from dual, but if that's not the case if I call that procedure from anywhere else it results with no_data_found.
Could someone please explain to me why is that???
Thx in advance :D
Ildiko

Sorry Frank, the message for Ildiko.
You found below context example
Login with user scott :
-- creation table dossiers
SQL> connect scott/tiger@oratest
Connected.
--creation de la table dossiers
CREATE TABLE DOSSIER(
NO_DOS    NUMBER(6),
DT_DOS    DATE,
TYPE_DOS VARCHAR2(50) CHECK (TYPE_DOS IN ('SECRET','NORMAL'))
--Insertions in table dossiers
SQL> insert into dossier values(1,trunc(sysdate),'SECRET');
1 row created.
SQL> insert into dossier values(2,trunc(sysdate),'SECRET');
1 row created.
SQL> insert into dossier values(3,trunc(sysdate),'SECRET');
1 row created.
SQL> insert into dossier values(4,trunc(sysdate),'NORMAL');
1 row created.
SQL> insert into dossier values(5,trunc(sysdate),'NORMAL');
1 row created.
SQL> commit;
Commit complete.
SQL> select * from dossier;
    NO_DOS DT_DOS    TYPE_DOS
         1 22-MAY-07 SECRET
         2 22-MAY-07 SECRET
         3 22-MAY-07 SECRET
         4 22-MAY-07 NORMAL
         5 22-MAY-07 NORMAL
-- Logon with user sys :
-- Attribution grants
grant execute on dbms_rls to scott;
grant execute on dbms_session to scott;
grant ADMINISTER DATABASE TRIGGER to scott;
grant alter session to scott ;
--Logon with user system :
--Création et attribution rôles
Create role sec_employe ;
Create role sec_manager;
Grant select, update,insert, delete on scott.dossier to sec_employe ;
Grant select, update,insert, delete on scott.dossier to sec_manager;
Grant sec_manager to scott;
Grant create any context to scott;
grant create table to scott;
grant create procedure to scott;
-Logon with user scott :
-- Création context package
SQL> create or replace package pkg_dossier_context
2   is
3     procedure set_manager;
4     procedure set_employe;
5    end;
Package created.
SQL> create or replace package body pkg_dossier_context
2       as
3   procedure set_manager
4      is
5    begin
6       dbms_session.set_context('scott_dossier','app_role','manager');
7    end;
8           --
9    procedure set_employe
10       is
11     begin
12       dbms_session.set_context('scott_dossier','app_role','employe');
13     end;
14   end;
Package body created.
-- Création context
SQL> create or replace context scott_dossier using pkg_dossier_context;
Context created.
-- Création du package de sécurité
SQL> create or replace package pkg_dossier_sec
2    as
3       function dossier_predicate(schema_name in varchar2, object_name in varchar2)
4         return varchar2;
5   end;
Package created.
SQL> create or replace package body pkg_dossier_sec
2     as
3        function dossier_predicate(schema_name in varchar2,object_name in varchar2)
4         return varchar2
5         is
6                 lv_predicate varchar2(1000):='';
7         begin
8                 if sys_context('scott_dossier','app_role') = 'manager' then
9                         lv_predicate:='type_dos=''SECRET'''; -- a le droit de voir uniquement
                                          --     les dossiers de type SECRET
10                elsif sys_context('scott_dossier','app_role') = 'employe' then
11                        lv_predicate:='type_dos=''NORMAL'''; -- a le droit de voir uniquement
                                      --les dossiers de type NORMAL
12                 else
13                        lv_predicate:='1=2'; -- block access
14                end if;
15               return lv_predicate;
16        end;
17     end;
Package body created.
-- Add la policy (politique)
SQL> begin
2        dbms_rls.add_policy(
3                  object_schema => 'SCOTT',
4                  object_name => 'DOSSIER',
5                  policy_name => 'SCOTT_DOSSIER_POLICY',
6                  function_schema => 'SCOTT',
7                  policy_function => 'pkg_dossier_sec.dossier_predicate',
8                   statement_types => 'select, insert, update, delete',
9                   update_check => TRUE,
10                  enable => TRUE,
11                  static_policy => FALSE);
12   end;
PL/SQL procedure successfully completed.
-- Création du trigger on logon
SQL> create or replace trigger scott_logon_trigger
2     after logon on database
3    declare
4     NB VARCHAR2(30) ;
5   begin
6       select granted_role
7        into nb
8        from dba_role_privs
9        where grantee='SCOTT' and granted_role='SEC_MANAGER' ;
10        pkg_dossier_context.set_manager;
11      exception
12         when no_data_found then
13         pkg_dossier_context.set_employe;
14   end;
Trigger created.
PL/SQL procedure successfully completed.
SQL> SELECT * FROM DOSSIER;
    NO_DOS DT_DOS    TYPE_DOS
         1 22-MAY-07 SECRET
         2 22-MAY-07 SECRET
         3 22-MAY-07 SECRET
Explication :
Scott a le rôle sec_manager donc il a le droit de voir uniquement les dossiers de type SECRET,
une clause de restriction se rajoute à ma requête initiale,
elle devient :SELECT * FROM DOSSIERS WHERE type_dos='SECRET' ;
-- Connect with user system :
SQL> revoke sec_manager from scott;
Revoke succeeded.
SQL> grant sec_employe to scott;
Grant succeeded.
--Connect with user scott :
SQL> connect scott/tiger@oratest;
Connected.
SQL> select * from dossier;
    NO_DOS DT_DOS    TYPE_DOS
         4 22-MAY-07 NORMAL
         5 22-MAY-07 NORMAL
--Pour enlever le policy
SQL> begin
2          dbms_rls.drop_policy(
3           object_schema => 'SCOTT',
4           object_name => 'DOSSIER',
5           policy_name => 'SCOTT_DOSSIER_POLICY');
6   end;
PL/SQL procedure successfully completed.
SQL> select * from dossier;
    NO_DOS DT_DOS    TYPE_DOS
         1 22-MAY-07 SECRET
         2 22-MAY-07 SECRET
         3 22-MAY-07 SECRET
         4 22-MAY-07 NORMAL
         5 22-MAY-07 NORMALEdited by: Salim Chelabi on 2008-12-16 10:54
Edited by: Salim Chelabi on 2008-12-16 11:26

Raise_application_error in after-logon-trigger

Hi,
I try to build a
after logon on database trigger,
this should execute some inserts into an audit-table, and if some conditions are not given, I want the user to be disconnected.
In this forum I found this thread with a trigger similar to my needs:
To prevent TOAD access
But RAISE_APPLICATION_ERROR in this trigger does not cancel the session and so the user stays connected to oracle. Now I am searching for a disconnect-statement!
Wolfram

Wolfram,
What we have here is
- a post without a 4 digit database version. Most questions have a version specific answer. The behavior you describe does not apply to all versions, and might even apply to SYSDBA connected users only. Is everyone connecting as SYSDBA?
- a post without a proper description of what the trigger does, and without a proper description of the business need. This is especially important as you seem to re-invent AUDIT CONNECT.
- a post from someone who already thinks he knows the answer.
Rest assured: there is no disconnect statement in PL/SQL
You would really need to come up with more details
- database version, 4 digits
- the actual trigger code
- what you are trying to accomplish in terms of business requirements
- why you can't use AUDIT
Sybrand Bakker
Senior Oracle DBA

Restrict User Connections Using Logon Trigger

Hi all,
Now I am restricting user connections from selected terminals, using following logon trigger.
It allows users with DBA privileged user.
How to restrict DBA Privileged users users ?
Note:- As per my application needs DBA privilege.
CREATE OR REPLACE TRIGGER on_logon
AFTER LOGON
ON DATABASE
DECLARE
VPROGRAM VARCHAR2(30);
Vusername VARCHAR2(30);
VTERMINAL VARCHAR2(30);
CURSOR user_prog IS
SELECT UPPER(program),UPPER(username),NVL(TERMINAL,'X') FROM v$session
WHERE audsid=sys_context('USERENV','SESSIONID');
BEGIN
OPEN user_prog;
FETCH user_prog INTO Vprogram,Vusername,VTERMINAL;
IF VTERMINAL NOT IN ( 'APP1','APP2','APP3')+
and Vusername='ABUL'+
THEN
RAISE_APPLICATION_ERROR(-20001, 'You are not allowed to login');
END IF;
CLOSE user_prog;
END;
Thanks i Advance
Abk

Your application needs the DBA role? That is a terrible design-- it violates every principle of secure coding.
Login triggers don't fire for users with the DBA role, so you won't be able to use a login trigger here. You could ditch the login trigger and configure invited and excluded nodes in the listener's sqlnet.ora file, i.e.
tcp.validnode_checking = yes
tcp.excluded_nodes = (hostname1,hostname2,hostname3)You'll have to restart the listener after making that change.
Justin

Enabling Level-12 trace in SYSTEM.LOGON trigger

I am trying to enable level-12 trace for a user as soon as it login to the database.
CREATE OR REPLACE TRIGGER SYSTEM.LOGON_ASPIRE
AFTER LOGON
ON DATABASE
BEGIN
if(upper(USER) = 'U_DATAHUB') then
EXECUTE IMMEDIATE 'ALTER SESSION SET EVENTS ''10046 TRACE NAME CONTEXT FOREVER,LEVEL 12''';
execute immediate 'alter session set current_schema=DATAHUB';
end if;
I have Grant DBA to user U_DATAHUB and I am able to generatr trace for all sessions..but all the trace file is showing this error
PARSING IN CURSOR #4 len=68 dep=2 uid=5 oct=42 lid=5 tim=14297715680259 hv=753686485 ad='0'
ALTER SESSION SET EVENTS '10046 TRACE NAME CONTEXT FOREVER,LEVEL 12'
END OF STMT
PARSE #4:c=0,e=18,p=0,cr=0,cu=0,mis=0,r=0,dep=2,og=0,tim=14297715680254
ERROR #2:err=1031 tim=2228813739
Skipped error 604 during the execution of SYSTEM.LOGON_ASPIRE
*** 2008-10-24 16:09:40.272
ksedmp: internal or fatal error
ORA-00604: error occurred at recursive SQL level 1
ORA-01031: insufficient privileges
ORA-06512: at line 192

See Note:376442.1 Recommended Method for Obtaining 10046 trace for Tuning, it seems the owner of the trigger must be sys:
CREATE OR REPLACE TRIGGER SYS.LOGON_ASPIRE
AFTER LOGON
ON DATABASE
WHEN (USER = 'U_DATAHUB')
BEGIN
EXECUTE IMMEDIATE 'ALTER SESSION SET EVENTS ''10046 TRACE NAME CONTEXT FOREVER,LEVEL 12''';
execute immediate 'alter session set current_schema=DATAHUB';
END;It worked for me...
/u01/app/oracle/admin/orcl/udump/orcl_ora_21932.trcOracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1
System name: Linux
Node name: caliope.localdomain
Release: 2.6.9-67.0.0.0.1.ELsmp
Version: #1 SMP Sun Nov 18 00:23:42 EST 2007
Machine: i686
Instance name: orcl
Redo thread mounted by this instance: 1
Oracle process number: 15
Unix process pid: 21932, image: [email protected] (TNS V1-V3)
*** ACTION NAME:() 2008-09-10 06:52:45.598
*** MODULE NAME:([email protected] (TNS V1-V3)) 2008-09-10 06:52:45.598
*** SERVICE NAME:(SYS$USERS) 2008-09-10 06:52:45.598
*** SESSION ID:(159.3667) 2008-09-10 06:52:45.598
=====================
PARSING IN CURSOR #2 len=40 dep=2 uid=0 oct=42 lid=0 tim=1192429263279537 hv=4026204711 ad='0'
alter session set current_schema=DATAHUB
END OF STMT
PARSE #2:c=1000,e=123,p=0,cr=0,cu=0,mis=0,r=0,dep=2,og=0,tim=1192429263279527
EXEC #2:c=0,e=48,p=0,cr=0,cu=0,mis=0,r=0,dep=2,og=0,tim=1192429263280625
=====================
PARSING IN CURSOR #1 len=186 dep=1 uid=100 oct=47 lid=0 tim=1192429263281298 hv=2889369088 ad='4177de24'
BEGIN
EXECUTE IMMEDIATE 'ALTER SESSION SET EVENTS ''10046 TRACE NAME CONTEXT FOREVER,LEVEL 12''';
execute immediate 'alter session set current_schema=DATAHUB';
END;
END OF STMT
EXEC #1:c=2999,e=2971,p=0,cr=0,cu=0,mis=1,r=1,dep=1,og=4,tim=1192429263281290
WAIT #0: nam='SQL*Net message to client' ela= 7 driver id=1650815232 #bytes=1 p3=0 obj#=-1 tim=1192429263282196
>
Enrique
Edited by: Enrique Orbegozo on Oct 24, 2008 4:29 PM

After Logon on Database Trigger Not Working From Client Terminal

Hi Every One
I Have a Problem, I'am Using Oracle 10g R2, I'd Written After Logon on Database Trigger, I'd Written The Trigger Under The Under The User With DBA Privileges, and it is work Fine, but it is work only when i Logon On The Database from The Server Terminal with any user, and If Logon From any Other Terminal It Is Not Work,
Can any One Know The Reason, Please Help me
Yasser Mokhtar

Please post the trigger code.

Trigger after logon

Hi,
I created a trigger to avoid users to run commands outside the Forms/Reports environment, which means they must execute their commands using the Application servers (App1 and App2, machine column, in v$session).
I need to send them the message "YOU MUST RUN YOUR COMMANDS USING FORMS" when a user called TST01 is TRYING to connect to the database , running Forms outside App1 or App2 machines .
Here is the code:
CREATE OR REPLACE TRIGGER tr_lock_user_out_forms
AFTER LOGON ON DATABASE
DECLARE
v_user sys.v_$session.username%TYPE;
v_mac sys.v_$session.machine%TYPE;
BEGIN
SELECT username, machine
INTO v_user, v_mac
FROM sys.v_$session
WHERE audsid = USERENV('SESSIONID')
AND audsid != 0
AND ROWNUM = 1;
EXCEPTION WHEN NO_DATA_FOUND THEN NULL;
IF (UPPER(v_user) = 'TST01') THEN
BEGIN
     IF LOWER(v_mac) NOT IN ('app1', 'app2')
     THEN
          RAISE_APPLICATION_ERROR(-20000, 'YOU MUST RUN YOUR COMMANDS USING FORMS');
     END IF;
END;
END IF;
END;
SHOW ERRORS
It's allowing user TST01 to connect to the db. Do you guys have any idea ?
Thanks in advance.

Thanks for the replies,
Naresh , the idea is to avoid users to connect to the DB without using Oracle Forms, and the message that the user would receive could be "PLEASE, CONNECT TO THE DATABASE USING FORMS ON AAP1 OR APP2" (sorry if the message I wrote before was unclear).
So, the users could not even connect to the DB if they are not login using Forms. Your idea is good but we have 3.000 tables for this user to access, and as after update cannot be used in schema or database levels, I think it won't worth using this event.
I'm trying other code but if any of you guys have another idea to correct the code below it'd be nice.
Thkx in advance.

Problems with After Report trigger Updating using User-defined functions

Hi,
I have a report which uses SQL to select data that uses a user-defined stored function in the WHERE clause.
I use the same SQL in the After Report trigger with and UPDATE statement to flag all records selected as being run.
Data is being selected by the report no problem, but the records are not being updated. In a test, If I remove the conditions using the user functions, the records update as expected. In Live conditions I must have these conditions in the script.
I originally tried putting the UPDATE in a formual column, but that would not fire on records where that page was not paged through (or paged to end) in the Runtime Previewer.
Can anyone advise?

In case anyone is interested.
The issue was that the stored functions have roles assigned for security.
PL/SQL for After Report doesn't seem to recognise the roles having been assigned for the report, so the implicit cursor update/select I had wouldn't work.
I changed the SELECT into an explicit CURSOR and introduced a FOR LOOP, keeping the UPDATE as an implicit statement.
I know see this was more of a PL/SQL issues than a report one, but such is life. So if anyone feels the urge to move it to the PL/SQL forum, then feel free!!
Have a problem free afternoon. :-)

Multiple logon trigger for a user

Hi,
can I create two (or more) distinct logon trigger for a user? If yes, this situation is "clean"? Both triggers are executed on logon time?

If you don't know what the wrapped source does
and you don't care about the order
then
clean := false ;-)
You filter access, but what if the unknkown wrapped source logs database access in some table on a user before your trigger DENIES access for that user/program?
You would try to find out what the already existing trigger does (third party software?), if you really want to be clean.

Urget: Regarding user logon Trigger

hi all
please help me my problem is
trigger is like
CREATE OR REPLACE TRIGGER USERMODE_USERMST_A_LOGON_TRG
AFTER LOGON OR STARTUP
ON DATABASE
BEGIN
UPDATE SCOTT.USER_MASTER SET STATUS = 'S';
commit;
END;
it execute successfully . but when i log on scott then it give me following error
ERROR:
ORA-00604: error occurred at recursive SQL level 1
ORA-04092: cannot COMMIT in a trigger
ORA-06512: at line 3
can we don't commit in database trigger...
Thanks
Singh

hi
SQL> CONNECT scott/tiger@irfan
Connected.
SQL> SELECT * FROM emp;
    EMPNO ENAME        JOB             MGR HIREDATE        SAL      COMM    DEPTNO A
7901 SMITH CLERK 7902 17-DEC-80 1000 20
     7499 ALLEN        SALESMAN       7698 20-FEB-81      1000       300        30
     7521 WARD         SALESMAN       7698 22-FEB-81      1000       500        30
     7566 JONES        MANAGER        7839 02-APR-81      1000                  20
     7654 MARTIN       SALESMAN       7698 28-SEP-81      1000      1400        30
     7698 BLAKE        MANAGER        7839 01-MAY-81      1000                  30
     7782 CLARK        MANAGER        7839 09-JUN-81      1000                  10
     7788 SCOTT        ANALYST        7566 19-APR-87      1000                  20
     7839 KING         PRESIDENT           17-NOV-81      1000                  10
     7844 TURNER       SALESMAN       7698 08-SEP-81      1000         0        30
     7876 ADAMS        CLERK          7788 23-MAY-87      1000                  20
     7900 JAMES        MANAGER        7698 03-DEC-81      1000                  30
     7902 FORD         ANALYST        7566 03-DEC-81      1000                  20
     7934 MILLER       CLERK          7782 23-JAN-82      1000                  10
     7999 ABCDEFGH     JOB            7839 09-FEB-06      1000         0        10
       16                                                 1000
       15                                                 1000
17 rows selected.
SQL> CREATE OR REPLACE TRIGGER USERMODE_USERMST_A_LOGON_TRG
2 AFTER LOGON OR STARTUP ON DATABASE
3 DECLARE
4 PRAGMA AUTONOMOUS_TRANSACTION;
5 BEGIN
6 UPDATE EMP SET SAL =0 WHERE empno=7901;
7 commit;
8 END;
9 .
SQL> /
Trigger created.
SQL> DISCONNECT
SQL> CONNECT scott/tiger@irfan
Connected.
[pre]
SQL> SELECT * FROM emp;
    EMPNO ENAME        JOB             MGR HIREDATE        SAL      COMM    DEPTNO A
7901 SMITH CLERK 7902 17-DEC-80 0 20     7499 ALLEN        SALESMAN       7698 20-FEB-81      1000       300        30
     7521 WARD         SALESMAN       7698 22-FEB-81      1000       500        30
     7566 JONES        MANAGER        7839 02-APR-81      1000                  20
     7654 MARTIN       SALESMAN       7698 28-SEP-81      1000      1400        30
     7698 BLAKE        MANAGER        7839 01-MAY-81      1000                  30
     7782 CLARK        MANAGER        7839 09-JUN-81      1000                  10
     7788 SCOTT        ANALYST        7566 19-APR-87      1000                  20
     7839 KING         PRESIDENT           17-NOV-81      1000                  10
     7844 TURNER       SALESMAN       7698 08-SEP-81      1000         0        30
     7876 ADAMS        CLERK          7788 23-MAY-87      1000                  20
     7900 JAMES        MANAGER        7698 03-DEC-81      1000                  30
     7902 FORD         ANALYST        7566 03-DEC-81      1000                  20
     7934 MILLER       CLERK          7782 23-JAN-82      1000                  10
     7999 ABCDEFGH     JOB            7839 09-FEB-06      1000         0        10
       16                                                 1000
       15                                                 1000
17 rows selected.Would you paste yours code here??
Khurram

Autotrace with logon trigger?

Hi,
I've a view and the view is be reading by an external program.
How can i see how and how long do they communicate ?
Thanks in advance.
With best regards
Nicole

Hi:
If you have a testing environment (that is definitely a must have) and can modify sources the simplest way to activate trace is add a 'alter session set sql_trace=true' at the beginning of the application, then run it, and then evaluate results.
Using a logon trigger for the user the application is connecting to is another way to accomplish the same, useful when the application cannot be modified. This is an example of the same:
CREATE TRIGGER
schema_owner.logon_tg AFTER LOGON ON schema_owner.SCHEMA
BEGIN
EXECUTE IMMEDIATE 'alter session set sql_trace=true';
END;
This will produce a trace file containing all of the statements executed by the session:
Trace files go to USER_DUMP_DEST, and need to be parsed with TKPROF in order to produce readable output.
Also, check to have timed_statistics=true, so it will report timing in the trace files.
Try to produce trace files, and post if you need assistance in interpreting results.
ciao
Andrea

Sql server 2012 Logon trigger not working for certain logins

Hello. I created a login trigger to insert data for each login in a table, and it works for all logins except one that is format domain\login
and the login ends with the dollar sign(actual name is domain\CTXDEVDCSI1$).
I had been using varchar, but after reading other forum posts, I changed the varchar's to nvarchar's, but it still fails for that id.
The errors written to the sql server error log were the usual "login failed due to trigger execution".
I had granted insert on the rvvlogindata table in dsa to public, and only one id wasn't able to login after that.
Any suggestions would be much appreciated!
Here's the modified table ddl:
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE TABLE [dbo].[rvvlogindata](
[sessionId] [int] NULL,
[LoginTime] [datetime] NULL,
[HostName] [nvarchar](50) NULL,
[ProgramName] [nvarchar](300) NULL,
[LoginName] [nvarchar](50) NULL,
[ClientHost] [nvarchar](50) NULL
) ON [PRIMARY]
GO
Here's the logon trigger code:
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
create trigger [LOGIN_IP_RESTRICTION] on all server for logon
as
Begin
Declare @LogonTriggerData xml,
@EventTime datetime,
@LoginName nvarchar(50),
@ClientHost nvarchar(50),
@HostName nvarchar(50),
@AppName nvarchar(300)
Set @LogonTriggerData = eventdata()
set @EventTime = @LogonTriggerData.value('(/EVENT_INSTANCE/PostTime)[1]', 'datetime')
set @LoginName = @LogonTriggerData.value('(/EVENT_INSTANCE/LoginName)[1]', 'varchar(50)')
set @ClientHost = @LogonTriggerData.value('(/EVENT_INSTANCE/ClientHost)[1]', 'varchar(50)')
set @HostName = HOST_NAME()
set @AppName = APP_NAME()
insert into dsa.dbo.rvvlogindata
sessionId,
LoginTime,
HostName,
ProgramName,
LoginName,
ClientHost
select @@spid,
@EventTime,
convert(nvarchar(50),@HostName),
convert(nvarchar(300),@AppName),
convert(nvarchar(50),@LoginName),
convert(nvarchar(50),@ClientHost)
END
GO
SET ANSI_NULLS OFF
GO
SET QUOTED_IDENTIFIER OFF
GO
ENABLE TRIGGER [LOGIN_IP_RESTRICTION] ON ALL SERVER
GO

Erland, I wanted to add more info to my reply earlier today.
sp_who2 showed no blocking, activity monitor from my local PC SSMS showed no major waits or high i/o or cpu activity.
I was wondering if you have any suggestions on how to find out what was the cause of the 5+ minute wait for SSMS on the remote desktop to respond and fully come up.
I definitely can't put this in production with this hanging delay possibly occurring there.
I was connecting as read_user when it hung.
sp_who2 output at the time was:
1    BACKGROUND                    sa   .   . NULL LOG WRITER      54631 0 04/10
06:59:43
1    0
2    BACKGROUND                    sa   .   . NULL RECOVERY WRITER 8673 0 04/10 06:59:43
2    0
3    BACKGROUND                    sa   .   . NULL LAZY WRITER     300691 0 04/10
06:59:43
3    0
4    BACKGROUND                    sa   .   . NULL RESOURCE MONITOR 1207010 0 04/10 06:59:43
4    0
5    BACKGROUND                    sa   .   . NULL XE TIMER        38828 0 04/10
06:59:43
5    0
6    BACKGROUND                    sa   .   . NULL XE DISPATCHER   1404 0 04/10
06:59:43
6    0
7    BACKGROUND                    sa   .   . master SIGNAL HANDLER 0 0 04/10 06:59:43
7    0
8    BACKGROUND                    sa   .   . NULL LOCK MONITOR    179978 0 04/10
06:59:43
8    0
9    sleeping                      sa   .   . master TASK MANAGER    0 11 04/21
08:37:04
9    0
10   sleeping                      sa   .   . master TASK MANAGER    0 0 04/10
06:59:44
10   0
11   BACKGROUND                    sa   .   . master TRACE QUEUE TASK 546 0 04/10 06:59:44
11   0
12   BACKGROUND                    sa   .   . NULL SYSTEM_HEALTH_MO 4930 0 04/10 06:59:44
12   0
13   BACKGROUND                    sa   .   . NULL RECEIVE         422 0 04/10
06:59:45
13   0
14   BACKGROUND                    sa   .   . master CHECKPOINT      79137 31811 04/10
06:59:46
14   0
15   BACKGROUND                    sa   .   . master TASK MANAGER    1606 0 04/10
06:59:46
15   0
16   BACKGROUND                    sa   .   . NULL UNKNOWN TOKEN   0 0 04/10 06:59:46
16   0
17   sleeping                      sa   .   . master TASK MANAGER    0 74 04/21
08:37:04
17   0
18   sleeping                      sa   .   . master TASK MANAGER    0 0 04/21
08:18:49
18   0
19   sleeping                      sa   .   . master TASK MANAGER    0 0 04/21
08:30:29
19   0
20   sleeping                      sa   .   . master TASK MANAGER    0 1 04/21
08:37:14
20   0
21   sleeping                      sa   .   . master TASK MANAGER    0 7 04/21
08:30:59
21   0
22   sleeping                      sa   .   . master TASK MANAGER    16 4 04/21
08:37:44
22   0
23   sleeping                      sa   .   . master TASK MANAGER    0 15 04/21
08:39:24
23   0
25   BACKGROUND                    sa   .   . master BRKR EVENT HNDLR 0 95 04/10 06:59:48
25   0
30   BACKGROUND                    sa   .   . master BRKR TASK       0 0 04/10
06:59:48
30   0
31   BACKGROUND                    sa   .   . master BRKR TASK       16926 0 04/10
06:59:48
31   0
32   BACKGROUND                    sa   .   . master BRKR TASK       0 0 04/10
06:59:48
32   0
34   BACKGROUND                    sa   .   . master BRKR TASK       10701 0 04/10
06:59:48
34   0
51   sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
03:16:56
51   0
52   sleeping                      reports_adm REPORTSDEVSI2   . JBOSS_Cluster_CRServer2011 AWAITING COMMAND 0 0 04/21
08:52:12 jTDS
52   0
53   sleeping                      NT AUTHORITY\SYSTEM SQLDEV2012      . msdb AWAITING COMMAND 0 0 04/10
06:59:58 SQLAgent - Email Logger                       53   0
54   sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:51 Citrix:Broker#1                               54   0
55   sleeping                      edit_user ASDEV1          . dsa AWAITING
COMMAND 0 0 04/21 08:55:27 jTDS
55   0
56   sleeping                      reports_adm REPORTSDEVSI2   . JBOSS_Cluster_CRServer2011 AWAITING COMMAND 0 0 04/21
08:52:12 jTDS
56   0
57   sleeping                      reports_adm REPORTSDEVSI2   . JBOSS_Cluster_CRServer2011 AWAITING COMMAND 0 0 04/21
08:52:12 jTDS
57   0
58   sleeping                      reports_adm REPORTSDEVSI2   . JBOSS_Cluster_CRServer2011 AWAITING COMMAND 0 0 04/21
08:52:12 jTDS
58   0
59   sleeping                      NT AUTHORITY\SYSTEM SQLDEV2012      . msdb AWAITING COMMAND 124 242 04/10
06:59:59 SQLAgent - Generic Refresher                  59   0
60   sleeping                      NT AUTHORITY\SYSTEM SQLDEV2012      . msdb AWAITING COMMAND 2790 1160 04/21
08:55:00 SQLAgent - Job invocation engine              60   0
61   sleeping                      reports_adm REPORTSDEVSI2   . JBOSS_Cluster_CRServer2011 AWAITING COMMAND 0 0 04/21
08:52:12 jTDS
61   0
62   sleeping                      reports_adm REPORTSDEVSI2   . JBOSS_Cluster_CRServer2011 AWAITING COMMAND 0 0 04/21
08:52:12 jTDS
62   0
63   sleeping                      reports_adm REPORTSDEVSI2   . JBOSS_Cluster_CRServer2011 AWAITING COMMAND 0 0 04/21
08:52:12 jTDS
63   0
64   sleeping                      reports_adm REPORTSDEVSI2   . JBOSS_Cluster_CRServer2011 AWAITING COMMAND 0 0 04/21
08:52:12 jTDS
64   0
65   sleeping                      reports_adm REPORTSDEVSI2   . JBOSS_Cluster_CRServer2011 AWAITING COMMAND 0 0 04/21
08:52:12 jTDS
65   0
66   sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
03:16:56
66   0
67   sleeping                      reports_adm REPORTSDEVSI2   . JBOSS_Cluster_CRServer2011 AWAITING COMMAND 0 0 04/21
08:52:12 jTDS
67   0
68   sleeping                      edit_user DCMA10685       . dsa AWAITING COMMAND 0 0 04/21
08:56:47 jTDS
68   0
69   sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:49 Citrix:Configuration                          69   0
70   sleeping                      rvanveen DCMA8460        . master AWAITING COMMAND 1794 7120 04/21
08:51:37 Microsoft SQL Server Management Studio        70   0
71   sleeping                      xsp_user XSPDEVSI2       . xspv5 AWAITING COMMAND 0 0 04/21
08:58:52 .Net SqlClient Data Provider                  71   0
72   sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:56:01 Citrix:Monitor                                72   0
73   sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:30 Citrix:Monitor                                73   0
74   sleeping                      rvanveen DCMA8460        . master AWAITING COMMAND 16 2 04/21
08:53:37 Microsoft SQL Server Management Studio - Query 74   0
75   sleeping                      rvanveen DCMA8460        . loginaudit AWAITING COMMAND 0 22 04/21
08:50:29 Microsoft SQL Server Management Studio - Query 75   0
76   sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
07:05:07
76   0
77   sleeping                      adm_jbossportal ASDEV1          . jbossportal AWAITING
COMMAND 0 0 04/21 08:40:27 jTDS
77   0
78   sleeping                      rvanveen DCMA8460        . master AWAITING COMMAND 110 542 04/21
08:46:17 Microsoft SQL Server Management Studio - Query 78   0
79   sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
07:05:56
79   0
80   sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:54 Citrix:MachineCreation                        80   0
81   sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
08:08:29
81   0
82   sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
07:02:13
82   0
83   sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
07:02:15
83   0
84   sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:44 Citrix:Monitor                                84   0
85   sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
07:11:05
85   0
86   sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:53 Citrix:AdIdentity                             86   0
87   sleeping                      DAIWA_USA\admsql SQLDEV2012      . master AWAITING COMMAND 15 2 04/21
08:56:20 Microsoft SQL Server Management Studio - Query 87   0
88   sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:36 Citrix:SiteServices                           88   0
89   sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:42 Citrix:Host                                   89   0
90   sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:47 Citrix:ConfigurationLogging                   90   0
91   RUNNABLE                      rvanveen DCMA8460        . master SELECT INTO
15 51 04/21 08:58:46 Microsoft SQL Server Management Studio - Query 91   0
92   sleeping                      rvanveen DCMA8460        . master AWAITING COMMAND 63 30 04/21
08:52:34 Microsoft SQL Server Management Studio - Query 92   0
94   sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:53 Citrix:DelegatedAdmin                         94   0
95   sleeping                      DAIWA_USA\admsql SQLDEV2012      . loginaudit AWAITING COMMAND 173 27 04/21
08:56:10 Microsoft SQL Server Management Studio        95   0
96   sleeping                      xsp_user XSPDEVSI2       . xspv5 AWAITING COMMAND 0 0 04/21
08:58:33 .Net SqlClient Data Provider                  96   0
97   sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
08:10:07
97   0
98   sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 31 38 04/21
08:00:31
98   0
99   sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
08:10:12
99   0
100 sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 282 04/21
08:10:14
100 0
101 sleeping                      DAIWA_USA\admsql SQLDEV2012      . master AWAITING COMMAND 0 8 04/21
08:56:50 Microsoft SQL Server Management Studio        101 0
102 sleeping                      DAIWA_USA\admsql SQLDEV2012      . master AWAITING COMMAND 31 0 04/21
08:54:57 Microsoft SQL Server Management Studio        102 0
103 sleeping                      read_user SQLDEV2012      . master AWAITING COMMAND 0 8 04/21
08:57:09 Microsoft SQL Server Management Studio        103 0
104 sleeping                      read_user SQLDEV2012      . dsa AWAITING COMMAND 0 0 04/21
08:57:09 Microsoft SQL Server Management Studio        104 0
105 sleeping                      rvanveen DCMA8460        . tempdb AWAITING COMMAND 8875 336 04/21
08:58:54 Microsoft SQL Server Management Studio        105 0
106 sleeping                      read_user SQLDEV2012      . master AWAITING COMMAND 16 0 04/21
08:57:39 Microsoft SQL Server Management Studio        106 0
107 sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:47 Citrix:EnvTest                                107 0
108 sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 2200 8514 04/21
08:00:31
108 0
109 sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
07:05:56
109 0
110 sleeping                      rvanveen DCMA8460        . master AWAITING COMMAND 0 0 04/21
08:58:48 Microsoft SQL Server Management Studio        110 0
113 sleeping                      Citrix_adm CTXDEVSI1       . XenApp6 AWAITING COMMAND 284 777 04/21
08:51:33 Citrix IMA                                    113 0
119 sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:42 Citrix:ConfigurationLoggingData               119 0
120 sleeping                      AMERICAS\CTXDEVDCSI1$ CTXDEVDCSI1    . CitrixXDFarm1 AWAITING COMMAND 0 0 04/21
08:58:26 Citrix:Storefront                             120 0
125 sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/16
13:55:16
125 0
126 sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 16 0 04/16
11:25:30
126 0
131 sleeping                      echouliak DCMA10685       . master AWAITING COMMAND 139 8 04/14
15:26:55 Microsoft SQL Server Management Studio        131 0
135 sleeping                      echouliak DCMA10685       . dsa AWAITING COMMAND 0 0 04/14
15:24:52 Microsoft SQL Server Management Studio - Query 135 0
136 sleeping                      echouliak DCMA10685       . dsa AWAITING COMMAND 0 0 04/14
15:00:17 Microsoft SQL Server Management Studio - Query 136 0
140 sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
07:05:56
140 0
145 sleeping                      edit_user INFADEVFS2      . dsa AWAITING COMMAND 0 0 04/21
07:05:56
145 0

Trace users by after logon trigger

Similar Messages

Maybe you are looking for