Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.misc -> Re: Trace file
If you got that from a book, throw it out of the window. This is simply NOT
true.
Trace files will be created either deliberately, because tracing is turned
on for the database, or the client enables tracing for that session OR when
the session crashes, ie complete ABnormally.
The trace file below is a typical example of the latter situation.
You seem to have asynchronous io enabled, but Oracle can't find the
asynchronous device.
This is a typical message that can result from a background process also.
It looks like you didn't set background_dump_dest and user_dump_dest in your
init file, or they have the same value. I wouldn't do that. In order to make
a clear separation between server problems and client problems you need to
make sure background_dump_dest and user_dump_dest go to two different
directories.
Hth,
--
Sybrand Bakker, Oracle DBA
Charles Hansis <chansis_at_earthlink.net> wrote in message
news:7vdfd0$d8g$1_at_ash.prod.itd.earthlink.net...
> Recently we noticed that we were rapidly accumulating trace files. After
> looking through several Oracle pubs, that didn't help, I am asking someone
> here to give me a hand. The books say that a trace file is created when
> Oracle has a process that complete normally. It also says that it names
the
> file after the process id that had the error. Below is a copy of one of
the
> trace files. They seem to appear in groups and on all the different
> instances that are running on this server. The server is a HP K410 w/
Oracle
> 8.0.4.
>
> /opt/oracle8/rdbms/log/ora_4070.trc
> Oracle8 Enterprise Edition Release 8.0.4.0.0 - Production
> PL/SQL Release 8.0.4.0.0 - Production
> ORACLE_HOME = /opt/oracle8
> System name: HP-UX
> Node name: Servername
> Release: B.10.20
> Version: A
> Machine: 9000/869
> Instance name: sid
> Redo thread mounted by this instance: 0 <none>
> Oracle process number: 0
> Unix process pid: 4070, image: oraclempeb
> File '/dev/async' not present : errno=2
>
> Thanks for the help
>
> JH
>
>
>
Received on Sat Oct 30 1999 - 00:51:39 CDT