在没备份undo的情况下,undo丢失,重启数据库报ORA-01157错误
2013-10-14 09:02
393 查看
今天做了一下undo隐藏参数的实验
在没有备份的情况下,删除正在使用的undo,然后关机
(本次使用的的oracle的隐藏参数,慎用!!!!!!!!!!!!!!)
idle> select * from V$VERSION;
BANNER
----------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi
PL/SQL Release 10.2.0.1.0 - Production
CORE10.2.0.1.0Production
TNS for Linux: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
sys@DNDN> startup
ORACLE instance started.
Total System Global Area 335544320 bytes
Fixed Size 2020640 bytes
Variable Size 117443296 bytes
Database Buffers 213909504 bytes
Redo Buffers 2170880 bytes
Database mounted.
ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
ORA-01110: data file 2: '/u01/app/oracle/oradata/dndn/undotbs1.dbf'
sys@DNDN> show parameter undo_t
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
undo_tablespace stringUNDOTBS1
在此之前我有建立有一个未使用的undo 名字叫undotbs(区别上面的undotbs1)(*注:若没有多余的undo,则见文章最后解决办法)
sys@DNDN>shutdown immediate;
idle> startup nomount;
ORACLE instance started.
Total System Global Area 335544320 bytes
Fixed Size 2020640 bytes
Variable Size 117443296 bytes
Database Buffers 213909504 bytes
Redo Buffers 2170880 bytes
#把undo_tablespace 修改成备用的undo
idle>alter system set undo_tablespace=undotbs scope=spfile;
#把undo改成手动管理
idle> alter system set undo_management=manual scope=spfile;
System altered.
#使用隐藏参数
idle> alter system set "_offline_rollback_segments"=true scope=spfile;
System altered.
idle> shutdown immediate;
idle> startup
ORACLE instance started.
Total System Global Area 335544320 bytes
Fixed Size 2020640 bytes
Variable Size 117443296 bytes
Database Buffers 213909504 bytes
Redo Buffers 2170880 bytes
Database mounted.
Database opened.
这样数据库就可以打开了!
查看UNDOTBS1 (之前丢失的表空间) 中的段的状态是否都是offline
idle> select segment_name,tablespace_name,status from dba_rollback_segs;
SEGMENT_NAME TABLESPACE_NAME STATUS
------------------------------ ------------------------------ ----------------
SYSTEM SYSTEM ONLINE
_SYSSMU1$ UNDOTBS1 OFFLINE
_SYSSMU2$ UNDOTBS1 OFFLINE
_SYSSMU3$ UNDOTBS1 OFFLINE
_SYSSMU4$ UNDOTBS1 OFFLINE
_SYSSMU5$ UNDOTBS1 OFFLINE
_SYSSMU6$ UNDOTBS1 OFFLINE
_SYSSMU7$ UNDOTBS1 OFFLINE
_SYSSMU8$ UNDOTBS1 OFFLINE
_SYSSMU9$ UNDOTBS1 OFFLINE
_SYSSMU10$ UNDOTBS1 OFFLINE
_SYSSMU11$ UNDOTBS OFFLINE
_SYSSMU12$ UNDOTBS OFFLINE
_SYSSMU13$ UNDOTBS OFFLINE
_SYSSMU14$ UNDOTBS OFFLINE
_SYSSMU15$ UNDOTBS OFFLINE
_SYSSMU16$ UNDOTBS OFFLINE
_SYSSMU17$ UNDOTBS OFFLINE
_SYSSMU18$ UNDOTBS OFFLINE
_SYSSMU19$ UNDOTBS OFFLINE
_SYSSMU20$ UNDOTBS OFFLINE
21 rows selected.
若UNDOTBS1 (之前丢失的表空间) 中的段的状态都是offline,则可以删除该undo表空间(否则,则要用到另一个隐藏参数"_corrupted_rollback_segments"把不为offline的段全用此参数设置即可删除该undo表空间 eg: alter system set "_corrupted_rollback_segments"='_SYSSMU8$' scope=spfile;或 alter system set "_corrupted_rollback_segments"='_SYSSMU8$','_SYSSMU9$' scope=spfile)
idle> drop tablespace undotbs1 including contents and datafiles;
当然打开后还要重置一下undo_management和_offline_rollback_segments
idle> alter system set undo_management=auto scope=spfile;
System altered.
idle> alter system reset "_offline_rollback_segments" scope=spfile sid='*';
System altered.
idle>shutdown immediate;
idle> startup
ORACLE instance started.
Total System Global Area 335544320 bytes
Fixed Size 2020640 bytes
Variable Size 121637600 bytes
Database Buffers 209715200 bytes
Redo Buffers 2170880 bytes
Database mounted.
Database opened.
ok!!!!!!
上面说的是有未使用的undo表空间的情况,若只有一个undo,且丢失损坏,则在数据库重启报错后,先设置隐藏参数_offline_rollback_segments和undo_management,重启,会再报错,再把这个undo给offline,就可以打开了,打开之后 删除丢失或损坏的undo,重建undo,修改参数文件指定undo,重置参数上面, 重启即可。(主要大概思路同上面方法)
注:隐藏参数
idle> select ksppinm from x$ksppi where ksppinm like '%roll%';
KSPPINM
--------------------------------------------------------------------------------
transactions_per_rollback_segment
rollback_segments
_rollback_segment_initial
_rollback_segment_count
_offline_rollback_segments
_corrupted_rollback_segments
_cleanup_rollback_entries
_rollback_stopat
fast_start_parallel_rollback
_mv_rolling_inv
10 rows selected.
在没有备份的情况下,删除正在使用的undo,然后关机
(本次使用的的oracle的隐藏参数,慎用!!!!!!!!!!!!!!)
idle> select * from V$VERSION;
BANNER
----------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi
PL/SQL Release 10.2.0.1.0 - Production
CORE10.2.0.1.0Production
TNS for Linux: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
sys@DNDN> startup
ORACLE instance started.
Total System Global Area 335544320 bytes
Fixed Size 2020640 bytes
Variable Size 117443296 bytes
Database Buffers 213909504 bytes
Redo Buffers 2170880 bytes
Database mounted.
ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
ORA-01110: data file 2: '/u01/app/oracle/oradata/dndn/undotbs1.dbf'
sys@DNDN> show parameter undo_t
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
undo_tablespace stringUNDOTBS1
在此之前我有建立有一个未使用的undo 名字叫undotbs(区别上面的undotbs1)(*注:若没有多余的undo,则见文章最后解决办法)
sys@DNDN>shutdown immediate;
idle> startup nomount;
ORACLE instance started.
Total System Global Area 335544320 bytes
Fixed Size 2020640 bytes
Variable Size 117443296 bytes
Database Buffers 213909504 bytes
Redo Buffers 2170880 bytes
#把undo_tablespace 修改成备用的undo
idle>alter system set undo_tablespace=undotbs scope=spfile;
#把undo改成手动管理
idle> alter system set undo_management=manual scope=spfile;
System altered.
#使用隐藏参数
idle> alter system set "_offline_rollback_segments"=true scope=spfile;
System altered.
idle> shutdown immediate;
idle> startup
ORACLE instance started.
Total System Global Area 335544320 bytes
Fixed Size 2020640 bytes
Variable Size 117443296 bytes
Database Buffers 213909504 bytes
Redo Buffers 2170880 bytes
Database mounted.
Database opened.
这样数据库就可以打开了!
查看UNDOTBS1 (之前丢失的表空间) 中的段的状态是否都是offline
idle> select segment_name,tablespace_name,status from dba_rollback_segs;
SEGMENT_NAME TABLESPACE_NAME STATUS
------------------------------ ------------------------------ ----------------
SYSTEM SYSTEM ONLINE
_SYSSMU1$ UNDOTBS1 OFFLINE
_SYSSMU2$ UNDOTBS1 OFFLINE
_SYSSMU3$ UNDOTBS1 OFFLINE
_SYSSMU4$ UNDOTBS1 OFFLINE
_SYSSMU5$ UNDOTBS1 OFFLINE
_SYSSMU6$ UNDOTBS1 OFFLINE
_SYSSMU7$ UNDOTBS1 OFFLINE
_SYSSMU8$ UNDOTBS1 OFFLINE
_SYSSMU9$ UNDOTBS1 OFFLINE
_SYSSMU10$ UNDOTBS1 OFFLINE
_SYSSMU11$ UNDOTBS OFFLINE
_SYSSMU12$ UNDOTBS OFFLINE
_SYSSMU13$ UNDOTBS OFFLINE
_SYSSMU14$ UNDOTBS OFFLINE
_SYSSMU15$ UNDOTBS OFFLINE
_SYSSMU16$ UNDOTBS OFFLINE
_SYSSMU17$ UNDOTBS OFFLINE
_SYSSMU18$ UNDOTBS OFFLINE
_SYSSMU19$ UNDOTBS OFFLINE
_SYSSMU20$ UNDOTBS OFFLINE
21 rows selected.
若UNDOTBS1 (之前丢失的表空间) 中的段的状态都是offline,则可以删除该undo表空间(否则,则要用到另一个隐藏参数"_corrupted_rollback_segments"把不为offline的段全用此参数设置即可删除该undo表空间 eg: alter system set "_corrupted_rollback_segments"='_SYSSMU8$' scope=spfile;或 alter system set "_corrupted_rollback_segments"='_SYSSMU8$','_SYSSMU9$' scope=spfile)
idle> drop tablespace undotbs1 including contents and datafiles;
当然打开后还要重置一下undo_management和_offline_rollback_segments
idle> alter system set undo_management=auto scope=spfile;
System altered.
idle> alter system reset "_offline_rollback_segments" scope=spfile sid='*';
System altered.
idle>shutdown immediate;
idle> startup
ORACLE instance started.
Total System Global Area 335544320 bytes
Fixed Size 2020640 bytes
Variable Size 121637600 bytes
Database Buffers 209715200 bytes
Redo Buffers 2170880 bytes
Database mounted.
Database opened.
ok!!!!!!
上面说的是有未使用的undo表空间的情况,若只有一个undo,且丢失损坏,则在数据库重启报错后,先设置隐藏参数_offline_rollback_segments和undo_management,重启,会再报错,再把这个undo给offline,就可以打开了,打开之后 删除丢失或损坏的undo,重建undo,修改参数文件指定undo,重置参数上面, 重启即可。(主要大概思路同上面方法)
注:隐藏参数
idle> select ksppinm from x$ksppi where ksppinm like '%roll%';
KSPPINM
--------------------------------------------------------------------------------
transactions_per_rollback_segment
rollback_segments
_rollback_segment_initial
_rollback_segment_count
_offline_rollback_segments
_corrupted_rollback_segments
_cleanup_rollback_entries
_rollback_stopat
fast_start_parallel_rollback
_mv_rolling_inv
10 rows selected.
相关文章推荐
- 在没备份undo的情况下,undo丢失,重启数据库报ORA-01157错误
- ORA-01157错误,丢失undo tablespace中数据文件的解决方法
- DBA手记之:数据库启动报ORA-01157和ORA-01110错误
- 总结Oracle8i 的UNDO表空间损坏(ORA-01092及ORA-00600【4193】)情况下的数据库不完全恢复的经历
- rac数据库重启之后备份控制文件报ORA-00245: control file backup failed;
- ORA-01157:无法标识/锁定数据文件,ORA-01110:表空间丢失错误
- 数据库数据文件有备份的恢复 ORA-01157 【续+1】
- 数据库数据文件没有备份的恢复 ORA-01157 【续+2】
- exp-00003的错误|如何从oracle10备份导入到oracle9 数据库中|如何从oracle的高版本备份导入到低版本中
- 对自建数据库'StuDB'出现“ORA-12505: TNS: 监听程序当前无法识别连接描述符中所给出的 SID,ora-24324 未初始化服务句柄 ora-01041 内部错误,hostdef扩展名不存在”的探索
- 数据库备份过程中经常遇到的九种情况(转)
- Linux环境下使用sqlplus登录Oracle,报'ORA-12547: TNS:lost contact’丢失连接错误
- 启动数据库ORA-12528错误
- mysqldump备份错误:诡异的#mysql50#.mozilla数据库
- 【数据恢复】解决ORA-600[4xxx]错误并打开数据库
- ORA-30052错误:修改undo-retention
- 一般情况下asp可以正常运行,但只要连接数据库就提示,Microsoft JET Database Engine 错误
- jdbc连接数据库报ORA-12519错误
- ora-01730:指定的列名数无效,这个错误有哪些情况下可能会出现?
- 恢复数据库备份时提示日志错误