3 Replies Latest reply on Nov 28, 2011 9:43 AM by Helios-GunesEROL

    PMON (ospid: 8143): terminating the instance due to error 472

    Athish
      Hi Friends,

      My Environment_

      OS : oel4u5
      Apps Version : R12.1.1
      DB Version : *11.1.0.7*

      When i am trying to start my ebiz 11g database the db started and its automatically going down because of PMON termination.  When am looking in to the alert log files its showing the below ora-600 errors,

      Resuming block recovery (PMON) for file 4 block 180627
      Block recovery from logseq 125, block 70 to scn 10132192035480
      Recovery of Online Redo Log: Thread 1 Group 2 Seq 125 Reading mem 0
      Mem# 0: /ebiz/oracle/db/apps_st/data/log2.dbf
      Block recovery completed at rba 125.281.16, scn 2359.364184220
      Errors in file /ebiz/oracle/db/tech_st/11.1.0/admin/TEST05_erptest05/diag/rdbms/test05/TEST05/trace/TEST05_pmon_8143.trc (incident=49647):
      ORA-00600: internal error code, arguments: [4194], [41], [37], [], [], [], [], [], [], [], [], []
      Errors in file /ebiz/oracle/db/tech_st/11.1.0/admin/TEST05_erptest05/diag/rdbms/test05/TEST05/trace/TEST05_pmon_8143.trc:
      ORA-00600: internal error code, arguments: [4194], [41], [37], [], [], [], [], [], [], [], [], []
      PMON (ospid: 8143): terminating the instance due to error 472
      Instance terminated by PMON, pid = 8143

      Following error which i found in the trace file /ebiz/oracle/db/tech_st/11.1.0/admin/TEST05_erptest05/diag/rdbms/test05/TEST05/trace/TEST05_pmon_8143.trc

      (call) sess: cur 5f1efd10, rec 5f1e5ff0, usr 5f1efd10; depth: 0
      ksudlc FALSE at location: 6
      (k2g table)
      error 472 detected in background process
      ORA-00600: internal error code, arguments: [4194], [41], [37], [], [], [], [], [], [], [], [], []
      *** 2011-11-27 20:19:33.113
      PMON (ospid: 8143): terminating the instance due to error 472

      Kindly Suggest me,

      Thanks
      Athish
        • 1. Re: PMON (ospid: 8143): terminating the instance due to error 472
          Helios-GunesEROL
          Hi;
          ORA-00600: internal error code,
          You are getting oracle internal error(ORA 600) which mean you could need to work wiht oracle support team. Please see below note, if its not help than i suggest log a sr asap:

          Troubleshoot an ORA-600 or ORA-7445 Error Using the Error Lookup Tool [ID 153788.1]

          Regard
          Helios
          • 2. Re: PMON (ospid: 8143): terminating the instance due to error 472
            Athish
            Hi Helios,

            We identified that the error was in undo corruption and We followed the below steps to over come above mention error.

            Steps as followed,

            Step 1:
            SQL> SELECT name,value FROM v$parameter WHERE name IN ('undo_management','undo_tablespace');

            NAME VALUE
            -------------------- --------------------
            undo_management MANUAL
            undo_tablespace UNDO_TBS

            Step2:
            SQL> select FILE_NAME, TABLESPACE_NAME from dba_data_files where TABLESPACE_NAME like 'UNDO%';

            FILE_NAME                         TABLESPACE_NAME
            ----------------------------------------------------------------
            /ebiz/oracle/db/apps_st/data/undotbs_02.dbf     UNDO_TBS
            /ebiz/oracle/db/apps_st/data/undotbs_01.dbf     UNDO_TBS

            Step 3: Create a new undo tablespace
            SQL> create UNDO tablespace UNDOTBS datafile '/ebiz/oracle/db/apps_st/data/undotbs01.dbf' size 1024m REUSE AUTOEXTEND ON NEXT 4096K MAXSIZE 1024M;
            Tablespace created.

            Step 4:
            SQL> ALTER SYSTEM SET undo_tablespace = 'UNDOTBS' scope=spfile;
            System altered.

            Step 5: set old undo tablespace offine mode and drop
            SQL> ALTER TABLESPACE UNDO_TBS offline;
            Tablespace altered.

            SQL> drop tablespace UNDO_TBS including contents and datafiles;
            Tablespace dropped.

            Step 6:
            Rebounced the db services

            Step 7: Changed the undo management parameter to AUTO
            SQL> alter system set undo_management='AUTO' scope=spfile;
            System altered.

            SQL> SELECT name,value FROM v$parameter WHERE name IN ('undo_management','undo_tablespace');

            NAME VALUE
            -------------------- --------------------
            undo_management AUTO
            undo_tablespace UNDOTBS

            Now the database is up and running with no issue and we cant find any ora error in the alert log file,

            ThaNks
            Athish
            • 3. Re: PMON (ospid: 8143): terminating the instance due to error 472
              Helios-GunesEROL
              Hi;

              Thanks for sharing steps Athish ;)

              Regard
              Helios