In article <8t100i$rae$1_at_soap.pipex.net>,
"Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote:
> <oratune_at_aol.com> wrote in message news:8stepl$20n$1_at_nnrp1.deja.com...
> > In article <8ssrcq$7kv$1_at_bob.news.rcn.net>,
> > "Steve Long" <steven.long_at_erols.com> wrote:
> > > To enable the SQL trace facility for your session, issue the
following
> > > statement:
> > >
> > > ALTER SESSION
> > > SET SQL_TRACE = TRUE;
> > >
> > > "CUJimmy" <public_at_asd-group.com> wrote in message
> > > news:8ss9e2$6lt$1_at_nnrp1.deja.com...
> > > > How can I turn on tracing on an Oracle 8i server so I can see
the
SQL
> > > > commands issued by a client program (the only one running) for
which I
> > > > dont have the source?
> > > >
> > > > TIA
> > > >
> > > >
> > > > Sent via Deja.com http://www.deja.com/
> > > > Before you buy.
> > >
> > >
> >
> > I doubt that the client program is invoking SQL*Plus therefore I
> > suggest that the sql_trace init<SID>.ora parameter be set to 'TRUE'
to
> > enable tracing for the instance. You might also want to check the
> > oracle_trace_collection_size and the max_dump_file_size parameters
to
> > ensure that you have them set large enough to capture the SQL.
> >
> > --
> > David Fitzjarrell
> > Oracle Certified DBA
>
> What I would be tempted to suggest is using
> DBMS_UTILITY.SET_SQL_TRACE_IN_SESSION , this avoids bouncing the
instance,
> and also the problem of forgetting to switch sql_trace off again. Once
> bitten twice shy
>
> --
> Niall Litchfield
> Oracle DBA
> Audit Commission UK
>
>
This would be an excellent suggestion however I cannot find this in
DBMS_UTILITY as it is installed on our instances (8.1.6). Am I missing
something?
--
David Fitzjarrell
Oracle Certified DBA
Sent via Deja.com http://www.deja.com/
Before you buy.
Received on Mon Oct 23 2000 - 09:29:25 CDT