Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> AW: RE: How to find out what caused job to fail?
Roland,
you can read the alert log file with vi (or notepad if you are on windows). It can be found in background_dump_dest (look in the init.ora for it). The naming convention is alert_<SID>.log. Oracle writes lots of information about what is going on in the database (e.g. tablespace modifications, log switches and tons more) into that file.
Trace files are written to background_dump_dest (for background processes), user_dump_dest (for user processes) or core_dump_dest (Oracle core dumps). All files are plain text files.
hth,
Helmut
> -----Ursprüngliche Nachricht-----
> Von: Roland.Skoldblom_at_ica.se [mailto:Roland.Skoldblom_at_ica.se]
> Gesendet: Montag, 4. Februar 2002 10:36
> An: Multiple recipients of list ORACLE-L
> Betreff: Ang: RE: How to find out what caused job to fail?
>
>
>
> But how do I use the alert log and where canI find the trace file?
>
>
> Roland
>
>
>
>
> yen-wee.tan_at_amd.com_at_fatcity.com den 2002-02-04 01:05 PST
>
> Sänd svar till ORACLE-L_at_fatcity.com
>
> Sänt av: root_at_fatcity.com
>
>
> Till: Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com>
> Kopia:
>
> Hi, you can find the reason in alert log or trace files.
> -----Original Message----- > From: Daiminger, Helmut [mailto:Helmut.Daiminger_at_KirchGruppe.de] > Sent: Monday, February 04, 2002 4:40 PM > To: Multiple recipients of list ORACLE-L > Subject: How to find out what caused job to fail?
> Hi!
> Is there a way to find out, why a database job failed?
> This is 8.1.7 on Solaris.
> Thanks, > Helmut
> INET: Roland.Skoldblom_at_ica.se
![]() |
![]() |