Immediate kill session in alert log file

hi..
i'm using db10.2.0 ,windows 2003 server
we're having alot of "immediate kill session " in the alert log file ,what could be causing it?
the log file looks lsomething ike that
Sat Oct 11 10:55:33 2008
Thread 1 advanced to log sequence 2390
Current log# 1 seq# 2390 mem# 0: D:\ORACLE\PRODUCT\10.2.0\ORADATA\ABS\REDO01.LOG
Current log# 1 seq# 2390 mem# 1: E:\DATABASE\ABS\REDO_LOGS\REDO01B.LOG
Sat Oct 11 11:08:23 2008
Immediate Kill Session#: 196, Serial#: 96
Immediate Kill Session: sess: B7A4F764 OS pid: 2744
Sat Oct 11 11:08:27 2008
Immediate Kill Session#: 183, Serial#: 62
Immediate Kill Session: sess: B823F4D0 OS pid: 2348
Sat Oct 11 11:08:33 2008
Immediate Kill Session#: 198, Serial#: 68
Immediate Kill Session: sess: B7A50A2C OS pid: 2856
Sat Oct 11 11:08:33 2008
Immediate Kill Session#: 77, Serial#: 349
Immediate Kill Session: sess: B8201168 OS pid: 5704
Sat Oct 11 11:08:34 2008
Immediate Kill Session#: 156, Serial#: 257
Immediate Kill Session: sess: B7A37FC4 OS pid: 3428
Sat Oct 11 11:08:41 2008
Immediate Kill Session#: 92, Serial#: 104
Immediate Kill Session: sess: B7A126C4 OS pid: 3500
Sat Oct 11 11:08:45 2008
Immediate Kill Session#: 178, Serial#: 17
Immediate Kill Session: sess: B7A44E5C OS pid: 3408
Sat Oct 11 11:08:51 2008
Immediate Kill Session#: 180, Serial#: 43
Immediate Kill Session: sess: B7A46124 OS pid: 1592
Sat Oct 11 11:08:56 2008
Immediate Kill Session#: 81, Serial#: 310
Immediate Kill Session: sess: B82036F8 OS pid: 5088
Sat Oct 11 11:08:57 2008
Immediate Kill Session#: 114, Serial#: 290
Immediate Kill Session: sess: B7A1F55C OS pid: 952
Sat Oct 11 11:09:02 2008
Immediate Kill Session#: 104, Serial#: 117
Immediate Kill Session: sess: B7A19774 OS pid: 4068
Sat Oct 11 11:09:11 2008
Immediate Kill Session#: 177, Serial#: 20
Immediate Kill Session: sess: B823BC78 OS pid: 2024
Sat Oct 11 11:09:16 2008
Immediate Kill Session#: 145, Serial#: 34
Immediate Kill Session: sess: B8228FF8 OS pid: 4012
Sat Oct 11 11:09:18 2008
Immediate Kill Session#: 72, Serial#: 265
Immediate Kill Session: sess: B7A06AF4 OS pid: 5592
Sat Oct 11 11:09:28 2008
Immediate Kill Session#: 176, Serial#: 9
Immediate Kill Session: sess: B7A43B94 OS pid: 1988
Sat Oct 11 11:09:37 2008
Immediate Kill Session#: 148, Serial#: 118
Immediate Kill Session: sess: B7A334A4 OS pid: 1216
Sat Oct 11 11:09:41 2008
Immediate Kill Session#: 110, Serial#: 1190
Immediate Kill Session: sess: B7A1CFCC OS pid: 2152
Sat Oct 11 11:09:46 2008
Immediate Kill Session#: 141, Serial#: 488
Immediate Kill Session: sess: B8226A68 OS pid: 5460
Sat Oct 11 11:09:51 2008
Immediate Kill Session#: 130, Serial#: 96
Immediate Kill Session: sess: B7A28B9C OS pid: 1312
Sat Oct 11 11:10:48 2008
Immediate Kill Session#: 101, Serial#: 1592
Immediate Kill Session: sess: B820F2C8 OS pid: 5936
Sat Oct 11 11:10:57 2008
Immediate Kill Session#: 170, Serial#: 5
Immediate Kill Session: sess: B7A4033C OS pid: 3356
Sat Oct 11 11:11:05 2008
Immediate Kill Session#: 138, Serial#: 46
Immediate Kill Session: sess: B7A2D6BC OS pid: 3156
Sat Oct 11 11:11:06 2008
Immediate Kill Session#: 111, Serial#: 1143
Immediate Kill Session: sess: B82150B0 OS pid: 5056
Sat Oct 11 11:11:09 2008
Immediate Kill Session#: 132, Serial#: 228
Immediate Kill Session: sess: B7A29E64 OS pid: 1628
Sat Oct 11 11:11:10 2008
Immediate Kill Session#: 150, Serial#: 560
Immediate Kill Session: sess: B7A3476C OS pid: 2568
Sat Oct 11 11:11:12 2008
Immediate Kill Session#: 155, Serial#: 165
Immediate Kill Session: sess: B822EDE0 OS pid: 3484
Sat Oct 11 11:11:18 2008
Immediate Kill Session#: 165, Serial#: 90
Immediate Kill Session: sess: B8234BC8 OS pid: 1968
Sat Oct 11 11:11:36 2008
Immediate Kill Session#: 116, Serial#: 221
Immediate Kill Session: sess: B7A20824 OS pid: 4848
Sat Oct 11 11:11:37 2008
Immediate Kill Session#: 192, Serial#: 54
Immediate Kill Session: sess: B7A4D1D4 OS pid: 3972
Sat Oct 11 11:11:45 2008
Immediate Kill Session#: 164, Serial#: 98
Immediate Kill Session: sess: B7A3CAE4 OS pid: 3888
Sat Oct 11 11:11:45 2008
Immediate Kill Session#: 121, Serial#: 17
Immediate Kill Session: sess: B821AE98 OS pid: 1200
Sat Oct 11 11:11:50 2008
Immediate Kill Session#: 109, Serial#: 330
Immediate Kill Session: sess: B8213DE8 OS pid: 3456
Sat Oct 11 11:11:56 2008
Immediate Kill Session#: 181, Serial#: 68
Immediate Kill Session: sess: B823E208 OS pid: 3324
Sat Oct 11 11:12:17 2008
Immediate Kill Session#: 214, Serial#: 85
Immediate Kill Session: sess: B7A5A06C OS pid: 2752
Sat Oct 11 11:12:20 2008
Immediate Kill Session#: 209, Serial#: 346
Immediate Kill Session: sess: B824E8F8 OS pid: 3844
Sat Oct 11 11:12:23 2008
Immediate Kill Session#: 154, Serial#: 152
Immediate Kill Session: sess: B7A36CFC OS pid: 3400
Sat Oct 11 11:12:26 2008
Immediate Kill Session#: 147, Serial#: 86
Immediate Kill Session: sess: B822A2C0 OS pid: 2536
Sat Oct 11 11:12:34 2008
Immediate Kill Session#: 79, Serial#: 1504
Immediate Kill Session: sess: B8202430 OS pid: 4052
Sat Oct 11 11:12:47 2008
Immediate Kill Session#: 189, Serial#: 234
Immediate Kill Session: sess: B8242D28 OS pid: 2128
Sat Oct 11 11:13:10 2008
Immediate Kill Session#: 118, Serial#: 95
Immediate Kill Session: sess: B7A21AEC OS pid: 3480
Sat Oct 11 11:13:13 2008
Immediate Kill Session#: 94, Serial#: 16
Immediate Kill Session: sess: B7A1398C OS pid: 2140
Sat Oct 11 11:14:24 2008
ALTER SYSTEM SET service_names='aba10g' SCOPE=MEMORY SID='abs';
Sat Oct 11 11:14:59 2008
Immediate Kill Session#: 97, Serial#: 1197
Immediate Kill Session: sess: B820CD38 OS pid: 4164
Sat Oct 11 11:15:07 2008
Immediate Kill Session#: 163, Serial#: 237
Immediate Kill Session: sess: B8233900 OS pid: 3224
Sat Oct 11 11:15:19 2008
Immediate Kill Session#: 140, Serial#: 230
Immediate Kill Session: sess: B7A2E984 OS pid: 1584
Sat Oct 11 11:15:41 2008
Thread 1 advanced to log sequence 2391
Current log# 4 seq# 2391 mem# 0: D:\ORACLE\PRODUCT\10.2.0\ORADATA\ABS\REDO4.LOG
Current log# 4 seq# 2391 mem# 1: E:\DATABASE\ABS\REDO_LOGS\REDO04B.LOG
Sat Oct 11 11:15:51 2008
Immediate Kill Session#: 88, Serial#: 541
Immediate Kill Session: sess: B7A10134 OS pid: 4676
Sat Oct 11 11:16:09 2008
Immediate Kill Session#: 78, Serial#: 358
Immediate Kill Session: sess: B7A0A34C OS pid: 6056

2011-06-27 02:27:12.215: [    RACG][261091968] [24623][261091968][ora.rac.rac1.inst]: clsrcqryapi: crs_qstat error
2011-06-27 02:27:12.215: [    RACG][261091968] [24623][261091968][ora.rac.rac1.inst]: clsrcpullupvip: Failed to get status of ora.srv01-025.vip
2011-06-27 02:27:12.810: [    RACG][282473088] [24623][282473088][ora.rac.rac1.inst]: clscconnect failed with clsc ret 9
2011-06-27 02:27:12.811: [    RACG][282473088] [24623][282473088][ora.rac.rac1.inst]: error connecting to CRSD at [(ADDRESS=(PROTOCOL=IPC)(KEY=CRSD_UI_SOCKET))] clsccon 184
2011-06-27 02:27:12.811: [    RACG][261091968] [24623][261091968][ora.rac.rac1.inst]: clsrcqryapi: crs_qstat error
2011-06-27 02:27:13.237: [    RACG][261091968] [24623][261091968][ora.rac.rac_srv.cs]: clsrcqryapi: crs_qstat error
2011-06-27 02:27:13.625: [    RACG][261091968] [24623][261091968][ora.rac.rac_srv.rac1.srv]: clsrcqryapi: crs_qstat error
2011-06-27 02:27:13.625: [    RACG][261091968] [24623][261091968][ora.rac.rac_srv.rac1.srv]: clsrcsmfread: cannot get status of resource 'ora.rac.rac_srv.rac1.srv'
2011-06-27 02:27:15.829: [  OCRMSG][261091968]prom_rpc: CLSC send failure..ret code 11
2011-06-27 02:27:15.829: [  OCRMSG][261091968]prom_rpc: possible OCR retry scenario
2011-06-27 02:27:15.881: [  OCRAPI][261091968]procr_open: Node Failure. Attempting retry #0
2011-06-27 02:27:16.096: [    RACG][261091968] [24623][261091968][ora.rac.rac_srv.rac1.srv]: clsrcqryapi: crs_qstat error
Edited by: user13481820 on Jun 26, 2011 10:53 PM

Similar Messages

  • Regarding error in alert -- immediate kill session

    Dear Gurus
    os - linux4.5
    oracle -10.2.0.4
    i have an error in my alert log file for node 2 as below(i m posting here main text what i found)
    Immediate Kill Session#: 73, Serial#: 39455
    Immediate Kill Session: sess: 0x402337f0ca0 OS pid: 17058
    Immediate Kill Session#: 74, Serial#: 38391
    Immediate Kill Session: sess: 0x402337f2208 OS pid: 25083
    Immediate Kill Session#: 76, Serial#: 6725
    Immediate Kill Session: sess: 0x40233833af0 OS pid: 17018
    Immediate Kill Session#: 128, Serial#: 54171
    Immediate Kill Session: sess: 0x4023383a5f8 OS pid: 25861
    Sun Aug 14 14:25:31 2011
    Process OS id : 25861 alive after kill
    Errors in file /u01/app/oracle/admin/prod/udump/prod_ora_8179.trc
    Immediate Kill Session: sess: 0x40233a3c1f8 OS pid: 28900
    Immediate Kill Session#: 534, Serial#: 12002
    Immediate Kill Session: sess: 0x40233a598e8 OS pid: 16102
    Sun Aug 14 14:35:30 2011
    ALTER SYSTEM SET service_names='prod' SCOPE=MEMORY SID='prod2';
    Sun Aug 14 21:00:50 2011
    Thread 2 advanced to log sequence 3684 (LGWR switch)
    Current log# 3 seq# 3684 mem# 0: +RLOG_GROUP/prod/redo03.log
    Mon Aug 15 18:56:50 2011
    Thread 2 advanced to log sequence 3685 (LGWR switch)
    trace file text is as
    post info) last post received: 109 0 4
    last post received-location: kslpsr
    last process to post me: 40233693738 1 6
    last post sent: 0 0 24
    last post sent-location: ksasnd
    last process posted by me: 40233693738 1 6
    (latch info) wait_event=0 bits=0
    Process Group: DEFAULT, pseudo proc: 0x40233786f80
    O/S info: user: oracle, term: UNKNOWN, ospid: 21196 (DEAD)
    OSD pid info: Unix process pid: 21196, image: oracle@dbrac2
    Short stack dump: unable to dump stack due to error 72
    Dump of memory from 0x00000402336539E0 to 0x0000040233653BE8
    402336539E0 00000010 00000000 1DC35CE0 00000402 [.........\......]
    402336539F0 00000010 000313A7 1DC60660 00000402 [........`.......]
    40233653A00 00000003 000313A7 312D7370 00000402 [........ps-1....]
    40233653AE0 00000007 000313A7 00000000 00000000 [................]
    40233653AF0 00000000 00000000 00000000 00000000 [................]
    Repeat 14 times
    40233653BE0 00000000 00000000
    SO: 0x402336a9318, type: 2, owner: (nil), flag: INIT/-/-/0x00
    (process) Oracle pid=55, calls cur/top: (nil)/0x401fe14f1c8, flag: (0) -
    int error: 0, call error: 0, sess error: 0, txn error 0
    (post info) last post received: 109 0 4
    last post received-location: kslpsr
    last process to post me: 40233693738 1 6
    last post sent: 0 0 24
    last post sent-location: ksasnd
    last process posted by me: 40233693738 1 6
    (latch info) wait_event=0 bits=0
    Process Group: DEFAULT, pseudo proc: 0x40233786f80
    O/S info: user: oracle, term: UNKNOWN, ospid: 21597 (DEAD)
    OSD pid info: Unix process pid: 21597, image: oracle@dbrac2
    Short stack dump: unable to dump stack due to error 72
    Dump of memory from 0x0000040233655858 to 0x0000040233655A60
    40233655850 0000000C 00000000 [........]
    40233655860 1DD637A8 00000402 00000010 000313A7 [.7..............]
    40233655870 FE14F1C8 00000401 00000003 000313A7 [................]
    40233655880 312CC588 00000402 00000013 0003129B [..,1............]
    40233655890 33D61950 00000402 0000000B 000313A7 [P..3............]
    402336558A0 339F1338 00000402 00000004 0003129B [8..3............]
    402336558B0 28A937E8 00000402 00000007 000313A7 [.7.(............]
    402336558C0 6259D858 00000401 00000053 000313A7 [X.Yb....S.......]
    402336558D0 28A938C8 00000402 00000007 000313A7 [.8.(............]
    402336558E0 28A956B8 00000402 00000007 000313A7 [.V.(............]
    402336558F0 28A95798 00000402 00000007 000313A7 [.W.(............]
    40233655900 28A9F000 00000402 00000007 000313A7 [...(............]
    40233655910 28A9E9E0 00000402 00000007 000313A7 [...(............]
    40233655920 00000000 00000000 00000000 00000000 [................]
    Repeat 19 times
    (latch info) wait_event=0 bits=0
    Process Group: DEFAULT, pseudo proc: 0x40233786f80
    O/S info: user: oracle, term: UNKNOWN, ospid: 27060 (DEAD)
    OSD pid info: Unix process pid: 27060, image: oracle@dbrac2
    Short stack dump: unable to dump stack due to error 72
    Dump of memory from 0x0000040233653FF8 to 0x0000040233654200
    40233653FF0 0000000A 00000000 [........]
    40233654000 1DC35E78 00000402 00000010 000313A7 [x^..............]
    40233654010 1DCD4AF0 00000402 00000003 000313A7 [.J..............]
    Repeat 16 times
    please give some hint what actually is it and why
    also at the end in my alert what does it means
    ALTER SYSTEM SET service_names='prod' SCOPE=MEMORY SID='prod2'
    regards

    By any chance if you back in the alert log just a little more does an ORA-00600 error appear before the immediate kill session messages? I found a few problem reports on the Oracle support site that might be of interest if there is:
    ORA-00600 [1301] - Instance Terminated by PMON After Killing Sessions
    ORA-600 [4072] Is Possible After Killing A Session Or Cancelling a Operation [ID 1113829.1]
    Database Crash ORA-00600: [ksqcmi:res3], [], [], [], [], [], [], [] and ORA-00600: [1100], [ID 1327043.1]
    HTH -- Mark D Powell --

  • ORA-28 in alert.log file

    please help.. getting ORA-28 in alert.log file.
    Mon Feb 25 17:46:05 2013
    ORA-28 signalled during: ALTER TABLESPACE DATA_APP_199903 READ ONLY...
    Mon Feb 25 17:48:54 2013
    ALTER TABLESPACE DATA_APP_199903 READ ONLY
    please let me know if you need any other info to help me.

    Error: ORA 28
    Text: your session has been killed
    Cause: A privileged user killed the session and it is no longer logged in to the database.
    Action: Contact the database administrator.
    The administrator may be attempting to perform an operation that requires users to be logged out.
    When the database administrator announces that the database is available, log in and resume work.So, its a message only not exactly an error. It happens when you or other DBA said alter tablespace tbs read only; and at the same time privileged user killed your session. So, nothing to worry/to do, just relogin and resume work.
    Regards
    Girish Sharma

  • RMAN success, but errors in alert.log file

    My RMAN backup script runs well, but generates errors in alert.log file.
    Here is the trace file contents:
    /usr/lib/oracle/xe/app/oracle/admin/XE/udump/xe_ora_3990.trc
    Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
    ORACLE_HOME = /usr/lib/oracle/xe/app/oracle/product/10.2.0/server
    System name: Linux
    Node name: plockton
    Release: 2.6.18-128.2.1.el5
    Version: #1 SMP Wed Jul 8 11:54:54 EDT 2009
    Machine: i686
    Instance name: XE
    Redo thread mounted by this instance: 1
    Oracle process number: 26
    Unix process pid: 3990, image: oracle@plockton (TNS V1-V3)
    *** 2009-07-23 23:05:01.835
    *** ACTION NAME:(0000025 STARTED111) 2009-07-23 23:05:01.823
    *** MODULE NAME:(backup full datafile) 2009-07-23 23:05:01.823
    *** SERVICE NAME:(SYS$USERS) 2009-07-23 23:05:01.823
    *** SESSION ID:(33.154) 2009-07-23 23:05:01.823
    *** 2009-07-23 23:05:18.689
    *** ACTION NAME:(0000045 STARTED111) 2009-07-23 23:05:18.689
    *** MODULE NAME:(backup archivelog) 2009-07-23 23:05:18.689
    Does anyone know why? Thanks.
    Richard

    I'm not sure if this will answer your question or not, but I believe these messages can likely be ignored.
    I'm currently running 10.2.0.1.0 Enterprise Edition in pre-production (yes, I know I should apply the latest patchset and I plan to do so as soon as I get a development box allocated to me and can test it's impact). I see the same types of messages that you've reported with each of my regularly-scheduled backups:
    a) The alert_<$SID>.log reports that there are errors in trace files:
    Mon Aug 10 04:33:49 2009
    Starting control autobackup
    Mon Aug 10 04:33:50 2009
    Errors in file /opt/oracle/admin/blah/udump/blah_ora_32520.trc:
    Mon Aug 10 04:33:50 2009
    Errors in file /opt/oracle/admin/blah/udump/blah_ora_32520.trc:
    Mon Aug 10 04:33:50 2009
    Errors in file /opt/oracle/admin/blah/udump/blah_ora_32520.trc:
    Control autobackup written to DISK device
    handle '/backup/physical/BLAH/RMAN/cf_c-2740124895-20090810-00'
    b) The .trc files, when you look at them contain no errors - only these "informational" messages:
    *** 2009-08-10 04:33:50.781
    *** ACTION NAME:(0000105 STARTED111) 2009-08-10 04:33:50.754
    *** MODULE NAME:(backup archivelog) 2009-08-10 04:33:50.754
    *** SERVICE NAME:(SYS$USERS) 2009-08-10 04:33:50.754
    *** SESSION ID:(126.28030) 2009-08-10 04:33:50.754
    c) I've verified that LOG_ARCHIVE_TRACE is set to 0:
    SQL*Plus> show parameter log_archive_trace
    NAME TYPE VALUE
    log_archive_trace integer 0
    As best I can discern from my own experience, these should just be ignored and I trust (read: "hope") they will simply go away once the latest patchset is applied. As for you running Oracle XE, a patchset is not an option, unfortunately.
    V/R
    -Eric

  • I am geting errors in my database alert log file ora-12012 and ora 44003

    Hi all,
    I am using oracle 10g ...10.2.0.1.0 and OS is solaris 10.......
    i am geting these errors in my database alert log file last two days..i am not geting why it is coming?
    ORA-12012: error on auto execute of job 8887
    ORA-44003: invalid SQL name
    and trace file is i got i am posting here please help any one is aware about this....
    System name: SunOS
    Node name: obrmzone1
    Release: 5.10
    Version: Generic_137111-06
    Machine: sun4v
    Instance name: ------
    Redo thread mounted by this instance: 1
    Oracle process number: 144
    Unix process pid: 26874, image:--------- (J000)
    *** ACTION NAME:(AUTO_SPACE_ADVISOR_JOB) 2011-06-10 22:00:49.372
    *** MODULE NAME:(DBMS_SCHEDULER) 2011-06-10 22:00:49.372
    *** SERVICE NAME:(SYS$USERS) 2011-06-10 22:00:49.372
    *** SESSION ID:(110.7114) 2011-06-10 22:00:49.372
    *** 2011-06-10 22:00:49.372
    ORA-12012: error on auto execute of job 8887
    ORA-44003: invalid SQL name
    thank you in advance,
    Dav

    I just google with "ORA-44003: invalid SQL name" and found below link:
    http://www.oracle-base.com/articles/10g/dbms_assert_10gR2.php
    SIMPLE_SQL_NAME
    The SIMPLE_SQL_NAME function checks the input string conforms to the basic characteristics of a simple SQL name:
    The first character of the name is alphabetic.
    The name only contains alphanumeric characters or the "_", "$", "#"
    Quoted names must be enclosed by double quotes and may contain any characters, including quotes provided they are represented by two quotes in a row ("").
    The function ignores leading and trailing white spaces are ignored
    The length of the input string is not validated.

  • Urgent Database Down - alert log file

    Hi Guru's
    this is the alert log file - today morning production database went down - any one can you please let me know the problem area!
    Thread 1 advanced to log sequence 17563
    Current log# 4 seq# 17563 mem# 0: E:\ORACLE\ORADATA\PNLDB\REDO04.LOG
    Thu Jan 26 08:12:56 2006
    KCF: write/open error block=0x7f0bc online=1
    file=12 F:\ORACLE\ORADATA\PNLDB\USERS02.DBF
    error=27069 txt: 'OSD-04026: Invalid parameter passed. (OS 520380)'
    Thu Jan 26 08:12:57 2006
    Errors in file f:\oracle\admin\pnldb\udump\pnldb_ora_1420.trc:
    ORA-01115: IO error reading block from file 12 (block # 517514)
    ORA-01110: data file 12: 'F:\ORACLE\ORADATA\PNLDB\USERS02.DBF'
    ORA-27091: skgfqio: unable to queue I/O
    ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
    OSD-04026: Invalid parameter passed. (OS 517513)
    ORA-01115: IO error reading block from file 12 (block # 132287)
    ORA-01110: data file 12: 'F:\ORACLE\ORADATA\PNLDB\USERS02.DBF'
    ORA-27091: skgfqio: unable to queue I/O
    ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
    OSD-04026: Invalid parameter passed. (OS 132286)
    Thu Jan 26 08:12:57 2006
    Errors in file f:\oracle\admin\pnldb\bdump\pnldb_dbw0_956.trc:
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    ORA-01114: IO error writing block to file 12 (block # 520380)
    ORA-01110: data file 12: 'F:\ORACLE\ORADATA\PNLDB\USERS02.DBF'
    ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
    OSD-04026: Invalid parameter passed. (OS 520380)
    DBW0: terminating instance due to error 1242
    Thu Jan 26 08:12:59 2006
    Errors in file f:\oracle\admin\pnldb\udump\pnldb_ora_1420.trc:
    ORA-00603: ORACLE server session terminated by fatal error
    ORA-01115: IO error reading block from file 12 (block # 517514)
    ORA-01110: data file 12: 'F:\ORACLE\ORADATA\PNLDB\USERS02.DBF'
    ORA-27091: skgfqio: unable to queue I/O
    ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
    OSD-04026: Invalid parameter passed. (OS 517513)
    ORA-01115: IO error reading block from file 12 (block # 132287)
    ORA-01110: data file 12: 'F:\ORACLE\ORADATA\PNLDB\USERS02.DBF'
    ORA-27091: skgfqio: unable to queue I/O
    ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
    OSD-04026: Invalid parameter passed. (OS 132286)
    Thu Jan 26 08:12:59 2006
    Errors in file f:\oracle\admin\pnldb\bdump\pnldb_pmon_3804.trc:
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    Instance terminated by DBW0, pid = 956
    Thanks
    Ravi

    You are having problems on disks E\ and F\ - possibly hardware problems.
    (Hopefully these disks are not network drives. If they are, your problem might be network contention. Network mounted drives are never a good idea for databases.)
    If this is truly urgent, then I encourage you to use your Oracle Support contract to open a service request for assistance.

  • 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

  • Prevent message to go to the alert.log file

    Hi
    How can I prevent any message (for exm. SHUTDOWN IMMEDIATE) to be written to alert.log file? Is it possible?
    Thanks
    John

    Of course this can be done with some scripting, but alot of work and totaly worthless, why dont you want it to be shown in your alert log?
    if shutdown immediate present
    then cache alert log, rewrite it to new alert log without the text shutdown immediate, but as i said earlier, useless. :)

  • Will the informations  be recorded in the alert.log file? -----No.168

    will the informations about the loss of a temporary file be recorded in the alert.log file?

    Yes, because whe your database starts needs to "mount" a tablespace with temporary files (case of tablespace "TEMP"). But don't worry with a loss of this tablespace because doesn't contain nothing when database starts.

  • Ora-07445 reported in the alert log file

    Hi all,
    We are using the following platform:-
    OS: Solaris Operating System (SPARC 32-bit)
    Oracle Server - Enterprise Edition / Product Version: 9.2.0.5.0
    We encountered the following problem:-
    There is Ora-07445 reported in the alert log file.
    "ORA-07445: exception encountered: core dump [kgghash()+308] [SIGSEGV] [Address not mapped to object] [0x3222
    000] [] []reported in the database."
    These errors are signaled in more than 3 independent, unexplained, occurrences every day.
    When this error occurred while User was accessing the application system, by right the case will be shown on the system, but they were no case found.
    alert log are as below:-
    Fri Jul 27 09:12:30 2007
    Errors in file /disc3/oracle9205/RFDB/udump/rfdb_ora_27371.trc:
    ORA-07445: exception encountered: core dump [kgghash()+340] [SIGSEGV] [Address not mapped to object] [0x3184000] [] []
    Fri Jul 27 09:22:10 2007
    Thread 1 advanced to log sequence 10730
    Current log# 2 seq# 10730 mem# 0: /disc3/oracle9205/RFDB/RDO/logRFDB2a.rdo
    Current log# 2 seq# 10730 mem# 1: /disc3/oracle9205/RFDB/RDO/logRFDB2b.rdo
    Fri Jul 27 09:29:26 2007
    Errors in file /disc3/oracle9205/RFDB/udump/rfdb_ora_27372.trc:
    ORA-07445: exception encountered: core dump [kgghash()+296] [SIGSEGV] [Address not mapped to object] [0x3182000] [] []
    The applications have encountered ora-3113 after a short period of time followed by ora-3114.
    application log:-
    RF0120-1 2007-Jul-27 09:46:57] Load m[RF0120-1 2007-Jul-27 09:29:30] SQLCODE: -3113
    [RF0120-1 2007-Jul-27 09:29:30] Error Code -4105 returning from get score pan no.
    [RF0120-1 2007-Jul-27 09:29:30] Message type :120
    [RF0120-1 2007-Jul-27 09:29:30] Primary Account Number(PAN) DE0
    02 :5440640155262702
    [RF0120-1 2007-Jul-27 09:29:30] Processing code DE003 :003000
    [RF0120-1 2007-Jul-27 09:29:30] Transaction amount DE004 :000000000001
    [RF0120-1 2007-Jul-27 09:29:30] Settlement amount DE005 :000000000000
    [RF0120-1 2007-Jul-27 09:29:30] Transmission Date and time
    DE007 :0727092717
    [RF0120-1 2007-Jul-27 09:29:30] Settlement conversion rate DE009 :60263158
    [RF0120-1 2007-Jul-27 09:29:30] System trace audit no. DE011 :754710
    [RF0120-1 2007-Jul-27 09:29:30] Local transaction time DE012 :092717
    [RF0120-1 2007-Jul-27 09:29:30] Local transaction date DE013 :0727
    [RF0120-1 2007-Jul-27 09:29:30] Expiration date D
    E014 :0712
    [RF0120-1 2007-Jul-27 09:29:30] Settlement date DE015 :0727
    [RF0120-1 2007-Jul-27 09:29:30] Merchant type DE018 :5311
    [RF0120-1 2007-Jul-27 09:29:30] Point-of-service(POS) entry code DE022 :051
    [RF0120-1 2007-Jul-27 09:29:30] Acquiring inst. ID code DE032 :001912
    [RF0120-1 2007-Jul-27 09:29:30] Forwarding Inst. ID code DE033 :001912
    [RF0120-1 2007-Jul-27 09:29:30] Retrieval ref. no.
    DE037 :754710356390
    [RF0120-1 2007-Jul-27 09:29:30] Autholization ID response DE038 :356390
    [RF0120-1 2007-Jul-27 09:29:30] Response code DE039 :00
    [RF0120-1 2007-Jul-27 09:29:30] Card acceptor terminal ID DE041 :19306002
    [RF0120-1 2007-Jul-27 09:29:30] Card acceptor ID code DE042 :000001106
    020132
    [RF0120-1 2007-Jul-27 09:29:30] Card acceptor Name/Location
    What could have caused the above mentioned errors i.e Ora-07445 ; ora-3113 / ora-3114? How to resolve the problem.
    Please help .
    Thanks.

    i am also facing the same some time in ora 9.2.0.6 on Sun OS 9 SPARC 64-bits
    Errors in file /oracle/oracle9i/admin/FINPROD/udump/finprod_ora_6076.trc:
    ORA-07445: exception encountered: core dump [0000000100FDE088] [SIGSEGV] [Address not mapped to object] [0x00000013A] [] []
    Thu Aug 30 08:52:39 2007
    Errors in file /oracle/oracle9i/admin/FINPROD/udump/finprod_ora_6078.trc:
    ORA-07445: exception encountered: core dump [0000000100FDE088] [SIGSEGV] [Address not mapped to object] [0x00000013A] [] []
    Thu Aug 30 09:41:49 2007

  • "Error in the alert log file " - please help

    Hi ALL,
    I am getting following errors in the alert log frequently.
    My database version is:
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi
    PL/SQL Release 10.2.0.1.0 - Production
    CORE 10.2.0.1.0 Production
    TNS for IBM/AIX RISC System/6000: Version 10.2.0.1.0 - Productio
    NLSRTL Version 10.2.0.1.0 - Production
    Thu Aug 30 16:58:19 2007
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2172K exceeds notification threshold (2048K)
    KGL object name :select object_name from all_objects where object_name='TOAD_PROFILER' and object_type='PACKAGE'
    Thu Aug 30 17:09:36 2007
    ************************************************************************************

    Additionally you can visit here:
    Alert Error from trc files--Heap size 5236K exceeds notification threshold
    geting error in alert log file
    Adith

  • Trace file with different name is alert log file.

    I am strange today
    i found a trace file generated in alert log file with name
    /bdump/stlbas_cjq0_1880.trc:
    but when i am trying to find out in bdump folder i cannot found
    any file with this named. instead i found /bdump/stlbas_cjq0_1853.trc
    is there any possibility of being this scenario ?
    database version:- 10.2.0.4
    Os:- sun solaries spark 64 bits
    Regards
    Halim

    The trace file has been removed/deleted from an OS user. I think you should verify that with OS logs.
    Thanks

  • Errors in Alert log file

    Hi,
    I have encountered following errors in alrt log file, its strange to see FAST_START_MTTR_TARGET is out of valid and aksing to use another value and that value is changing every second, it should be in increasing order or it should be consistent. I think i have a serious problem, so anyone could help me out on this. I am getting this "FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 24381 instead" error regurarly.
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 24381 instead.
    Wed Jan 16 23:40:34 2008
    Completed checkpoint up to RBA [0x2aadb.2.10], SCN: 5473742880
    Wed Jan 16 23:45:51 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 24017 instead.
    Wed Jan 16 23:46:21 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 23647 instead.
    Wed Jan 16 23:46:52 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 23298 instead.
    Wed Jan 16 23:47:22 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 22906 instead.
    Wed Jan 16 23:47:52 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 22507 instead.
    Wed Jan 16 23:48:22 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 22133 instead.
    Wed Jan 16 23:48:52 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 21786 instead.
    Wed Jan 16 23:49:22 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 21443 instead.
    Wed Jan 16 23:49:52 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 21062 instead.
    Wed Jan 16 23:50:22 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 20698 instead.
    Wed Jan 16 23:53:53 2008
    Incremental checkpoint up to RBA [0x2aadb.31b4.0], current log tail at RBA [0x2aadb.3e38.0]
    Thu Jan 17 00:00:54 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 19582 instead.
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 16287 instead.
    Thu Jan 17 00:34:01 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 15902 instead.
    Thu Jan 17 00:34:31 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 14638 instead.
    Thu Jan 17 00:35:01 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 13600 instead.
    Thu Jan 17 00:35:31 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12773 instead.
    Thu Jan 17 00:36:02 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12460 instead.
    Thu Jan 17 00:36:32 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12338 instead.
    Thu Jan 17 00:37:01 2008
    Process P187 died, see its trace file
    Thu Jan 17 00:37:02 2008
    FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12248 instead.
    Thu Jan 17 00:37:02 2008
    Process P188 died, see its trace file
    Thu Jan 17 00:37:03 2008
    Process P189 died, see its trace file
    Thu Jan 17 00:37:04 2008
    Process P190 died, see its trace file
    Thu Jan 17 00:37:16 2008
    Process J000 died, see its trace file
    Thu Jan 17 00:37:16 2008
    kkjcre1p: unable to spawn jobq slave process
    Thu Jan 17 00:37:16 2008
    Errors in file /oracle/BP3/saptrace/background/bp3_cjq0_4788.trc:
    Process J000 died, see its trace file
    Thu Jan 17 00:37:22 2008
    kkjcre1p: unable to spawn jobq slave process
    Thu Jan 17 00:37:22 2008
    Errors in file /oracle/BP3/saptrace/background/bp3_cjq0_4788.trc:
    Thanks
    Jafar

    This parameter, FAST_START_MTTR_TARGET ranges from 0 to 3600 seconds. It is important to specify your oracle version, since a similar issue is reported for the 10gR1 release.
    The solution for it would be to increase the value to the suggested one in the alert.log file, but it could be completely out of range from the valid values, so set it to zero and let the oracle instance calculate the value. You can check the output at the V$INSTANCE_RECOVERY view at the columns TARGET_MTTR, and ESTIMATED_MTTR prior to proceeding with modificaiton.
    On the other hand, I suggest you to read this metalink note
    Kkjcre1p: Unable To Spawn Jobq Slave Process, Error 1089
         Doc ID:      Note:344275.1
    for the Kkjcre1p error message.
    ~ Madrid

  • Errors appeared in alert log file should send an email

    Hi,
    I have one requirement to do, as i am new dba, i dont know how to do this,
    sendmail is configured on my unix machine, but dont know how to send the errors appeared in alert logfile should send an email to administrator.
    daily, it has to check the errors in alert log file, if any errors occurs(ORA- errors or WARNING errors) should send an email to administrator.
    please help me how to do it

    Hi,
    There are many methods for interrogating the alert log and sending e-mail. Here are my notes:
    http://www.dba-oracle.com/t_alert_log_monitoring_errors.htm
    - PL/SQL or Java with e-mail alert: http://www.dba-village.com/village/dvp_papers.PaperDetails?PaperIdA=2383
    - Shell script - Database independent and on same level as alert log file and e-mail.
    - OEM - Too inflexible for complex alert log analysis rules
    - SQL against the alert log - You can define the alert log file as an external table and detect messages with SQL and then e-mail.
    Because the alert log is a server side flat file and because e-mail is also at the OS-level, I like to use a server side scell script. It's also far more robust then OEM, especially when combining and evaluating multiple alert log events. Jon Emmons has great notes on this:
    http://www.lifeaftercoffee.com/2007/12/04/when-to-use-shell-scripts/
    If you are on Windows, see here:
    http://www.dba-oracle.com/t_windows_alert_log_script.htm
    For UNIX, Linux, Jon Emmons has a great alert log e-mail script.
    Hope this helps . . . .
    Donald K. Burleson
    Oracle Press author

  • ORA- errors in alert log file

    I wanted to know when the ORA- errors are reported into the alert.log file?
    And which tye of errors are reported into it?
    And if i wanted to log all the ORA-errors in the alert log then is there any setting for that?

    You can find the type of errors reported in the link above.
    Also, you maynot like to log ORA-00942: table or view does not exist, ORA-00904: : invalid identifier type of errors in alert.log - right? You may want to research at setting up events for generating trace files on specific error numbers you are looking at. That might resolve your problem - hth.

Maybe you are looking for

  • Save for Web only let me save as jpg!

    For some reason, I got a file that's only let me do Save for Web in jpg format. I choose png24, click save and it changes to jpg in the save dialog. Then I created a blank doc, copy everything from the problem file over to the new file and I can Save

  • How can I save a CYMK PSD file as a PDF in CS5?

    I am able to make the file in CS4 on another computer I use (PC).  However when I try to save a CYMK PSD file as a PDF in Photoshop CS5 I don't see the option in the drop down menu?  Any ideas?  Here are some of the file details CMYK PSD 8 bits/chann

  • How may load an external (html) file in swf? Anyone!!!!!

    hi all,     How may load an external html file in swf? such as google.com in a movieclip. anyone may help me.........????????

  • "Toggle mask visibility" shortcut?

    Is there a keyboard shortcut for "Toggle mask visibility"? I can do this by ALT-clicking on the layer's mask, but I would like to assign a shortcut for this on a button on my Wacom Intuos 4 drawing tablet. So far I haven't found a menu shortcut for i

  • [java] Failed at "Could not get DeploymentManager".

    I am running the second example in the BPEL Help tutorial. In that we are supposed to run ant from tutorials\127.OrderBookingTutorial\PriceQuote and it gives error because it is not able to resolve my PC name 5mq9p91. I changed couple of build.proper