Sybrand Bakker <postbus_at_sybrandb.demon.nl> wrote in message news:<un21iu09ipasik2i43kishaobva00qifme_at_4ax.com>...
> On 1 Jul 2002 07:27:40 -0700, rees_chris_at_hotmail.com (chris) wrote:
>
> >Hi all,
> >
> >Basically a while ago one of our DBAs turned tracing on for one of our
> >Oracle 8 databases to help resolve issues we were having with RMAN
> >backups. This tracing is producing large, circa 50Mb .trc files in
> >the $user_dump_dest directory. Unfortunately this DBA has now left
> >and none of the remaining DBAs know how to turn this tracing off.
> >
> >Being a none DBA person myself I don't know where to look. Can anyone
> >tell me where the RMAN tracing level is set or indeed how to turn RMAN
> >tracing off all together. It must be somewhere specific to the SID
> >because the other databases on the same server do not produce such
> >large trace files.
> >
> >Server is running AIX 4.3.3.
> >
> >Let me know if you require more info to help sort this out
> >
> >TIA
> >
> >Chris
>
>
> There is NO RMAN specific tracing. RMAN traces only occur when RMAN
> experiences errors.
> That said the affected instance must have the sql_trace init.ora
> parameter set to true.
>
> Hth
>
>
> Sybrand Bakker, Senior Oracle DBA
>
> To reply remove -verwijderdit from my e-mail address
There are 2 command line options that make rman produce log files.
One is "msglog" (a high level log file that reports backup sets and
timings among other things). The other is "debug" which is a lower
level log file to be used only when necessary.
Received on Mon Jul 01 2002 - 16:04:15 CDT
