标签云
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,881)
- DB2 (22)
- MySQL (82)
- Oracle (1,706)
- 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 (72)
- Oracle Bug (8)
- Oracle RAC (56)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (29)
- Oracle备份恢复 (660)
- 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)
-
最近发表
- 记录一次云存储资源到期之后引起的数据库恢复
- 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系统数据库恢复过程
- OBET-Oracle Block Editor Tool使用说明
- 几乎动用了所有手段的Oracle故障恢复
- Oracle Block Edit Tool (obet) 功能增强–2026.07
- Oracle 19c 202607补丁(RUs+OJVM)-19.32
分类目录归档:Oracle
增加默认值列exp DIRECT=Y导出,导入遭遇ORA-01400
最近的一次数据迁移中使用exp导出遭遇到ORA-01400: cannot insert NULL into 错误,凭着经验对其进行了重现,确定是由于增加默认值的列,使用DIRECT=Y 导出导致该问题
创建测试表
创建一张表,并且增加带默认值而且不为空的列,然后使用exp DIRECT=Y 导出数据
SQL> select * from v$version;
BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
PL/SQL Release 11.2.0.4.0 - Production
CORE 11.2.0.4.0 Production
TNS for Linux: Version 11.2.0.4.0 - Production
NLSRTL Version 11.2.0.4.0 - Production
SQL> create table t_xifenfei as select * from dba_objects;
Table created.
SQL> alter table t_xifenfei add (c_xifenfei varchar2(30) default 'www.xifenfei.com' not null);
Table altered.
SQL> select c_xifenfei from t_xifenfei where rownum<10;
C_XIFENFEI
------------------------------
www.xifenfei.com
www.xifenfei.com
www.xifenfei.com
www.xifenfei.com
www.xifenfei.com
www.xifenfei.com
www.xifenfei.com
www.xifenfei.com
www.xifenfei.com
9 rows selected.
[oracle@bogon ~]$ exp xff/oracle tables=t_xifenfei FEEDBACK=10000 COMPRESS=NO \
> BUFFER=102400000 STATISTICS=none DIRECT=Y recordlength=65535 file=/tmp/t_xifenfei.dmp
Export: Release 11.2.0.4.0 - Production on Tue Aug 21 15:56:52 2018
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
server uses ZHS16GBK character set (possible charset conversion)
About to export specified tables via Direct Path ...
. . exporting table T_XIFENFEI
........
86421 rows exported
Export terminated successfully without warnings.
测试导入数据
导入到另外一个用户下面
[oracle@bogon ~]$ imp xff1/oracle file=/tmp/t_xifenfei.dmp fromuser=xff touser=xff1
Import: Release 11.2.0.4.0 - Production on Tue Aug 21 15:57:53 2018
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Export file created by EXPORT:V11.02.00 via direct path
Warning: the objects were exported by XFF, not by you
import done in US7ASCII character set and AL16UTF16 NCHAR character set
import server uses ZHS16GBK character set (possible charset conversion)
. importing XFF's objects into XFF1
. . importing table "T_XIFENFEI"
IMP-00019: row rejected due to ORACLE error 1400
IMP-00003: ORACLE error 1400 encountered
ORA-01400: cannot insert NULL into ("XFF1"."T_XIFENFEI"."C_XIFENFEI")
Column : SYS
Column : ICOL$
Column :
Column : 20
Column : 2
Column : TABLE
Column : 24-AUG-2013:11:37:35
Column : 24-AUG-2013:11:47:37
Column : 2013-08-24:11:37:35
Column : VALID
Column : N
Column : N
Column : N
Column : 1
Column :
Column :
IMP-00019: row rejected due to ORACLE error 1400
IMP-00003: ORACLE error 1400 encountered
ORA-01400: cannot insert NULL into ("XFF1"."T_XIFENFEI"."C_XIFENFEI")
这里可以看到,故障已经重现ORA-01400: cannot insert NULL into,无法将空值插入到刚刚新加的默认值的列中
使用常规导出
[oracle@bogon ~]$ exp xff/oracle tables=t_xifenfei FEEDBACK=10000
COMPRESS=NO BUFFER=102400000 STATISTICS=none file=/tmp/t_xifenfei1.dmp
Export: Release 11.2.0.4.0 - Production on Tue Aug 21 16:00:50 2018
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
server uses ZHS16GBK character set (possible charset conversion)
About to export specified tables via Conventional Path ...
. . exporting table T_XIFENFEI
........
86421 rows exported
Export terminated successfully without warnings.
导入数据
[oracle@bogon ~]$ imp xff1/oracle file=/tmp/t_xifenfei1.dmp fromuser=xff touser=xff1 Import: Release 11.2.0.4.0 - Production on Tue Aug 21 16:04:47 2018 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options Export file created by EXPORT:V11.02.00 via conventional path Warning: the objects were exported by XFF, not by you import done in US7ASCII character set and AL16UTF16 NCHAR character set import server uses ZHS16GBK character set (possible charset conversion) . importing XFF's objects into XFF1 . . importing table "T_XIFENFEI" 86421 rows imported Import terminated successfully without warnings. [oracle@bogon ~]$ [oracle@bogon ~]$ sqlplus xff1/oracle SQL*Plus: Release 11.2.0.4.0 Production on Tue Aug 21 16:10:16 2018 Copyright (c) 1982, 2013, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> select c_xifenfei from t_xifenfei where rownum<10; C_XIFENFEI ------------------------------ www.xifenfei.com www.xifenfei.com www.xifenfei.com www.xifenfei.com www.xifenfei.com www.xifenfei.com www.xifenfei.com www.xifenfei.com www.xifenfei.com 9 rows selected.
通过测试证明,对于11g新特性增加默认值,而且非为空的列,如果使用exp常规方法导入,再导出没有任何问题,如果使用DIRECT=Y特性,将导致导入失败(ORA-01400).这是由于11g的快速增加列和默认值且不为空的新特性导致的(直接修改字典,并没有真正的去修改数据底层存储).
查询mos发现匹配bug: Bug 13961541 : EXP WITH DIRECT=Y CAN NOT HANDLE ADD COLUMN DEFAULT NOT NULL FEATURE IN 11G
数据库升级报ORA-07445 joxchrcnv
朋友在aix平台数据库10.2.0.3升级到10.2.0.5过程中,运行catupgrd.sql脚本,遭遇ORA-07445 joxchrcnv错误
--catupgrd.sql前台报错
Table altered.
Table altered.
BEGIN
*
ERROR at line 1:
ORA-03113: end-of-file on communication channel
ERROR:
ORA-03114: not connected to ORACLE
--trace文件报错
*** 2018-08-09 14:41:29.742
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [joxchrcnv+00a8]
[SIGSEGV] [Address not mapped to object] [0x500000040] [] []
Current SQL statement for this session:
REVOKE all ON SYS.hs_bulk_seq FROM PUBLIC
----- PL/SQL Call Stack -----
object line object
handle number name
7000000e9942b80 2 anonymous block
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedst+001c bl ksedst1 000000000 ? 000000001 ?
ksedmp+0290 bl ksedst 104C1FC50 ?
ssexhd+03e0 bl ksedmp 300001D15 ?
0000441C ? 00000000
joxcdtu+0088 bl joxchrcnv 11019B760 ? 7000000E2CEBC70 ?
FFFFFFFFFFE82A0 ?
7000000E37EFDC8 ? 000000000 ?
000000000 ? 000000002 ?
7000000E1A8B250 ?
joxcnas+007c bl joxcdtu 110008BE0 ? 7000000E5FD3670 ?
FFFFFFFFFFE71C0 ?
4642408300000004 ?
104BAF6F0 ? 7000000E6BE6B48 ?
joxsnm_+0020 bl joxcnas 7000000E5FD4E30 ? 000000001 ?
000000000 ? 7000000E2CEB8D0 ?
7000000E991C6E0 ? 11019B760 ?
FFFFFFFFFFE82E0 ?
joxsnm+0010 bl 03754C58
kkdlJavasnmAltName+ bl 01FC3B1C
0048
qcdlgbo+0908 bl _ptrgl
qcdlgob+0560 bl qcdlgbo FFFFFFFFFFEF8C0 ? 11019B760 ?
11057B380 ? 7000000E2CEC960 ?
000000000 ? 104DA95B0 ?
700000010017FA0 ? 400000000 ?
qcsfgob+0220 bl qcdlgob FFFFFFFFFFE8B20 ? 1058251F8 ?
FFFFFFFFFFE9000 ? 000000001 ?
00000000B ? 000000000 ?
0000000C7 ?
qcsprfro+04a4 bl qcsfgob 1104300C0 ? 000000000 ?
1100C1848 ? 11019B760 ?
qcsprfro_tree+0454 bl qcsprfro 000000000 ? 000000000 ?
FFFFFFFFFFE8DE8 ? 000000000 ?
qcsprfro_tree+0258 bl qcsprfro_tree 000000001 ? 000000000 ?
FFFFFFFFFFE8DA0 ? 11057B380 ?
7000000E1ACA8F8 ? 000000000 ?
qcspafq+0068 bl qcsprfro_tree 11058DEA0 ? FFFFFFFFFFE9040 ?
FFFFFFFFFFE8E50 ?
4822208200000010 ?
10277AD14 ? 110118F58 ?
qcspqbDescendents+0 bl qcspafq 000000000 ? 110008BE0 ?
3a0 FFFFFFFFFFEFF70 ?
qcspqb+00ac bl qcspqbDescendents 10008CC20 ? 000000000 ?
7000000E2CEC638 ?
kkmdrv+003c bl qcspqb FFFFFFFFFFE9080 ?
88832081E9999F10 ?
FFFFFFFFFFE9080 ?
opiSem+1450 bl kkmdrv 000000000 ? 000001068 ?
11019E058 ? 11058DA68 ?
opiprs+01ac bl opiSem FFFFFFFFFFEFF70 ? 110502A18 ?
00000002A ? 000000001 ?
kksParseChildCursor bl opiprs 10008CC20 ? 000000000 ?
+0640 104C29C50 ? 07FFFFFF8 ?
000000FE8 ? 000000001 ?
rpiswu2+0368 bl _ptrgl
kksLoadChild+20cc bl rpiswu2 7000000EAA86FE0 ? 000000000 ?
000000000 ? 000000000 ?
000000000 ? 000000000 ?
000000000 ? 000000000 ?
kxsGetRuntimeLock+0 bl kksLoadChild 11019B760 ? 7000000E9AE5520 ?
89c 7000000E38176D8 ?
kksfbc+2830 bl kxsGetRuntimeLock 11019B760 ? 11057B380 ?
FFFFFFFFFFF18D8 ? 000000000 ?
000000000 ?
kkspsc0+1570 bl kksfbc 11057B380 ? 3FFFF2858 ?
108E381B6C0 ? 110502A18 ?
00000002A ? 000000000 ?
000000000 ? 000000000 ?
kksParseCursor+00d4 bl kkspsc0 110431A68 ? 110502A18 ?
00000002A ? 310231CF0 ?
610431A68 ?
222000000000000A ?
000000000 ?
opiosq0+0b40 bl 01FC69A4
opipls+0638 bl opiosq0 3EA6B0DF8 ? 110008BE0 ?
110118F58 ?
22200000EAADBE88 ?
000000000 ?
opiodr+0b2c bl _ptrgl
rpidrus+01dc bl opiodr 6600000000 ? 6E2D017E0 ?
FFFFFFFFFFF6C80 ? AFFFF5CD0 ?
skgmstack+00c8 bl _ptrgl
rpidru+0088 bl skgmstack 7000000E37EFB20 ?
FFFFFFFFFFF5C30 ?
FFFFFFFFFFF6080 ?
26214040000010F0 ?
100417334 ?
rpiswu2+0368 bl _ptrgl
rpidrv+097c bl rpiswu2 7000000EAA86FE0 ? 11019B760 ?
FFFFFFFFFFF6400 ? 000000004 ?
7000000E37EFB50 ? 0E9942BE0 ?
7000000E9942BF0 ? 000000000 ?
psddr0+02dc bl 01FC6E18
psdnal+01d0 bl psddr0 A00000000 ? 6600000000 ?
FFFFFFFFFFF6C80 ?
3100000000 ?
pevm_EXIM+0120 bl _ptrgl
pfrinstr_EXIM+0034 bl pevm_EXIM 1105BD288 ? 000000000 ?
pfrrun_no_tool+005c bl _ptrgl
pfrrun+1064 bl pfrrun_no_tool 5800000000 ? 110231CF0 ?
FFFFFFFFFFF6FA0 ?
plsql_run+06e8 bl pfrrun 110449078 ?
peicnt+0244 bl plsql_run 110449078 ? 1000000000418 ?
000000000 ?
kkxexe+0250 bl peicnt FFFFFFFFFFF82D8 ? 110449078 ?
opiexe+3024 bl kkxexe 1104DAEC8 ?
kpoal8+0ef0 bl opiexe FFFFFFFFFFFB954 ? 1103AA798 ?
FFFFFFFFFFF9AF0 ?
opiodr+0b2c bl _ptrgl
ttcpip+1020 bl _ptrgl
opitsk+117c bl 01FC6888
opiino+09d0 bl opitsk 1EFFFFD920 ? 000000000 ?
opiodr+0b2c bl _ptrgl
opidrv+04a4 bl opiodr 3C102A7758 ? 404C72B18 ?
FFFFFFFFFFFF8E0 ? 0102A7750 ?
sou2o+0090 bl opidrv 3C02A288DC ? 400000010 ?
FFFFFFFFFFFF8E0 ?
opimai_real+01bc bl 01FC30F4
main+0098 bl opimai_real 000000000 ? 000000000 ?
__start+0098 bl main 000000000 ? 000000000 ?
--------------------- Binary Stack Dump ---------------------
根据Catupgrd.sql Fails with ORA-3113/ORA-7445 During Grant Select On ALL_JOBS to Public with Grant Option (Doc ID 419309.1)文档,处理建议
1. Make sure LD_LIBRARY_PATH or LIBPATH is set correctly: AIX ==== export LIBPATH=$ORACLE_HOME/lib:$LIBPATH HP-UX ===== export LD_LIBRARY_PATH=$ORACLE_HOME/lib export SHLIB_PATH=$ORACLE_HOME/lib32 HP Tru-64 ======== export LD_LIBRARY_PATH=$ORACLE_HOME/lib SUN Sparc Solaris-64Bit ================== export LD_LIBRARY_PATH_64=$ORACLE_HOME/lib export LD_LIBRARY_PATH=$ORACLE_HOME/lib32 SUN Sparc Solaris-32Bit ================== export LD_LIBRARY_PATH=$ORACLE_HOME/lib Linux ===== export LD_LIBRARY_PATH=$ORACLE_HOME/lib 2. Make sure ORA_NLS parameter is set correctly. See the following notes for assistance: Note 77442.1 (ORA_NLS32, ORA_NLS33, ORA_NLS10) Environment Variables explained. 3. Make sure Listener is also started with the correct environment variables if you were doing remote connection from client through sqlnet rather than local connection to database. 4. Shutdown the database and rerun the upgrade: SQL> SHUTDOWN IMMEDIATE SQL> STARTUP UPGRADE SQL> SPOOL patch.log SQL> @?/rdbms/admin/catupgrd.sql 5. If the above failed then it might be due to the libjox *.a file is not replaced during upgrade or install.
由于软件升级不正常,导致数据库升级出现该问题,在升级软件过程中,一定检查升级软件和升级结果
记录正常open库报ORA-600 2662
数据库版本10.2.0.3 32位
SQL> select * from v$version; BANNER ---------------------------------------------------------------- Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Prod PL/SQL Release 10.2.0.3.0 - Production CORE 10.2.0.3.0 Production TNS for 32-bit Windows: Version 10.2.0.3.0 - Production NLSRTL Version 10.2.0.3.0 - Production
数据库启动alert日志报大量ORA-600和ORA-07445错误
Tue Jul 31 09:56:45 2018 Started redo application at Thread 1: logseq 7593, block 46691 Tue Jul 31 09:56:45 2018 Recovery of Online Redo Log: Thread 1 Group 2 Seq 7593 Reading mem 0 Mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO02.LOG Tue Jul 31 09:56:45 2018 RECOVERY OF THREAD 1 STUCK AT BLOCK 779 OF FILE 2 Tue Jul 31 09:56:45 2018 RECOVERY OF THREAD 1 STUCK AT BLOCK 4430 OF FILE 2 Tue Jul 31 09:56:45 2018 Hex dump of (file 3, block 23704) in trace file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_p002_248.trc Corrupt block relative dba: 0x00c05c98 (file 3, block 23704) Fractured block found during crash/instance recovery Data in bad block: type: 6 format: 2 rdba: 0x00c05c98 last change scn: 0x0000.05c3cad2 seq: 0x16 flg: 0x06 spare1: 0x0 spare2: 0x0 spare3: 0x0 consistency value in tail: 0xe4be0601 check value in block header: 0x5c03 computed block checksum: 0x2e7b Tue Jul 31 09:56:45 2018 Completed redo application Tue Jul 31 09:56:46 2018 Reread of rdba: 0x00c05c98 (file 3, block 23704) found same corrupted data RECOVERY OF THREAD 1 STUCK AT BLOCK 40841 OF FILE 8 Tue Jul 31 09:56:46 2018 RECOVERY OF THREAD 1 STUCK AT BLOCK 297 OF FILE 2 Tue Jul 31 09:56:46 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_p002_248.trc: ORA-00600: internal error code, arguments: [kssadpm1], [], [], [], [], [], [], [] Tue Jul 31 09:56:46 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_p001_2320.trc: ORA-00600: internal error code, arguments: [545], [0xCA15AE84], [3], [16], [], [], [], [] ORA-00600: internal error code, arguments: [545], [0xCA15AE84], [3], [16], [], [], [], [] ORA-00600: internal error code, arguments: [545], [0xCA15AE84], [3], [16], [], [], [], [] ORA-00600: internal error code, arguments: [545], [0xCA15AE84], [3], [8], [], [], [], [] Tue Jul 31 09:56:46 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_p004_2116.trc: ORA-00600: internal error code, arguments: [kssdmc: null so], [], [], [], [], [], [], [] ORA-00600: internal error code, arguments: [kssdmc: null so], [], [], [], [], [], [], [] ORA-00600: internal error code, arguments: [kssdmc: null so], [], [], [], [], [], [], [] ORA-00600: internal error code, arguments: [kssdmc: null so], [], [], [], [], [], [], [] ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x7C3429C1] [ADDR:0xCA800000] [UNABLE_TO_READ] [] Tue Jul 31 09:56:46 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_p000_220.trc: ORA-00600: internal error code, arguments: [ksfdchkfobrerr1], [0xBB9852DC], [0xA7EC530C], [], [], [], [], [] Tue Jul 31 09:56:46 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_p003_252.trc: ORA-00600: internal error code, arguments: [kssrc_test_cleanup:popall], [0xCA000304], [], [], [], [], [], [] Tue Jul 31 09:56:46 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_p001_228.trc: ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_kghalf+895] [PC:0x603BEBF3] [ADDR:0xFFFFFFF8] [UNABLE_TO_READ] [] Tue Jul 31 09:56:46 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_lgwr_1848.trc: ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_ksarcv+243] [PC:0x5B2223] [ADDR:0x206C000C] [UNABLE_TO_READ] [] Tue Jul 31 09:56:47 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_p000_220.trc: ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_kslwlmod+166] [PC:0x46946A] [ADDR:0x54F8] [UNABLE_TO_WRITE] [] ORA-00081: address range [0x75C80047, 0x75C8004B) is not readable ORA-00600: internal error code, arguments: [ksfdchkfobrerr1], [0xBB9852DC], [0xA7EC530C], [], [], [], [], [] Tue Jul 31 09:56:47 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_ckpt_1852.trc: ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_kcbs_dump_adv_state+471] [PC:0x59B403] [ADDR:0xCC60CBAD] [UNABLE_TO_READ] [] ORA-00600: internal error code, arguments: [kssrc_test_cleanup:popall], [0xCA000304], [], [], [], [], [], [] Tue Jul 31 09:56:47 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_pmon_1828.trc: ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_kews_idle_wait+378] [PC:0x60BE2E] [ADDR:0x1820D468] [UNABLE_TO_WRITE] [] Tue Jul 31 09:56:47 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_p004_236.trc: ORA-00081: address range [0x75C80041, 0x75C80045) is not readable ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x7C3429C1] [ADDR:0xCA800000] [UNABLE_TO_READ] []
检查主要坏块
主要影响数据库恢复的坏块,system不言而喻,block 2也比较敏感
E:\>dbv file=E:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\TTTS.DAT DBVERIFY: Release 10.2.0.3.0 - Production on 星期三 8月 1 00:24:52 2018 Copyright (c) 1982, 2005, Oracle. All rights reserved. DBVERIFY - 开始验证: FILE = E:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\TTTS.DAT 页 2 流入 - 很可能是介质损坏 Corrupt block relative dba: 0x02000002 (file 8, block 2) Fractured block found during dbv: Data in bad block: type: 29 format: 2 rdba: 0x02000002 last change scn: 0x0000.05c45a54 seq: 0x2 flg: 0x04 spare1: 0x0 spare2: 0x0 spare3: 0x0 consistency value in tail: 0x9e601d02 check value in block header: 0xea86 computed block checksum: 0xc434 DBVERIFY - 验证完成 检查的页总数: 121600 处理的页总数 (数据): 58606 失败的页总数 (数据): 0 处理的页总数 (索引): 45192 失败的页总数 (索引): 0 处理的页总数 (其它): 4453 处理的总页数 (段) : 0 失败的总页数 (段) : 0 空的页总数: 13348 标记为损坏的总页数: 1 流入的页总数: 1 最高块 SCN : 96716847 (0.96716847) E:\>dbv FILE = E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF DBVERIFY: Release 10.2.0.3.0 - Production on 星期三 8月 1 00:28:28 2018 Copyright (c) 1982, 2005, Oracle. All rights reserved. DBVERIFY - 开始验证: FILE = E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF 页 68377 流入 - 很可能是介质损坏 Corrupt block relative dba: 0x00410b19 (file 1, block 68377) Fractured block found during dbv: Data in bad block: type: 6 format: 2 rdba: 0x00410b19 last change scn: 0x0000.05c45bdf seq: 0x1 flg: 0x06 spare1: 0x0 spare2: 0x0 spare3: 0x0 consistency value in tail: 0x4f3b0601 check value in block header: 0x465b computed block checksum: 0x11c7 DBV-00200: 块 dba 4262777 已标记为损坏 DBVERIFY - 验证完成 检查的页总数: 74240 处理的页总数 (数据): 46209 失败的页总数 (数据): 0 处理的页总数 (索引): 9729 失败的页总数 (索引): 0 处理的页总数 (其它): 1923 处理的总页数 (段) : 0 失败的总页数 (段) : 0 空的页总数: 16378 标记为损坏的总页数: 2 流入的页总数: 1 最高块 SCN : 96757289 (0.96757289)
尝试recover数据库,open数据库
E:\>sqlplus / as sysdba SQL*Plus: Release 10.2.0.3.0 - Production on 星期二 7月 31 15:40:05 2018 Copyright (c) 1982, 2006, Oracle. All Rights Reserved. 连接到: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production With the Partitioning, OLAP and Data Mining options SQL> recover database; 完成介质恢复。 SQL> alter database open; 数据库已更改。
数据库报ORA-600 2662错误
该数据库没有增加隐含隐含参数(屏蔽一致性,屏蔽事务),数据库直接启动之后报ORA-600 2662
Tue Jul 31 15:40:15 2018 SMON: enabling cache recovery Tue Jul 31 15:40:16 2018 Successfully onlined Undo Tablespace 1. Tue Jul 31 15:40:16 2018 SMON: enabling tx recovery Tue Jul 31 15:40:16 2018 Database Characterset is ZHS16GBK replication_dependency_tracking turned off (no async multimaster replication found) Starting background process QMNC QMNC started with pid=32, OS id=1152 Tue Jul 31 15:40:17 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_1288.trc: ORA-00600: internal error code, arguments: [2662], [0], [96736891], [0], [96752794], [4264138], [], [] Tue Jul 31 15:40:18 2018 Non-fatal internal error happenned while SMON was doing logging scn->time mapping. SMON encountered 1 out of maximum 100 non-fatal internal errors. Tue Jul 31 15:40:18 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_1288.trc: ORA-00600: internal error code, arguments: [2662], [0], [96736892], [0], [96752794], [4264138], [], [] Non-fatal internal error happenned while SMON was doing extent coalescing. SMON encountered 3 out of maximum 100 non-fatal internal errors. Tue Jul 31 15:40:19 2018 db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a user-specified limit on the amount of space that will be used by this database for recovery-related files, and does not reflect the amount of space available in the underlying filesystem or ASM diskgroup. Hex dump of (file 8, block 2) in trace file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_mmon_1740.trc Corrupt block relative dba: 0x02000002 (file 8, block 2) Fractured block found during buffer read Data in bad block: type: 29 format: 2 rdba: 0x02000002 last change scn: 0x0000.05c45a54 seq: 0x2 flg: 0x04 spare1: 0x0 spare2: 0x0 spare3: 0x0 consistency value in tail: 0x9e601d02 check value in block header: 0xea86 computed block checksum: 0xc434 Reread of rdba: 0x02000002 (file 8, block 2) found same corrupted data Tue Jul 31 15:40:20 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_1288.trc: ORA-00600: internal error code, arguments: [2662], [0], [96736902], [0], [96752794], [4264138], [], [] Tue Jul 31 15:40:20 2018 Completed: alter database open Tue Jul 31 15:40:20 2018 Non-fatal internal error happenned while SMON was doing extent coalescing. SMON encountered 4 out of maximum 100 non-fatal internal errors. Tue Jul 31 15:40:21 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_1288.trc: ORA-00600: internal error code, arguments: [2662], [0], [96736922], [0], [96752794], [4264138], [], [] Non-fatal internal error happenned while SMON was doing extent coalescing. SMON encountered 5 out of maximum 100 non-fatal internal errors. Tue Jul 31 15:40:22 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_j000_1076.trc: ORA-00600: 内部错误代码, 参数: [2662], [0], [96736954], [0], [96754130], [12615382], [], [] Tue Jul 31 15:40:22 2018 DEBUG: Replaying xcb 0xbba2d2e4, pmd 0xab1920fc for failed op 8 Reconstructing Uhdr 0x800019 for xcb 0xbba2d2e4, pmd 0xab1920fc Doing block recovery for file 2 block 25 Block recovery from logseq 7594, block 63 to scn 96736910 Tue Jul 31 15:40:22 2018 Recovery of Online Redo Log: Thread 1 Group 3 Seq 7594 Reading mem 0 Mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO03.LOG Block recovery completed at rba 7594.82.16, scn 0.96736911 DEBUG: Restoring block headers for xcb 0xbba2d2e4, pmd 0xab1920fc DEBUG: Finished replay for xcb 0xbba2d2e4, pmd 0xab1920fc for failed op 8 Tue Jul 31 15:40:22 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_j000_1076.trc: ORA-00603: ORACLE 服务器会话因致命错误而终止 ORA-00600: 内部错误代码, 参数: [2662], [0], [96736955], [0], [96754130], [12615382], [], [] ORA-00600: 内部错误代码, 参数: [2662], [0], [96736954], [0], [96754130], [12615382], [], [] Tue Jul 31 15:40:31 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_1288.trc: ORA-00600: internal error code, arguments: [2662], [0], [96736963], [0], [96752794], [4264138], [], [] Tue Jul 31 15:40:31 2018 Non-fatal internal error happenned while SMON was doing extent coalescing. SMON encountered 6 out of maximum 100 non-fatal internal errors. Tue Jul 31 15:40:41 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_1288.trc: ORA-00600: internal error code, arguments: [2662], [0], [96736967], [0], [96752794], [4264138], [], [] Tue Jul 31 15:41:03 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_pmon_1448.trc: ORA-00474: SMON process terminated with error Tue Jul 31 15:41:03 2018 PMON: terminating instance due to error 474 Tue Jul 31 15:41:03 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_j004_1344.trc: ORA-00474: SMON process terminated with error Tue Jul 31 15:41:03 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_j003_2104.trc: ORA-00474: SMON process terminated with error Tue Jul 31 15:41:03 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_j002_932.trc: ORA-00474: SMON process terminated with error Tue Jul 31 15:41:04 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_j001_1680.trc: ORA-00474: SMON process terminated with error Tue Jul 31 15:41:04 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_q000_2336.trc: ORA-00474: SMON process terminated with error Tue Jul 31 15:41:05 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_lgwr_552.trc: ORA-00474: SMON process terminated with error Tue Jul 31 15:41:05 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_dbw0_1420.trc: ORA-00474: SMON process terminated with error Tue Jul 31 15:41:05 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_dbw1_2556.trc: ORA-00474: SMON process terminated with error Tue Jul 31 15:41:05 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_psp0_1812.trc: ORA-00474: SMON process terminated with error Tue Jul 31 15:41:05 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_mman_1924.trc: ORA-00474: SMON process terminated with error Tue Jul 31 15:41:05 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_ckpt_2940.trc: ORA-00474: SMON process terminated with error Tue Jul 31 15:41:10 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\bdump\orcl_reco_660.trc: ORA-00474: SMON process terminated with error Instance terminated by PMON, pid = 1448 Tue Jul 31 15:41:57 2018
这是一个不常见的错误,没有使用隐含参数强制拉库,数据库正常open成功,但是由于system坏块,导致数据库启动之后报ORA-600 2662错误(再次证明2662不一定只有强制拉库发生,正常open的库也有可能,主要取决block scn和datafile scn,如果不是open过程必须要访问的block,那可能在open之后由于访问需要再报出来该错误).这个问题比较简单,因为open成功之后再crash,而且该坏块引起smon报错但是并没有ora-600 4xxx相关错误,因此根据经验,直接在数据库open之后,处理掉system异常报错对象和坏块对象即可.另外block 2 比较特殊,需要对其上面的对象进行处理
Tue Jul 31 15:55:54 2018 Hex dump of (file 8, block 2) in trace file e:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_3664.trc Corrupt block relative dba: 0x02000002 (file 8, block 2) Completely zero block found during reading space header Reread of blocknum=2, file=E:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\TTTS.DAT. found same corrupt data Reread of blocknum=2, file=E:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\TTTS.DAT. found same corrupt data Reread of blocknum=2, file=E:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\TTTS.DAT. found same corrupt data Reread of blocknum=2, file=E:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\TTTS.DAT. found same corrupt data Reread of blocknum=2, file=E:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\TTTS.DAT. found same corrupt data Tue Jul 31 15:55:54 2018 Errors in file e:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_3664.trc: ORA-07445: 出现异常错误: 核心转储 [ACCESS_VIOLATION] [_krbodmpcx+243] [PC:0x2317857] [ADDR:0x8] [UNABLE_TO_READ] [] ORA-19880: 数据文件 E:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\TTTS.DAT 的空间标头已损坏, 块 2 备份已中止
补充ora-600 2662 block记录
----------------------------------------
SO: BB97A97C, type: 24, owner: BB882B10, flag: INIT/-/-/0x00
(buffer) (CR) PR: BB8029D8 FLG: 0x100000
class bit: 00000000
kcbbfbp: [BH: B9FCF268, LINK: BB97A9A0]
where: kdswh06: kdscgr, why: 0
BH (B9FCF268) file#: 1 rdba: 0x004110ca (1/69834) class: 1 ba: B9832000
set: 9 blksize: 8192 bsi: 0 set-flg: 2 pwbcnt: 0
dbwrid: 0 obj: 573 objn: 575 tsn: 0 afn: 1
hash: [bb9151ec,bb9151ec] lru: [b9fcf378,b9fcf200]
ckptq: [NULL] fileq: [NULL] objq: [b9fcf3d0,aa776524]
use: [bb97a9a0,bb97a9a0] wait: [NULL]
st: XCURRENT md: SHR tch: 0
flags:
LRBA: [0x0.0.0] HSCN: [0xffff.ffffffff] HSUB: [65535]
Using State Objects
----------------------------------------
SO: BB97A97C, type: 24, owner: BB882B10, flag: INIT/-/-/0x00
(buffer) (CR) PR: BB8029D8 FLG: 0x100000
class bit: 00000000
kcbbfbp: [BH: B9FCF268, LINK: BB97A9A0]
where: kdswh06: kdscgr, why: 0
buffer tsn: 0 rdba: 0x004110ca (1/69834)
scn: 0x0000.05c4549a seq: 0x01 flg: 0x06 tail: 0x549a0601
frmt: 0x02 chkval: 0xc60a type: 0x06=trans data


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

