滥觞:网海拾贝
现在脱手脱手想法式处置这个活动变乱和含有活动变乱的回滚段了。
起首筹备drop这个表试试看(先备份,然后drop,然后重修):
先是运用CTAS备份这个表:
SQL> create table WAP_AUTHPRICE_USER_SP_RD060308 tablespace INDEX_SUBN01 nologging as
select * from WAP_AUTHPRICE_USER_SP_RD where 1=2;
2
Table created.
SQL> insert into WAP_AUTHPRICE_USER_SP_RD060308 nologging
2 select * from WAP_AUTHPRICE_USER_SP_RD;
insert into WAP_AUTHPRICE_USER_SP_RD060308 nologging
*
ERROR at line 1:
ORA-01555: snapshot too old: rollback segment number 19 with name "_SYSSMU19 $"
too small
SQL> insert into WAP_AUTHPRICE_USER_SP_RD060308 nologging
2 select * from WAP_AUTHPRICE_USER_SP_RD where rownum<100;
99 rows created.
SQL> rollback;
Rollback complete.
SQL>
我们看到,每次扫表到阿谁回滚段中的数据库时,琐细就会报ORA-01555了。
由此揣度,全数的对表的FTS都市失败,比方exp:
oracle@rdb01:/oracle > exp report/slienttop parfile=a.par
Export: Release 9.2.0.5.0 - Production on Thu Mar 9 14:31:45 2006
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to: Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning and OLAP options
JServer Release 9.2.0.5.0 - Production
Export done in ZHS16GBK character set and UTF8 NCHAR character set
About to export specified tables via Direct Path ...
. . exporting table WAP_AUTHPRICE_USER_SP_RD
EXP-00056: ORACLE error 942 encountered
ORA-00942: table or view does not exist
Export terminated successfully with warnings.
oracle@rdb01:/oracle >
现在,只要运用DUL了:
DUL> unload report.WAP_AUTHPRICE_USER_SP_RD;
. unloading table WAP_AUTHPRICE_USER_SP_RD
9430056 rows unloaded
DUL> exit
oracle@rdb01:/data/tmp/dul > gzip REPORT_WAP_AUTHPRICE_USER_SP_RD.dmp
oracle@rdb01:/data/tmp/dul > ll REPORT_WAP_AUTHPRICE_USER_SP_RD.dm*
-rw-r--r-- 1 oracle dba 49514464 Mar 13 14:18 REPORT_WAP_AUTHPRICE_USER_SP_RD.dmp.gz
oracle@rdb01:/data/tmp/dul >
这时,俄然想到运用oracledebug来跟踪一下历程也许会话,梗概会有点收获:
SQL> oradebug setospid 15664
ORA-00072: process "Unix process pid: 15664, image: " is not active
SQL> oradebug setospid 15664
ORA-00072: process "Unix process pid: 15664, image: " is not active
SQL>
SQL> select pid, spid, username from v $process where spid=15664;
PID SPID USERNAME
---------- ------------ ---------------
63 15664 oracle
SQL>
SQL> oradebug setorapid 63
ORA-00072: process "Unix process pid: 15664, image: oracle@rdb01 (TNS V1-V3)" is not active
SQL>
显然,这个效果是和我们刚刚在垄断琐细上kill process,以及在数据库中kill session的效果是不合的——我们不能找到这些process和session的行为了。
因为alert.log的内容曾经被人清空了,可是数据库中可以看到:
USN NAME STATUS TABLESPACE_NAME ADDR SID SERIAL# USERNAME PROGRAM MACHINE OSUSER
---------- ---------- --------------- -------------------- ---------------- ------ ------- ---------- -------------------- ---------- ----------
19 _SYSSMU19 $ PENDING OFFLINE UNDOTBS1 C0000001A7BF5218 71 39809 REPORT sqlldr@RPT01 (TNS CS_RPT01 report16
这个回滚段曾经破损,而且活动变乱是一个sqlloader的历程(刚刚看到的数据库中sid 71正在执行的sql语句刚好也是多么一个insert语句)。由此证领略除夜白我最初的揣度。因为某种缘故起因,开拓职员将正在执行的sqlloader历程kill了,而此时刚好有一行活动在回滚段中,这个事变发生在12/30/05 01:48:33 此后,因为没有实时的创造和处置这个成果,数据库的日记曾经被覆盖反复,再之后,就发生了我们现在看到的情况。
固然alert.log的内容不在了,可是按照事变发生的工夫,我们找到了响应的trace--report_ora_15664.trc,内中有如下的内容:
AV女伶 SESSION ID:(71.25999) 2005-12-30 01:48:33.580
AV女伶 2005-12-30 01:48:33.580
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [4193], [2987], [2984], [], [], [], [], []
Current SQL statement for this session:
INSERT INTO WAP_AUTHPRICE_USER_SP_RD (LOCATIONID,ICPID,SUBSCAT,ICPATTR,ICPCODE,COUNTS,PERIOD,STAT_TIME) VALUES (:LOCATIONID,:ICPID,:SUBSCAT,:ICPATTR,:ICPCODE,:COUNTS,:PERIOD,TO_DATE(:STAT_TIME,'yyyy-mm-dd hh24:mi:ss'))
ORA-00600 [4193],这类错误一样寻常即是活动回滚段破损一类的错误了,注意的可以搜查metalink。
现在我曾经订定了一套执行料理,下周一脱手脱手处置这个成果(因为24*7,这类有风险的垄断必须要写通知报到公司的率领和客户的率领,层层审批,呵呵)。。。
版权声明:
原创作品,容许转载,转载时请务必以超链接方式标明文章 原始因由 、作者信息和本声明。否则将清查法律责任。