PMON: terminating instance due to error 472

ORA-00600: internal error code, arguments: [4194], [41], [37], [], [], [], [], [], [], [], [], []

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

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

Steps to change undo tablespace as followed:

Step 1: Check the Undo Parameters

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

undo_management MANUAL
undo_tablespace UNDO_TBS

Step 2: Check the Undo Tablespace file information.

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

-------------------------- ---------------
/oracle/data/undotbs_02.dbf UNDO_TBS
/oracle/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: Set the undo tablespace to new one created in previous step.

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

Step 5: Set old undo tablespace offline mode and then drop it.

Tablespace altered.

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

Step 6: Restart 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');

undo_management AUTO
undo_tablespace UNDOTBS

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.