标签云
asm恢复 bbed bootstrap$ dul kcbzib_kcrsds_1 kccpb_sanity_check_2 kcratr_nab_less_than_odr MySQL恢复 obet ORA-00312 ORA-00704 ORA-00742 ORA-01110 ORA-01200 ORA-01555 ORA-01578 ORA-01595 ORA-600 2662 ORA-600 2663 ORA-600 3020 ORA-600 4000 ORA-600 4137 ORA-600 4193 ORA-600 4194 ORA-600 16703 ORA-600 kcbzib_kcrsds_1 ORA-600 KCLCHKBLK_4 ORA-600 kcratr_nab_less_than_odr ORA-15042 ORA-15196 ORACLE 12C oracle dul ORACLE PATCH Oracle Recovery Tools oracle加密恢复 oracle勒索 oracle勒索恢复 oracle异常恢复 ORACLE恢复 Oracle 恢复 ORACLE数据库恢复 oracle碎片 OSD-04016 YOUR FILES ARE ENCRYPTED 比特币加密文章分类
- MongoDB (1)
- MongoDB恢复 (1)
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (112)
- 数据库 (1,885)
- DB2 (22)
- MySQL (82)
- Oracle (1,710)
- Data Guard (53)
- EXADATA (8)
- GoldenGate (24)
- ORA-xxxxx (168)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (15)
- ORACLE 21C (3)
- Oracle 23ai (8)
- Oracle ASM (73)
- Oracle Bug (8)
- Oracle RAC (56)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (29)
- Oracle备份恢复 (663)
- Oracle安装升级 (108)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (91)
- PostgreSQL (37)
- pdu工具 (7)
- PostgreSQL恢复 (13)
- SQL Server (34)
- SQL Server恢复 (14)
- TimesTen (7)
- 达梦数据库 (5)
- 达梦恢复 (3)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (51)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (34)
- MongoDB (1)
-
最近发表
- 恢复案例分享:win丢失数据文件恢复
- 记录19c ASM磁盘掉线触发ORA-59048故障处理
- aix平台Oracle数据库由于断电无法启动故障处理
- 断电引起ORA-600 3005故障处理
- 记录一次云存储资源到期之后引起的数据库恢复
- Firebird 损坏数据库数据抢救工具—firebirdext
- Oracle 19c 202610补丁(RUs+OJVM)-19.33
- 由于con$.con#值达到极限,触发数据库增加约束报ORA-600 12807错误
- MongoDB 离线提取工具—mongoext
- .bres勒索病毒加密数据库dmp文件可恢复
- ORA-600 krsm_mrp_rebuild_lf_list.lno_mismatch
- 记录一次0丢失的ORA-00354: 损坏重做日志块标头故障恢复
- 不当数据库恢复操作导致一个月数据丢失
- obet快速修复oracle 位图损坏块
- 不太常见的10.2.0.1的oracle redo损坏恢复
- obet forcecopy功能抢救硬件故障中的数据文件
- kcratr_nab_less_than_odr和system坏块故障处理
- 通过obet 恢复system坏块,打开数据库
- obet dbv功能完整说明
- 分享一例运行在aix上的sap系统数据库恢复过程
分类目录归档:ORA-xxxxx
ORA-01555 caused by SQL statement below
一.发现ORA-01555
Mon Dec 26 10:08:22 2011
ORA-01555 caused by SQL statement below (Query Duration=49146 sec, SCN: 0x0b4b.17f5ae42):
Mon Dec 26 10:08:22 2011
SELECT COMPANY_ID,
COMPANY_MOBILE,
TO_CHAR(NVL(REG_DATE, SYSDATE - 100), 'yyyymmddhh24miss'),
BAK_FIELD2
FROM TAB_XN_COMPANY
WHERE (COMPANY_STATUS = 1 OR
(COMPANY_STATUS = 3 AND
NVL(UNREG_DATE, SYSDATE + 100) >=
TO_DATE('20111226094500', 'yyyymmddhh24miss')))
AND NVL(REG_DATE, SYSDATE - 100) <=
TO_DATE('20111226095959', 'yyyymmddhh24miss')
AND PAY_TYPE > 0
二.数据库状态
[oracle@ora02 ~]$ sqlplus "/ as sysdba"
SQL*Plus: Release 9.2.0.4.0 - Production on Wed Jan 4 10:48:17 2012
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.4.0 - Production
SQL> show parameter undo;
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
undo_management string AUTO
undo_retention integer 10800
undo_suppress_errors boolean FALSE
undo_tablespace string UNDOTBS1
SQL> select sum(maxbytes)/1024/1024/1024,
2 SUM(USER_BYTES)/1024/1024/1024 FROM dba_data_files where tablespace_NAME='UNDOTBS1';
SUM(MAXBYTES)/1024/1024/1024 SUM(USER_BYTES)/1024/1024/1024
---------------------------- ------------------------------
61.9999847 32.6834106
SQL> SELECT DISTINCT STATUS "状态",
2 COUNT(*) "EXTENT数量",
3 SUM(BYTES) / 1024 / 1024 / 1024 "UNDO大小"
4 FROM DBA_UNDO_EXTENTS
5 GROUP BY STATUS;
状态 EXTENT数量 UNDO大小
--------- ---------- ----------
ACTIVE 1 .000976563
EXPIRED 2549 31.2333298
UNEXPIRED 3 .000175476
通过undo_retention保留时间为10800秒,而该sql执行了49146秒,在这49146秒钟,TAB_XN_COMPANY表中的数据被修改,而且被修改的undo数据在10800秒后被覆盖导致,导致原查询语句不能获取到scn小于或者等于查询时候的数据块内容(在undo中),所以出现ORA-01555。从这里也可以看出来,在undo空间还剩余的情况下,如果超过了undo_retention限制,undo内容还是有可能被覆盖,而不是使用未使用的undo
三.出现ORA-1555原因
The ORA-1555 errors can happen when a query is unable to access enough undo to build a copy of the data at the time the query started. Committed “versions” of blocks are maintained along with newer uncommitted “versions” of those blocks so that queries can access data as it existed in the database at the time of the query. These are referred to as “consistent read” blocks and are maintained using Oracle undo management.
就是一个查询要访问某个数据块,而这个数据块在这个查询执行过程中修改过,那么该查询需要查询undo中数据块,而undo中该数据块已经不存在,从而出现ORA-1555
四.ORA-1555解决方法
Case 1 – Rollback Overwritten
1.缩短sql运行时间
2.增加undo_retention,这个同时需要考虑undo空间大小
3.减少commit(rollback)次数
4.在一条sql中尽量使数据块访问一次
4.1)Using a full table scan rather than an index lookup
4.2)Introducing a dummy sort so that we retrieve all the data, sort it and then sequentially visit these data blocks.
Case 2 – Rollback Transaction Slot Overwritten
这种问题,主要是延迟块清理导致,一般建议在进行大批量的dml操作后,使用全表(全index)扫描执行一遍,或者收集全部统计信息
ORA-07445[kslgetl()+120]/ORA-00108错误解决
一.数据库版本
SQL> select * from v$version; BANNER ---------------------------------------------------------------- Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi PL/SQL Release 10.2.0.4.0 - Production CORE 10.2.0.4.0 Production TNS for Linux: Version 10.2.0.4.0 - Production NLSRTL Version 10.2.0.4.0 - Production
二.alert中发现ORA-07445[kslgetl()+120]/ORA-00108错误
Mon Dec 19 09:19:42 2011 found dead dispatcher 'D000', pid = (13, 1) Mon Dec 19 09:19:42 2011 dispatcher 'D000' encountered error getting listening address Mon Dec 19 09:19:42 2011 Errors in file /opt/oracle/admin/gaxt/bdump/gaxt_ora_16297.trc: ORA-07445: exception encountered: core dump [kslgetl()+120] [SIGSEGV] [Address not mapped to object] [0x000000208] [] [] ORA-00108: failed to set up dispatcher to accept connection asynchronously Mon Dec 19 09:19:45 2011 found dead dispatcher 'D000', pid = (21, 2) Mon Dec 19 09:19:45 2011 dispatcher 'D000' encountered error getting listening address Mon Dec 19 09:19:45 2011 Errors in file /opt/oracle/admin/gaxt/bdump/gaxt_ora_16299.trc: ORA-07445: exception encountered: core dump [kslgetl()+120] [SIGSEGV] [Address not mapped to object] [0x000000208] [] [] ORA-00108: failed to set up dispatcher to accept connection asynchronously
三.trace文件信息
Oracle process number: 15
Unix process pid: 10607, image: oracle@gongantest (D000)
Warning: keltnfy call to ldmInit failed with error 46
*** 2011-12-19 19:21:40.100
network error encountered getting listening address:
NS Primary Error: TNS-12533: TNS:illegal ADDRESS parameters
NS Secondary Error: TNS-12560: TNS:protocol adapter error
NT Generic Error: TNS-00503: Illegal ADDRESS parameters
OPIRIP: Uncaught error 108. Error stack:
ORA-00108: failed to set up dispatcher to accept connection asynchronously
Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object), addr: 0x208, PC: [0x7a06b8, kslgetl()+120]
*** 2011-12-19 19:21:40.107
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [kslgetl()+120] [SIGSEGV] [Address not mapped to object] [0x000000208] [] []
ORA-00108: failed to set up dispatcher to accept connection asynchronously
Current SQL information unavailable - no session.
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedst()+31 call ksedst1() 000000000 ? 000000001 ?
2B91BE8F7D50 ? 2B91BE8F7DB0 ?
2B91BE8F7CF0 ? 000000000 ?
ksedmp()+610 call ksedst() 000000000 ? 000000001 ?
2B91BE8F7D50 ? 2B91BE8F7DB0 ?
2B91BE8F7CF0 ? 000000000 ?
ssexhd()+629 call ksedmp() 000000003 ? 000000001 ?
2B91BE8F7D50 ? 2B91BE8F7DB0 ?
2B91BE8F7CF0 ? 000000000 ?
__restore_rt()+0 call ssexhd() 00000000B ? 2B91BE8F8D70 ?
2B91BE8F8C40 ? 2B91BE8F7DB0 ?
2B91BE8F7CF0 ? 000000000 ?
kslgetl()+120 signal __restore_rt() 0600E7560 ? 0000000E8 ?
09AAE5728 ? 0000009A9 ?
000003980 ? 09AAE5740 ?
ksfglt()+108 call kslgetl() 0600E7560 ? 000000001 ?
09AAE5728 ? 0000009A9 ?
000003980 ? 09AAE5740 ?
四.在MOS上找到相关文章[ID 1298804.1]
Applies to: Oracle Server - Enterprise Edition - Version: 11.1.0.6 to 11.1.0.7 - Release: 11.1 to 11.1 Information in this document applies to any platform. Symptoms The following errors are seen in the trace file written by an ORA-7445 [kslgetl]: network error encountered getting listening address: NS Primary Error: TNS-12533: TNS:illegal ADDRESS parameters NS Secondary Error: TNS-12560: TNS:protocol adapter error NT Generic Error: TNS-00503: Illegal ADDRESS parameters OPIRIP: Uncaught error 108. Error stack: ORA-00108: failed to set up dispatcher to accept connection asynchronously Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object), addr: 0x130, PC: [0x82f09dc, kslgetl()+80] The trace file indicates that there is no session: Current SQL information unavailable - no session. The Call Stack Trace in the ORA-7445 trace file contains a function list similar to: kslgetl <- PGOSF57_ksfglt <- kghfre <- kmnsbf <- nsbfr <- nsiofrrg <- nsiocancel <- nsopen_shutitdown <- nsclose <- nsgblclose <- nsgblTRMHelper <- nsgblRealTerm <- nlstdstp <- npinlt <- ksuabt <- opidrv <- sou2o <- opimai_real <- main <- libc_start_main Cause The trace file first reports: Warning: keltnfy call to ldmInit failed with error 46 The ORA-7445 is not the starting point here. This exception is just a spin-off from ORA-180 and it is possible that different internal errors may be seen, such as ORA-600 [504], depending on what is happening when the ORA-180 is encountered. The cause for the ORA-180 is related to the inital message at the beginning of the trace file: "keltnfy call to ldmInit failed with error 46" and this is followed by: "network error encountered getting listening address:" The error code (here: 46) is the key for solving the issue. This warning says that ldmInit() returned error 46 which is LDMERR_HOST_NOT_FOUND (host not found). This error is returned if the OS call gethostbyname() fails with an error. So these appears to be a network specific issue. Solution 1) Check permission on /etc/hosts $ ls -l /etc/hosts -rw-r--r-- 2 root root 194 Oct 17 2006 /etc/hosts Check if /etc/hosts file is correctly configured <ip address> <fully qualified hostname> <simple or short hostname> <alias, if applicable> ( all of this on one line ). 2) Check the hostname: $ hostname $ ping `hostname` Make sure you are able to ping the hostname 3) Check if /etc/nodename is correctly configured If you have DNS setup, ping is not a tool to diagnose DNS problem. A better tool to use is nslookup, dnsquery, or dig. $ nslookup <shortname> $ nslookup <long name> $ nslookup <ip address> The forward and reverse lookup should succeed and return consistent address/info. 4) Check nsswitch.conf $ more nsswitch.confhosts: files dnsMake sure host lookup is also done through the /etc/hosts file and not just dns. It is recommended that FILES come first before DNS. Also, check the resolv.conf. This makes sure that the DNS is working properly.
在这里看到虽然数据库的版本不一样,alert和trace中的错误不完全一致,但是很相似。是由于主机名不能被正常访问导致,所以尝试这从主机名相关部分着手解决。
五.查看主机名相关信息,解决问题
[oracle@gongantest ~]$ ls -l /etc/hosts
-rw-r--r-- 2 root root 176 Dec 16 13:43 /etc/hosts
[oracle@gongantest ~]$ hostname
gongantest
[oracle@gongantest ~]$ ping gongantest
ping: unknown host gongantest
[oracle@gongantest ~]$ more /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
#192.168.11.60 gongantest
--发现改主机名的dns被注释掉
[oracle@gongantest ~]$ ping gongantest
PING gongantest (192.168.11.60) 56(84) bytes of data.
From 192.168.9.66 icmp_seq=2 Destination Host Unreachable
From 192.168.9.66 icmp_seq=3 Destination Host Unreachable
From 192.168.9.66 icmp_seq=4 Destination Host Unreachable
--- gongantest ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3999ms, pipe 3
--除掉注释,测试不通
[root@gongantest ~]# ifconfig
eth1 Link encap:Ethernet HWaddr 00:14:22:10:96:CA
inet addr:192.168.9.66 Bcast:192.168.11.255 Mask:255.255.252.0
inet6 addr: fe80::214:22ff:fe10:96ca/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4207222 errors:0 dropped:0 overruns:0 frame:0
TX packets:2482964 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1156547557 (1.0 GiB) TX bytes:565900103 (539.6 MiB)
--发现该机器的ip为192.168.9.66,修改hosts文件。
--初步确定出现问题的原因是因为机器迁移,使用了新ip,注释掉了hosts文件中错误ip
[root@gongantest ~]# vi /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
192.168.9.66 gongantest
[oracle@gongantest ~]$ ping gongantest
PING gongantest (192.168.9.66) 56(84) bytes of data.
64 bytes from gongantest (192.168.9.66): icmp_seq=1 ttl=64 time=0.037 ms
64 bytes from gongantest (192.168.9.66): icmp_seq=2 ttl=64 time=0.031 ms
64 bytes from gongantest (192.168.9.66): icmp_seq=3 ttl=64 time=0.033 ms
--- gongantest ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.031/0.033/0.037/0.007 ms
--ping测试正常
继续观察
--观察d000进程是否启动 [oracle@gongantest ~]$ ps -ef|grep ora_ oracle 10180 1 0 13:23 ? 00:00:00 ora_pmon_gaxt oracle 10182 1 0 13:23 ? 00:00:00 ora_psp0_gaxt oracle 10184 1 0 13:23 ? 00:00:00 ora_mman_gaxt oracle 10186 1 0 13:23 ? 00:00:00 ora_dbw0_gaxt oracle 10188 1 0 13:23 ? 00:00:02 ora_lgwr_gaxt oracle 10190 1 0 13:23 ? 00:00:00 ora_ckpt_gaxt oracle 10192 1 0 13:23 ? 00:00:00 ora_smon_gaxt oracle 10194 1 0 13:23 ? 00:00:00 ora_reco_gaxt oracle 10196 1 0 13:23 ? 00:00:00 ora_cjq0_gaxt oracle 10198 1 0 13:23 ? 00:00:00 ora_mmon_gaxt oracle 10200 1 0 13:23 ? 00:00:00 ora_mmnl_gaxt oracle 10204 1 0 13:23 ? 00:00:00 ora_s000_gaxt oracle 10210 1 0 13:23 ? 00:00:00 ora_arc0_gaxt oracle 10212 1 0 13:23 ? 00:00:00 ora_arc1_gaxt oracle 10214 1 0 13:23 ? 00:00:00 ora_qmnc_gaxt oracle 10218 1 0 13:23 ? 00:00:00 ora_j000_gaxt oracle 10222 1 0 13:24 ? 00:00:00 ora_q000_gaxt oracle 10234 1 0 13:24 ? 00:00:00 ora_q001_gaxt oracle 10609 1 0 13:32 ? 00:00:00 ora_d000_gaxt oracle 10639 9962 0 13:35 pts/0 00:00:00 grep ora_ --观察alert日志未出现该错误 Mon Dec 26 13:32:18 2011 Errors in file /opt/oracle/admin/gaxt/bdump/gaxt_ora_10607.trc: ORA-07445: exception encountered: core dump [kslgetl()+120] [SIGSEGV] [Address not mapped to object] [0x000000208] [] [] ORA-00108: failed to set up dispatcher to accept connection asynchronously Mon Dec 26 13:32:21 2011 found dead dispatcher 'D000', pid = (13, 85) Mon Dec 26 13:36:04 2011 Thread 1 advanced to log sequence 232 (LGWR switch) Current log# 1 seq# 232 mem# 0: /opt/oracle/oradata/gaxt/redo01.log
至此ORA-07445[kslgetl()+120]/ORA-00108错误解决
ORA-00600[4194]故障解决
朋友数据库因为断电,导致数据库正常启动片刻之后,自动down掉
一、alert日志
Starting ORACLE instance (normal) LICENSE_MAX_SESSION = 0 LICENSE_SESSIONS_WARNING = 0 Picked latch-free SCN scheme 2 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 = 58720256 __large_pool_size = 4194304 __java_pool_size = 4194304 __streams_pool_size = 4194304 nls_date_format = yyyy-mm-dd hh24:mi:ss sga_target = 335544320 control_files = /u02/ezhou/control01.ctl db_block_size = 8192 compatible = 10.2.0.1.0 log_archive_dest = /u02/arch log_archive_max_processes= 10 db_file_multiblock_read_count= 16 fast_start_mttr_target = 300 undo_management = AUTO undo_tablespace = UNDOTBS1 remote_login_passwordfile= EXCLUSIVE db_domain = dispatchers = (PROTOCOL=TCP) (SERVICE=ezhouXDB) job_queue_processes = 10 background_dump_dest = /u01/pp/oracle/admin/ezhou/bdump user_dump_dest = /u01/pp/oracle/admin/ezhou/udump core_dump_dest = /u01/pp/oracle/admin/ezhou/cdump audit_file_dest = /u01/pp/oracle/admin/ezhou/adump db_name = ezhou open_cursors = 400 sql_trace = TRUE pga_aggregate_target = 94371840 MMAN started with pid=4, OS id=5539 PMON started with pid=2, OS id=5535 DBW0 started with pid=5, OS id=5541 LGWR started with pid=6, OS id=5543 SMON started with pid=8, OS id=5547 CJQ0 started with pid=10, OS id=5577 RECO started with pid=9, OS id=5575 Sat Dec 10 17:15:40 2011 starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))' MMNL started with pid=12, OS id=5581 MMON started with pid=11, OS id=5579 Sat Dec 10 17:15:40 2011 starting up 1 shared server(s) ... PSP0 started with pid=3, OS id=5537 CKPT started with pid=7, OS id=5545 Sat Dec 10 17:15:42 2011 ALTER DATABASE MOUNT Sat Dec 10 17:15:46 2011 Setting recovery target incarnation to 3 Sat Dec 10 17:15:47 2011 Successful mount of redo thread 1, with mount id 4055654398 Sat Dec 10 17:15:47 2011 Database mounted in Exclusive Mode Completed: ALTER DATABASE MOUNT Sat Dec 10 17:15:47 2011 ALTER DATABASE OPEN Sat Dec 10 17:15:47 2011 Beginning crash recovery of 1 threads Sat Dec 10 17:15:47 2011 Started redo scan Sat Dec 10 17:15:48 2011 Completed redo scan 319 redo blocks read, 98 data blocks need recovery Sat Dec 10 17:15:50 2011 Started redo application at Thread 1: logseq 24, block 3 Sat Dec 10 17:15:50 2011 Recovery of Online Redo Log: Thread 1 Group 3 Seq 24 Reading mem 0 Mem# 0 errs 0: /u02/ezhou/redo03.log Sat Dec 10 17:15:50 2011 Completed redo application Sat Dec 10 17:15:51 2011 Completed crash recovery at Thread 1: logseq 24, block 322, scn 6168722 98 data blocks read, 98 data blocks written, 319 redo blocks read Sat Dec 10 17:15:51 2011 LGWR: STARTING ARCH PROCESSES ARC1 started with pid=17, OS id=5645 ARC0 started with pid=16, OS id=5643 ARC3 started with pid=19, OS id=5649 ARC4 started with pid=20, OS id=5651 ARC2 started with pid=18, OS id=5647 ARC6 started with pid=22, OS id=5655 ARC7 started with pid=23, OS id=5657 ARC5 started with pid=21, OS id=5653 ARC8 started with pid=24, OS id=5659 Sat Dec 10 17:15:52 2011 ARC0: Archival started ARC1: Archival started ARC2: Archival started ARC3: Archival started ARC4: Archival started ARC5: Archival started ARC6: Archival started ARC7: Archival started ARC8: Archival started ARC9: Archival started LGWR: STARTING ARCH PROCESSES COMPLETE ARC9 started with pid=25, OS id=5661 Sat Dec 10 17:15:52 2011 Thread 1 advanced to log sequence 25 Sat Dec 10 17:15:53 2011 ARC2: STARTING ARCH PROCESSES Sat Dec 10 17:15:53 2011 ARC6: Becoming the 'no FAL' ARCH ARC6: Becoming the 'no SRL' ARCH Sat Dec 10 17:15:53 2011 ARC3: Becoming the heartbeat ARCH Sat Dec 10 17:15:53 2011 Thread 1 opened at log sequence 25 Current log# 1 seq# 25 mem# 0: /u02/ezhou/redo01.log Current log# 1 seq# 25 mem# 1: /u02/ezhou/redo01a.rdo Successful open of redo thread 1 Sat Dec 10 17:15:53 2011 SMON: enabling cache recovery Sat Dec 10 17:15:54 2011 ARCa: Archival started ARC2: STARTING ARCH PROCESSES COMPLETE ARCa started with pid=26, OS id=5663 Sat Dec 10 17:15:57 2011 Successfully onlined Undo Tablespace 1. Sat Dec 10 17:15:57 2011 SMON: enabling tx recovery Sat Dec 10 17:15:57 2011 Database Characterset is AL32UTF8 replication_dependency_tracking turned off (no async multimaster replication found) Starting background process QMNC QMNC started with pid=27, OS id=5666 Sat Dec 10 17:16:13 2011 Errors in file /u01/pp/oracle/admin/ezhou/bdump/ezhou_smon_5547.trc: ORA-00600: internal error code, arguments: [4194], [30], [27], [], [], [], [], [] Sat Dec 10 17:16:17 2011 Completed: ALTER DATABASE OPEN Sat Dec 10 17:16:27 2011 Doing block recovery for file 2 block 4124 Block recovery from logseq 25, block 68 to scn 6168829 Sat Dec 10 17:16:27 2011 Recovery of Online Redo Log: Thread 1 Group 1 Seq 25 Reading mem 0 Mem# 0 errs 0: /u02/ezhou/redo01.log Mem# 1 errs 0: /u02/ezhou/redo01a.rdo Block recovery stopped at EOT rba 25.126.16 Block recovery completed at rba 25.126.16, scn 0.6168829 Doing block recovery for file 2 block 73 Block recovery from logseq 25, block 68 to scn 6168786 Sat Dec 10 17:16:28 2011 Recovery of Online Redo Log: Thread 1 Group 1 Seq 25 Reading mem 0 Mem# 0 errs 0: /u02/ezhou/redo01.log Mem# 1 errs 0: /u02/ezhou/redo01a.rdo Block recovery completed at rba 25.69.16, scn 0.6168789 Sat Dec 10 17:16:28 2011 Errors in file /u01/pp/oracle/admin/ezhou/bdump/ezhou_smon_5547.trc: ORA-01595: error freeing extent (2) of rollback segment (5)) ORA-00607: Internal error occurred while making a change to a data block ORA-00600: internal error code, arguments: [4194], [30], [27], [], [], [], [], [] Sat Dec 10 17:16:30 2011 Errors in file /u01/pp/oracle/admin/ezhou/bdump/ezhou_j002_5690.trc: ORA-00600: internal error code, arguments: [4194], [30], [27], [], [], [], [], [] Sat Dec 10 17:16:37 2011 Doing block recovery for file 2 block 4124 Block recovery from logseq 25, block 68 to scn 6168829 Sat Dec 10 17:16:37 2011 Recovery of Online Redo Log: Thread 1 Group 1 Seq 25 Reading mem 0 Mem# 0 errs 0: /u02/ezhou/redo01.log Mem# 1 errs 0: /u02/ezhou/redo01a.rdo Block recovery completed at rba 25.126.16, scn 0.6168830 Doing block recovery for file 2 block 73 Block recovery from logseq 25, block 68 to scn 6168841 Sat Dec 10 17:16:37 2011 Recovery of Online Redo Log: Thread 1 Group 1 Seq 25 Reading mem 0 Mem# 0 errs 0: /u02/ezhou/redo01.log Mem# 1 errs 0: /u02/ezhou/redo01a.rdo Block recovery completed at rba 25.149.16, scn 0.6168843 Sat Dec 10 17:16:37 2011 Errors in file /u01/pp/oracle/admin/ezhou/bdump/ezhou_j002_5690.trc: ORA-12012: error on auto execute of job 8886 ORA-00607: Internal error occurred while making a change to a data block Sat Dec 10 17:16:41 2011 Errors in file /u01/pp/oracle/admin/ezhou/bdump/ezhou_j003_5692.trc: ORA-00600: internal error code, arguments: [4194], [30], [27], [], [], [], [], [] Sat Dec 10 17:16:42 2011 DEBUG: Replaying xcb 0x32a2b17c, pmd 0x32bdbd24 for failed op 8 Doing block recovery for file 2 block 4124 Block recovery from logseq 25, block 68 to scn 6168829 Sat Dec 10 17:16:42 2011 Recovery of Online Redo Log: Thread 1 Group 1 Seq 25 Reading mem 0 Mem# 0 errs 0: /u02/ezhou/redo01.log Mem# 1 errs 0: /u02/ezhou/redo01a.rdo Block recovery completed at rba 25.126.16, scn 0.6168830 Sat Dec 10 17:16:43 2011 Errors in file /u01/pp/oracle/admin/ezhou/bdump/ezhou_j003_5692.trc: ORA-00600: internal error code, arguments: [4194], [30], [27], [], [], [], [], [] ORA-00600: internal error code, arguments: [4194], [30], [27], [], [], [], [], [] Sat Dec 10 17:16:46 2011 Errors in file /u01/pp/oracle/admin/ezhou/bdump/ezhou_j003_5692.trc: ORA-00600: internal error code, arguments: [4194], [30], [27], [], [], [], [], [] ORA-00600: internal error code, arguments: [4194], [30], [27], [], [], [], [], [] Sat Dec 10 17:17:46 2011 DEBUG: Replaying xcb 0x32a2b17c, pmd 0x32bdbd24 for failed op 8 Doing block recovery for file 2 block 4124 Block recovery from logseq 25, block 68 to scn 6168829 Sat Dec 10 17:17:46 2011 Recovery of Online Redo Log: Thread 1 Group 1 Seq 25 Reading mem 0 Mem# 0 errs 0: /u02/ezhou/redo01.log Mem# 1 errs 0: /u02/ezhou/redo01a.rdo Block recovery completed at rba 25.126.16, scn 0.6168830 Sat Dec 10 17:17:48 2011 Errors in file /u01/pp/oracle/admin/ezhou/bdump/ezhou_pmon_5535.trc: ORA-00600: internal error code, arguments: [4194], [30], [27], [], [], [], [], [] Sat Dec 10 17:17:49 2011 Errors in file /u01/pp/oracle/admin/ezhou/bdump/ezhou_pmon_5535.trc: ORA-00600: internal error code, arguments: [4194], [30], [27], [], [], [], [], [] PMON: terminating instance due to error 472 Instance terminated by PMON, pid = 5535
二、MOS记录
ERROR: ORA-600 [4194] [a] [b] VERSIONS: versions 6.0 to 10.1 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
三、解决办法
1、修改参数
undo_management= MANUAL
undo_tablespace= SYSTEM
2、打开数据库,删除当前undo空间,重建新undo空间
3、修改参数
undo_management= AUTO
undo_tablespace= UNDOTBSNEW
4、重新启动数据库

加我微信(17813235971)
加我QQ(107644445)

