Create or replace database trigger turn_tracing_on after logon on
schema.scott
Begin
Execute immediate 'alter session set events=''10046 trace name context
forever, level 8''';
End;
/
That should give you more then enough info to trace, especially on 9i.
--
Mladen Gogala
Oracle DBA
Hi!
I think administer database trigger privilege isn't an issue here, it's not
needed when creating schema level logon trigger.
Try to run your execute immediate command first from command line under your
user:
exec Execute immediate 'alter session set events=''10046 trace name context
forever,
Does the user whom you created the trigger have alter session privilege?
Tanel.
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Tuesday, August 12, 2003 4:39 PM
As system (8.1.7.3):
create or replace trigger TRIGGER_NAME
after logon on
Yes I tried granting alter session first
-Original Message-
Sent: Tuesday, August 12, 2003 11:24 PM
To: Multiple recipients of list ORACLE-L
Does the user whom you created the trigger have alter session privilege?
Tanel.
- Original Message -
To: Multiple recipients of
As system (8.1.7.3):
create or replace trigger TRIGGER_NAME
after logon on SCHEMA.schema
begin
Execute immediate 'alter session set events=''10046 trace name context
forever, level 12''';
end;
When I logon after creating this trigger as the user SCHEMA I get the
error message insufficient
Senthil
Are you using direct-path loader?
Dennis Williams
DBA, 80%OCP, 100% DBA
Lifetouch, Inc.
[EMAIL PROTECTED]
-Original Message-
Sent: Monday, August 11, 2003 9:39 AM
To: Multiple recipients of list ORACLE-L
Hi All,
I'm loading a set of data into one of my schema. And wanted
Try with ADMINISTER DATABASE TRIGGER On 2003.08.13 04:29, Jack van Zanen
wrote:
Yes I tried granting alter session first
-Original Message-
Sent: Tuesday, August 12, 2003 11:24 PM
To: Multiple recipients of list ORACLE-L
Does the user whom you created the trigger have alter session
Issue this command from SQL*Plus prior to starting your SQL*Loader session:
ALTER SYSTEM SET max_dump_file_size = unlimited;
ALTER SYSTEM SET timed_statistics = true;
ALTER SYSTEM SET EVENTS '10046 trace name context forever, level 12';
Then, issue this command after the session has started:
That is why my advice was 10046 trace name context forever, level 8, not
SQL_TRACE.
With 10046, level 8 you can still get waits (tkprof in 9i understands them).
You cannot
Get explain plan because direct path doesn't use SQL to insert into the
database.
--
Mladen Gogala
Oracle DBA
Mladen
Yes, when I saw your posting, I assumed that was what you were getting
at. I'll have to remember this one if I have trouble with a SQL*Loader
session.
Dennis Williams
DBA, 80%OCP, 100% DBA
Lifetouch, Inc.
[EMAIL PROTECTED]
-Original Message-
Sent: Monday, August 11, 2003
Hi All,
I'm loading a set of data into one of my schema. And wanted to take the
trace files also.
I tried the follwoing.
1. Identified the sid,serila# for the sql*loader session.
2. used the follwoing,
exec sys.dbms_system.set_sql_trace_in_session(19,11250,TRUE);
but this is not generation
11 matches
Mail list logo