ALLSTARS_ORACLE 发表于 2017-4-14 17:42:25

Ora-00604 ORA-01595 Ora-00607错误的解决


今天某省的数据库因停电,数据库不能启动,具体日志如下:
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       = 503316480
  __large_pool_size        = 16777216
  __java_pool_size         = 16777216
  __streams_pool_size      = 0
  sga_target               = 2147483648
  control_files            = /u01/app/oracle/oradata/orcl/control01.ctl, /u01/app/oracle/oradata/orcl/control02.ctl, /u01/app/oracle/oradata/orcl/control03.ctl
  db_block_size            = 8192
  __db_cache_size          = 1593835520
  compatible               = 10.2.0.1.0
  db_file_multiblock_read_count= 16
  db_recovery_file_dest    = /u01/app/oracle/flash_recovery_area
  db_recovery_file_dest_size= 4294967296
  undo_management          = AUTO
  undo_tablespace          = UNDOTBS1
  remote_login_passwordfile= EXCLUSIVE
  db_domain                =
  dispatchers              = (PROTOCOL=TCP) (SERVICE=orclXDB)
  job_queue_processes      = 10
  background_dump_dest     = /u01/app/oracle/admin/orcl/bdump
  user_dump_dest           = /u01/app/oracle/admin/orcl/udump
  core_dump_dest           = /u01/app/oracle/admin/orcl/cdump
  audit_file_dest          = /u01/app/oracle/admin/orcl/adump
  db_name                  = orcl
  open_cursors             = 300
  pga_aggregate_target     = 3361734656
PMON started with pid=2, OS id=13553
PSP0 started with pid=3, OS id=13555
MMAN started with pid=4, OS id=13557
DBW0 started with pid=5, OS id=13559
DBW1 started with pid=6, OS id=13561
DBW2 started with pid=7, OS id=13563
DBW3 started with pid=8, OS id=13565
LGWR started with pid=9, OS id=13567
CKPT started with pid=10, OS id=13569
SMON started with pid=11, OS id=13571
RECO started with pid=12, OS id=13573
CJQ0 started with pid=13, OS id=13575
MMON started with pid=14, OS id=13577
Wed Aug 28 19:20:38 2013
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=15, OS id=13579
Wed Aug 28 19:20:38 2013
starting up 1 shared server(s) ...
Wed Aug 28 19:20:38 2013
ALTER DATABASE   MOUNT
Wed Aug 28 19:20:43 2013
Setting recovery target incarnation to 1
Wed Aug 28 19:20:43 2013
Successful mount of redo thread 1, with mount id 1352456327
Wed Aug 28 19:20:43 2013
Database mounted in Exclusive Mode
Completed: ALTER DATABASE   MOUNT
Wed Aug 28 19:20:43 2013
ALTER DATABASE OPEN
Wed Aug 28 19:20:43 2013
Beginning crash recovery of 1 threads
parallel recovery started with 16 processes
Wed Aug 28 19:20:43 2013
Started redo scan
Wed Aug 28 19:20:43 2013
Completed redo scan
3019 redo blocks read, 35 data blocks need recovery
Wed Aug 28 19:20:43 2013
Started redo application at
Thread 1: logseq 830, block 57247
Wed Aug 28 19:20:43 2013
Recovery of Online Redo Log: Thread 1 Group 5 Seq 830 Reading mem 0
  Mem# 0 errs 0: /u01/app/oracle/oradata/orcl/redo05.log
Wed Aug 28 19:20:43 2013
Completed redo application
Wed Aug 28 19:20:43 2013
Completed crash recovery at
Thread 1: logseq 830, block 60266, scn 12893955839056
35 data blocks read, 0 data blocks written, 3019 redo blocks read
Wed Aug 28 19:20:43 2013
Thread 1 advanced to log sequence 831
Thread 1 opened at log sequence 831
  Current log# 1 seq# 831 mem# 0: /u01/app/oracle/oradata/orcl/redo01.log
Successful open of redo thread 1
Wed Aug 28 19:20:43 2013
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Wed Aug 28 19:20:43 2013
SMON: enabling cache recovery
Wed Aug 28 19:20:44 2013
Successfully onlined Undo Tablespace 1.
Wed Aug 28 19:20:44 2013
SMON: enabling tx recovery
Wed Aug 28 19:20:44 2013
Database Characterset is ZHS16GBK
Wed Aug 28 19:20:45 2013
Errors in file /u01/app/oracle/admin/orcl/udump/orcl_ora_13586.trc:
ORA-00600: internal error code, arguments: , , , [], [], [], [], []
Wed Aug 28 19:20:46 2013
Errors in file /u01/app/oracle/admin/orcl/bdump/orcl_smon_13571.trc:
ORA-00600: internal error code, arguments: , , , [], [], [], [], []
DEBUG: Replaying xcb 0xd862a508, pmd 0xd9532200 for failed op 8
Doing block recovery for file 2 block 2006
No block recovery was needed
Wed Aug 28 19:20:48 2013
Doing block recovery for file 2 block 2284
Block recovery from logseq 831, block 65 to scn 12893955839129
Wed Aug 28 19:20:48 2013
Recovery of Online Redo Log: Thread 1 Group 1 Seq 831 Reading mem 0
  Mem# 0 errs 0: /u01/app/oracle/oradata/orcl/redo01.log
Block recovery stopped at EOT rba 831.69.16
Block recovery completed at rba 831.69.16, scn 3002.464016536
Doing block recovery for file 2 block 73
Block recovery from logseq 831, block 65 to scn 12893955839127
Wed Aug 28 19:20:48 2013
Recovery of Online Redo Log: Thread 1 Group 1 Seq 831 Reading mem 0
  Mem# 0 errs 0: /u01/app/oracle/oradata/orcl/redo01.log
Block recovery completed at rba 831.69.16, scn 3002.464016536
Wed Aug 28 19:20:48 2013
Errors in file /u01/app/oracle/admin/orcl/bdump/orcl_smon_13571.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: , , , [], [], [], [], []
Wed Aug 28 19:20:50 2013
Errors in file /u01/app/oracle/admin/orcl/bdump/orcl_smon_13571.trc:
ORA-00600: internal error code, arguments: , , , [], [], [], [], []
Doing block recovery for file 2 block 1573
Block recovery from logseq 831, block 69 to scn 12893955839134
Wed Aug 28 19:20:52 2013
Recovery of Online Redo Log: Thread 1 Group 1 Seq 831 Reading mem 0
  Mem# 0 errs 0: /u01/app/oracle/oradata/orcl/redo01.log
Block recovery stopped at EOT rba 831.72.16
Block recovery completed at rba 831.72.16, scn 3002.464016541
Doing block recovery for file 2 block 25
Block recovery from logseq 831, block 69 to scn 12893955839132
Wed Aug 28 19:20:52 2013
Recovery of Online Redo Log: Thread 1 Group 1 Seq 831 Reading mem 0
  Mem# 0 errs 0: /u01/app/oracle/oradata/orcl/redo01.log
Block recovery completed at rba 831.72.16, scn 3002.464016541
Wed Aug 28 19:20:52 2013
Errors in file /u01/app/oracle/admin/orcl/bdump/orcl_smon_13571.trc:
ORA-01595: error freeing extent (3) of rollback segment (2))
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: , , , [], [], [], [], []
Wed Aug 28 19:21:24 2013
WARNING: inbound connection timed out (ORA-3136)
Wed Aug 28 19:25:07 2013
Errors in file /u01/app/oracle/admin/orcl/udump/orcl_ora_13586.trc:
ORA-00600: internal error code, arguments: , , , [], [], [], [], []
ORA-00600: internal error code, arguments: , , , [], [], [], [], []
Wed Aug 28 19:25:10 2013
Errors in file /u01/app/oracle/admin/orcl/ud

ALLSTARS_ORACLE 发表于 2017-4-14 17:43:00


通过查看trace文件,以及分析数据文件大小,初步判断数据库安装后就没有进行合理管理,这些所谓的DBA,哎,又我来处理,好吧,回去再收拾你们,先处理事情。以下这段很重要:从中看出问题所在,
----- Redo read statistics for thread 1 -----
Read rate (ASYNC): 93090Kb in 0.31s => 293.25 Mb/sec
Total physical reads: 93090Kb
Longest record: 32Kb, moves: 0/273011 (0%)
Change moves: 118544/592850 (19%), moved: 22Mb
Longest LWN: 1024Kb, moves: 22/13043 (0%), moved: 8Mb
Last redo scn: 0x0bba.1ba5e935 (12893955680565)
----------------------------------------------
*** 2013-08-28 19:20:46.365
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: , , , [], [], [], [], []
Current SQL statement for this session:
insert into smon_scn_time (thread, time_mp, time_dp, scn, scn_wrp, scn_bas,  num_mappings, tim_scn_map) values (0, :1, :2, :3, :4, :5, :6, :7)
----- Call Stack Trace -----
RA-00600: internal error code, arguments: , , , [], [], [], [], []
Current SQL statement for this session:
insert into smon_scn_time (thread, time_mp, time_dp, scn, scn_wrp, scn_bas,  num_mappings, tim_scn_map) values (0, :1, :2, :3, :4, :5, :6, :7)
----- Call Stack Trace -----


页: [1]
查看完整版本: Ora-00604 ORA-01595 Ora-00607错误的解决