2008R2 Oracle.exe crashes, no details in alert log/trc files

On 2008R2 Oracle.exe for 11.2.0.3 crashes, no details in alert log/trc files, System event log does have the following.
Is it possible to interpret this errorstack?
From Event log:
--> SYSTEM Event Viewer entry:
Time logged: 12/2/2013 11:09:58 AM
event logged: The OracleServiceOPERABI service terminated unexpectedly. It has done this 1 time(s).
--> APPLICATION Event Viewer entry:
Time logged: 12/2/2013 11:09:25 AM
event logged:
Faulting application name: ORACLE.EXE, version: 11.2.0.3, time stamp: 0x51d6f508
Faulting module name: ORACLE.EXE, version: 11.2.0.3, time stamp: 0x51d6f508
Exception code: 0xc0000409
Fault offset: 0x0000000006e35f42
Faulting process id: 0x1f50
Faulting application start time: 0x01cec5e27b3c9d08
Faulting application path: d:\oracle\11203db\bin\ORACLE.EXE
Faulting module path: d:\oracle\11203db\bin\ORACLE.EXE
Report Id: 1cd2d597-5b6c-11e3-9607-3640b5bdc967
Thanks.
-SteveC

"We did open a case with Oracle, but as no Oracle information to go off of, they requested we open a case with Microsoft, and here I am."
Actually, this is NOT opening a case with Microsoft. This is making a post in a technical forum. If you consider this critical, you should open an official case with Microsoft by calling their support line. They will walk you through steps
to try to pull more information from the system, because what you have posted does not give enough information other than an error occurred in Oracle.exe. If it turns out to be an issue with Oracle, you will pay for the support call. If it turns
out to be a bug with Microsoft, I don't believe they charge you. But if it is not a bug, then they would charge you.
.:|:.:|:. tim

Similar Messages

Oracle 10g Enterprise Manager console giving Alert log

Dear all
I have One HP server running Oracle 10g on Redhat Enterprise Linux 3.0 and two other systems with Oracle 9i and 8i. I have written sql query in my Oracle10g system which updates the database in 9i.
The sql statement is
CREATE MATERIALIZED VIEW ADASNAP REFRESH FAST START WITH SYSDATE NEXT SYSDATE+1 AS
SELECT * FROM ADA@WCMMISLINK;
CREATE MATERIALIZED VIEW BGTABSNAP REFRESH FAST START WITH SYSDATE NEXT SYSDATE+1 AS
SELECT * FROM BGTAB@WCMMISLIN;
The above query is sheduled to run every day .
and i get the following Alert log in 10g enterprise manager console
Generic Alert log ORA-12012: error on auto execute of job 54
ORA-04052: error occured when looking up remote object WCMM.SYS@WCMMSERVERLINK
ORA-00604: error occured at recursive SQL level 3
ORA-12514: tns no listener
ORA-06512: AT "SYS.DBMS_SNAPSHOT" line 1883
can you guid me why the above error are occuring
the ORA-12514: tns no listener
the above error why it is occuring , then listener is running on oracle 10g server and other 8i and 9i server also and i am able to connect from oracle10g to other oracle 8i and 9i from sql plus and viceversa..
what could be the problem with tns listener
Regards
Niranjan

Hi Ugonic
Sorry both are same, it's spelling mistake it's " WCMMISLINK". Acutally, my database is getting updated but this alert log is getting generated in enterprise manager console of 10g.
The sql statement is
CREATE MATERIALIZED VIEW ADASNAP REFRESH FAST START WITH SYSDATE NEXT SYSDATE+1 AS
SELECT * FROM ADA@WCMMISLINK;
CREATE MATERIALIZED VIEW BGTABSNAP REFRESH FAST START WITH SYSDATE NEXT SYSDATE+1 AS
SELECT * FROM BGTAB@WCMMISLINK;
The above query is sheduled to run every day .
and i get the following Alert log in 10g enterprise manager console
Generic Alert log ORA-12012: error on auto execute of job 54
ORA-04052: error occured when looking up remote object WCMM.SYS@WCMMSERVERLINK
ORA-00604: error occured at recursive SQL level 3
ORA-12514: tns no listener
ORA-06512: AT "SYS.DBMS_SNAPSHOT" line 1883
can you guid me why the above error are occuring
Regards
Niranjan

At what point oracle write "Checkpoint not complete" in alert log ?

DB version: 10.2.0.4/RHEL 5.8
During a batch run, we encountered lots of 'Checkpoint not complete' errors in alert log.
Later we discovered that ORLs were sized only 50mb and this DB had only 3 redo log group. Since this is the potential cause, we are going create at least 10 Redo log groups and increase Redo log size to 500MB.
But , I want to know what exactly causes oracle to write "Checkpoint not complete" in alert log ?
For the purpose of this discussion, I am assuming we have only 1 ORL per redo log group. Is my below assumption correct ?
ORL1
|----------------> ORL1 file got full, so, LGWR starts writing to ORL2 file. Checkpoint occurs at log switch
|                    DBWR writes modified blocks associated with the redo entries in ORL1 to datafiles
|
V
ORL2
|----------------> ORL2 file got full, LGWR wants to start writing to ORL3 file. Checkpoint is initiated at log switch.
|                    But checkpoint can't be finished due to unknowN reasons
|
V
ORL3
|---------------->

Your assumption is only partly right.
I would illustrate it like
ORL1
|
|----------------> ORL1 file got full, so, LGWR starts writing to ORL2 file. Checkpoint occurs at log switch
|                    DBWR starts writing modified blocks associated with the redo entries in ORL1 to datafiles
|
V
ORL2
|----------------> ORL2 file got full, LGWR starts writing to ORL3 file.
|                    Checkpoint for ORL2 is initiated at log switch.
|
V
ORL3
|
|----------------> ORL3 file (the last member) also got full very quickly . LGWR wants to start the 'new cycle' by
                    writing (Reusing) to ORL1. But the checkpoint intiated by the log switch of ORL1 from the previous cycle is
                    not complete yet !! .
Basically you get this error when LGWR attempts to reuse an online redo log file (ORL1 in the above example) and finds that it cannot.
This is because the remaining ORL files (ORL2 and ORL3) got fully written before DB writer finished checkpointing the modified blocks associated with ORL1 yet.
Until the checkpoint of ORL1 is complete, the DB effectively hangs and user sessions have to wait until LGWR can safely reuse ORL1
Yes a larger redo log size of 10 groups can help. But make sure the I/O subsytem where ORLs are stored has no latency issues.

Alert log/trace file

alert log file is generated daily or it will be updated daily?
is trace file part of alert log file or its a seperate file?
how trace file differ's from alert log file.?
thankx....

>>
alert log file is generated daily or it will be updated daily?
>
When oralce starts every first time, oracle does create a alert log file and whenever oracle wants to update the alertlog file, it updates the existing one and in case of missing alert log, it re-create the alert log and updates it.
>>
is trace file part of alert log file or its a seperate file?
>>
No.
>>
how trace file differ's from alert log file.?
>>
alert log contains database activities list carried out in the related database.
trace file can be generated due to number of reasons, like, hardware problems, due to oracle internal errors, user errors, whenever you trace a session and etc.
Jaffar

Questions regarding Alert log & Control file

Hello,
This is my first post to this forum. I'm new at administrating a database 11.2.0.3. I have couple of questions regarding Oracle DB.
1)Which one is preferred method among the two?
Checking alert log fie manually or automating a shell script for checking alert log file.
2) Does setting CONTROL_FILE_RECORD_KEEP_TIME parameter to zero make the database unrecoverable, if RMAN recovery catalog is not used?
Any help will be highly appreciated. Thanks in advance.
Regards

1)Which one is preferred method among the two?
Checking alert log fie manually or automating a shell script for checking alert log file.
That depends on your comfortability - But checking alert log is good.
2) Does setting CONTROL_FILE_RECORD_KEEP_TIME parameter to zero make the database unrecoverable, if RMAN recovery catalog is not used?
Yes - you cannot recover your database if it set zero and doesn't have recovery catalog.

Oracle Error with no Error in Alert log

Hi,
I am getting an error that I am viewing via OEM on a delete statement. The error is as follows:
The EXPLAIN PLAN cannot be viewed because the cached plan for this cursor is malformed
The sql that is running against it is:
delete from job_depot_object job_depot_object where job_id = ( select job.job_id from job_option_value jov, job job where jov.option_id = 236 and option_value = 'Y' and job.object_type_id = 30 and jov.job_id = job.job_id and jov.job_version_id = job.job_version_id and job.job_id = job_depot_object.job_id and job.job_version_id = job_depot_object.job_version_id group by job.job_id ) and depot_object_version_id = ( select job.job_version_id from job_option_value jov, job job, job_result jre, job_depot_object jdo where jov.option_id = 236 and option_value = 'Y' and job.object_type_id = 30 and jov.job_id = job.job_id and jov.job_version_id = job.job_version_id and job.job_id = job_depot_object.job_id and job.job_version_id = job_depot_object.job_version_id group by job.job_version_id )
Any thoughts to what is going wrong?

Are you able to get the explain plan of the same statement directly at the sql*plus prompt?
This could be related to the bug:
Bug 3043373 : Abstract: MALFORMED EXECUTION PLAN IN V$SQL_PLAN WITH FILTER OPERATIONS
There is a patch available on top of the 9.2.0.6 version. The bug has been filed on the base data dictionary views in the database. To confirm, I would suggest that you verify the problem from sql*plus first.
Jaffar

Oracle database crashing.Need help.

Hi
We have an oracle 11.1.0.7.0 database running on windows 2003 R2. All of a sudden as of today the server crashed.
Trace logs are as below.
Can anyone provide any help on how to diagnose the issue.
Thanks
*** 2011-04-26 00:30:15.291
Process diagnostic dump for W000, OS id=6212
Memory (Avail/Total): Ph:1919M/3839M, Ph+PgF:2554M/4446M, VA:1260M/2047M
CPU Load: 61%
Stack:
------------------- Call Stack Trace ---------------------
calling location entry point arg #1 arg #2 arg #3 arg #4
7C82847C 00000000 00000000 00000000 00000000 00000000
77E61C88 77E61C96 00001aa8 00001388 00000000 0f45e55c
_skgpwwait()+128                                                 00000000                                                         00001aa8 00001388 004c4b40 0bab7ca0
ksliwat()+2180                                                  skgpwwait()+0 0f45e5c8 0babb460 2f371f7c 004c4b40
kslwaitctx()+146                                                ksliwat()+0 2ea568b0 2ea568b0 000001f4 00000000
kslwait()+158                                                   kslwaitctx()+0 0f45e7bc 000001f4 0f45e7bc 06097a59
ksvrdp()+26715                                                  kslwait()+0 000001f4 0000003e 00000000 0f45fd90
opirip()+813                                                    ksvrdp()+0 00000003 0dc6e918 0dc85e78 0d6ff2dc
opidrv()+1357                                                   opirip()+0 00000032 00000004 0f45fea8 00000000
sou2o()+45                                                      opidrv()+0 00000032 00000004 0f45fea8 00000000
opimaireal()+263 _sou2o()+0                                                       0f45fe9c 00000032 00000004 0f45fea8
opimai()+92                                                     opimai_real()+0 00000003 0f45fed4 00000000 00000000
BackgroundThreadStart@4()+529                                   opimai()+0 00000003 0f45ff20 89a96710 0d6f0030
77E6482C 00000000 0b1a4c18 00000000 00000000 0b1a4c18
00000000 00000000 00000000 00000000 00000000 00000000
---------------- End of Call Stack Trace -----------------
Call stack acquisition performance stats:
setup time (lock acquis., memory alloc.): 0 ms
frame get time (time the target proc was suspended): 0 ms
symbol translation time: 0 ms
total time: 0 ms
Process diagnostic dump actual duration=0.109000 sec
(max dump time=30.000000 sec)
*** 2011-04-26 00:30:15.400
Waited for process W000 to initialize for 107276 seconds
*** 2011-04-26 00:50:21.400
Process diagnostic dump for W000, OS id=11304
Memory (Avail/Total): Ph:1923M/3839M, Ph+PgF:2563M/4446M, VA:1268M/2047M
CPU Load: 43%
Stack:
------------------- Call Stack Trace ---------------------
calling location entry point arg #1 arg #2 arg #3 arg #4
7C82847C 00000000 00000000 00000000 00000000 00000000
77E61C88 77E61C96 000019b0 00001388 00000000 0d85e55c
_skgpwwait()+128                                                 00000000                                                         000019b0 00001388 004c4b40 0bab7ca0
ksliwat()+2180                                                  skgpwwait()+0 0d85e5c8 0babb460 2f371494 004c4b40
kslwaitctx()+146                                                ksliwat()+0 2ea26d20 2ea26d20 000001f4 00000000
kslwait()+158                                                   kslwaitctx()+0 0d85e7bc 000001f4 0d85e7bc 06097a59
ksvrdp()+26715                                                  kslwait()+0 000001f4 0000003e 00000000 0d85fd90
opirip()+813                                                    ksvrdp()+0 00000003 0c8ee914 0c935e6c 0c79f2d8
opidrv()+1357                                                   opirip()+0 00000032 00000004 0d85fea8 00000000
sou2o()+45                                                      opidrv()+0 00000032 00000004 0d85fea8 00000000
opimaireal()+263 _sou2o()+0                                                       0d85fe9c 00000032 00000004 0d85fea8
opimai()+92                                                     opimai_real()+0 00000003 0d85fed4 00000000 00000000
BackgroundThreadStart@4()+529                                   opimai()+0 00000003 0d85ff20 89b057d0 0c790030
77E6482C 00000000 0b18e3c8 00000000 00000000 0b18e3c8
00000000 00000000 00000000 00000000 00000000 00000000
---------------- End of Call Stack Trace -----------------
Call stack acquisition performance stats:
setup time (lock acquis., memory alloc.): 0 ms
frame get time (time the target proc was suspended): 0 ms
symbol translation time: 0 ms
total time: 0 ms
Process diagnostic dump actual duration=0.109000 sec
(max dump time=30.000000 sec)
*** 2011-04-26 00:50:21.509
Waited for process W000 to initialize for 110881 seconds
*** 2011-04-26 01:50:27.697
Process diagnostic dump for W000, OS id=10832
Memory (Avail/Total): Ph:1926M/3839M, Ph+PgF:2566M/4446M, VA:1266M/2047M
CPU Load: 11%
Stack:
------------------- Call Stack Trace ---------------------
calling location entry point arg #1 arg #2 arg #3 arg #4
7C82847C 00000000 00000000 00000000 00000000 00000000
77E61C88 77E61C96 000018fc 00001388 00000000 0dd0e55c
_skgpwwait()+128                                                 00000000                                                         000018fc 00001388 004c4b40 0bab7ca0
ksliwat()+2180                                                  skgpwwait()+0 0dd0e5c8 0babb460 2f36f3dc 004c4b40
kslwaitctx()+146                                                ksliwat()+0 2ea26d20 2ea26d20 000001f4 00000000
kslwait()+158                                                   kslwaitctx()+0 0dd0e7bc 000001f4 0dd0e7bc 06097a59
ksvrdp()+26715                                                  kslwait()+0 000001f4 0000003e 00000000 0dd0fd90
opirip()+813                                                    ksvrdp()+0 00000003 0c54e918 0c565e78 09a2f2dc
opidrv()+1357                                                   opirip()+0 00000032 00000004 0dd0fea8 00000000
sou2o()+45                                                      opidrv()+0 00000032 00000004 0dd0fea8 00000000
opimaireal()+263 _sou2o()+0                                                       0dd0fe9c 00000032 00000004 0dd0fea8
opimai()+92                                                     opimai_real()+0 00000003 0dd0fed4 00000000 00000000
BackgroundThreadStart@4()+529                                   opimai()+0 00000003 0dd0ff20 89c36268 09a20030
77E6482C 00000000 0b187fb8 00000000 00000000 0b187fb8
00000000 00000000 00000000 00000000 00000000 00000000
---------------- End of Call Stack Trace -----------------
Call stack acquisition performance stats:
setup time (lock acquis., memory alloc.): 0 ms
frame get time (time the target proc was suspended): 0 ms
symbol translation time: 0 ms
total time: 0 ms
Process diagnostic dump actual duration=0.109000 sec
(max dump time=30.000000 sec)
*** 2011-04-26 01:50:27.806
Waited for process W000 to initialize for 112681 seconds
*** 2011-04-26 02:20:27.884
Process diagnostic dump for W000, OS id=9720
Memory (Avail/Total): Ph:1919M/3839M, Ph+PgF:2557M/4446M, VA:1266M/2047M
CPU Load: 43%
Stack:
------------------- Call Stack Trace ---------------------
calling location entry point arg #1 arg #2 arg #3 arg #4
7C82847C 00000000 00000000 00000000 00000000 00000000
77E61C88 77E61C96 00001a00 00001388 00000000 0dd0e55c
_skgpwwait()+128                                                 00000000                                                         00001a00 00001388 004c4b40 0bab7ca0
ksliwat()+2180                                                  skgpwwait()+0 0dd0e5c8 0babb460 2f36f3dc 004c4b40
kslwaitctx()+146                                                ksliwat()+0 2ea26d20 2ea26d20 000001f4 00000000
kslwait()+158                                                   kslwaitctx()+0 0dd0e7bc 000001f4 0dd0e7bc 06097a59
ksvrdp()+26715                                                  kslwait()+0 000001f4 0000003e 00000000 0dd0fd90
opirip()+813                                                    ksvrdp()+0 00000003 0c52e918 0c545e78 09a2f2dc
opidrv()+1357                                                   opirip()+0 00000032 00000004 0dd0fea8 00000000
sou2o()+45                                                      opidrv()+0 00000032 00000004 0dd0fea8 00000000
opimaireal()+263 _sou2o()+0                                                       0dd0fe9c 00000032 00000004 0dd0fea8
opimai()+92                                                     opimai_real()+0 00000003 0dd0fed4 00000000 00000000
BackgroundThreadStart@4()+529                                   opimai()+0 00000003 0dd0ff20 80828c73 09a20030
77E6482C 00000000 0b187f70 00000000 00000000 0b187f70
00000000 00000000 00000000 00000000 00000000 00000000
---------------- End of Call Stack Trace -----------------
Call stack acquisition performance stats:
setup time (lock acquis., memory alloc.): 0 ms
frame get time (time the target proc was suspended): 0 ms
symbol translation time: 0 ms
total time: 0 ms
Process diagnostic dump actual duration=0.110000 sec
(max dump time=30.000000 sec)
*** 2011-04-26 02:20:27.994
Waited for process W000 to initialize for 115689 seconds
*** 2011-04-26 03:10:36.994
Process diagnostic dump for W000, OS id=10068
*** 2011-04-26 03:10:37.103
Memory (Avail/Total): Ph:1933M/3839M, Ph+PgF:2575M/4446M, VA:1267M/2047M
CPU Load: 32%
Stack:
------------------- Call Stack Trace ---------------------
calling location entry point arg #1 arg #2 arg #3 arg #4
7C82847C 00000000 00000000 00000000 00000000 00000000
77E61C88 77E61C96 00001a00 00001388 00000000 0dd0e55c
_skgpwwait()+128                                                 00000000                                                         00001a00 00001388 004c4b40 0d1dceb8
ksliwat()+2180                                                  skgpwwait()+0 0dd0e5c8 0d1e0678 2f36f3dc 004c4b40
kslwaitctx()+146                                                ksliwat()+0 2ea26d20 2ea26d20 000001f4 00000000
kslwait()+158                                                   kslwaitctx()+0 0dd0e7bc 000001f4 0dd0e7bc 06097a59
ksvrdp()+26715                                                  kslwait()+0 000001f4 0000003e 00000000 0dd0fd90
opirip()+813                                                    ksvrdp()+0 00000003 0c52e918 0c545e78 09a2f2dc
opidrv()+1357                                                   opirip()+0 00000032 00000004 0dd0fea8 00000000
sou2o()+45                                                      opidrv()+0 00000032 00000004 0dd0fea8 00000000
opimaireal()+263 _sou2o()+0                                                       0dd0fe9c 00000032 00000004 0dd0fea8
opimai()+92                                                     opimai_real()+0 00000003 0dd0fed4 00000000 00000000
BackgroundThreadStart@4()+529                                   opimai()+0 00000003 0dd0ff20 8a7c5db0 09a20030
77E6482C 00000000 0b1a9bc0 00000000 00000000 0b1a9bc0
00000000 00000000 00000000 00000000 00000000 00000000
---------------- End of Call Stack Trace -----------------
Call stack acquisition performance stats:
setup time (lock acquis., memory alloc.): 0 ms
frame get time (time the target proc was suspended): 0 ms
symbol translation time: 0 ms
total time: 0 ms
Process diagnostic dump actual duration=0.109000 sec
(max dump time=30.000000 sec)
*** 2011-04-26 03:10:37.103
error 2103 detected in background process
OPIRIP: Uncaught error 447. Error stack:
*** 2011-04-26 03:35:37.103
ORA-00447: fatal error in background process
ORA-02103: PCC: inconsistent cursor cache (out-of-range cuc ref)
Edited by: user8952784 on Apr 25, 2011 12:53 PM

Hello,
What is MOS?
MOS stand for My Oracle Support (formelly called Metalink). You'll find below their link:
https://support.oracle.com/
You'll need the Customer Support Identifier ( CSI ) to get an account.
As soon as, you can logon to MOS, then open a Service Request and send them the Alert log, trace file, ... and if possible an Incident Package so that they can diagnose the error you got.
As you are in 11.1 you can generate an Incident Package with the help of the Automatic Diagnostic Repository ( ADR ). You may follow the procedure below to create the Incident Package and manage the call with MOS:
http://download.oracle.com/docs/cd/E11882_01/server.112/e17120/diag002.htm#CHDJDBCH
Hope this help.
Best regards,
Jean-Valentin

Oracle database crashes frequently

Dear all,
One of my oracle databases is crashing with a word being written to the alert.log. What I see in the log is a log switch information. Is there a way of enhancing log information. (something similar to 10046 trace with different trace levels 4,8,12)
Windows EE 2003 - 64-bit
Oracle 10g Release 2 (10.2.0.4) 64-bit
Memory - 4GB
CPU - 1 Quadcore 2.33GHz
Avg CPU utilization - 20%
How do I find the cause and make Oracle write more information in the alert log?
Thanks for your tips & help.
Regards

Oracle Lover3 wrote:
OS remains up, its only Oracle that crashes.
After starting the Windows service for database, when I try to start Oracle, it comes out saying "End of file communication". I have to restart the server to get rid of this.And you call it Oracle crashes?
Something wrong in your environment.
Pls, check for Event log for any related error messages.

Job number from alert log file to information

Hello!
I have a question about job numbers in alert log file. Today one of our Oracle 10g R2 [10.2.0.4] RAC nodes crashed. After examining alert log file for one of the nodes I saw a lot of messages like:
Tue Jul 26 11:52:43 2011
Errors in file /u01/app/oracle/admin/zeme/bdump/zeme2_j002_28952.trc:
ORA-12012: error on auto execute of job *20627358*
ORA-12705: Cannot access NLS data files or invalid environment specified
Tue Jul 26 11:52:43 2011
Errors in file /u01/app/oracle/admin/zeme/bdump/zeme2_j001_11018.trc:
ORA-12012: error on auto execute of job *20627357*
ORA-12705: Cannot access NLS data files or invalid environment specified
Tue Jul 26 11:52:43 2011
Errors in file /u01/app/oracle/admin/zeme/bdump/zeme2_j000_9684.trc:
ORA-12012: error on auto execute of job *20627342*
ORA-12705: Cannot access NLS data files or invalid environment specified
After examining trc files I have found no further information about error except session ids.
My question is: how to find what job caused these messages to appear in alert log file.
How do I map number in alert log file to some "real" information (owner, statement executed, schedule)?
Marx.

Sorry for the delay
Try this to find the job :
select job, what from dba_jobs ;
How do I find NLS_LANG version?SQL> show parameter NLS_LANG
Do you mean ALTER SESSION inside a job?I meant anywhere, but your question is better.
ORA-12705 - Common Reasons and How to Resolve Them [ID 158654.1]
If OS is Windows lookout for NLS_LANG=NA in the registry
Is it possible you are doing this somewhere ?
ALTER SESSION SET NLS_DATE_FORMAT = 'RRRR-MM-DD\"T\"HH24:MI:SS';NLS database settings are superseded by NLS instance settings
SELECT * from NLS_SESSION_PARAMETERS;
These are the settings used for the current SQL session.
NLS_LANG could be set in a profile for example.
NLS_LANG=_AMERICA.WE8ISO8859P1 ( correct )
NLS_LANG=AMERICA.WE8ISO8859P1 ( Incorrect )
you need to set the "_" as separator.
Windows
set NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
Unix
export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
mseberg
Edited by: mseberg on Jul 28, 2011 3:51 PM
Edited by: mseberg on Jul 29, 2011 4:05 AM

Who writes alert log file?

Hi guys ,
I have been searching for answer to this question,.............
Which process(backgroud process) writes to alert log file?

Trace files for user processes are normally in the user_dump. They are created only when tracing is requested OR when Oracle encounters an error.
The alert.log is a file that is used to continously display the status of the database as it changes with important events (e.g. archival of log, alter system commands, ora-1555 errors, indexes unusable, datafile space allocation etc). Most of these are issues which affect the entire instance/database. However, where a sever error is encountered in a user process, Oracle writes a trace file in user_dump_dest for that error and a message indicating the error and the name of the trace file to the alert.log.
Similarly, the background processes may also be writing to their own trace files to indcate status /tracing.
The level of detail being logged can vary by version and by setting specific database events (if specified by Oracle Support) in the instance.
See http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/manproc.htm#sthref729
Hemant K Chitale

Question about the Initialization Parameters Information in the Alert.log

Hi, All -
What is the correct answer for the following question.
Specifically, what information does Oracle provide you with in the alert.log regarding initialization parameters?
a. Values of all initialization parameters at startup
b. Values of initialization parameters modified since last startup
c. Values of initialization parameters with non-default values
d. Only values of initialization parameters that cannot be modified dynamically.
I think the answer should be B, but I would like to confirm.

The answer is C
http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/process.htm#sthref1633
The alert log is a special trace file. The alert log of a database is a chronological log of messages and errors, and includes the following items:
All internal errors (ORA-600), block corruption errors (ORA-1578), and deadlock errors (ORA-60) that occur
Administrative operations, such as CREATE, ALTER, and DROP statements and STARTUP, SHUTDOWN, and ARCHIVELOG statements
Messages and errors relating to the functions of shared server and dispatcher processes
Errors occurring during the automatic refresh of a materialized view
The values of all initialization parameters that had nondefault values at the time the database and instance start
Kamran Agayev A. (10g OCP)
http://kamranagayev.wordpress.com

ARC0: media recovery disabled in Alert.log? What is ist?

Hello this is Standing in my Alert.log;
Dump file c:\timDB\oracle\dump\bgdump\tim1ALRT.LOG
Tue Jun 21 13:08:18 2005
ORACLE V8.1.7.0.0 - Production vsnsta=0
vsnsql=e vsnxtr=3
Windows NT Version 4.0 Service Pack 6, CPU type 586
Tue Jun 21 13:08:18 2005
Thread 1 advanced to log sequence 5496
Current log# 4 seq# 5496 mem# 0: C:\TIMDB\ORA_BACKUP\TIM\ORA_REDO\TIM1LOG4.RDO
Current log# 4 seq# 5496 mem# 1: C:\TIMDB\ORA_DB\TIM\ORA_REDO2\TIM1LOG4.RDO
Tue Jun 21 13:08:18 2005
ARC0: media recovery disabled
What is Wrong wiht my Oracle?

This problem occurs because an archive process has been started but it has nothing to do because the database is in NOARCHIVELOG mode. This could be rather serious if it is expected that the database runs in ARCHIVELOG mode.
This happens when only log_archive_start = true. Which means an archive process is started on database startup, but because the database is not actually in archivelog mode, the archiver reports the above message.
To verify use v$database view. The LOG_MODE is NOARCHIVELOG even though log_archive_start = true.
Put the database in archivelog mode:
1.1. Mount the database.
1.2. Issue the command: ALTER DATABASE ARCHIVELOG;
Jaffar

ORA.00600 Error in alert log file

Hi all,
I'm using Enterprise Linux Red hat 5 OS and Oracle version 10.2.0.1.0
I checked alert log file, yesterday i got this error,
* Errors in file /opt/oracle/admin/ssharp/udump/ssharp_ora_11162.trc:
ORA-00600: internal error code, arguments: [kksfbc-reparse-infinite-loop], [0xB7F8F6B4], [], [], [], [], [], []
Fri Mar 11 19:44:51 2011
Memory Notification: Library Cache Object loaded into SGA
Heap size 3784K exceeds notification threshold (2048K) *
how to solve this issue?
thanks in advance

Hello,
ORA-00600: internal error code, arguments: [kksfbc-reparse-infinite-loop], [0xB7F8F6B4], [], [], [], [], [], []For this kind of error you should open a Service Request to My Oracle Support and, send them all the information you can (Alert log, trace files, ...).
More over, as you are in *10.2.0.1*, you may apply the latest patchset to the Database (10.2.0.4 / 10.2.0.5). Sometime, ORA-00600 may be due to a Bug. So, perhaps, by chance, applying a Patch set can help to solve this kind of issue.
Anyway, first of all, contact the Support.
Hope this help.
Best regards,
Jean-Valentin

Managing Alert log files : Best practices?

DB Version : 10.2.0.4
Several of our DBs' alert logs have become quite large. I know that oracle will create a brand new alert log file if i delete the existing one.
But i just want to know how you guys manage your alert log files. Do you guys archive (move to a different directory) and recreate a brand new alert log. Just want to know if there any best practices i could follow.

ScottsTiger wrote:
DB Version : 10.2.0.4
Several of our DBs' alert logs have become quite large. I know that oracle will create a brand new alert log file if i delete the existing one.
But i just want to know how you guys manage your alert log files. Do you guys archive (move to a different directory) and recreate a brand new alert log. Just want to know if there any best practices i could follow.Every end of day (or every periodic time) archive your alert.log and move other directory then remove alert.log.Next time Database instance will automatically create own alert.log

Oracle client crashed Windows NT java.exe DrWatson

hi all,
I got this crash dump information from DrWatson Log in the NT machine where my application server was running. We were load testing with arround 90 users to test out the application and we came accross this problem.
we are running on NT machine using oracle Client
connection though Oracle ODBC driver.
using OCI interface.
there are no sessions cached in oracle server.
there is also no memory leak in the system
can some one give idea isolating the problem and possible information on how to avoid one such bug.
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
06e0f740 77f67586 00c8b580 6064f221 00c8b580 60a27460 ntdll!NtWaitForSingleObject
06e0f758 60b4dea2 00a3a700 60a274d4 00000000 60a27460 ntdll!RtlEnterCriticalSection
06e0f774 60a1985e 60a27460 00a3a700 60a27460 06e0f7f4 oran8!nsgblRealTerm
06e0f7c8 60a19638 00000000 00c9328c 00c8f100 00c8f8a0 oranl8!nlstdtrm
06e0f7e0 60a1997c 06e0f7f4 06e0f80c 60b11f5a 60a27460 oranl8!nlstdtrm
06e0f7ec 60b11f5a 60a27460 00c9328c 00c93240 00c8f8a0 oranl8!nlstdstp
06e0f80c 60b1223d 00c9328c 00c933e0 0733881c 0733881c oran8!nigtrm
06e0f834 604b9f66 073388c0 00000000 073387a8 0733899c oran8!nigtrm
06e0f850 604826a1 0733881c 06e0f880 6042a2e3 0733881c oraclient8!xaolog
06e0f85c 6042a2e3 0733881c 06e0f8dc 00c3de90 00c8d500 oraclient8!upidhs
06e0f880 60401364 073387a8 0733899c 00000000 01938d40 oraclient8!kpudtch
06e0f894 600010c4 073387a8 0733899c 00000000 00c3de90 oraclient8!OCIServerDetach
01938d40 00a324c0 022d6fa8 00000ca2 00000000 01938d18 ocijdbc8!<nosymbols>
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
008abd4c 60a13d26 00000000 60a0ba90 60a0bac0 0724a7e8 oranl8!nlhthdel
008abd6c 60a1171c 008abdf8 0724a7e8 64707714 00c933d0 oranl8!nlpassp
008abd9c 60a115c7 008abdf8 0724a7e8 64707714 0000000b oranl8!nlpagsp
008abdcc 64701d62 008abdf8 0724a7e8 64707714 0000000b oranl8!nlpagbp
008abe48 60b5f6f2 00000001 008ac3c4 0732b48c 0732b4a8 orantcp8!<nosymbols>
008ac28c 60b407fc 00c92910 00000001 008ac3c4 0732b48c oran8!ntconn
008ac39c 60b3f99a 00c92508 00000001 008ac3c4 008ad20c oran8!nsopen
008ac5b4 60b3f1f4 00c9253c 00c92508 00c92528 008ad2a8 oran8!nscall
008ac7b8 60b157a0 00c92610 00c9253c 008ad2f0 008ad2a8 oran8!nscall
008ad338 60b61c7c 008ad378 000000c2 60b9ebf0 00001803 oran8!niotns
008af4b4 60429b1e 008ad378 000000c2 00001803 07376df4 oran8!osncon
008af4e4 604b4695 00c2c8e0 00000016 00000000 00001803 oraclient8!kpudbcx
008af6d8 604b9ece 00000000 00c2c8e0 00000016 00000000 oraclient8!xaolog
008af6fc 604823a3 073594dc 00c2c8e0 00000016 00000000 oraclient8!xaolog
008af720 60429f64 073594dc 00c2c8e0 00000016 00000000 oraclient8!upiah0
008af764 60401340 07359468 0735965c 00c2c8e0 00000016 oraclient8!kpuatch
008af788 60001261 07359468 0735965c 00c2c8e0 00000016 oraclient8!OCIServerAttach
00c2a3cc 00000000 00000000 00000001 00c2c9a0 00000000 ocijdbc8!<nosymbols>
073593c4 00000300 07353b80 07353b80 00000000 00000000 java!<nosymbols>
I appreciate your response and thankingyou in advance

Hi Ramesh,
Have u find any solution to this problem.I am also facing the same problem.
Regards
Abhishek

2008R2 Oracle.exe crashes, no details in alert log/trc files

Similar Messages

Maybe you are looking for