有朋友找我,说他们的数据库被加密后缀名为:.[data@recovery.sx].data
通过分析发现这个文件被破坏的相对较少
通过一些技术处理,直接open数据库,并且顺利导出数据
如果您遇到此类加密情况,无法解决请联系我们,提供专业ORACLE数据库恢复技术支持
Phone:17813235971 Q Q:107644445 E-Mail:dba@xifenfei.com
有朋友找我,说他们的数据库被加密后缀名为:.[data@recovery.sx].data
数据库启动报ORA-00600 6006错误
Tue Sep 29 14:31:31 2020 SMON: enabling tx recovery Tue Sep 29 14:31:31 2020 Database Characterset is AL32UTF8 Opening with internal Resource Manager plan where NUMA PG = 2, CPUs = 4 Tue Sep 29 14:31:34 2020 SMON: Restarting fast_start parallel rollback Tue Sep 29 14:31:34 2020 replication_dependency_tracking turned off (no async multimaster replication found) Starting background process QMNC QMNC started with pid=64, OS id=2860 Tue Sep 29 14:31:39 2020 Errors in file g:\oracle\product\10.2.0\admin\orcl\bdump\orcl_p000_1084.trc: ORA-00600: internal error code, arguments: [6006], [1], [], [], [], [], [], [] Tue Sep 29 14:31:44 2020 SMON: Parallel transaction recovery slave got internal error SMON: Downgrading transaction recovery to serial Tue Sep 29 14:31:48 2020 Completed: ALTER DATABASE OPEN Tue Sep 29 14:31:48 2020 Errors in file g:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_3084.trc: ORA-00600: internal error code, arguments: [6006], [1], [], [], [], [], [], [] Tue Sep 29 14:31:48 2020 db_recovery_file_dest_size of 8192 MB is 0.00% used. This is a user-specified limit on the amount of space that will be used by this database for recovery-related files, and does not reflect the amount of space available in the underlying filesystem or ASM diskgroup. Tue Sep 29 14:31:53 2020 ORACLE Instance orcl (pid = 16) - Error 600 encountered while recovering transaction (1, 8) on object 53228. Tue Sep 29 14:31:54 2020 Errors in file g:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_3084.trc: ORA-00600: internal error code, arguments: [6006], [1], [], [], [], [], [], [] Tue Sep 29 14:32:03 2020 Errors in file g:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_3084.trc: ORA-00600: internal error code, arguments: [6006], [1], [], [], [], [], [], [] Tue Sep 29 14:32:07 2020 ORACLE Instance orcl (pid = 16) - Error 600 encountered while recovering transaction (1, 8) on object 53228. Tue Sep 29 14:32:07 2020 Errors in file g:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_3084.trc: ORA-00600: internal error code, arguments: [6006], [1], [], [], [], [], [], [] Tue Sep 29 14:32:13 2020 Errors in file g:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_3084.trc: ORA-00600: internal error code, arguments: [6006], [1], [], [], [], [], [], [] ORACLE Instance orcl (pid = 16) - Error 600 encountered while recovering transaction (1, 8) on object 53228. Tue Sep 29 14:32:15 2020 Errors in file g:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_3084.trc: ORA-00600: internal error code, arguments: [6006], [1], [], [], [], [], [], [] Tue Sep 29 14:32:21 2020 Errors in file g:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_3084.trc: ORA-00600: internal error code, arguments: [6006], [1], [], [], [], [], [], [] Tue Sep 29 14:32:23 2020 ORACLE Instance orcl (pid = 16) - Error 600 encountered while recovering transaction (1, 8) on object 53228. Tue Sep 29 14:32:23 2020 Errors in file g:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_3084.trc: ORA-00600: internal error code, arguments: [6006], [1], [], [], [], [], [], [] Tue Sep 29 14:32:30 2020 Errors in file g:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_3084.trc: ORA-00600: internal error code, arguments: [6006], [1], [], [], [], [], [], [] Tue Sep 29 14:32:31 2020 Errors in file g:\oracle\product\10.2.0\admin\orcl\bdump\orcl_pmon_3860.trc: ORA-00474: SMON process terminated with error Tue Sep 29 14:32:31 2020 PMON: terminating instance due to error 474
因为这个错误提示比较明显“ORACLE Instance orcl (pid = 16) – Error 600 encountered while recovering transaction (1, 8) on object 53228.”和以前的文章:ORACLE Instance XFF (pid = 18) – Error 600 encountered while recovering transaction非常相似,由于数据库异常关闭导致事务无法正常回滚.通过屏蔽回滚(event 10513),然后对相关对象进行处理(表导出数据,重新导入;index 进行重建),可以实现数据库的完美恢复
关于ORA-600 6006 ORA-600 6856解释
ORA-00600: internal error code, arguments: [6006], [1], [], [], [], [], [], [] Oracle is undoing an index leaf key operation. If the key is not found, --oracle 回滚index leaf key操作,如果这个值不存在,报ORA-600 6006错误 ORA-00600: internal error code, arguments: [6856], [0], [60], [], [], [] SMON is trying to recover a dead transaction. But the undo application runs into an internal error (trying to delete a row that is already deleted). --oracle 的回滚操作尝试删除一个已经删除的记录报ORA-600 6856错误
一般由于归档日志丢失或者非归档库可能在数据库启动的时候出现类似如下错误
SQL> startup ORACLE instance started. Total System Global Area 2137886720 bytes Fixed Size 2282960 bytes Variable Size 587205168 bytes Database Buffers 1543503872 bytes Redo Buffers 4894720 bytes Database mounted. ORA-01113: file 1 needs media recovery ORA-01110: data file 1: 'F:\ORADATA\XIFENFEI\SYSTEM01.DBF'
主要是由于数据文件不一致需要比较老的日志,但是日志不存在从而导致该问题
现在可以通过Oracle Recovery Tools工具一键解决
SQL> recover database; Media recovery complete. SQL> alter database open; Database altered.
软件下载:OraRecovery下载
使用说明:使用说明
17813235971 |
QQ 咨询 |