VAX/VMS - Trace File Ownership/Permissions
From: Stephen Turner <sturner_at_athena.mit.edu>
Date: 1995/11/27
Message-ID: <49cq4j$icr_at_senator-bedfellow.MIT.EDU>#1/1
Date: 1995/11/27
Message-ID: <49cq4j$icr_at_senator-bedfellow.MIT.EDU>#1/1
We've recently enabled SQL Trace for developers' use -
but the trace files created are owned by our "ORACLE DBA"
VMS account, and no-one else has read permission to these
files, so developers can't use TKPROF on the trace files.
Does anyone know how ownership and file permissions for these
trace files are controlled and can be altered?
Thanks,