Troubleshooting Tips For Instance Shutdown Due To Error 472 11g

This guide was created to help you when you terminate an instance due to the “Error 472 11g” error code.

ORA-00600: Marketing Manager Internal Error, Args: [4194], [41], [37], [], [], [], [], [], [], [], [] , [ ]

We have determined that the error is indeed undo corruption and have taken the following steps to fix the mention error.

Step 1: Check your undo settings

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

NAME to VALUE
————————–
undo_management MANUAL
undo_tablespace UNDO_TBS

Step 2: Check the undo tablespace file information.

SQL>FILE_NAME, select TABLESPACE_NAME from dba_data_files where TABLESPACE_NAME is like "UNDO%";

FILE_NAME TABLESPACE_NAME
———————-
/oracle/data/undotbs_02.dbf UNDO_TBS
/oracle/data/undotbs_01.dbf UNDO_TBS

Step 3: Create a recovery tablespace

SQL> Create UNDO UNDOTBS tablespace data file '/ebiz/oracle/db/apps_st/data/undotbs01.dbf' size 1024m AUTOEXTEND reuse ON NEXT 4096K MAXSIZE 1024M;
The tablespace has been created.

Step 6: In the previous step, specify a separate recreation of the undo tablespace.

SQL> ALTER SYSTEM SET undo_tablespace = 'UNDOTBS' scope=spfile;
The system has changed.

Step 5: Old RiverPress Set reverse tablespace offline and then even lower. AGE

sql> TABLESPACE UNDO_TBS offline;
The tablespace has changed. Drop

sql>UNDO_TBS tablespace including contents and data files;
Tablespace removed.

Step 6: Restart these services

db step 7: Change the undo application setting to AUTO

SQL> change system mapping undo_management='AUTO' scope=spfile;
The system has been changed.

terminating the instance due to error 472 11g

If the pmon user corrupted the process with kill -9
terminating the instance due to error 472 11g, you should get this error in this warning log file.

The Oracle instance was automatically stopped after the instance was started due to the following Oracle error mentioned:

Reason:
Anomaly detected. Repeat between entries and even undo (undo) entries.
We check the undo record number of the applied change against the undo record number recorded in the reverse block. This error is reported even if validation fails. This error may indicate a corrupted segment.
Note. Depending on the situationYou may need to restore from a database backup.

Error in file /u01/app/oracle/diag/rdbms/db1/db1/trace/db1_smon_11168.trc (incident=1014790):ORA-00600: major error code, args: [4194],[],[],[],[],[],[],[],[],[],[],[]replication_dependency_tracking disabled (multi-master asynchronous replication not found)Incident details in: /u01/app/oracle/diag/rdbms/db1/db1/incident/incdir_1014790/db1_smon_11168_i1014790.trc2016-06-30 11:13:35.355000 +05:30Start QMNC background processQMNC started with pid=25, OS ID=11249ARC3: archiving startedARC0: STARTING FULL ARCH PROCESSESCompleted: CHANGE DATABASE OPEN2016-06-30 11:13:36.558000 from +05:30db_recovery_file_dest_size 163840 MB is used at 1.12%. Usually thisconfigurable limit on the amount of free space useddatabase for recovery-related files and never reflects the numberavailable space in the underlying file system or ASM disk group.Execute recovery lock on file 3 with restrictions 26014Recovery Block Resume (PMON) for Application Block 3 26014Block fetch via logseq 13618, block 56 in scn 3980712372Select to Online Redo Log: Thread First, Group 1, Sequence13618, memory read 0 Storage #0: /u02/oradata/db1/redo_1_1.log Repository number individually: /u02/oradata/db1/redo_1_2.log Storage #2: /u02/oradata/db1/redo_1_3.logBlock dependency recovery stopped at EOT rba 13618.106.16Block recovery from RBA 13618.106.16 completed, scn 0.3980712368Stop file recovery 3 die 160Resume Block Recovery (PMON) to recover multiple file blocks 160Block from logseq 13618, stub 56 on scn 3980712329Network Redo Log Recovery: Thread 1, Group 1, Sequence 13618, Memory Read 0 Storage #0: /u02/oradata/db1/redo_1_1.log Storage #1: /u02/oradata/db1/redo_1_2.log Storage #2: /u02/oradata/db1/redo_1_3.logBlock fetch succeeded rba at 13618.59.16, scn 0.3980712330Error in file /u01/app/oracle/diag/rdbms/db1/db1/trace/db1_smon_11168.trc:ORA-01595: debug extension (10) connected to cancel segment (3))ORA-00600: internal error signal, args: [4194],[],[],[],[],[],[],[],[],[],[],[]Running a background SMCO processSMCO is running pid=29 with OS ID=11268.The trace dump is involved in id=[cdmp_20160630111337]2016-06-30 11:13:37.819000 background +05:30CJQ0 loading processCJQ0 started with pid=28, OS ID=112762016-06-30 11:13:41.579000 +05:30Error in file /u01/app/oracle/diag/rdbms/db1/db1/trace/db1_j001_11285.trc (incident=1014942):ORA-00600: Device error code, args: [4194],[],[],[],[],[],[],[],[],[],[],[ ]Incident details /u01/app/oracle/diag/rdbms/db1/db1/incident/incdir_1014942/db1_j001_11285_i1014942 in: .trc/u01/app/oracle/diag/rdbms/db1/db1/trace/db1_j004_11291.trc file error:2016-06-30 11:13:43.111000 +05:30Time block for restoring sheet 3 district 26014 in progressResume recovery block (PMON) for file or possibly block 26014Get block logseq 13618 st 56 in scn 3980712372Recovery to online redo log: Thread 1 Group 1 Seq 13618 Read Memory 0 Storage #0: /u02/oradata/db1/redo_1_1.log Storage #1: /u02/oradata/db1/redo_1_2.log Storage #2: /u02/oradata/db1/redo_1_3.logBlock rba restore on 13618.106.16, scn 0.3980712374 politeError in report /u01/app/oracle/diag/rdbms/db1/db1/trace/db1_j000_11283.trc (incident=1014934):ORA-00600: internal error code, Threads: [4194], [], [], [], [], [], [], [], [], [], [], []Incident functions in: /u01/app/oracle/diag/rdbms/db1/db1/incident/incdir_1014934/db1_j000_11283_i1014934.trcTrace dump only id=[cdmp_20160630111343]2016-06-30 performance 11:13:45.937000 +05:30File recovery block 3, block 26014Recovery Resume Prevention (PMON) for File 3, Obstruction 26014Getting block from logseq 13618, block sixty in scn 3980712372extractionnetwork redo log: Thread 1 Group 1 Seq 13618 Reading mem 0 Storage #4: /u02/oradata/db1/redo_1_1.log Storage #1: /u02/oradata/db1/redo_1_2.log Storage# Step 2: /u02/oradata/db1/redo_1_3.logFinished restoring rba block from 13618.106.16, scn 0.3980712374Error in file /u01/app/oracle/diag/rdbms/db1/db1/trace/db1_j000_11283.trc:ORA-00600: internal error code, args: [4194],[],[],[],[],[],[],[],[],[],[],[]Error in document /u01/app/oracle/diag/rdbms/db1/db1/trace/db1_j001_11285.trc (incident=1014943):ORA-00600: internal error code, args: [4194],[],[],[],[],[],[],[],[],[],[],[]ORA-00600: internal error code, args: [4194],[],[],[],[],[],[],[],[],[],[],[]Incident details in: /u01/app/oracle/diag/rdbms/db1/db1/incident/incdir_1014943/db1_j001_11285_i1014943.trc2016-06-30 11:13:46.903000 +05:30The trace dump must have id = [cdmp_20160630111346].2016-06-30 11:13:48.279000 +05:30Error in file /u01/app/oracle/diag/rdbms/db1/db1/trace/db1_j001_11285.trc:ORA-00600: internal error code, args: [4194],[],[],[],[],[],[],[],[],[],[],[]ORA-00600: internal error codes, arguments: [4194],[],[],[],[],[],[],[],[],[],[],[]Run trace dump: id=[cdmp_20160630111349]Incident notification in: /u01/app/oracle/diag/rdbms/db1/db1/incident/incdir_1019488/db1_j001_11285_i1019488.trcError in file /u01/app/oracle/diag/rdbms/db1/db1/incident/incdir_1019488/db1_j001_11285_i1019488.trc:ORA-00603: ORACLE server session terminated due to dangerous errorORA-00600: insideLower error code, arguments: [4194],[],[],[],[],[],[],[],[],[],[],[]ORA-00600: internal error code, args: [4194],[],[],[],[],[],[],[],[],[],[],[]Running a trace dump will be id=[cdmp_20160630111351]2016-06-30 11:13:53.489000 +05:30Do

Zakończenie Instancji Z Powodu Błędu 472 11g
De Instantie Beëindigen Vanwege Fout 472 11g
Terminar La Instancia Debido Al Error 472 11g
Avsluta Instansen På Grund Av Fel 472 11g
Beenden Der Instanz Aufgrund Von Fehler 472 11g
Завершение экземпляра из-за ошибки 472 11g
Résiliation De L'instance En Raison D'une Erreur 472 11g
Encerrando A Instância Devido Ao Erro 472 11g
오류 472 11g로 인한 인스턴스 종료
Chiusura Dell'istanza A Causa Di Un Errore 472 11g