I need help... "terminating instance due to error 1242"

ALERT LOG
KCF: write/open error block=0x79 online=1
file=2 D:\APPS\SIXX\ORACLEEXE\ORADATA\XE\UNDO.DBF
error=27072 txt: 'OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 33) The process cannot access the file because another process has locked a portion of the file.'
Tue Apr 24 02:08:11 2007
Errors in file d:\apps\sixx\oracleexe\app\oracle\admin\xe\bdump\xe_dbw0_3668.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
ORA-01114: IO error writing block to file 2 (block # 121)
ORA-01110: data file 2: 'D:\APPS\SIXX\ORACLEEXE\ORADATA\XE\UNDO.DBF'
ORA-27072: File I/O error
OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 33) The process cannot access the file because another process has locked a portion of the file.
DBW0: terminating instance due to error 1242
Tue Apr 24 02:08:12 2007
Errors in file d:\apps\sixx\oracleexe\app\oracle\admin\xe\bdump\xe_q001_1048.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Tue Apr 24 02:08:12 2007
Errors in file d:\apps\sixx\oracleexe\app\oracle\admin\xe\bdump\xe_psp0_3040.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Tue Apr 24 02:08:12 2007
Errors in file d:\apps\sixx\oracleexe\app\oracle\admin\xe\bdump\xe_lgwr_3568.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Tue Apr 24 02:08:13 2007
Errors in file d:\apps\sixx\oracleexe\app\oracle\admin\xe\bdump\xe_mman_2788.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Tue Apr 24 02:08:13 2007
Errors in file d:\apps\sixx\oracleexe\app\oracle\admin\xe\bdump\xe_ckpt_2896.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Tue Apr 24 02:08:14 2007
Errors in file d:\apps\sixx\oracleexe\app\oracle\admin\xe\bdump\xe_j000_1028.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Tue Apr 24 02:08:15 2007
Errors in file d:\apps\sixx\oracleexe\app\oracle\admin\xe\bdump\xe_pmon_3504.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Tue Apr 24 02:08:25 2007
Errors in file d:\apps\sixx\oracleexe\app\oracle\admin\xe\bdump\xe_reco_2164.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Tue Apr 24 02:08:25 2007
Errors in file d:\apps\sixx\oracleexe\app\oracle\admin\xe\bdump\xe_smon_3964.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Tue Apr 24 02:08:28 2007
Instance terminated by DBW0, pid = 3668

Hi>
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Cause: The Database is in NOARCHIVELOG mode and a database file was detected as inaccessible due to media failure
Action: restore accessibility to the file mentioned in the error stack and restart the instance.
(Restore the undo datafile) and restart the instance.
Regards
Message was edited by:
user500658

Similar Messages

  • CKPT : Terminating instance due to Error 472

    Hi All,
    I got the above error and the system stopped and restarted on the DR side.
    Snippet from Alert file before shutdown
    ===========================
    Wed Nov 27 22:39:12 2013
    Thread 1 advanced to log sequence 10770
      Current log# 2 seq# 10770 mem# 0: /var/opt/oracle/oradata/xxxx/redo02.log
    Wed Nov 27 22:39:12 2013
    ARC0: Evaluating archive   log 1 thread 1 sequence 10769
    ARC0: Beginning to archive log 1 thread 1 sequence 10769
    Creating archive destination LOG_ARCHIVE_DEST_1: '/var/opt/oracle/oradata/xxxx/archive/1_10769.dbf'
    ARC0: Completed archiving  log 1 thread 1 sequence 10769
    Wed Nov 27 23:18:37 2013
    CKPT: terminating instance due to error 472
    Instance terminated by CKPT, pid = 22682
    After restart following is snippet
    =======================
    Wed Nov 27 23:19:19 2013
    Starting ORACLE instance (force)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    SCN scheme 3
    Using log_archive_dest parameter default value
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up ORACLE RDBMS Version: 9.2.0.1.0.
    System parameters with non-default values:
      processes                = 300
      timed_statistics         = TRUE
      shared_pool_size         = 486539264
      large_pool_size          = 436207616
      java_pool_size           = 33554432
      control_files            = /var/opt/oracle//oradata/xxxx/control01.ctl, /var/opt/oracle//oradata/xxxx/control02.ctl, /var/opt/oracle//oradata/xxxx/control03.ctl
      db_block_size            = 4096
      db_cache_size            = 1761607680
      compatible               = 9.2.0.0.0
      log_archive_start        = TRUE
      log_archive_dest_1       = LOCATION=/var/opt/oracle//oradata/xxxx/archive
      log_archive_format       = %t_%s.dbf
      db_file_multiblock_read_count= 8
      fast_start_mttr_target   = 300
      undo_management          = AUTO
      undo_tablespace          = UNDOTBS1
      undo_retention           = 900
      remote_login_passwordfile= EXCLUSIVE
      db_domain                =
      instance_name            = xxxx
      dispatchers              = (protocol=TCP)
      job_queue_processes      = 10
      hash_join_enabled        = FALSE
      background_dump_dest     = /var/opt/oracle//admin/xxxx/bdump
      user_dump_dest           = /var/opt/oracle//admin/xxxx/udump
      core_dump_dest           = /var/opt/oracle//admin/xxxx/cdump
      sort_area_size           = 524288
      db_name                  = xxxx
      open_cursors             = 300
      star_transformation_enabled= FALSE
      query_rewrite_enabled    = FALSE
      pga_aggregate_target     = 524288000
      aq_tm_processes          = 1
    PMON started with pid=2
    DBW0 started with pid=3
    LGWR started with pid=4
    CKPT started with pid=5
    SMON started with pid=6
    RECO started with pid=7
    CJQ0 started with pid=8
    QMN0 started with pid=9
    Wed Nov 27 23:19:25 2013
    starting up 1 shared server(s) ...
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    ARCH: STARTING ARCH PROCESSES
    ARC0 started with pid=12
    ARC0: Archival started
    ARC1 started with pid=13
    Wed Nov 27 23:19:25 2013
    ARCH: STARTING ARCH PROCESSES COMPLETE
    Wed Nov 27 23:19:25 2013
    ARC1: Archival started
    ARC1: Thread not mounted
    Wed Nov 27 23:19:25 2013
    ARC0: Thread not mounted
    Wed Nov 27 23:19:26 2013
    ALTER DATABASE   MOUNT
    Wed Nov 27 23:19:32 2013
    Successful mount of redo thread 1, with mount id 1572646464.
    Wed Nov 27 23:19:32 2013
    Database mounted in Exclusive Mode.
    Completed: ALTER DATABASE   MOUNT
    Wed Nov 27 23:19:32 2013
    ALTER DATABASE OPEN
    Wed Nov 27 23:19:32 2013
    Beginning crash recovery of 1 threads
    Wed Nov 27 23:19:32 2013
    Started first pass scan
    Wed Nov 27 23:19:33 2013
    Completed first pass scan
    11410 redo blocks read, 798 data blocks need recovery
    Wed Nov 27 23:19:33 2013
    Started recovery at
    Thread 1: logseq 10770, block 3829, scn 0.0
    Recovery of Online Redo Log: Thread 1 Group 2 Seq 10770 Reading mem 0
      Mem# 0 errs 0: /var/opt/oracle/oradata/xxxx/redo02.log
    Wed Nov 27 23:19:33 2013
    Ended recovery at
    Thread 1: logseq 10770, block 15239, scn 0.1667153707
    798 data blocks read, 798 data blocks written, 11410 redo blocks read
    Crash recovery completed successfully
    ==============
    Was the CKPT Termination caused by some error in Redo Logs which needed recovery?

    Lookup the Error messages documentation.
    Error 472 is
    "PMON process terminated with error "
    CKPT detected that PMON had "died" and so it forcibly terminated the database instance. (The background processes monitor each other and are designed to terminate the database instance if a critical process dies).
    Look for a trace file.
    PMON died because of a resource issue or a bug or a server issue or because it was killed (by the OS or a user or process with oracle / administrator privileges)
    Hemant K Chitale

  • PMON: terminating instance due to error 28

    Hi ,
    OS : AIX 5.3
    Oracle : 10.2.0.4
    Problem :
    Database instance crashed .
    Alert log shows :
    Tue Jun 26 13:21:18 2012
    Thread 1 advanced to log sequence 4097 (LGWR switch)
    Current log# 1 seq# 4097 mem# 0: /oracle/abcd/oradata1/redo/abcd_redo_g1m1.dbf
    Current log# 1 seq# 4097 mem# 1: /oracle/abcd/oradata2/redo/abcd_redo_g1m2.dbf
    Tue Jun 26 14:29:56 2012 ---> Instance terminated
    Errors in file /oracle/abcd/oratrace/bdump/abcd_pmon_2834484.trc:
    ORA-00028: your session has been killed
    Tue Jun 26 14:29:56 2012
    PMON: terminating instance due to error 28
    Termination issued to instance processes. Waiting for the processes to exit
    Instance terminated by PMON, pid = 2834484
    Tue Jun 26 15:09:00 2012 --> Instance started manually at this point
    Starting ORACLE instance (normal)
    Trace file shows :
    /oracle/abcd/oratrace/bdump/abcd_pmon_2834484.trc
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    ORACLE_HOME = /oracle/product/10.2.0/ora10gr2
    System name: AIX
    Node name: a838dae0
    Release: 3
    Version: 5
    Machine: 00047961D600
    Instance name: abcd
    Redo thread mounted by this instance: 1
    Oracle process number: 2
    Unix process pid: 2834484, image: oracle@a838dae0 (PMON)
    *** 2012-06-26 14:29:56.830
    *** SERVICE NAME:(SYS$BACKGROUND) 2012-06-26 14:29:56.801
    *** SESSION ID:(225.1) 2012-06-26 14:29:56.801
    error 28 detected in background process
    ORA-00028: your session has been killed
    OS logs does not have any errors when the instance got terminated .
    I would like to know what is the cause for this error ? when such errors occurs ?

    @pavan , thanks for the advise . I shall work with Unix admin on how best we can trace it out if it occurs next time .
    However , I have one more question :
    I did a small test to crash the instance by killing the pmon process at OS level . When I did that only the following message got recorded in the alert log :
    Wed Jun 27 04:39:26 2012
    PSP0: terminating instance due to error 472 --> error code is 472
    Instance terminated by PSP0, pid = 4970
    But the issue I see in produciton db is something different , the alert log shows :
    ORA-00028: your session has been killed
    Tue Jun 26 14:29:56 2012
    PMON: terminating instance due to error 28 ----> error code is 28
    Termination issued to instance processes. Waiting for the processes to exit
    Instance terminated by PMON, pid = 2834484
    I have started to belive that the PMON was not killed from OS level . I dont think error ORA-00028 gets recorded when you kill pmon from OS level as I could not reproduce in my testing as well.
    Anyways , thanks for your help on this.

  • DBW0: terminating instance due to error 27061

    Hi,
    PROD
    Db 9.2.0.8
    AIX 5.2
    Suddenly database crashed. What I found in alert log file and trace file find below.
    I started database it started normally but it took much time to start. Suggest me why it occurred and what I need to change so that I could not face again it.
    Alert log file:
    ARC1: Completed archiving log 2 thread 1 sequence 3653
    Mon May 9 21:14:43 2011
    Errors in file /vol01/oracle/product/admin/prod/bdump/prod_dbw0_695450.trc
    ORA-27061: skgfospo: waiting for async I/Os failed
    IBM AIX RISC System/6000 Error: 22: Invalid argument
    Mon May 9 21:14:43 2011
    DBW0: terminating instance due to error 27061
    Instance terminated by DBW0, pid = 695450
    Trace file prod_dbw0_695450.trc:
    Redo thread mounted by this instance: 1
    Oracle process number: 3
    Unix process pid: 695450, image: oracle@prod (DBW0)
    *** 2011-05-09 21:14:43.089
    *** SESSION ID:(2.1) 2011-05-09 21:14:43.028
    error 27061 detected in background process
    ORA-27061: skgfospo: waiting for async I/Os failed
    IBM AIX RISC System/6000 Error: 22: Invalid argument
    During database starting find below some of the lines of alert log file:
    Completed: ALTER DATABASE MOUNT
    Tue May 10 08:46:17 2011
    ALTER DATABASE OPEN
    Tue May 10 08:46:17 2011
    Beginning crash recovery of 1 threads
    Tue May 10 08:46:17 2011
    Started redo scan
    Tue May 10 08:46:32 2011
    Completed redo scan
    1884170 redo blocks read, 61752 data blocks need recovery
    Tue May 10 08:46:45 2011
    Started recovery at
    Thread 1: logseq 3653, block 1324175, scn 0.0
    Tue May 10 08:46:46 2011
    Recovery of Online Redo Log: Thread 1 Group 2 Seq 3653 Reading mem 0
    Mem# 0 errs 0: /vol01/oracle/product/oradata/prod/redo2a.log
    Mem# 1 errs 0:/vol02/oracle/product/oradata/prod//redo2b.log
    Tue May 10 08:46:57 2011
    Recovery of Online Redo Log: Thread 1 Group 3 Seq 3654 Reading mem 0
    Mem# 0 errs 0: /vol01/oracle/product/oradata/prod/redo3a.log
    Mem# 1 errs 0: /vol02/oracle/product/oradata/prod/redo3b.log
    Tue May 10 08:53:02 2011
    Completed redo application
    Tue May 10 08:53:13 2011
    Ended recovery at
    Thread 1: logseq 3654, block 1111196, scn 3.3471125210
    61752 data blocks read, 38719 data blocks written, 1884170 redo blocks read
    Crash recovery completed successfully
    Thanks

    Check metalink note 464768.1. The version mentioned in the note is 10.2.0.1 + but I think it applies in your case too.
    Confirm it by raising an SR with Oracle Support.

  • MMON: terminating instance due to error 472

    Hi,
    my Oracle DB 10.2.0.1 runs on an Linux Debian 3.1. My database crash in the early morning, i look in the alert.log and find one line.
    Mon Feb 5 04:48:05 2007
    MMON: terminating instance due to error 472
    Instance terminated by MMON, pid = 3273
    Can you help me, what can i do with this error message?
    Thanks
    Blue

    Hi Blue,
    I would open an SR on Metalink on this. . . .
    MMON: terminating instance due to error 472Explanation: A severe error occurred so this instance died
    See the server side trace file files and alert log messages. The trace file will have additonal details.

  • LGWR: terminating instance due to error 204

    Hi,
    I was running some batch process on Oracle 8.1.7 on windows XP OS. After running for a while like 3 hrs
    my oracle instance crashed giving me error in alert log file as .
    LGWR: terminating instance due to error 204
    Instance terminated by LGWR, pid = 1028
    Therafter i tried to restart the database but i get erroe as ORA:03113 End of communication file.
    When I see the alter log file it says
    " Rolling back half complete log switch of thread 1
    LGWR: terminating instance due to error 204
    Instance terminated by LGWR, pid = 2608
    Could anyone please help me out in solving this problem ?
    I would be grateful.
    The output of alertlog is
    Thread 1 advanced to log sequence 2633
    Current log# 2 seq# 2633 mem# 0: D:\ORA817HM\ORADATA\ORATEST\REDO02.LOG
    Thread 1 advanced to log sequence 2634
    Current log# 3 seq# 2634 mem# 0: D:\ORA817HM\ORADATA\ORATEST\REDO01.LOG
    Thread 1 advanced to log sequence 2635
    Current log# 1 seq# 2635 mem# 0: D:\ORA817HM\ORADATA\ORATEST\REDO03.LOG
    Tue Dec 30 01:03:44 2003
    Thread 1 advanced to log sequence 2636
    Current log# 2 seq# 2636 mem# 0: D:\ORA817HM\ORADATA\ORATEST\REDO02.LOG
    LGWR: terminating instance due to error 204
    Instance terminated by LGWR, pid = 1028
    Dump file D:\ora817HM\admin\oratest\bdump\oratestALRT.LOG

    It seems like a bad issue happened with a group of
    Redo Logs. Your database is in Archivelog mode ?
    If your database is or not in archivelogmode we can
    recover it creating it using the controlfile and
    dropping and recreating the Redo Logs again.
    If the database is in NoArchivelog mode will be
    easier.
    Joel P�rez

  • ASMB: terminating instance due to error 15064

    ASMB: terminating instance due to error 15064                            
    Database is shutdown and alert file show following messages.            
    ORA-15064: communication failure with ASM instance                      
    ORA-03135: connection lost contact                                      
    Tue Apr 15 16:11:14 2014                                                
    ASMB: terminating instance due to error 15064                           
    Termination issued to instance processes. Waiting for the processes to exit  
    Tue Apr 15 16:11:24 2014                                                
    Instance termination failed to kill one or more processes               
    Instance terminated by ASMB, pid = 2884110                              
    Tue Apr 15 16:15:19 2014                                                
    Below is the output of trace file erp_asmb_2884110.trc:             
    more /u01/app/oracle/admin/erp/bdump/erp_asmb_2884110.trc        
    /u01/app/oracle/admin/erp/bdump/erp_asmb_2884110.trc            
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production 
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1                       
    System name: AIX                                                        
    Node name: erpnew                                                 
    Release: 1                                                              
    Version: 6                                                              
    Machine: 00C5CAD44C00                                                   
    Instance name: erp                                                  
    Redo thread mounted by this instance: 1                                 
    Oracle process number: 28                                               
    Unix process pid: 2884110, image: oracle@erpnew (ASMB)            
    *** 2014-04-15 16:11:14.003                                             
    *** SERVICE NAME:(SYS$BACKGROUND) 2014-04-15 16:11:13.353               
    *** SESSION ID:(1959.1) 2014-04-15 16:11:13.353                         
    error 15064 detected in background process                              
    ORA-15064: communication failure with ASM instance                      
    ORA-03135: connection lost contact                                      
    *** 2014-04-15 16:11:24.600                                             
    Instance termination failed to kill one or more processes               
    ksuitm_check: OS PID=7079012 is still alive                             
    *** 2014-04-15 16:11:24.601                                             
    Dumping diagnostic information for oracle@erpnew:                 
    OS pid = 7079012                                                        
    loadavg : 23.36 9.55 8.59                                               
    swap info: free_mem = 113237.14M rsv = 1260.00M                         
      alloc = 34190.07M avail = 322560.00M swap_free = 288369.93M            
      F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD             
    ERROR: process 7079012 is not alive                                      

    Hi ,
    Database can get crashed with ORA-15064 due to following things ,
    + OS level resource starvation
    Or
    + Oracle defect .
    So,without proper information it will be hard to conclude.
    I would suggest you to open a service request with support with below information ,
    -- ASM and RDBMS alertlog file
    -- If ASM instance crash ,then gather diagcollection information from cluster level with the help of TFA ,covering atleast 4 hours +/- of the issue
    -- generated trace files from rdbms and ASM level ,particularly diag trace file if generated.
    -- Patch details of this impacted environment .
    Regards,
    Aritra

  • Terminating instance due to error 481

    Hi,
    My database is in rac(2-node) environment.Suddenly it got terminated and the error which it produced is
    SMON:terminating instance due to error 481.
    it got stated inb alert log file.There is not trace file.
    Thanks in advance

    Seems, there is some issue with LMON. You've not specified platform or oracle version.
    I think Metalink Note:3149370.8, 313306.1 ,6500033.8 and 6018125.8 will be of your use. You may need oracle support to confirm any associated bug.

  • PMON: terminating instance due to error 602

    Hello everybody,
    I have serious trouble with Oracle database. My environment: Oracle Enterprise edition 10.2.0.5. OS: Oracle Linux 5.7
    When oracle get distribution transactions in 3-5 minutes it crashes with information:
    alert.log
    Thu Jul 05 14:47:32 ALMT 2012
    DISTRIB TRAN 4a5453.5DD801009C96A7544B5A4C41505030322C7365727665722C50313030
    is local tran 49.15.2237 (hex=31.0f.8bd)
    insert pending prepared tran, scn=1834678863 (hex=0.6d5afa4f)
    DISTRIB TRAN 4a5453.61D801009C96A7544B5A4C41505030322C7365727665722C50313030
    is local tran 51.1.2181 (hex=33.01.885)
    insert pending prepared tran, scn=1834678938 (hex=0.6d5afa9a)
    DISTRIB TRAN 4a5453.5CD801009C96A7544B5A4C41505030322C7365727665722C50313030
    is local tran 67.6.992 (hex=43.06.3e0)
    insert pending prepared tran, scn=1834678824 (hex=0.6d5afa28)
    Thu Jul 05 14:47:32 ALMT 2012
    Errors in file /u01/app/oracle/admin/clprod/bdump/clprod_pmon_12599.trc:
    ORA-07445: exception encountered: core dump [koklcom()+59] [SIGSEGV] [Address not mapped to object] [0x0000001E4] [] []
    Thu Jul 05 14:47:33 ALMT 2012
    Errors in file /u01/app/oracle/admin/clprod/bdump/clprod_pmon_12599.trc:
    ORA-00602: internal programming exception
    ORA-07445: exception encountered: core dump [koklcom()+59] [SIGSEGV] [Address not mapped to object] [0x0000001E4] [] []
    Thu Jul 05 14:47:33 ALMT 2012
    PMON: terminating instance due to error 602
    Instance terminated by PMON, pid = 12599
    And crashes everytime when I starting in 3-5 minutes. Only when I run procedure for forcing rollback all distribution transactions dbms_transaction.purge_lost_db_entry(x.local_tran_id); it stops crashing.
    We didn't contact with Oracle support yet. Our developers recommend to apply patch 10.2.0.5.6 but I haven't found so error in patch description.
    Anybody can help me?

    See MOS ID 8650138.8
    It says that this issue is fixed in 10.2.0.5.6 Patch Set Update indeed

  • Database Crash - LGWR: terminating instance due to error 227

    Hi,
    We´re having a problem with our database. The server reboots abnormally and the database shutdown abort, when we bring online the machine the database didn´t open.
    Analyzing the logs, we found a corrupt problem. see the alert file:
    Corrupt block relative dba: 0x00000003 (file 0, block 3)
    Completely zero block found during controlfile block read
    LGWR: terminating instance due to error 227
    Instance terminated by LGWR, pid = 2080
    Dump file E:\ORACLE\PDS\bdump\pdsALRT.LOG
    So ... we try to starts the database and he didn´t mount, we only startup nomount. see the log above:
    Oracle Server Manager Release 3.1.7.0.0 - Production
    Copyright (c) 1997, 1999, Oracle Corporation. All Rights Reserved.
    Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
    JServer Release 8.1.7.0.0 - Production
    SVRMGR> connect internal
    Password:
    Connected.
    SVRMGR> startup nomount
    ORACLE instance started.
    Total System Global Area 633632796 bytes
    Fixed Size 75804 bytes
    Variable Size 167411712 bytes
    Database Buffers 466067456 bytes
    Redo Buffers 77824 bytes
    SVRMGR> alter database mount;
    alter database mount
    ORA-03113: end-of-file on communication channel
    SVRMGR>
    We doesn´t mount the database, so we can´t do a recovery.
    Anybody knows the resolution of this problem ??
    Regards,
    Eduardo

    We can´t do a recover because database is not mounted.
    We don´t have a backup of the controlfile and didn´t make the "alter database backup controlfile to trace"
    Thanks,
    Eduardo

  • PMON: terminating instance due to error 476

    i met an error when the database was open,and then the database was down.
    i looked for the alert log and the correspoding trace file,there is some information in the two files.
    the content in the alert log are:
    PMON: terminating instance due to error 476
    Instance terminated by PMON, pid = 2999
    the content in the trace file are:
    /export/home/oracle/admin/orcl/bdump/orcl_pmon_2999.trc
    Oracle8i Enterprise Edition Release 8.1.6.0.0 - Production
    With the Partitioning option
    JServer Release 8.1.6.0.0 - Production
    ORACLE_HOME = /export/home/oracle
    System name: SunOS
    Node name: KFDB2
    Release: 5.7
    Version: Generic_106541-15
    Machine: sun4u
    Instance name: orcl
    Redo thread mounted by this instance: 1
    Oracle process number: 2
    Unix process pid: 2999, image: oracle@KFDB2 (PMON)
    *** 2003-03-10 11:14:12.217
    *** SESSION ID:(1.1) 2003-03-10 11:14:12.025
    error 476 detected in background process
    how can i resolve the problem.
    thanks

    This particular problem is because of continous write from memory(SGA) to HDD.
    If you are using MTS then disable it and see the results.
    I faced the same problem on compaq server with SCO Unix but we have RAID is enabled.
    As we disabled the RAID then the above error disappers.
    So, if you have RAID configured then disable it and see the results.
    Disable also the parallel and partion option.
    Regards
    Nikhil Wani
    Vadodara

  • USER: terminating instance due to error 472 (Oracle 10g)

    Hi folks,
    We come across a problem that our instance was down suddenly. When checking with the alert log file, it shows that the instance was terminated due to error 472. Did you come across such situation before? Any suggestions would be welcomed.
    Following are some information about our Oracle and the log file, trace file.
    Oracle Database 10g Release 10.2.0.2.0 - Production
    ORACLE_HOME = /app/oracle/lmes
    System name: Linux
    Node name: lmes-oracle2.ust.hk
    Release: 2.4.21-32.ELsmp
    Version: #1 SMP Fri Apr 15 21:17:59 EDT 2005
    Machine: i686
    Alert Log File
    Fri Feb 23 09:11:07 2007
    Shutting down archive processes
    Fri Feb 23 09:11:12 2007
    ARCH shutting down
    ARC2: Archival stopped
    Fri Feb 23 15:16:09 2007
    The value (30) of MAXTRANS parameter ignored.
    kupprdp: master process DM00 started with pid=32, OS id=1072
    to execute - SYS.KUPM$MCP.MAIN('SYS_EXPORT_SCHEMA_01', 'SYSTEM', 'KUPC$C_1_20070223151610', 'KUPC$S_1_20070223151610', 0);
    kupprdp: worker process DW01 started with worker id=1, pid=33, OS id=1077
    to execute - SYS.KUPW$WORKER.MAIN('SYS_EXPORT_SCHEMA_01', 'SYSTEM');
    Fri Feb 23 15:16:28 2007
    Thread 1 advanced to log sequence 1309
    Current log# 3 seq# 1309 mem# 0: /app/oracle/oradata/elop/redo03.log
    Fri Feb 23 15:20:29 2007
    The value (30) of MAXTRANS parameter ignored.
    kupprdp: master process DM00 started with pid=32, OS id=1526
    to execute - SYS.KUPM$MCP.MAIN('SYS_EXPORT_SCHEMA_01', 'SYSTEM', 'KUPC$C_1_20070223152029', 'KUPC$S_1_20070223152029', 0);
    kupprdp: worker process DW01 started with worker id=1, pid=33, OS id=1528
    to execute - SYS.KUPW$WORKER.MAIN('SYS_EXPORT_SCHEMA_01', 'SYSTEM');
    Fri Feb 23 22:15:35 2007
    Thread 1 advanced to log sequence 1310
    Current log# 1 seq# 1310 mem# 0: /app/oracle/oradata/elop/redo01.log
    Fri Feb 23 23:04:10 2007
    USER: terminating instance due to error 472
    Instance terminated by USER, pid = 7779
    Trace File - elop_lgwr_2312.trc
    /app/oracle/admin/elop/bdump/elop_lgwr_2312.trc
    Oracle Database 10g Release 10.2.0.2.0 - Production
    ORACLE_HOME = /app/oracle/lmes
    System name: Linux
    Node name: lmes-oracle2.ust.hk
    Release: 2.4.21-32.ELsmp
    Version: #1 SMP Fri Apr 15 21:17:59 EDT 2005
    Machine: i686
    Instance name: elop
    Redo thread mounted by this instance: 1
    Oracle process number: 6
    Unix process pid: 2312, image: [email protected] (LGWR)
    *** SERVICE NAME:() 2007-02-23 09:10:07.372
    *** SESSION ID:(331.1) 2007-02-23 09:10:07.372
    LGWR: Archivelog for thread 1 sequence 1308 will NOT be compressed
    tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x1)
    tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0x1)
    Maximum redo generation record size = 156160 bytes
    Maximum redo generation change vector size = 150672 bytes
    tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x10)
    tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0x10)
    *** 2007-02-23 15:16:27.116
    LGWR: Archivelog for thread 1 sequence 1309 will NOT be compressed
    *** 2007-02-23 22:15:35.383
    LGWR: Archivelog for thread 1 sequence 1310 will NOT be compressed
    Trace File - elop_ora_2336.trc
    /app/oracle/admin/elop/udump/elop_ora_2336.trc
    Oracle Database 10g Release 10.2.0.2.0 - Production
    ORACLE_HOME = /app/oracle/lmes
    System name: Linux
    Node name: lmes-oracle2.ust.hk
    Release: 2.4.21-32.ELsmp
    Version: #1 SMP Fri Apr 15 21:17:59 EDT 2005
    Machine: i686
    Instance name: elop
    Redo thread mounted by this instance: 1
    Oracle process number: 15
    Unix process pid: 2336, image: [email protected]
    *** SERVICE NAME:() 2007-02-23 09:10:05.988
    *** SESSION ID:(324.3) 2007-02-23 09:10:05.988
    Thread 1 checkpoint: logseq 1307, block 2, scn 27684035
    cache-low rba: logseq 1307, block 30724
    on-disk rba: logseq 1307, block 33205, scn 27699991
    start recovery at logseq 1307, block 30724, scn 0
    ----- Redo read statistics for thread 1 -----
    Read rate (ASYNC): 1240Kb in 0.03s => 40.38 Mb/sec
    Total physical reads: 4096Kb
    Longest record: 21Kb, moves: 0/1975 (0%)
    Change moves: 1/24 (4%), moved: 0Mb
    Longest LWN: 285Kb, moves: 0/245 (0%), moved: 0Mb
    Last redo scn: 0x0000.01a6ab16 (27699990)
    ----- Recovery Hash Table Statistics ---------
    Hash table buckets = 32768
    Longest hash chain = 2
    Average hash chain = 346/345 = 1.0
    Max compares per lookup = 1
    Avg compares per lookup = 4783/5281 = 0.9
    *** 2007-02-23 09:10:06.132
    KCRA: start recovery claims for 346 data blocks
    *** 2007-02-23 09:10:07.153
    KCRA: blocks processed = 346/346, claimed = 346, eliminated = 0
    *** 2007-02-23 09:10:07.154
    Recovery of Online Redo Log: Thread 1 Group 1 Seq 1307 Reading mem 0
    ----- Recovery Hash Table Statistics ---------
    Hash table buckets = 32768
    Longest hash chain = 2
    Average hash chain = 346/345 = 1.0
    Max compares per lookup = 2
    Avg compares per lookup = 3424/5126 = 0.7
    tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x1)
    tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0x1)
    Error in executing triggers on database startup
    *** 2007-02-23 09:10:11.557
    ksedmp: internal or fatal error
    ORA-00604: error occurred at recursive SQL level 1
    ORA-12663: Services required by client not available on the server
    ORA-36961: Oracle OLAP is not available.
    ORA-06512: at "SYS.OLAPIHISTORYRETENTION", line 1
    ORA-06512: at line 15
    Thanks & Regards,
    Liona

    Hi,
    I have the same error:
    I have gridcontrol 10gR3 installed on VM / Linux 4 AS box. This is second time down time:
    finally I found the DB tiers is down.
    I have the following message:
    Private_strands 18 at log switch
    Thread 1 advanced to log sequence 215
    Current log# 2 seq# 215 mem# 0: /u02/ora/gridcontrol10g/oradata/emrep/redo02.log
    Thu Apr 19 14:30:33 2007
    Private_strands 18 at log switch
    Thread 1 advanced to log sequence 216
    Current log# 3 seq# 216 mem# 0: /u02/ora/gridcontrol10g/oradata/emrep/redo03.log
    Thu Apr 19 15:42:34 2007
    Private_strands 18 at log switch
    Thread 1 advanced to log sequence 217
    Current log# 4 seq# 217 mem# 0: /u02/ora/gridcontrol10g/oradata/emrep/redo04.log
    Thu Apr 19 16:52:05 2007
    LGWR: terminating instance due to error 472
    Instance terminated by LGWR, pid = 26049
    Thu Apr 19 17:27:08 2007
    I have no idea why this happen. is it because DB is ona VM machine?
    I remember one time whe I took a snapshot on VM server, grid control services are down for a moment, 4 minutes, WebCache seemed cleaned, this page is gone, after 3 minutes, it comes back.
    Anyone has the same issue, please share your experience.
    Thanks a lot,
    Hank
    Message was edited by:
    Hank@AHM

  • Dbw0: terminating instance due to error 472

    Running RH linux 6.2, and EE 8.1.6.1.
    Am using MTS and have applied oracle's patch
    on the ora601 bug.
    HOwever I have come across a terminated instance with error 472 on two occasions. Both times I was running a soak test for first 15+ hrs and then 20+ hrs when the database crashed.
    Any ideas ?

    Alert Log :
    Current log# 14 seq# 31016 mem# 0: /db/prime/oradata/onlinelogs/redo14a.log
    Sun Apr 19 06:54:26 2009
    Thread 1 advanced to log sequence 31017
    Current log# 15 seq# 31017 mem# 0: /db/prime/oradata/onlinelogs/redo15a.log
    Sun Apr 19 06:59:01 2009
    Thread 1 advanced to log sequence 31018
    Current log# 11 seq# 31018 mem# 0: /db/prime/oradata/onlinelogs/redo11a.log
    Sun Apr 19 07:00:28 2009
    DBW0: terminating instance due to error 472
    Termination issued to instance processes. Waiting for the processes to exit
    Sun Apr 19 07:00:38 2009
    Instance termination failed to kill one or more processes
    Instance terminated by DBW0, pid = 331960
    Sun Apr 19 07:29:04 2009
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 3
    Autotune of undo retention is turned on.
    IMODE=BR

  • PMON: terminating instance due to error 471. database down

    Linux ES 2.6.9-78.0.5.EL #1 Wed Sep 24 05:29:49 EDT 2008 i686 i686 i386 GNU/Linux
    oracle 10.2.4
    Intiall version is 10.2.0. we have same problem in old version of oracle 10g. yesterday I have upgarded into 10.2.4.
    still the database is down due the following error . Please let me know the issues
    ue Aug 25 19:16:28 2009
    Errors in file /opt/app/oracle/admin/Test/bdump/test_pmon_20000.trc:
    ORA-00471: Message 471 not found; No message file for product=RDBMS, facility=ORA
    Tue Aug 25 19:16:28 2009
    PMON: terminating instance due to error 471
    Instance terminated by PMON, pid = 20000
    Wed Aug 26 10:22:11 2009

    In the trace file
    4AE1A660 00000000 00000000 6361726F 0000656C
    4AE1A670 00000000 00000000 00000000 00000000 [................]
    4AE1A680 00000000 00000000 00000006 662D6C76
    4AE1A690 30396E69 742E6264 6F706972 2E746E69
    4AE1A6A0 2E6D6F63 00007561 00000000 00000000
    4AE1A6B0 00000000 00000000 00000000 00000000 [................]
    4AE1A6C0 00000000 00000000 00000000 0000001A [................]
    4AE1A6D0 4E4B4E55 004E574F 00000000 00000000 [UNKNOWN.........]
    4AE1A6E0 00000000 00000000 00000000 00000000 [................]
    4AE1A6F0 00000008 30303032 00000036 00000000 [....20006.......]
    4AE1A700 00000000 00000000 00000000 00000005 [................]
    4AE1A710 6361726F 7640656C 69662D6C 6430396E
    4AE1A720 72742E62 696F7069 632E746E 612E6D6F
    4AE1A730 44282075 29305742 00000000 00000000
    4AE1A740 00000028 00000002 00000000 00000000 [(...............]
    4AE1A750 00000000 00000000 00000000 00000000 [................]
    Repeat 8 times
    4AE1A7E0 00000000 00000000 00000000 00000200 [................]
    4AE1A7F0 00000000 00000000 00000000 00000000 [................]
    4AE1A800 4AF80EE4 4AE1ADC0 4AE1A248 00000000 [...J...JH..J....]
    4AE1A810 4A045AA4 00000000 00000000 00000000 [.Z.J............]
    4AE1A820 00000000 00000000 00000000 00000000 [................]
    4AE1A830 4AE1A830 4AE1A830 00B80000 00B30000 [0..J0..J........]
    4AE1A840 000450D1 00043DC5 016F9355 00000000 [.P...=..U.o.....]
    4AE1A850 00000000 00000000 00000000 00000000 [................]
    4AE1A860 00000000 00000814 00000000 00000088 [................]
    4AE1A870 00000000 00000814 00000000 00000000 [................]
    4AE1A880 00000000 00000000 00000000 00000000 [................]
    Repeat 3 times
    4AE1A8C0 FFFFFFB6 00000006 [........]
    error 471 detected in background process
    ORA-00471: Message 471 not found; No message file for product=RDBMS, facility=ORA
    Edited by: user8680248 on 25/08/2009 18:53

  • LGWR: terminating instance due to error 321

    Hi,
    I received the below error and terminated oracle service's,How do i resolve it?
    version:oracle 9.2.0.1
    os : windows 2003
    Tue Aug 26 04:17:21 2008
    Errors in file e:\oracle\sales\admin\bdump\sales_lgwr_2292.trc:
    ORA-00321: log 1 of thread 1, cannot update log file header
    ORA-00312: online log 1 thread 1: 'E:\ORACLE\sales\ORADATA\REDO01.LOG'
    ORA-27091: skgfqio: unable to queue I/O
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
    Tue Aug 26 04:17:21 2008
    Errors in file e:\oracle\sales\admin\bdump\sales_lgwr_2292.trc:
    ORA-00321: log 1 of thread 1, cannot update log file header
    LGWR: terminating instance due to error 321
    Tue Aug 26 04:17:23 2008
    Errors in file e:\oracle\sales\admin\bdump\sales_pmon_2260.trc:
    ORA-00321: log of thread , cannot update log file header

    Hi,
    Looks like the lgwr can't write the logfile because this still on use.
    Can you please post the e:\oracle\sales\admin\bdump\sales_pmon_2260.trc information, also is your DB on archive log mode?
    can you run this script?
    set heading on
    set echo off
    set linesize 150
    set pagesize 500
    column day format a16 heading 'Dia'
    column d_0 format a3 heading '00'
    column d_1 format a3 heading '01'
    column d_2 format a3 heading '02'
    column d_3 format a3 heading '03'
    column d_4 format a3 heading '04'
    column d_5 format a3 heading '05'
    column d_6 format a3 heading '06'
    column d_7 format a3 heading '07'
    column d_8 format a3 heading '08'
    column d_9 format a3 heading '09'
    column d_10 format a3 heading '10'
    column d_11 format a3 heading '11'
    column d_12 format a3 heading '12'
    column d_13 format a3 heading '13'
    column d_14 format a3 heading '14'
    column d_15 format a3 heading '15'
    column d_16 format a3 heading '16'
    column d_17 format a3 heading '17'
    column d_18 format a3 heading '18'
    column d_19 format a3 heading '19'
    column d_20 format a3 heading '20'
    column d_21 format a3 heading '21'
    column d_22 format a3 heading '22'
    column d_23 format a3 heading '23'
    column Total format 9999
    column status format a8
    column member format a40
    column archived heading 'Archived' format a8
    column bytes heading 'Bytes|(MB)' format 9999
    Ttitle 'Log Info' skip 2
    select l.group#,f.member,l.archived,l.bytes/1078576 bytes,l.status,f.type
    from v$log l, v$logfile f
    where l.group# = f.group#
    Ttitle off
    prompt =========================================================================================================================
    Ttitle 'Log Switch on hour basis' skip 2
    select to_char(FIRST_TIME,'DY, DD-MON-YYYY') dia,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'00',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'00',1,0))) d_0,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'01',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'01',1,0))) d_1,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'02',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'02',1,0))) d_2,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'03',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'03',1,0))) d_3,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'04',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'04',1,0))) d_4,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'05',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'05',1,0))) d_5,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'06',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'06',1,0))) d_6,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'07',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'07',1,0))) d_7,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'08',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'08',1,0))) d_5,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'09',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'09',1,0))) d_9,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'10',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'10',1,0))) d_10,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'11',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'11',1,0))) d_11,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'12',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'12',1,0))) d_12,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'13',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'13',1,0))) d_13,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'14',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'14',1,0))) d_14,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'15',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'15',1,0))) d_15,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'16',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'16',1,0))) d_16,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'17',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'17',1,0))) d_17,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'18',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'18',1,0))) d_18,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'19',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'19',1,0))) d_19,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'20',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'20',1,0))) d_20,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'21',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'21',1,0))) d_21,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'22',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'22',1,0))) d_22,
    decode(sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'23',1,0)),0,'-',sum(decode(substr(to_char(FIRST_TIME,'HH24'),1,2),'23',1,0))) d_23,
    count(trunc(FIRST_TIME)) Total
    from v$log_history
    group by to_char(FIRST_TIME,'DY, DD-MON-YYYY')
    order by to_date(substr(to_char(FIRST_TIME,'DY, DD-MON-YYYY'),5,15) )
    Cheers,
    Francisco Munoz Alvarez
    www.oraclenz.com

Maybe you are looking for