标签云
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-00600[kcfrbd_3]故障解决
朋友一数据库因为断电,被重建控制文件等操作折腾的最后出现在启动的时候出现ORA-00600[kcfrbd_3]
Wed Dec 05 10:26:34 2012 Thread 1 advanced to log sequence 11 Thread 1 opened at log sequence 11 Current log# 1 seq# 11 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO01.LOG Successful open of redo thread 1 Wed Dec 05 10:26:34 2012 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Wed Dec 05 10:26:34 2012 SMON: enabling cache recovery Wed Dec 05 10:26:35 2012 Successfully onlined Undo Tablespace 1. Dictionary check beginning Dictionary check complete Wed Dec 05 10:26:35 2012 SMON: enabling tx recovery Wed Dec 05 10:26:35 2012 Database Characterset is ZHS16GBK Wed Dec 05 10:26:35 2012 Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_548.trc: ORA-00600: internal error code, arguments: [kcfrbd_3], [2], [2279045], [1], [2277120], [2277120], [], [] replication_dependency_tracking turned off (no async multimaster replication found) Wed Dec 05 10:26:36 2012 Fatal internal error happened while SMON was doing active transaction recovery. Wed Dec 05 10:26:36 2012 Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_548.trc: ORA-00600: internal error code, arguments: [kcfrbd_3], [2], [2279045], [1], [2277120], [2277120], [], [] SMON: terminating instance due to error 474
这个错误很明显:数据库已经open成功了,但是因为有事务不能正常被回滚,然后数据库的smon进程异常,从而使得数据库不能正常启动,解决该问题的方法也是很简单,就是常规的undo处理思路(使用人工undo管理,event屏蔽事务,隐含参数屏蔽回滚段),然后重建undo表空间,这个时候可以结合txchecker来检测是否有异常事务:如果有重要基表对象异常,需要重建库;如果是个别其他对象异常,可以通过重建该对象解决
ORA-00600[qmxtriCheckAndRewriteQb0]
数据库报ORA-00600[qmxtriCheckAndRewriteQb0]
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
ORACLE_HOME = /u01/oracle/product/10.2.0
System name: AIX
Node name: abc
Release: 3
Version: 5
Machine: 00C58A644C00
Instance name: XFF2
Redo thread mounted by this instance: 2
Oracle process number: 434
Unix process pid: 492340, image: oracle@abc
*** ACTION NAME:() 2012-11-12 08:46:47.132
*** MODULE NAME:() 2012-11-12 08:46:47.132
*** SERVICE NAME:(ORCL) 2012-11-12 08:46:47.132
*** CLIENT ID:() 2012-11-12 08:46:47.132
*** SESSION ID:(870.58602) 2012-11-12 08:46:47.132
*** 2012-11-12 08:46:47.132
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [qmxtriCheckAndRewriteQb0], [], [], [], [], [], [], []
Current SQL statement for this session:
SELECT EXTRACTVALUE(配置,'//SYSTEM[@XTH="'||:B1 ||'"]/FILE') ,
WHERE EXTRACTVALUE(配置,'//SYSTEM[@XTH="'||:B1 ||'"]/BM')=:B2 AND ROWNUM<2
----- PL/SQL Call Stack -----
object line object
handle number name
70000021d535f70 25 procedure ZLTOOLS.ZL_MBRUNLOG_INSERT
7000002b6819368 1 anonymous block
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedst+001c bl ksedst1 000000000 ? 000000000 ?
ksedmp+0290 bl ksedst 104A2C690 ?
ksfdmp+0018 bl 03F26C3C
kgerinv+00dc bl _ptrgl
kgeasnmierr+004c bl kgerinv 7000002F735A838 ? 000000000 ?
000000000 ? 000000000 ?
0FFFFBFFF ?
IPRA.$qmxtriCheckAn bl 03F25970
dRewriteQb_rec+0194
IPRA.$qmxtriCheckAn bl IPRA.$qmxtriCheckAn 1000881EC ? 000000000 ?
dRewriteQb_rec+006c dRewriteQb_rec 000000000 ?
IPRA.$qmxtriCheckAn bl IPRA.$qmxtriCheckAn FFFFFFFFFFF07E0 ? 000000033 ?
dRewriteQb_rec+006c dRewriteQb_rec 1056037F8 ?
qmxtriCheckAndRewri bcl dmqlKMlod+00c0 000000000 ? 110421CB0 ?
teQb+0094 FFFFFFFFFFE87C0 ?
qmxtrxq+0210 bl 03F252EC
qmxtrxop+00a4 bl qmxtrxq FFFFFFFFFFF25B8 ?
700000282F66DD0 ? 110195E98 ?
koksspend+02b0 bl qmxtrxop 100346AB4 ?
kkmdrvend+01a8 bl koksspend 000000001 ? 104B3A8A8 ?
000000000 ?
kkmdrv+004c bl kkmdrvend FFFFFFFFFFE8BE0 ?
883843401048F2F8 ?
opiSem+13c0 bl kkmdrv 000000000 ? 000000000 ?
000000000 ? 11022AC50 ?
opiDeferredSem+0234 bl opiSem FFFFFFFFFFE9CE0 ?
7000001E327CCE0 ? 000000111 ?
100000001 ?
opitca+01e8 bl opiDeferredSem
kksFullTypeCheck+00 bl 03F25230
1c
rpiswu2+034c bl _ptrgl
kksSetBindType+0d28 bl rpiswu2 70000030850C178 ?
3300000033 ?
FFFFFFFFFFF0570 ?
FFFFFFFFFFF0578 ?
7000002F6F0C700 ?
33104027D8 ?
FFFFFFFFFFF1F48 ? 000000000 ?
kksfbc+1054 bl kksSetBindType 70000030F58F400 ? 1107CB418 ?
70000001003B800 ?
10200003000 ? 110000FF8 ?
7000000100ECAB8 ?
FFFFFFFFFFF1480 ?
481A408400003000 ?
opiexe+098c bl 01F960BC
opipls+185c bl opiexe FFFFFFFFFFF3900 ?
FFFFFFFFFFF39E8 ?
FFFFFFFFFFF38A0 ?
opiodr+0ae0 bl _ptrgl
rpidrus+01bc bl opiodr 66FFFF54B0 ? 608736A20 ?
FFFFFFFFFFF67C0 ?
1510195E98 ?
skgmstack+00c8 bl _ptrgl
rpidru+0088 bl skgmstack 102320840 ? 000000000 ?
000000002 ? 000000000 ?
FFFFFFFFFFF5F88 ?
rpiswu2+034c bl _ptrgl
rpidrv+095c bl rpiswu2 70000030850C178 ? 110469C28 ?
11044AA58 ? 000000000 ?
FFFFFFFFFFF5D60 ?
3300000000 ? 000000000 ?
000000000 ?
psddr0+02bc bl 03F266D4
psdnal+01d0 bl psddr0 1500000000 ? 6600000000 ?
FFFFFFFFFFF67C0 ?
30100BACC8 ?
pevm_EXECC+01f8 bl _ptrgl
pfrinstr_EXECC+0070 bl pevm_EXECC 10147B2A4 ? 000000000 ?
700000262828B72 ?
pfrrun_no_tool+005c bl _ptrgl
pfrrun+1014 bl pfrrun_no_tool FFFFFFFFFFF6B20 ?
7000002B6819368 ? 3100ECBB0 ?
plsql_run+06b4 bl pfrrun 1107D84A8 ?
peicnt+0224 bl plsql_run 1107D84A8 ? 10001102676F8 ?
000000000 ?
kkxexe+0250 bl peicnt FFFFFFFFFFF7E38 ? 1107D84A8 ?
opiexe+2ef8 bl kkxexe 11047E1C8 ?
kpoal8+0edc bl opiexe FFFFFFFFFFFB454 ?
FFFFFFFFFFFB1A8 ?
FFFFFFFFFFF9628 ?
opiodr+0ae0 bl _ptrgl
ttcpip+1020 bl _ptrgl
opitsk+1124 bl 01F96AC8
opiino+0990 bl opitsk 0FFFFD490 ? 000000000 ?
opiodr+0ae0 bl _ptrgl
opidrv+0484 bl 01F95914
sou2o+0090 bl opidrv 3C02D99B7C ? 4A076D928 ?
FFFFFFFFFFFF390 ?
opimai_real+01bc bl 01F93294
main+0098 bl opimai_real 000000000 ? 000000000 ?
__start+0098 bl main 000000000 ? 000000000 ?
--------------------- Binary Stack Dump ---------------------
通过这个trace的部分信息可以得到:
1.操作系统版本AIX x64(5.3)
2.数据库版本10.2.0.4
3.sql语句调用EXTRACTVALUE函数
4.Call Stack Trace信息
查询MOS[ID 467350.1]发现匹配信息
Cause Bug 6030982 ORA-600 [QMXTRICHECKANDREWRITEQB0] WITH QUERY USING EXTRACTVALUE FUNCTION Solution This bug is going to be fixed in furture 10.2.0.5.0 and 11g At the mean time , user can workaround by set event = "19027 trace name context forever, level 1" within init.ora or spfile file then bounce database. or SQL> alter session set events ='19027 trace name context forever, level 1'; SQL> Alter system flush shared_pool; -- Execute affected query
通过mos可以确定:
1.是因为数据库执行EXTRACTVALUE函数遇到该bug
2.在11g和10.2.0.5中修复该bug
3.可以通过设置event = “19027 trace name context forever, level 1″来临时解决该问题
个人处理建议
1.如果数据库方便升级,那建议升级处理
2.如果数据库不便立马升级,建议在业务低估时设置session event 19027,然后 flush shared_pool,执行报错sql,如果问题解决,在合适时间设置system event来临时屏蔽该问题.
expdp遭遇ORA-39006/ORA-39213故障解决
expdp导出数据遇到ORA-39006/ORA-39213错误,通过执行执行dbms_metadata_util.load_stylesheets解决
expdp工作异常
--导出awr信息 SQL> @?/rdbms/admin/awrextr.sql ………… Exception encountered in AWR_EXTRACT ORA-39006: internal error ORA-39213: Metadata processing is not available begin * ERROR at line 1: ORA-31623: a job is not attached to this session via the specified handle ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79 ORA-06512: at "SYS.DBMS_DATAPUMP", line 911 ORA-06512: at "SYS.DBMS_DATAPUMP", line 4710 ORA-06512: at "SYS.DBMS_SWRF_INTERNAL", line 656 ORA-06512: at "SYS.DBMS_SWRF_INTERNAL", line 962 ORA-06512: at line 3 --导出一个表 $ expdp "'/ as sysdba'" dumpfile=xifenfei.dmp tables=scott.t_xifenfei Export: Release 10.2.0.1.0 - 64bit Production on Wednesday, 31 October, 2012 13:03:20 Copyright (c) 2003, 2005, Oracle. All rights reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production With the Partitioning, OLAP and Data Mining options ORA-39006: internal error ORA-39213: Metadata processing is not available
错误提示
$ oerr ora 39006 39006, 00000, "internal error" // *Cause: An unexpected error occurred while processing a Data Pump job. // Subsequent messages supplied by DBMS_DATAPUMP.GET_STATUS // will further describe the error. // *Action: Contact Oracle Customer Support. $ oerr ora 39213 39213, 00000, "Metadata processing is not available" // *Cause: The Data Pump could not use the Metadata API. Typically, // this is caused by the XSL stylesheets not being set up properly. // *Action: Connect AS SYSDBA and execute dbms_metadata_util.load_stylesheets // to reload the stylesheets.
解决ORA-39006/ORA-39213问题
--查询数据库已经安装组件 SQL> col COMP_NAME for a35 SQL> select comp_name, version, status from dba_registry; COMP_NAME VERSION STATUS ----------------------------------- ------------------------------ ---------------------- Oracle Database Catalog Views 10.2.0.1.0 VALID Oracle Database Packages and Types 10.2.0.1.0 VALID Oracle Workspace Manager 10.2.0.1.0 VALID JServer JAVA Virtual Machine 10.2.0.1.0 VALID Oracle XDK 10.2.0.1.0 VALID Oracle Database Java Packages 10.2.0.1.0 VALID Oracle Expression Filter 10.2.0.1.0 VALID Oracle Data Mining 10.2.0.1.0 VALID Oracle Text 10.2.0.1.0 VALID Oracle XML Database 10.2.0.1.0 VALID Oracle Rules Manager 10.2.0.1.0 VALID Oracle interMedia 10.2.0.1.0 VALID OLAP Analytic Workspace 10.2.0.1.0 VALID Oracle OLAP API 10.2.0.1.0 VALID OLAP Catalog 10.2.0.1.0 VALID Spatial 10.2.0.1.0 VALID Oracle Enterprise Manager 10.2.0.1.0 VALID 17 rows selected. --如果缺少下面组件,使用下面对应的程序安装 Oracle Database Catalog Views Oracle Database Packages and Types JServer JAVA Virtual Machine Oracle XDK Oracle Database Java Packages --使用下面脚本安装(根据组件选择) SQL> connect / as sysdba SQL> @$ORACLE_HOME/javavm/install/initjvm.sql SQL> connect / as sysdba SQL> @$ORACLE_HOME/xdk/admin/initxml.sql SQL> connect / as sysdba SQL> @$ORACLE_HOME/rdbms/admin/catjava.sql SQL> connect / as sysdba SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql --执行sys.dbms_metadata_util.load_stylesheets SQL> execute sys.dbms_metadata_util.load_stylesheets; PL/SQL procedure successfully completed.
测试expdp导出
$ expdp "'/ as sysdba'" dumpfile=xifenfei.dmp tables=scott.t_xifenfei Directory=AWR_DIR Export: Release 10.2.0.1.0 - 64bit Production on Wednesday, 31 October, 2012 14:18:04 Copyright (c) 2003, 2005, Oracle. All rights reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production With the Partitioning, OLAP and Data Mining options Starting "SYS"."SYS_EXPORT_TABLE_01": '/******** AS SYSDBA' dumpfile=xifenfei.dmp tables=scott.t_xifenfei Directory=AWR_DIR Estimate in progress using BLOCKS method... Processing object type TABLE_EXPORT/TABLE/TABLE_DATA Total estimation using BLOCKS method: 7 MB Processing object type TABLE_EXPORT/TABLE/TABLE . . exported "SCOTT"."T_XIFENFEI" 5.374 MB 57376 rows Master table "SYS"."SYS_EXPORT_TABLE_01" successfully loaded/unloaded ****************************************************************************** Dump file set for SYS.SYS_EXPORT_TABLE_01 is: /data/enmotech/xifenfei.dmp Job "SYS"."SYS_EXPORT_TABLE_01" successfully completed at 14:18:11
测试证明,在不缺少相关组件的情况下,使用dbms_metadata_util.load_stylesheets可以解决expdp导出报ORA-39006/ORA-39213错误;如果缺少组件,需要先安装对应组件,然后再执行dbms_metadata_util.load_stylesheets解决该问题

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

