ORACLE表有逻辑坏块时EXPDP导出报错排查

某用户反馈EXPDP导出脚本异常中断，接入排查后发现导出某表时报错，后台ALERT日志中也有相应报错；最终确认排查为逻辑坏块问题，经沟通得知为某个时间段的备份表，后续排除此表后重新设置EXPDP脚本，可以正常导出，如下为相关日志：

单独导出表的报错排查：
[oracle@test1 ~]$ expdp system/oracle directory=expdphis  dumpfile=T1.dmp tables=test.test11_0301_BUGGY logfile=T1.log cluster=noExport: Release 11.2.0.4.0 - Production on Sat Jan 22 12:19:11 2022Copyright (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, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
FLASHBACK automatically enabled to preserve database integrity.
Starting "SYSTEM"."SYS_EXPORT_TABLE_03":  system/******** directory=expdphis dumpfile=T1.dmp tables=test.test11_0301_BUGGY logfile=T1.log cluster=no
Estimate in progress using BLOCKS method...
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 3.817 GB
Processing object type TABLE_EXPORT/TABLE/PROCACT_INSTANCE
Processing object type TABLE_EXPORT/TABLE/TABLE
Processing object type TABLE_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type TABLE_EXPORT/TABLE/COMMENT
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type TABLE_EXPORT/TABLE/TRIGGERJob "SYSTEM"."SYS_EXPORT_TABLE_03" stopped due to fatal error at Sat Jan 22 12:22:22 2022 elapsed 0 00:03:04检查后台ALERT日志：
Sat Jan 22 12:19:18 2022
DM00 started with pid=1820, OS id=22939, job SYSTEM.SYS_EXPORT_TABLE_03
ALTER TABLE "SYSTEM"."SYS_EXPORT_TABLE_03" ADD (UNIQUE (process_order, duplicate))
Sat Jan 22 12:19:28 2022
CREATE INDEX SYS_MTABLE_000061006_IND_1 ON "SYSTEM"."SYS_EXPORT_TABLE_03" (object_schema, object_name, object_type)
CREATE INDEX SYS_MTABLE_000061006_IND_2 ON "SYSTEM"."SYS_EXPORT_TABLE_03" (base_process_order)
Sat Jan 22 12:19:29 2022
DW00 started with pid=167, OS id=23647, wid=1, job SYSTEM.SYS_EXPORT_TABLE_03
Sat Jan 22 12:20:21 2022
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x2] [PC:0x6DC0806, klufprd()+302] [flags: 0x0, count: 1]
Errors in file /u01/app/oracle/diag/rdbms/test/test1/trace/test1_dw00_23647.trc  (incident=497337):
ORA-07445: exception encountered: core dump [klufprd()+302] [SIGSEGV] [ADDR:0x2] [PC:0x6DC0806] [Address not mapped to object] []
Incident details in: /u01/app/oracle/diag/rdbms/test/test1/incident/incdir_497337/test1_dw00_23647_i497337.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Sat Jan 22 12:20:23 2022
Dumping diagnostic data in directory=[cdmp_20220122122023], requested by (instance=1, osid=23647 (DW00)), summary=[incident=497337].
Sat Jan 22 12:20:23 2022
Sweep [inc][497337]: completed
Sweep [inc2][497337]: completed
Sat Jan 22 12:21:54 2022
Thread 1 advanced to log sequence 49130 (LGWR switch)Current log# 20 seq# 49130 mem# 0: /hisdata/datafile/group_20.630.1076516067Current log# 20 seq# 49130 mem# 1: /hisdata/datafile/group_20.12531.1076516069
Sat Jan 22 12:21:54 2022
LNS: Standby redo logfile selected for thread 1 sequence 49130 for destination LOG_ARCHIVE_DEST_2
Sat Jan 22 12:21:54 2022
Archived Log entry 4742 added for thread 1 sequence 49129 ID 0xbcb39845 dest 1:
Sat Jan 22 12:22:22 2022
ALTER SYSTEM SET service_names='SYS$SYS.KUPC$S_1_20220122121913.test','test' SCOPE=MEMORY SID='test1';
ALTER SYSTEM SET service_names='test' SCOPE=MEMORY SID='test1';Sat Jan 22 11:31:55 2022
LNS: Standby redo logfile selected for thread 1 sequence 49125 for destination LOG_ARCHIVE_DEST_2
Sat Jan 22 11:31:55 2022
Archived Log entry 4722 added for thread 1 sequence 49124 ID 0xbcb39845 dest 1:
Sat Jan 22 11:32:43 2022
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x2] [PC:0x6DC0806, klufprd()+302] [flags: 0x0, count: 1]
Errors in file /u01/app/oracle/diag/rdbms/test/test1/trace/test1_dw03_66684.trc  (incident=517785):
ORA-07445: exception encountered: core dump [klufprd()+302] [SIGSEGV] [ADDR:0x2] [PC:0x6DC0806] [Address not mapped to object][]
Incident details in: /u01/app/oracle/diag/rdbms/test/test1/incident/incdir_517785/test1_dw03_66684_i517785.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Sat Jan 22 11:32:45 2022
Dumping diagnostic data in directory=[cdmp_20220122113245], requested by (instance=1, osid=66684 (DW03)), summary=[incident=51
7785].
Sat Jan 22 11:32:45 2022
Sweep [inc][517785]: completed
Sweep [inc2][517785]: completed
Sat Jan 22 11:33:50 2022
CREATE TABLE "ET$34613C510001" (    "RQ", "PATIENT_NO", "KSDM", "FEE", "BQZJ", "BQJS", "BQJC", "SQJC") ORGANIZATION EXTERNAL ( TYPE ORACLE_DATAPUMP DEFAULT DIRECTORY "EXPDPHIS" ACCESS PARAMETERS ( DEBUG = (0 , 0) DATAPUMP INTERNAL TABLE "test"."Z
Y_YJK_JCMX"  JOB ( "SYSTEM","SYS_EXPORT_SCHEMA_02",23) WORKERID 1 PARALLEL 1 VERSION '11.2.0.4.0' ENCRYPTPASSWORDISNULL  COMPR
ESSION ENABLED  ENCRYPTION DISABLED ) LOCATION ('bogus.dat') )  PARALLEL 1 REJECT LIMIT UNLIMITEDAS SELECT /*+ PARALLEL(KU$,1) */ "RQ", "PATIENT_NO", "KSDM", "FEE", "BQZJ", "BQJS", "BQJC", "SQJC"FROM RELATIONAL("test"."ZY_YJK_JCMX" NOT XMLTYPE) AS OF SCN 21109504765917 KU$ DROP TABLE "ET$34613C510001" PURGE
Sat Jan 22 11:34:56 2022
ALTER SYSTEM SET service_names='SYS$SYS.KUPC$S_1_20220122102337.test','test' SCOPE=MEMORY SID='test1';
Sat Jan 22 11:34:57 2022
DW01 terminating with fatal err=39078, pid=683, wid=2, job SYSTEM.SYS_EXPORT_SCHEMA_02
Sat Jan 22 11:34:57 2022
DW00 terminating with fatal err=39078, pid=2233, wid=1, job SYSTEM.SYS_EXPORT_SCHEMA_02
Sat Jan 22 11:34:57 2022
DW02 terminating with fatal err=39079, pid=2662, wid=3, job SYSTEM.SYS_EXPORT_SCHEMA_02
ALTER SYSTEM SET service_names='test' SCOPE=MEMORY SID='test1';相关TRACE日志：
[oracle@test1 ~]$ more /u01/app/oracle/diag/rdbms/test/test1/trace/test1_dw03_66684.trc
Trace file /u01/app/oracle/diag/rdbms/test/test1/trace/test1_dw03_66684.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.2.0.4/dbhome_1
System name:    Linux
Node name:      test1
Release:        4.14.35-2025.404.1.2.el7uek.x86_64
Version:        #2 SMP Wed Jan 27 20:30:12 PST 2021
Machine:        x86_64
Instance name: test1
Redo thread mounted by this instance: 1
Oracle process number: 2723
Unix process pid: 66684, image: oracle@test1 (DW03)*** 2022-01-22 10:24:22.556
*** SESSION ID:(8230.2561) 2022-01-22 10:24:22.556
*** CLIENT ID:() 2022-01-22 10:24:22.556
*** SERVICE NAME:(SYS$BACKGROUND) 2022-01-22 10:24:22.556
*** MODULE NAME:(Data Pump Worker) 2022-01-22 10:24:22.556
*** ACTION NAME:(SYS_EXPORT_SCHEMA_02) 2022-01-22 10:24:22.556KUPC: Setting remote flag for this process to FALSE*** 2022-01-22 11:32:43.553
*** MODULE NAME:(Data Pump Worker) 2022-01-22 11:32:43.557
*** ACTION NAME:(SYS_EXPORT_SCHEMA_02) 2022-01-22 11:32:43.557Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x2] [PC:0x6DC0806, klufprd()+302] [flags: 0x0, count: 1]
Incident 517785 created, dump file: /u01/app/oracle/diag/rdbms/test/test1/incident/incdir_517785/test1_dw03_66684_i51778
5.trc
ORA-07445: exception encountered: core dump [klufprd()+302] [SIGSEGV] [ADDR:0x2] [PC:0x6DC0806] [Address not mapped to object][]ssexhd: crashing the process...
Shadow_Core_Dump = PARTIAL
ksdbgcra: writing core file to directory '/u01/app/oracle/diag/rdbms/test/test1/cdump'

ORACLE表有逻辑坏块时EXPDP导出报错排查相关推荐

oracle报错7001,Oracle 10g expdp导出报错ORA-4031的解决方法
数据库是10.2.0.4 操作系统是aix,在执行expdp导出多个方案对象时报ORA-39014,ORA-39029,ORA-31671,ORA-39079,ORA-06512,ORA-04031: ...
oracle 10g expdp导出报错ora-4031的解决方法
数据库是10.2.0.4 操作系统是aix,在执行expdp导出多个方案对象时报ORA-39014,ORA-39029,ORA-31671,ORA-39079,ORA-06512,ORA-04031: ...
oracle生成3个零,expdp导出报错：ORA-39001: ORA-39200: ORA-02019:
问题已解决,需要在本地数据库,用sys用户,执行 GRANT exp_full_database TO db_exp; (db_exp为本地数据库用户) C:\Users\jadl>s ...
oracle system表空间有坏块,修复系统表空间坏块
刚接手一个小库准备rman全备一下结果报错说有一个坏块无法备份查看alert日志发现system表空间存在一个坏块 Errors in file /u01/app/oracle/admin/sms/ ...
Oracle corrupt block（坏块）详解
转自:http://blog.csdn.net/tianlesoftware/article/details/5024966 一. 坏块说明 1.1 相关链接在看坏块之前,先看几个相关的链接,在后面 ...
oracle 11g跳过坏块,oracle 使用Dbms_Repair跳过坏块
原博文: http://blog.chinaunix.net/uid-77311-id-3051382.html 使用Dbms_Repair跳过坏块步骤1:表tb_test中有坏块(模拟坏块同方法1 ...
oracle检查表是否有坏块,Oracle数据库坏块检查与修复
摘要:简述数据库坏块,发现并处理Oracle的物理坏块.逻辑坏块以下摘自网络并规整: 一.数据库坏块介绍数据库的数据块有固定的格式和结构,分三层:cache layer,transaction l ...
oracle控制文件有坏块处理过程
oracle控制文件有坏块处理过程问题解决方案问题客户环境11.2.0.4 rac red6.7 查看集群资源信息 crsctl status res -t 发现: ora.orcl.db 1 ...
oracle数据库报错代码,【案例】Oracle数据库dbv检查坏块时报错代码：6106解决办法...
[案例]Oracle数据库dbv检查坏块时报错代码:6106解决办法时间:2016-10-24 21:02 来源:Oracle研究中心作者:HTZ 点击: 次天萃荷净 Oracle研 ...

ORACLE表有逻辑坏块时EXPDP导出报错排查

ORACLE表有逻辑坏块时EXPDP导出报错排查相关推荐

最新文章

热门文章