标签云
asm mount asm 恢复 asm恢复 bbed bootstrap$ dul eking In Memory kcbzib_kcrsds_1 kccpb_sanity_check_2 kfed MySQL恢复 ORA-00312 ORA-00607 ORA-00704 ORA-01110 ORA-01555 ORA-01578 ORA-08103 ORA-600 2662 ORA-600 3020 ORA-600 4000 ORA-600 4137 ORA-600 4193 ORA-600 4194 ORA-600 16703 ORA-15042 ORA-15196 ORACLE 12C oracle dul ORACLE PATCH Oracle Recovery Tools oracle加密恢复 oracle勒索 oracle异常恢复 ORACLE恢复 Oracle 恢复 ORACLE数据库恢复 oracle 比特币 OSD-04016 sql加密恢复 YOUR FILES ARE ENCRYPTED 勒索恢复 比特币 oracle 比特币加密文章分类
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (91)
- 数据库 (1,419)
- DB2 (22)
- MySQL (58)
- Oracle (1,305)
- Data Guard (41)
- EXADATA (7)
- GoldenGate (20)
- ORA-xxxxx (150)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (12)
- ORACLE 21C (3)
- Oracle ASM (58)
- Oracle Bug (7)
- Oracle RAC (42)
- Oracle 安全 (6)
- Oracle 开发 (26)
- Oracle 监听 (26)
- Oracle备份恢复 (438)
- Oracle安装升级 (71)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (63)
- PostgreSQL (10)
- SQL Server (26)
- SQL Server恢复 (7)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (24)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (7)
-
最近发表
- O/S-Error: (OS 23) 数据错误(循环冗余检查) 数据库恢复
- 数据库open报ORA-00959: tablespace ‘UNDOTBS1′ does not exist分析
- ASM删除表空间恢复
- ORA-12518 ORA-27302: 错误发生在: ssthrddcr
- plsql 插入blob
- 分享运气超级好的一次drop tablespace 数据恢复
- segment header异常对象删除处理
- Oracle 数据库(RDBMS)的版本支持状态摘要 (Doc ID 1674382.1)
- [back2023@proxy.tg].eking勒索数据库恢复
- ORA-600 ktbsdp2 处理
- win文件系统损坏oracle恢复
- asm disk 磁盘部分被清空恢复
- File #xxx found in data dictionary but not in controlfile. Creating OFFLINE file ‘MISSING00XXX’ in the controlfile
- commit_wait和commit_logging设置不当导致数据库无法正常启动
- ORA-00742 ORA-00312故障恢复
- 110T oracle故障恢复
- ora-600 kcratr_scan_lastbwr
- .asistchinadecryption扩展名勒索数据库恢复
- .[decrypt20@firemail.cc].eking 数据库勒索恢复
- ocr磁盘组掉盘故障处理
友情链接
标签归档:ORA-00959
数据库open报ORA-00959: tablespace ‘UNDOTBS1′ does not exist分析
有一个朋友找到我,说数据库重启之后无法正常启动,提示ORA-00959 UNDOTBS1表空间不存在
在数据库的启动过程中,这个是一个很常见的错误,一般出现这类错误的原因是由于undo_tablespace指定的undo表空间不存在导致.但是这个库比较明显,设置了undo_management=manual, undo_tablespace=system,依旧数据库需要找undotbs1表空间,进一步分析数据库当前表空间情况

该数据库确实没有undotbs1表空间,基于以上信息,初步怀疑很可能是undo回滚段异常,通过对于oracle基表进行分析,发现信息


基于上面的信息,可以确认回滚段中确实有四条记录指向被删除的undotbs1,而且还有一条undo回滚段信息为need recovery状态.进一步分析数据库alert日志
--创建undotbs2表空间,并重启数据库 Sun Sep 26 14:42:16 2021 create undo tablespace UNDOTBS2 datafile '/data/oradata/xifenfei/undotbs001.dbf' size 120G reuse autoextend on next 500m maxsize unlimited Sun Sep 26 14:46:46 2021 Completed: create undo tablespace UNDOTBS2 datafile '/data/oradata/xifenfei/undotbs001.dbf' size 120G reuse autoextend on next 500m maxsize unlimited Sun Sep 26 14:47:13 2021 [16927] Successfully onlined Undo Tablespace 10. [16927] **** active transactions found in undo Tablespace 2 - moved to Pending Switch-Out state. [16927] active transactions found/affinity dissolution incompletein undo tablespace 2 during switch-out. ALTER SYSTEM SET undo_tablespace='UNDOTBS2' SCOPE=BOTH; Sun Sep 26 14:49:25 2021 Shutting down instance (immediate) Shutting down instance: further logons disabled Stopping background process QMNC ---第一次尝试删除undotbs1失败 Sun Sep 26 15:06:30 2021 drop tablespace UNDOTBS1 INCLUDING CONTENTS AND DATAFILES CASCADE CONSTRAINTS Sun Sep 26 15:47:26 2021 ORA-1013 signalled during: drop tablespace UNDOTBS1 INCLUDING CONTENTS AND DATAFILES CASCADE CONSTRAINTS ... Sun Sep 26 15:48:40 2021 Shutting down instance (immediate) Shutting down instance: further logons disabled Stopping background process QMNC --加上该隐含参数,继续重启库删除undotbs1,依旧删除失败 _corrupted_rollback_segments= "_SYSSMU28_1306132068$" Sun Sep 26 15:53:34 2021 QMNC started with pid=31, OS id=20454 Completed: ALTER DATABASE OPEN Sun Sep 26 15:55:32 2021 drop tablespace UNDOTBS1 INCLUDING CONTENTS AND DATAFILES CASCADE CONSTRAINTS ………… Sun Sep 26 16:45:47 2021 ORA-1013 signalled during: drop tablespace UNDOTBS1 INCLUDING CONTENTS AND DATAFILES CASCADE CONSTRAINTS... Sun Sep 26 16:46:00 2021 Shutting down instance (immediate) Shutting down instance: further logons disabled Stopping background process QMNC ---加上以下参数,并尝试重启数据库删除undotbs1成功 _corrupted_rollback_segments= "_SYSSMU31_201790566$" _corrupted_rollback_segments= "_SYSSMU30_2395098326$" _corrupted_rollback_segments= "_SYSSMU29_306369076$" _corrupted_rollback_segments= "_SYSSMU28_1306132068$" Sun Sep 26 16:47:24 2021 QMNC started with pid=31, OS id=23421 Completed: ALTER DATABASE OPEN Sun Sep 26 16:47:40 2021 drop tablespace UNDOTBS1 INCLUDING CONTENTS AND DATAFILES CASCADE CONSTRAINTS ………… Mon Sep 27 01:44:56 2021 Deleted file /data/oradata/xifenfei/undotbs01.dbf Deleted file /data/oradata/xifenfei/undotbs02.dbf Deleted file /data/oradata/xifenfei/undotbs03.dbf Deleted file /data/oradata/xifenfei/undotbs04.dbf Deleted file /data/oradata/xifenfei/undotbs05.dbf Deleted file /data/oradata/xifenfei/undotbs06.dbf Completed: drop tablespace UNDOTBS1 INCLUDING CONTENTS AND DATAFILES CASCADE CONSTRAINTS
从这里基本上可以看出来,操作之人非常草率,在oracle回滚段还在被占用状态,直接尝试删除老undo表空间,在无法删除之后,直接暴力的使用undo回滚段异常参数,然后进行undo表空间删除.这样操作的后果屏蔽了事务的一致性,导致后续可能导致数据库一系列异常.对当前库启动过程进行跟踪发现
数据库启动的过程中查询undo$中的undotbs1信息,而该表空间不存在,所以出现此类报错,从而导致数据库无法正常启动.知道问题原因所在,那通过undo$记录,数据库即可正常启动.