RE: DBMS_SYSTEM.KSDWRT question
Thanks Kirti ... Raj __ Rajendra Jamadagni MIS, ESPN Inc. Rajendra dot Jamadagni at ESPN dot com Any opinion expressed here is personal and doesn't reflect that of ESPN Inc. QOTD: Any clod can have facts, but having an opinion is an art! *This e-mail message is confidential, intended only for the named recipient(s) above and may contain information that is privileged, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 and delete this e-mail message from your computer, Thank you.*2
RE: DBMS_SYSTEM.KSDWRT question
Raj, Here is a trial run with those procedures... will tell you what those do. SQL> alter session set sql_trace=true; Session altered. SQL> exec dbms_system.ksdwrt(1, 'From Kirti'); -- Write to trace file (1=Trace, 2=alert, 3=both). PL/SQL procedure successfully completed. SQL> exec dbms_system.ksdddt; -- Add a time stamp to trace file PL/SQL procedure successfully completed. SQL> exec dbms_system.ksdind(30); -- Print ':' upto 30 times (max, I think) in trace file PL/SQL procedure successfully completed. SQL> exec dbms_system.ksdfls; -- Still not found what this does... PL/SQL procedure successfully completed. SQL> alter session set sql_trace=false; Session altered. Look for those in the following trace: = PARSING IN CURSOR #1 len=49 dep=0 uid=0 oct=47 lid=0 tim=3675829616 hv=3932217178 ad='a36d5018' BEGIN dbms_system.ksdwrt(1, 'From Kirti'); END; END OF STMT PARSE #1:c=0,e=1,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=4,tim=3675829616 >From Kirti < EXEC #1:c=0,e=0,p=0,cr=0,cu=0,mis=0,r=1,dep=0,og=4,tim=3675829616 *** 2002-06-20 14:19:46.578 = PARSING IN CURSOR #1 len=32 dep=0 uid=0 oct=47 lid=0 tim=3675830849 hv=2233699027 ad='a36b8990' BEGIN dbms_system.ksdddt; END; END OF STMT PARSE #1:c=0,e=0,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=4,tim=3675830849 *** 2002-06-20 14:19:46.578 << EXEC #1:c=0,e=0,p=0,cr=0,cu=0,mis=0,r=1,dep=0,og=4,tim=3675830849 *** 2002-06-20 14:19:57.010 = PARSING IN CURSOR #1 len=36 dep=0 uid=0 oct=47 lid=0 tim=3675831893 hv=1989824971 ad='a36bc900' BEGIN dbms_system.ksdind(30); END; END OF STMT PARSE #1:c=1,e=1,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=4,tim=3675831893 ::EXEC #1:c=0,e=0,p=0,cr=0,cu=0,mis=0,r=1,dep=0,og=4,tim=3675831893 *** 2002-06-20 14:20:10.772 = PARSING IN CURSOR #1 len=32 dep=0 uid=0 oct=47 lid=0 tim=3675833269 hv=752639005 ad='a36bfc10' BEGIN dbms_system.ksdfls; END; END OF STMT PARSE #1:c=0,e=0,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=4,tim=3675833269 EXEC #1:c=0,e=0,p=0,cr=0,cu=0,mis=0,r=1,dep=0,og=4,tim=3675833269 *** 2002-06-20 14:20:21.173 = PARSING IN CURSOR #1 len=34 dep=0 uid=0 oct=42 lid=0 tim=3675834309 hv=1582735206 ad='a3693370' alter session set sql_trace=false END OF STMT PARSE #1:c=0,e=0,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=4,tim=3675834309 EXEC #1:c=0,e=0,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=4,tim=3675834309 - Kirti -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Deshpande, Kirti INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
RE: DBMS_SYSTEM.KSDWRT question
Addition: DBMS_SYSTEM.KCFRMS - resets counters displayed by MAX_WAIT in V$SESSION_EVENT, and MAXIORTM, MAXIOWTM in V$FILESTAT views. - Kirit -Original Message- Sent: Thursday, June 20, 2002 2:33 PM To: '[EMAIL PROTECTED]' Cc: '[EMAIL PROTECTED]' Raj, Here is a trial run with those procedures... will tell you what those do. SQL> alter session set sql_trace=true; Session altered. SQL> exec dbms_system.ksdwrt(1, 'From Kirti'); -- Write to trace file (1=Trace, 2=alert, 3=both). PL/SQL procedure successfully completed. SQL> exec dbms_system.ksdddt; -- Add a time stamp to trace file PL/SQL procedure successfully completed. SQL> exec dbms_system.ksdind(30); -- Print ':' upto 30 times (max, I think) in trace file PL/SQL procedure successfully completed. SQL> exec dbms_system.ksdfls; -- Still not found what this does... PL/SQL procedure successfully completed. SQL> alter session set sql_trace=false; Session altered. Look for those in the following trace: = PARSING IN CURSOR #1 len=49 dep=0 uid=0 oct=47 lid=0 tim=3675829616 hv=3932217178 ad='a36d5018' BEGIN dbms_system.ksdwrt(1, 'From Kirti'); END; END OF STMT PARSE #1:c=0,e=1,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=4,tim=3675829616 >From Kirti < EXEC #1:c=0,e=0,p=0,cr=0,cu=0,mis=0,r=1,dep=0,og=4,tim=3675829616 *** 2002-06-20 14:19:46.578 = PARSING IN CURSOR #1 len=32 dep=0 uid=0 oct=47 lid=0 tim=3675830849 hv=2233699027 ad='a36b8990' BEGIN dbms_system.ksdddt; END; END OF STMT PARSE #1:c=0,e=0,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=4,tim=3675830849 *** 2002-06-20 14:19:46.578 << EXEC #1:c=0,e=0,p=0,cr=0,cu=0,mis=0,r=1,dep=0,og=4,tim=3675830849 *** 2002-06-20 14:19:57.010 = PARSING IN CURSOR #1 len=36 dep=0 uid=0 oct=47 lid=0 tim=3675831893 hv=1989824971 ad='a36bc900' BEGIN dbms_system.ksdind(30); END; END OF STMT PARSE #1:c=1,e=1,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=4,tim=3675831893 ::EXEC #1:c=0,e=0,p=0,cr=0,cu=0,mis=0,r=1,dep=0,og=4,tim=3675831893 *** 2002-06-20 14:20:10.772 = PARSING IN CURSOR #1 len=32 dep=0 uid=0 oct=47 lid=0 tim=3675833269 hv=752639005 ad='a36bfc10' BEGIN dbms_system.ksdfls; END; END OF STMT PARSE #1:c=0,e=0,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=4,tim=3675833269 EXEC #1:c=0,e=0,p=0,cr=0,cu=0,mis=0,r=1,dep=0,og=4,tim=3675833269 *** 2002-06-20 14:20:21.173 = PARSING IN CURSOR #1 len=34 dep=0 uid=0 oct=42 lid=0 tim=3675834309 hv=1582735206 ad='a3693370' alter session set sql_trace=false END OF STMT PARSE #1:c=0,e=0,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=4,tim=3675834309 EXEC #1:c=0,e=0,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=4,tim=3675834309 - Kirti -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Deshpande, Kirti INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
RE: DBMS_SYSTEM.KSDWRT question
Title: RE: DBMS_SYSTEM.KSDWRT question Thanks Tony, I have been told not to use standard auditing ... Raj __ Rajendra Jamadagni MIS, ESPN Inc. Rajendra dot Jamadagni at ESPN dot com Any opinion expressed here is personal and doesn't reflect that of ESPN Inc. QOTD: Any clod can have facts, but having an opinion is an art! -Original Message-From: Aponte, Tony [mailto:[EMAIL PROTECTED]]Sent: Thursday, June 20, 2002 2:35 PMTo: [EMAIL PROTECTED]Cc: [EMAIL PROTECTED]Subject: RE: DBMS_SYSTEM.KSDWRT question We've been using KSDWRT in logon and table triggers (as well as in maintenance jobs for our 24x7 databases that didn't have a UTL_FILE_DIR entry) and have yet to encounter a problem. I trussed a background process that used the procedure and it wrote to the files using the same I/O commands that it uses for other commands (like ALTER DATABASE BACKUP CONTROLFILE TO TRACE). For the other procedures I'd do truss the session connected to a development server to see what they cause at the OS level. Is there a reason why you aren't using standard auditing to capture DDL activity? HTH Tony Aponte *This e-mail message is confidential, intended only for the named recipient(s) above and may contain information that is privileged, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 and delete this e-mail message from your computer, Thank you.*2
RE: DBMS_SYSTEM.KSDWRT question
Title: RE: DBMS_SYSTEM.KSDWRT question We've been using KSDWRT in logon and table triggers (as well as in maintenance jobs for our 24x7 databases that didn't have a UTL_FILE_DIR entry) and have yet to encounter a problem. I trussed a background process that used the procedure and it wrote to the files using the same I/O commands that it uses for other commands (like ALTER DATABASE BACKUP CONTROLFILE TO TRACE). For the other procedures I'd do truss the session connected to a development server to see what they cause at the OS level. Is there a reason why you aren't using standard auditing to capture DDL activity? HTH Tony Aponte -Original Message- From: Jamadagni, Rajendra [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 11:34 AM To: Multiple recipients of list ORACLE-L Subject: DBMS_SYSTEM.KSDWRT question Hi all, on our 8161 database, I want to capture all the DDLs issued by non SYS users (believe me, some developers still do). As production locking is away by few weeks, I wrote a database level trigger to capture all the DDL statements. But on 8161 it fails due to a bug when a distribution transaction is taking place (as the trigger uses autonomous transaction). Alternatively I am thinking of using DBMS_SYSTEM.KSDWRT ... does it have any such side effects? Basically, does it affect current transaction at all? Is it transaction independent? Also on the similar lines, does anyone know what these procedures do? I tried running them on a test database, but couldn't see anything ... in the session or in the alert log. dbms_system.KSDIND; dbms_system.KCFRMS; dbms_system.KSDDDT; dbms_system.KSDFLS; Thanks in advance Raj __ Rajendra Jamadagni MIS, ESPN Inc. Rajendra dot Jamadagni at ESPN dot com Any opinion expressed here is personal and doesn't reflect that of ESPN Inc. QOTD: Any clod can have facts, but having an opinion is an art!
