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

Similar Messages

  • 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.

  • ORA-01555 in alert log file

    Hi,
    I am occasionally seeing ORA-01555 in the alert log file, but the query length is so long that I could not see the full query in the alert log file.
    Where can i view the query which is causing this issue?
    Thanks
    SA

    You can see the full query by using below query, just put the respective sql_id.
    SELECT
    SUBSTR(SQL_TEXT, 1 + (i - 1) * 80, 80) SQL_TEXT
    FROM
    DBA_HIST_SQLTEXT HST,
    (SELECT ROWNUM I FROM DBA_HIST_SQLTEXT WHERE ROWNUM <=
    60)
    WHERE
    HST.SQL_ID = '&SQL_ID'
    And according to query length and undo space available please set the undo_retention appropriatley.
    regards
    Jafar

  • ORA-1142 in alert log file

    hello everybody,
    I am getting the following ORA error in my Alert Log file.........
    alter tablespace SYSTEM end backup
    Sun Apr 13 01:42:58 2008
    ORA-1142 signalled during: alter tablespace SYSTEM end backup..
    what is this error??

    The version of oracle i am running is
    Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production
    PL/SQL Release 9.2.0.7.0 - Production
    CORE 9.2.0.7.0 Production
    TNS for Solaris: Version 9.2.0.7.0 - Production
    NLSRTL Version 9.2.0.7.0 - Production........
    Section of the Alert Log displaying the message................
    Sun Apr 13 05:40:57 2008
    Thread 1 advanced to log sequence 109947
    Current log# 3 seq# 109947 mem# 0: /u09/oradata/inora/redo/redo03.log
    Current log# 3 seq# 109947 mem# 1: /u10/oradata/inora/ctrl/redo03.log
    Sun Apr 13 05:40:57 2008
    ARCH: Evaluating archive log 2 thread 1 sequence 109946
    ARCH: Beginning to archive log 2 thread 1 sequence 109946
    Creating archive destination LOG_ARCHIVE_DEST_1: '/u08/oradata/inora/archive/inora_1_109946.dbf'
    Sun Apr 13 05:40:57 2008
    ARC1: Evaluating archive log 2 thread 1 sequence 109946
    ARC1: Unable to archive log 2 thread 1 sequence 109946
    Log actively being archived by another process
    Sun Apr 13 05:40:57 2008
    ARCH: Completed archiving log 2 thread 1 sequence 109946
    Sun Apr 13 05:40:59 2008
    Thread 1 advanced to log sequence 109948
    Current log# 1 seq# 109948 mem# 0: /u09/oradata/inora/redo/redo01.log
    Current log# 1 seq# 109948 mem# 1: /u10/oradata/inora/ctrl/redo01.log
    Sun Apr 13 05:40:59 2008
    ARCH: Evaluating archive log 3 thread 1 sequence 109947
    ARCH: Beginning to archive log 3 thread 1 sequence 109947
    Creating archive destination LOG_ARCHIVE_DEST_1: '/u08/oradata/inora/archive/inora_1_109947.dbf'
    Sun Apr 13 05:40:59 2008
    ARC0: Evaluating archive log 3 thread 1 sequence 109947
    ARC0: Unable to archive log 3 thread 1 sequence 109947
    Log actively being archived by another process
    Sun Apr 13 05:40:59 2008
    ARCH: Completed archiving log 3 thread 1 sequence 109947
    Sun Apr 13 05:42:10 2008
    alter tablespace SYSTEM end backup
    Sun Apr 13 05:42:10 2008
    ORA-1142 signalled during: alter tablespace SYSTEM end backup
    Sun Apr 13 05:42:11 2008
    Thread 1 advanced to log sequence 109949
    Current log# 2 seq# 109949 mem# 0: /u10/oradata/inora/ctrl/redo02.log
    Current log# 2 seq# 109949 mem# 1: /u09/oradata/inora/redo/redo02.log
    Sun Apr 13 05:42:11 2008
    ARCH: Evaluating archive log 1 thread 1 sequence 109948
    ARCH: Beginning to archive log 1 thread 1 sequence 109948
    Creating archive destination LOG_ARCHIVE_DEST_1: '/u08/oradata/inora/archive/inora_1_109948.dbf'
    Sun Apr 13 05:42:11 2008
    ARC1: Evaluating archive log 1 thread 1 sequence 109948
    ARC1: Unable to archive log 1 thread 1 sequence 109948
    Log actively being archived by another process

  • Receiving Alerts on ORA- error in Alert Log File

    Hi,
    I am using 10.2.0.5 OEM grid control and same versioned agent on my database servers. I have configured the alert email notification if there is any ORA- error message in my alert log file. The metric i selcted for this is "Generic Alert Log Error Status". In notification email, i see only the message that there is generic error message in the alert log file. Is there any way to set this notification so that i receive the exact ORA- error message in my alert notification email if there is any kind of ORA- error found in my alert log file?
    Thanks
    Salman

    Please look into the Metalink Note: 458605.1
    Subject: Receiving "Clear" Notifications Unexpectedly for 'Generic Alert Log Error Status' Metric

  • Getting ORA-28 in alert log file

    Hi,
    We are getting ORA-28 in alert log.
    " ORA-28 ALTER DATABASE BACKUP CONTROLFILE....."
    please suggest.
    Thanks

    Could you post 20 lines before and after this error occurred in alertlog
    Cheers

  • 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

  • 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.

  • 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

  • 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

  • Getting ORA-01476 and ORA-06512 in alert log

    I am getting this error in my alert log file frequently
    ORA-12012: error on auto execute of job 734
    ORA-12008: error in materialized view refresh path
    ORA-01476: divisor is equal to zero
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 803
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 860
    ORA-06512: at "SYS.DBMS_IREFRESH", line 683
    ORA-06512: at "SYS.DBMS_REFRESH", line 195
    ORA-06512: at line 1
    can anybody help in finding the cause and solution for this?
    Thanks and Regards
    Thiagarajan.

    The root error for this issue can be found here:
    ORA-01476: divisor is equal to zero
    You should debug your materialized view, it is dealing with divisors whose value is equal to zero, and your procedure isn't capable of handling this exception. Try to perform a manual refresh to verify this error is repeatable and look for division operations, then debug values.
    ~ Madrid

  • 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.

  • How to check particular error in alert log file

    Hi all,
    How to check particular error in alert log file,for supose if i get error in batabase yesterday 4 pm & today i want to check alert log file to get basic idea..it might be a big file so how to check that particular error..
    Thanks & regards,
    Eswar..

    What's your oracle version?
    If you are in 11g you can use adrci tool
    1- set homes diag/rdbms/orawiss/ORAWISS/ : the rdbms home
    2- show alert -P "MESSAGE_TEXT LIKE '%ORA-%'" -term : to find all the ORA-% errors in the alert file
    3- show alert -P "MESSAGE_TEXT LIKE '%ORA-%' and originating_timestamp > systimestamp-51 " -term : to find all the ORA-% errors in the alert file during the last 51 days,
    4- show alert -P "MESSAGE_TEXT LIKE '%ORA-%' and originating_timestamp > systimestamp-1/24 " -term : to find all the ORA-% errors in the alert file during the last hour,
    5- show alert -P "MESSAGE_TEXT LIKE '%ORA-12012%' and originating_timestamp > systimestamp-1/24 " -term : to find the particular ORA-12012 error in the alert file during the last hour,
    Example:
    [oracle@wissem wissem]$ adrci
    ADRCI: Release 11.2.0.1.0 - Production on Wed May 4 10:24:54 2011
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    ADR base = "/home/oracle/app/oracle"
    adrci> set homes diag/rdbms/orawiss/ORAWISS/
    adrci> show alert -P "MESSAGE_TEXT LIKE '%ORA-'" -term
    ADR Home = /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS:
    adrci> show alert -P "MESSAGE_TEXT LIKE '%ORA-%'" -term
    ADR Home = /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS:
    2010-12-11 19:45:41.289000 +01:00
    ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/home/oracle/app/oracle/oradata/ORAWISS/system01.dbf'
    ORA-1547 signalled during: ALTER DATABASE RECOVER  database until time '2011-01-21:10:48:00'  ...
    Errors in file /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS/trace/ORAWISS_j000_5692.trc:
    ORA-12012: error on auto execute of job 29
    ORA-01435: user does not exist
    2011-03-15 11:39:37.571000 +01:00
    opiodr aborting process unknown ospid (31042) as a result of ORA-609
    2011-03-15 12:04:15.111000 +01:00
    opiodr aborting process unknown ospid (3509) as a result of ORA-609
    adrci>
    adrci> show alert -P "MESSAGE_TEXT LIKE '%ORA-%' and originating_timestamp > systimestamp-51 " -term
    ADR Home = /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS:
    2011-03-15 10:19:45.316000 +01:00
    Errors in file /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS/trace/ORAWISS_j006_5536.trc:
    ORA-12012: error on auto execute of job 26
    ORA-01435: user does not exist
    Errors in file /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS/trace/ORAWISS_j000_5692.trc:
    ORA-12012: error on auto execute of job 29
    ORA-01435: user does not exist
    2011-03-15 11:39:37.571000 +01:00
    opiodr aborting process unknown ospid (31042) as a result of ORA-609
    2011-03-15 12:04:15.111000 +01:00
    opiodr aborting process unknown ospid (3509) as a result of ORA-609
    adrci>

  • 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

  • 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

Maybe you are looking for