Ora-00600:internal error code, arguments: [4194], [42], [41], [], [], [], [], [] Solution

Source: Internet
Author: User
Tags rollback

Come here this morning, found an instance of a database did not get up, so the start operation, but the strange is to start the normal, in a few seconds after the start of the system crashes, the process is not, in the SYS can restart, the START process all normal, but the phenomenon is the same. After viewing the Alert.log, you find the following information:

Sun Feb 25 10:49:28 2007
Starting ORACLE instance (normal)
license_max_session = 0
license_sessions_warning = 0
Picked Latch-free SCN Scheme 2
Using log_archive_dest_10 parameter default value as Use_db_recovery_file_dest
Autotune of undo retention is turned on.
Imode = BR
Ilat = 18
License_max_users = 0
SYS Auditing is disabled
Ksdpec:called for event 13740 prior to Event Group initialization
Starting up ORACLE RDBMS version:10.2.0.1.0.
System parameters with Non-default values:
processes = 150
__shared_pool_size = 117440512
__large_pool_size = 4194304
__java_pool_size = 4194304
__streams_pool_size = 0
Nls_language = American
Sga_target = 599785472
Control_files =/home/u01/app/oracle/oradata/orcl/control01.ctl,/home/u01/app/oracle/oradata/orcl/control0 2.ctl,/home/u01/app/oracle/oradata/orcl/control03.ctl
Db_block_size = 8192
__db_cache_size = 465567744
compatible = 10.2.0.1.0 db_file_multiblock_read_count= 16
Db_recovery_file_dest =/home/u01/app/oracle/flash_recovery_area
Db_recovery_file_dest_size= 2147483648
Undo_management = AUTO
Undo_tablespace = UNDOTBS1
Remote_login_passwordfile= EXCLUSIVE
Db_domain =
Dispatchers = (protocol=tcp) (SERVICE=ORCLXDB)
Job_queue_processes = 10
Background_dump_dest =/home/u01/app/oracle/admin/orcl/bdump
User_dump_dest =/home/u01/app/oracle/admin/orcl/udump
Core_dump_dest =/home/u01/app/oracle/admin/orcl/cdump
Audit_file_dest =/home/u01/app/oracle/admin/orcl/adump
Db_name = ORCL
Open_cursors = 300
Pga_aggregate_target = 199229440
Pmon started with pid=2, OS id=15504
Mman started with pid=4, OS id=15508
PSP0 started with pid=3, OS id=15506
DBW0 started with pid=5, OS id=15510
LGWR started with pid=6, OS id=15512
CKPT started with pid=7, OS id=15514
Smon started with pid=8, OS id=15516
Reco started with pid=9, OS id=15518
CJQ0 started with pid=10, OS id=15520
Mmon started with pid=11, OS id=15522
Sun Feb 25 10:49:32 2007
Starting up 1 Dispatcher (s) to network address ' (Address= (Partial=yes) (protocol=tcp)) ' ...
MMNL started with pid=12, OS id=15524
Sun Feb 25 10:49:32 2007
Starting up 1 Shared server (s) ... Sun Feb 25 10:49:33 2007
ALTER DATABASE MOUNT
Sun Feb 25 10:49:38 2007
Setting recovery target incarnation to 2
Sun Feb 25 10:49:38 2007
Successful mount of Redo thread 1 with Mount ID 1143260989
Sun Feb 25 10:49:38 2007
Database mounted in Exclusive Mode
Completed:alter DATABASE MOUNT
Sun Feb 25 10:49:38 2007
ALTER DATABASE OPEN
Sun Feb 25 10:49:38 2007
Beginning crash recovery of 1 threads
Parallel recovery started with 3 processes
Sun Feb 25 10:49:38 2007
Started Redo scan
Sun Feb 25 10:49:38 2007
Completed Redo Scan
2215 Redo blocks read, data blocks need recovery
Sun Feb 25 10:49:39 2007
Started Redo application at
Thread 1:logseq 1050, block 92122
Sun Feb 25 10:49:39 2007
Recovery of Online Redo log:thread 1 Group 2 Seq 1050 Reading MEM 0
mem# 0 errs 0:/home/u01/app/oracle/oradata/orcl/redo02.log
Sun Feb 25 10:49:39 2007
Recovery of Online Redo log:thread 1 Group 3 Seq 1051 Reading Mem 0
mem# 0 errs 0:/home/u01/app/oracle/oradata/orcl/redo03.log
Sun Feb 25 10:49:39 2007
Completed Redo Application
Sun Feb 10:49:39 2007 Completed crash Recovery at
Thread 1:logseq 1051, block 1174, SCN 4827420640
Data blocks read, data blocks written, 2215 redo blocks Read
Sun Feb 25 10:49:39 2007
Thread 1 advanced to log sequence 1052
Thread 1 opened at log sequence 1052
Current log# 1 seq# 1052 mem# 0:/home/u01/app/oracle/oradata/orcl/redo01.log
Successful open of Redo thread 1
Sun Feb 25 10:49:39 2007
MTTR advisory is disabled because fast_start_mttr_target are not set
Sun Feb 25 10:49:39 2007
Smon:enabling Cache Recovery
Sun Feb 25 10:49:41 2007
Successfully onlined Undo tablespace 1.
Sun Feb 25 10:49:41 2007
smon:enabling TX Recovery
Sun Feb 25 10:49:41 2007
Database Characterset is UTF8
Replication_dependency_tracking turned off (no async multimaster replication found)
Starting background Process QMNC
QMNC started with pid=19, OS id=15538
Sun Feb 25 10:49:49 2007
Db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
User-specified limit on the amount of spaces that'll be used by this
Database for recovery-related files, and does not reflect the amount of
Spaces available in the underlying filesystem or ASM DiskGroup.
Sun Feb 25 10:49:49 2007
Completed:alter DATABASE OPEN Sun Feb 25 10:49:53 2007
Errors in FILE/HOME/U01/APP/ORACLE/ADMIN/ORCL/BDUMP/ORCL_J002_15544.TRC:
Ora-00600:internal error code, arguments: [4194], [42], [41], [], [], [], [], []
Sun Feb 25 10:49:55 2007
Doing block recovery to file 2 block 6132
Block recovery from Logseq 1052, blocks 136 to SCN 4827422434
Sun Feb 25 10:49:55 2007
Recovery of Online Redo log:thread 1 Group 1 Seq 1052 Reading Mem 0
mem# 0 errs 0:/home/u01/app/oracle/oradata/orcl/redo01.log
Block recovery completed at RBA 1052.5592.16, SCN 1.532455139
Doing block recovery to file 2 block 41
Block recovery from Logseq 1052, blocks to SCN 4827420772
Sun Feb 25 10:49:55 2007
Recovery of Online Redo log:thread 1 Group 1 Seq 1052 Reading Mem 0
mem# 0 errs 0:/home/u01/app/oracle/oradata/orcl/redo01.log
Block recovery completed at RBA 1052.136.16, SCN 1.532453477
Sun Feb 25 10:49:57 2007
Errors in FILE/HOME/U01/APP/ORACLE/ADMIN/ORCL/BDUMP/ORCL_J000_15540.TRC:
Ora-00600:internal error code, arguments: [4194], [42], [41], [], [], [], [], []
Sun Feb 25 10:49:58 2007
Debug:replaying xcb 0x4261f68c, PMD 0x427dde28 for failed op 8
Doing block recovery to file 2 block 6132
Block recovery from Logseq 1052, blocks 136 to SCN 4827422434
Sun Feb 25 10:49:58 2007
Recovery of Online Redo log:thread 1 Group 1 Seq 1052 Reading Mem 0
mem# 0 errs 0:/home/u01/app/oracle/oradata/orcl/redo01.log
Block recovery completed at RBA 1052.5592.16, SCN 1.532455139
Sun Feb 25 10:50:02 2007
Errors in FILE/HOME/U01/APP/ORACLE/ADMIN/ORCL/BDUMP/ORCL_J000_15540.TRC:
Ora-00600:internal error code, arguments: [4194], [42], [41], [], [], [], [], []
Ora-00600:internal error code, arguments: [4194], [42], [41], [], [], [], [], []
Errors in FILE/HOME/U01/APP/ORACLE/ADMIN/ORCL/BDUMP/ORCL_J000_15540.TRC:
Ora-00600:internal error code, arguments: [4194], [42], [41], [], [], [], [], []
Ora-00600:internal error code, arguments: [4194], [42], [41], [], [], [], [], []
Sun Feb 25 10:50:13 2007
Debug:replaying xcb 0x4261f68c, PMD 0x427dde28 for failed op 8
Doing block recovery to file 2 block 6132
Block recovery from Logseq 1052, blocks 136 to SCN 4827422434
Sun Feb 25 10:50:13 2007
Recovery of Online Redo log:thread 1 Group 1 Seq 1052 Reading Mem 0
mem# 0 errs 0:/home/u01/app/oracle/oradata/orcl/redo01.log
Block recovery completed at RBA 1052.5592.16, SCN 1.532455139
Sun Feb 25 10:50:15 2007
Thread 1 cannot allocate new log, sequence 1053
Private Strand Flush Not complete
Current log# 1 seq# 1052 mem# 0:/home/u01/app/oracle/oradata/orcl/redo01.log
Sun Feb 25 10:50:18 2007
Errors in FILE/HOME/U01/APP/ORACLE/ADMIN/ORCL/BDUMP/ORCL_DBW0_15510.TRC:
Ora-00600:internal error code, arguments: [4194], [42], [41], [], [], [], [], []
Sun Feb 25 10:50:18 2007
Errors in FILE/HOME/U01/APP/ORACLE/ADMIN/ORCL/BDUMP/ORCL_DBW0_15510.TRC:
Ora-00600:internal error code, arguments: [4194], [42], [41], [], [], [], [], []
Sun Feb 25 10:50:18 2007
Dbw0:terminating instance due to error 471
Instance terminated by DBW0, PID = 15510
Sun Feb 25 10:55:31 2007
Starting ORACLE instance (normal)
license_max_session = 0
license_sessions_warning = 0
Picked Latch-free SCN Scheme 2
Using log_archive_dest_10 parameter default value as Use_db_recovery_file_dest
Autotune of undo retention is turned on.
Imode=br

Analysis log found main reported: ora-00600:internal error code, arguments: [4194], [42], [41], [], [], [], [], []

Refer to the relevant information on Metalink for the following error message: 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 to the undo block.

This error was reported when the validation fails.

ARGUMENTS:
Arg [A] Maximum undo record number in Undo block
Arg [b] Undo record number from Redo block

IMPACT:
PROCESS failure
POSSIBLE ROLLBACK SEGMENT corruption

Suggestions:

This is the error may indicate a rollback segment corruption.

This could require a recovery from a database backup depending on
The situation.

The first time I used the recover database until cancel and ALTER DATABASE open Resetlogs, the results were still wrong.

Through several cases on the network, the feeling of possible ROLLBACK SEGMENT corruption is not large, so the method of rebuilding undo is adopted.

The second operation method is as follows: Sql> startup Mount
ORACLE instance started.

Total System Global area 599785472 bytes
Fixed Size 1220772 bytes
Variable Size 125833052 bytes
Database buffers 465567744 bytes
Redo buffers 7163904 bytes
Database mounted.
sql> Create undo tablespace undotbs02 datafile '/home/u01/app/oracle/oradata/orcl/undotbs02.dbf ' size 100m
2;
Create undo tablespace undotbs02 datafile '/home/u01/app/oracle/oradata/orcl/undotbs02.dbf ' size 100m
*
ERROR at line 1:
Ora-01109:database not open


Sql> select name from V$datafile;

NAME
--------------------------------------------------------------------------------
/home/u01/app/oracle/oradata/orcl/system01.dbf
/home/u01/app/oracle/oradata/orcl/undotbs01.dbf
/home/u01/app/oracle/oradata/orcl/sysaux01.dbf
/home/u01/app/oracle/oradata/orcl/users01.dbf

sql> ALTER DATABASE datafile '/home/u01/app/oracle/oradata/orcl/undotbs

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.