Encountered ORA-00600: internalerrorcode, arguments: [4194] ORA-155

Encountered ORA-00600: internalerrorcode, arguments: [4194] ORA-1552

Encountered ORA-00600: internal error code, arguments: [4194] ORA-1552

Reference

ORA-600 [4194] "Undo Record Number Mismatch While Adding Undo Record" (Document ID 39283.1)

ORA-01552 While Creating Undo Tablespace (Doc ID 443570.1)

Step by step to resolve ORA-600 4194 4193 4197 on database crash (Document ID 1428786.1)

When the database is started with CARSH, an error is reported.

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

The error is described as follows:

DESCRIPTION: A mismatch has been detected between Redo records and rollback (Undo) records. we are validating the Undo record number relating to the change being applied against the maximum undo record number recorded in the undo block. this error is reported when the validation fails. ARGUMENTS: Arg [a] Maximum Undo record number in Undo block Arg [B] Undo record number from Redo block

However, the following error occurs during actual processing:

The reason is as follows in the MOS document:

Disable the CDC trigger and then undo tablespace can be created successfully.

You need to disable the CDC trigger.

_ System_trig_enabled = false

SQL> conn/as sysdba

SQL> ALTER TRIGGER sys. cdc_alter_ctable_before DISABLE;

SQL> ALTER TRIGGER sys. cdc_create_ctable_after DISABLE;

SQL> ALTER TRIGGER sys. cdc_create_ctable_before DISABLE;

SQL> ALTER TRIGGER sys. cdc_drop_ctable_before DISABLE;

So the solution is summarized as follows (it is best to back up before processing ):

1. Shut down the database shutdown immediate

2. Start the database and run startup mount in the mount State to execute the following statements:

Alter system set "_ system_trig_enabled" = false scope = both;

Alter trigger sys. cdc_alter_ctable_before DISABLE;

Alter trigger sys. cdc_create_ctable_after DISABLE;

Alter trigger sys. cdc_create_ctable_before DISABLE;

Alter trigger sys. cdc_drop_ctable_before DISABLE;

3. Shut down the database shutdown immediate and restart it to the mount status again.

Modify parameters

Alter system set undo_management = manual scope = spfile;

Alter system set event = '2014 trace name context forever, level 2 'scope = spfile;

4. Shut down the database and start it to the startup restrict status,

1. shutdown immediate;

2. startup restrict;

5. View select tablespace_name, status, segment_name from dba_rollback_segs where status! = 'Offline'; indicates that a record exists. If a record exists, it can be

Create UNDO tablespace datafile 'file' size xxxM;

If MOS does not provide a processing step, you may need to set _ uploupted_rollback_segments as follows:

Restart and delete the rollback segments with these exceptions.

6. Delete the old UNDO tablespace, including the data file drop tablespace including contents and datafiles;

7. Shut down the database shutdown immediate and start it to the startup nomount status.

8. Modify the UNDO tablespace to create a new variable space. alter system set undo_tablespace = 'new _ undotablespace 'scope = spfile;

9. Restart the database shutdown immediate; startup;

10. Shut down the database, start to the mount status, and modify the parameters.

1. alter system set undo_management = auto scope = spfile;

2. alter system set event = ''scope = spfile;

3. alter system set "_ system_trig_enabled" = true scope = both;

11. Restart the database again.

This article permanently updates the link address: