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!
