Oracle 数据泵异常JOB状态DEFINING处理
10.2.0.5数据泵导入hang住,JOB变为异常DEFINING状态.
前台输出以及日志输出:
Import: Release 10.2.0.5.0 - 64bit Production on Thursday, 14 January, 2021 14:02:50Copyright (c) 2003, 2007, Oracle. All rights reserved.
;;;
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Master table "SYSTEM"."SYS_IMPORT_SCHEMA_03" successfully loaded/unloaded
查看数据泵JOB状态:
SQL> select job_name,state from dba_datapump_jobs;JOB_NAME STATE
------------------------------ ------------------------------
SYS_IMPORT_SCHEMA_03 DEFINING
SYS_IMPORT_FULL_01 NOT RUNNING
SYS_EXPORT_SCHEMA_02 NOT RUNNING
SYS_EXPORT_SCHEMA_01 NOT RUNNING
SYS_IMPORT_SCHEMA_01 NOT RUNNING
SYS_IMPORT_SCHEMA_02 NOT RUNNING
尝试停止该JOB SYS_IMPORT_SCHEMA_03
$ expdp ‘/ as sysdba’ attach=SYS_IMPORT_SCHEMA_03
Export: Release 10.2.0.5.0 - 64bit Production on Thursday, 14 January, 2021 15:26:33
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORA-31626: job does not exist
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79
ORA-06512: at "SYS.KUPV$FT", line 435
ORA-31638: cannot attach to job SYS_IMPORT_SCHEMA_03 for user SYS
ORA-31632: master table "SYS.SYS_IMPORT_SCHEMA_03" not found, invalid, or inaccessible
ORA-00942: table or view does not exist
无法停止.
根据MOS1626201.1提供SQL查询JOB master主表:
SQL> SELECT o.status, o.object_id, o.object_type,2 o.owner||'.'||object_name "OWNER.OBJECT"3 FROM dba_objects o, dba_datapump_jobs j4 WHERE o.owner=j.owner_name AND o.object_name=j.job_name5 AND j.job_name NOT LIKE 'BIN$%' ORDER BY 4,2;
STATUS OBJECT_ID OBJECT_TYPE OWNER.OBJECT
---------------------------------------------------------------------------------------------------------------------------------------------------------------
VALID 617965 TABLE HB.SYS_EXPORT_SCHEMA_01
VALID 617968 TABLE HB.SYS_EXPORT_SCHEMA_02
VALID 91021 TABLE SYSTEM.SYS_IMPORT_FULL_01
VALID 86818 TABLE SYSTEM.SYS_IMPORT_SCHEMA_01
VALID 395030 TABLE SYSTEM.SYS_IMPORT_SCHEMA_02
VALID 633461 TABLE SYSTEM.SYS_IMPORT_SCHEMA_03
干掉这个主表:
SQL> drop table SYSTEM.SYS_IMPORT_SCHEMA_03 purge;
drop table SYSTEM.SYS_IMPORT_SCHEMA_03 purge
ERROR at line 1:
ORA-00054: resource busy and acquire with NOWAIT specified
此时表可能被锁住或占用.
查询会话占用该job情况:
SQL> select JOB_NAME,ATTACHED_SESSIONS,DATAPUMP_SESSIONS from dba_datapump_jobs;
JOB_NAME ATTACHED_SESSIONS DATAPUMP_SESSIONS
------------------------------ ----------------- -----------------
SYS_IMPORT_SCHEMA_03 0 2
SYS_IMPORT_FULL_01 0 0
SYS_EXPORT_SCHEMA_02 0 0
SYS_EXPORT_SCHEMA_01 0 0
SYS_IMPORT_SCHEMA_01 0 0
SYS_IMPORT_SCHEMA_02 0 0
通过v$ lock以及v$ locked_object判断状态表是否有锁.
SQL> select object_id,session_id,locked_mode from v$locked_object where object_id=633461;OBJECT_ID SESSION_ID LOCKED_MODE
---------- ---------- -----------633461 1575 3
定位会话并杀会话:
SQL> select sid,serial# from v$session where sid=1575;SID SERIAL#----- ---------1575 42458
SQL> alter system kill session '1575,42458,@1' immediate;
alter system kill session '1575,42458,@1' immediate
*
ERROR at line 1:
ORA-00026: missing or invalid session ID//锁资源未释放
操作系统层面杀锁:
SQL> select a.spid,b.sid,b.serial#,b.username from v$process a,v$session b where a.addr=b.paddr and b.status='KILLED';
SPID SID SERIAL# USERNAME
------------ ---------- ---------- ------------------------------
28508560 1575 42458 SYSTEM
资源成功释放:
SQL> select a.spid,b.sid,b.serial#,b.username from v$process a,v$session b where a.addr=b.paddr and b.status='KILLED';
no rows selectedSQL> select sid,serial# from v$session where sid=1575;
no rows selectedSQL> select object_id,session_id,locked_mode from v$locked_object where object_id=633461;
no rows selected
再次查询该JOB状态:
SQL> select job_name,state,owner_name from dba_datapump_jobs;
JOB_NAME STATE OWNER_NAME
------------ ------------------------------ ------------------------------
SYS_IMPORT_FULL_01 NOT RUNNING SYSTEM
SYS_EXPORT_SCHEMA_02 NOT RUNNING HB
SYS_IMPORT_SCHEMA_03 NOT RUNNING SYSTEM
SYS_EXPORT_SCHEMA_01 NOT RUNNING HB
SYS_IMPORT_SCHEMA_01 NOT RUNNING SYSTEM
SYS_IMPORT_SCHEMA_02 NOT RUNNING SYSTEM
//变为NOT RUNNING
再次执行导入成功!
Oracle 数据泵异常JOB状态DEFINING处理相关推荐
- Oracle数据泵备份与恢复 命令 expdp/impdp 用法详解
Oracle数据泵备份与恢复 命令 expdp/impdp 用法详解 关于expdp和impdp 使用EXPDP和IMPDP时应该注意的事项: EXP和IMP是客户端工具程序,它们既可以在客户 ...
- 如何将mysql导出数据泵_Oracle数据库之ORACLE 数据泵导入导出数据
本文主要向大家介绍了Oracle数据库之ORACLE 数据泵导入导出数据,通过具体的内容向大家展现,希望对大家学习Oracle数据库有所帮助. 一.摘要 在平常备库和数据库迁移的时候,当遇到大的数据库 ...
- Oracle数据泵详解
Oracle数据泵详解 Oracle Database 10g中采用了数据泵(Data Dump)技术,使DBA或开发人员可以将数据库元数据(对象定义)和数据快速移动到另一个oracle数据库中 ...
- oracle数据泵的原理,oracle 数据泵 详解
导出数据 1)按用户导 expdp scott/tiger@orcl schemas=scott dumpfile=expdp.dmp DIRECTORY=dir logfile=expdp.log ...
- oracle 查看数据泵,1.Oracle数据泵介绍
1. Oracle 数据泵介绍 Oracle数据泵是用来替换原始的export和import工具(exp,imp) 它从Oracle 10g开始提供 它可以快速和高效的将数据从一个数据库移动到另一个数 ...
- oracle数据泵导出 不全,Oracle RAC数据泵导出问题处理
1. 设置导出文件路径 sqlplus / as sysdba SQL> alter session set container=spdb1pdb; SQL> create directo ...
- oracle 数据泵导入导出 expdp/impdp
一. 导出/入前检查 查看用户默认表空间 select USERNAME,DEFAULT_TABLESPACE,TEMPORARY_TABLESPACE from dba_users where US ...
- 导出/导入DataPump参数TRACE - 如何诊断Oracle数据泵(文档 ID 286496.1)
导出/导入DataPump参数TRACE - 如何诊断Oracle数据泵(文档 ID 286496.1) 1.介绍 在Oracle10g中,我们引入了新的数据库实用程序Export Data Pump ...
- oracle 数据泵导出简单使用版
<oracle 数据泵导出简单使用版> 1.数据泵可以导出表,表空间,用户schema,数据库 注意:导出表空间和数据库要求用户必须具有DBA 角色或EXP_FULL_DATABASE 角 ...
最新文章
- 哪些人适合参加UI设计培训
- 西湖首届本科生开招!每名学生配三位学术导师,大二全员海外交流
- libuv 高性能事件驱动库 简介
- typescript ajax,TypeScript的应用方式
- 【建议】如何优雅的提问?
- python获取对象的大小_Python实现计算对象的内存大小示例
- bash中正则表达式
- notepad出现中文显示方格处理方法
- 弹出浮动页面html怎么写,C# 浮动窗体实现(自定义弹出窗口)
- 常见视频高速接口分析MIPI,LVDS,RGB,HDMI
- 从技术雷达看持续交付
- PHP实现zip字典破解
- Redis下载安装-Windows版本
- DFI(Deep/DynamicFlow Inspection,深度/动态流检测)
- React Suspense 尝鲜,处理前后端IO异步操作
- HDU 4960 Another OCD Patient 简单DP
- 最快的计算机操作,自学电脑操作怎样比较快?
- 图形学--(中点画线法+Bresenham画线算法)
- 基于大数据的能力开放平台解决方案
- rule of thumb - “经验法则”或者“拇指规则”