标签云
asm恢复 bbed bootstrap$ dul kcbzib_kcrsds_1 kccpb_sanity_check_2 kcratr_nab_less_than_odr MySQL恢复 ORA-00312 ORA-00704 ORA-00742 ORA-01110 ORA-01200 ORA-01555 ORA-01578 ORA-01595 ORA-600 2662 ORA-600 3020 ORA-600 4000 ORA-600 4137 ORA-600 4193 ORA-600 4194 ORA-600 16703 ORA-600 kcbzib_kcrsds_1 ORA-600 KCLCHKBLK_4 ORA-600 kcratr_nab_less_than_odr ORA-600 kdsgrp1 ORA-15042 ORA-15196 ORACLE 12C oracle dul ORACLE PATCH Oracle Recovery Tools oracle加密恢复 oracle勒索 oracle勒索恢复 oracle异常恢复 ORACLE恢复 Oracle 恢复 ORACLE数据库恢复 oracle 比特币 OSD-04016 YOUR FILES ARE ENCRYPTED 勒索恢复 比特币加密文章分类
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (110)
- 数据库 (1,827)
- DB2 (22)
- MySQL (80)
- Oracle (1,656)
- Data Guard (53)
- EXADATA (8)
- GoldenGate (24)
- ORA-xxxxx (168)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (15)
- ORACLE 21C (3)
- Oracle 23ai (8)
- Oracle ASM (69)
- Oracle Bug (8)
- Oracle RAC (54)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (29)
- Oracle备份恢复 (624)
- Oracle安装升级 (103)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (86)
- PostgreSQL (37)
- pdu工具 (7)
- PostgreSQL恢复 (13)
- SQL Server (34)
- SQL Server恢复 (14)
- TimesTen (7)
- 达梦数据库 (3)
- 达梦恢复 (1)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (45)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (28)
-
最近发表
- ORA-600 kcratr_nab_less_than_odr和ORA-600 4193故障处理
- aix环境10g由于控制器异常导致ORA-600 4000故障处理
- ORA-600 3716故障处理
- 不当恢复truncate数据导致数据库不能open处理
- 注意:PostgreSQL库出现readme_to_recover勒索
- Oracle 19c 202601补丁(RUs+OJVM)-19.30
- Patch_SCN快速解决ORA-600 2663故障
- 在生产环境错误执行dd命令破坏asm磁盘故障恢复
- obet实现对数据文件坏块检测功能
- oracle linux 8.10注意pmlogger导致空间被大量占用
- obet快速修改scn/resetlogs恢复数据库(缺少归档,ORA-00308)
- 使用DBMS_PDB.RECOVER抢救单个pdb
- aix环境写入大文件设置combehin提高效率
- 记录一次国产数据库被rm -rf /*删除的救援过程
- 数据库启动报 maximum number of processes () exceeded分析
- ORA-600 [ksunfy : too few sessions]
- 由于数据块scn大于数据库scn导致ORA-600 kcbzib_kcrsds_1错误
- ORA-600 ktbair2: illegal inheritance恢复
- 一键恢复ORA-00704 ORA-00702故障—202512
- PostgreSQL查询一个表相关的所有oid
分类目录归档:Oracle
不当恢复truncate数据导致数据库不能open处理
有客户误truncate操作干掉了数据库中的几张表,然后尝试通过FY_Recover_Data进行恢复,恢复到一半然后终止了,数据库结果就起不来了(具体什么原因不知道,肯定是各种不合适的操作引起的故障),我接手故障的时候,数据库被强制resetlogs,报ORA-600 2662错误
Fri Jan 30 10:24:16 2026 alter database open resetlogs RESETLOGS is being done without consistancy checks. This may result in a corrupted database. The database should be recreated. RESETLOGS after incomplete recovery UNTIL CHANGE 49708968810 Clearing online redo logfile 1 /u01/oracle/oradata/orcl/redo01.log Clearing online log 1 of thread 1 sequence number 1069648 Clearing online redo logfile 1 complete Clearing online redo logfile 2 /u01/oracle/oradata/orcl/redo02.log Clearing online log 2 of thread 1 sequence number 1069649 Clearing online redo logfile 2 complete Clearing online redo logfile 3 /u01/oracle/oradata/orcl/redo03.log Clearing online log 3 of thread 1 sequence number 1069647 Clearing online redo logfile 3 complete Resetting resetlogs activation ID 1738690566 (0x67a25006) Online log /u01/oracle/oradata/orcl/redo01.log: Thread 1 Group 1 was previously cleared Online log /u01/oracle/oradata/orcl/redo02.log: Thread 1 Group 2 was previously cleared Online log /u01/oracle/oradata/orcl/redo03.log: Thread 1 Group 3 was previously cleared Fri Jan 30 10:24:17 2026 Setting recovery target incarnation to 3 Fri Jan 30 10:24:17 2026 Assigning activation ID 1751706121 (0x6868ea09) Thread 1 opened at log sequence 1 Current log# 1 seq# 1 mem# 0: /u01/oracle/oradata/orcl/redo01.log Successful open of redo thread 1 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Fri Jan 30 10:24:17 2026 SMON: enabling cache recovery Errors in file /u01/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_14707.trc (incident=123363): ORA-00600: 内部错误代码, 参数: [2662], [11], [2464328561], [11], [2464328917], [12583040], [], [], [], [] Incident details in: /u01/oracle/diag/rdbms/orcl/orcl/incident/incdir_123363/orcl_ora_14707_i123363.trc Fri Jan 30 10:24:18 2026 Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Errors in file /u01/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_14707.trc: ORA-00600: 内部错误代码, 参数: [2662], [11], [2464328561], [11], [2464328917], [12583040], [], [], [], [] Errors in file /u01/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_14707.trc: ORA-00600: 内部错误代码, 参数: [2662], [11], [2464328561], [11], [2464328917], [12583040], [], [], [], [] Error 600 happened during db open, shutting down database USER (ospid: 14707): terminating the instance due to error 600 Instance terminated by USER, pid = 14707 ORA-1092 signalled during: alter database open resetlogs... Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Errors in file /u01/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_14707.trc: ORA-00600: 内部错误代码, 参数: [2662], [11], [2464328564], [11], [2464328917], [12583040], [], [], [], [] ORA-00600: 内部错误代码, 参数: [2662], [11], [2464328563], [11], [2464328917], [12583040], [], [], [], [] ORA-01092: ORACLE 实例终止。强制断开连接 ORA-00600: 内部错误代码, 参数: [2662], [11], [2464328561], [11], [2464328917], [12583040], [], [], [], [] Errors in file /u01/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_14707.trc: ORA-27300: 操作系统系统相关操作: semctl 失败, 状态为: 22 ORA-27301: 操作系统故障消息: Invalid argument ORA-27302: 错误发生在: sskgpwpost1 ORA-27303: 附加信息: semid = 32779 ORA-00600: 内部错误代码, 参数: [2662], [11], [2464328564], [11], [2464328917], [12583040], [], [], [], [] ORA-00600: 内部错误代码, 参数: [2662], [11], [2464328563], [11], [2464328917], [12583040], [], [], [], [] ORA-01092: ORACLE 实例终止。强制断开连接 ORA-00603: ORACLE server session terminated by fatal error ORA-00600: internal error code, arguments: [2662], [11], [2464328564], [11], [2464328917], [12583040], [] ORA-00600: internal error code, arguments: [2662], [11], [2464328563], [11], [2464328917], [12583040], [] ORA-01092: ORACLE instance terminated. Disconnection forced ORA-00600: internal error code, arguments: [2662], [11], [2464328561], [11], [2464328917], [12583040], []
通过Oracle数据库异常恢复检查脚本(Oracle Database Recovery Check)脚本检查发现有文件被offline,且resetlogs 信息不对

通过obet工具(Oracle数据块编辑工具( Oracle Block Editor Tool)-obet)对resetlogs相关信息进行修改
OBET> set mode edit mode set to: edit OBET> set file 18 filename set to: /tmp/FY_RST_DATA.DAT (file#18) OBET> copy resetlogscn file 1 to file 18 Confirm Modify resetlogscn: Source: file#1 (/u01/oracle/oradata/orcl/system01.dbf) Target: file#18 (/tmp/FY_RST_DATA.DAT) Proceed? (Y/YES to confirm): y Successfully copied resetlog SCN information from file#1 to file#18. OBET> copy chkscn file 1 to file 18 Confirm Modify chkscn: Source: file#1 (/u01/oracle/oradata/orcl/system01.dbf) Target: file#18 (/tmp/FY_RST_DATA.DAT) Proceed? (Y/YES to confirm): y Successfully copied checkpoint SCN information from file#1 to file#18. OBET> sum Check value for File /tmp/FY_RST_DATA.DAT, Block 1: current = 0xF8EA, required = 0xFCEA OBET> sum check Warning: Unknown option 'check', ignored Check value for File /tmp/FY_RST_DATA.DAT, Block 1: current = 0xF8EA, required = 0xFCEA OBET> sum apply Confirm applying checksum: File: /tmp/FY_RST_DATA.DAT Block: 1 Offset in block: 16 (file offset: 0x00002010) Original value: 0xF8EA New value: 0xFCEA Confirm? (Y/YES to proceed): y Verification successful: Stored checksum matches calculated value (0xFCEA). Checksum applied successfully.
然后尝试打开库,报ORA-600 kdourp_inorder2错误
Database Characterset is ZHS16GBK Errors in file /u01/oracle/diag/rdbms/orcl/orcl/trace/orcl_smon_9198.trc (incident=159324): ORA-00600: internal error code, arguments: [kdourp_inorder2], [16], [0], [146], [108], [], [], [], [], [] Incident details in: /u01/oracle/diag/rdbms/orcl/orcl/incident/incdir_159324/orcl_smon_9198_i159324.trc Stopping background process MMNL Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Block recovery from logseq 2, block 39 to scn 49708988852 Recovery of Online Redo Log: Thread 1 Group 2 Seq 2 Reading mem 0 Mem# 0: /u01/oracle/oradata/orcl/redo02.log Block recovery completed at rba 2.42.16, scn 11.2464348597 ORACLE Instance orcl (pid = 14) - Error 600 encountered while recovering transaction (14, 8) on object 14. Errors in file /u01/oracle/diag/rdbms/orcl/orcl/trace/orcl_smon_9198.trc: ORA-00600: internal error code, arguments: [kdourp_inorder2], [16], [0], [146], [108], [], [], [], [], [] Stopping background process MMON Fri Jan 30 11:42:26 2026 Errors in file /u01/oracle/diag/rdbms/orcl/orcl/trace/orcl_smon_9198.trc (incident=159325): ORA-00600: internal error code, arguments: [kdourp_inorder2], [16], [0], [146], [108], [], [], [], [], [] Incident details in: /u01/oracle/diag/rdbms/orcl/orcl/incident/incdir_159325/orcl_smon_9198_i159325.trc Starting background process MMON Fri Jan 30 11:42:27 2026 MMON started with pid=49, OS id=10684 Starting background process MMNL Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Block recovery from logseq 2, block 39 to scn 49708988852 Recovery of Online Redo Log: Thread 1 Group 2 Seq 2 Reading mem 0 Mem# 0: /u01/oracle/oradata/orcl/redo02.log Block recovery completed at rba 2.42.16, scn 11.2464348597 ORACLE Instance orcl (pid = 14) - Error 600 encountered while recovering transaction (14, 8) on object 14. Errors in file /u01/oracle/diag/rdbms/orcl/orcl/trace/orcl_smon_9198.trc: ORA-00600: internal error code, arguments: [kdourp_inorder2], [16], [0], [146], [108], [], [], [], [], []
该报错比较明显是由于undo回滚段异常导致,通过屏蔽回滚段,open库成功.后续对客户truncate的表进行分析,比较悲催由于没有第一时间保护现场而且对所在表空间进行了大量写入操作,导致truncate数据恢复较少.
Oracle 19c 202601补丁(RUs+OJVM)-19.30
| Description | Database Update | GI Update | Windows Bundle Patch |
| JAN2026(19.30.0.0.0) | 38632161 | 38629535 | 38597735 |
| OCT2025(19.29.0.0.0) | 38291812 | 38298204 | 38111211 |
| JUL2025 (19.28.0.0.0) | 37960098 | 37957391 | 37962957 |
| APR2025 (19.27.0.0.0) | 37642901 | 37641958 | 37532350 |
| JAN2025 (19.26.0.0.0) | 37260974 | 37257886 | 37486199 |
| OCT2024 (19.25.0.0.0) | 36912597 | 36916690 | 36878821 |
| JUL2024 (19.24.0.0.0) | 36582781 | 36582629 | 36521936 |
| APR2024 (19.23.0.0.0) | 36233263 | 36233126 | 36219938 |
| JAN2024 (19.22.0.0.0) | 35943157 | 35940989 | 35962832 |
| OCT2023 (19.21.0.0.0) | 35643107 | 35642822 | 35681552 |
| JUL2023 (19.20.0.0.0) | 35320081 | 35319490 | 35348034 |
| APR2023 (19.19.0.0.0) | 35042068 | 35037840 | 35046439 |
| JAN2023 (19.18.0.0.0) | 34765931 | 34762026 | 34750795 |
| Oct2022 (19.17.0.0.0) | 34419443 | 34416665 | 34468114 |
| JUL2022 (19.16.0.0.0) | 34133642 | 34130714 | 34110685 |
| APR2022 (19.15.0.0.0) | 33806152 | 33803476 | 33829175 |
| JAN2022 (19.14.0.0.0) | 33515361 | 33509923 | 33575656 |
| OCT2021(19.13.0.0.0) | 33192793 | 33182768 | 33155330 |
| JUL2021 (19.12.0.0.0) | 32904851 | 32895426 | 32832237 |
| APR2021 (19.11.0.0.0) | 32545013 | 32545008 | 32409154 |
| JAN2021 (19.10.0.0.0) | 32218454 | 32226239 | 32062765 |
| OCT2020 (19.9.0.0.0) | 31771877 | 31750108 | 31719903 |
| JUL2020 (19.8.0.0.0) | 31281355 | 31305339 | 31247621 |
| APR2020 (19.7.0.0.0) | 30869156 | 30899722 | 30901317 |
| JAN2020 (19.6.0.0.0) | 30557433 | 30501910 | 30445947 |
| OCT2019 (19.5.0.0.0) | 30125133 | 30116789 | 30151705 |
| JUL2019 (19.4.0.0.0) | 29834717 | 29708769 | NA |
| APR2019 (19.3.0.0.0) | 29517242 | 29517302 | NA |
| Description | OJVM Update | OJVM + DB Update | OJVM + GI Update |
| JAN2025(19.30.0.0.26.01.20) | 38523609 | 38658587 | 38658588 |
| OCT2025(19.29.0.0.25.10.21) | 38194382 | 38273545 | 38273558 |
| JUL2025 (19.28.0.0.250715) | 37847857 | 37952354 | 37952382 |
| APR2025 (19.27.0.0.250415) | 37499406 | 37591483 | 37591516 |
| JAN2025 (19.26.0.0.250121) | 37102264 | 37262172 | 37262208 |
| OCT2024 (19.25.0.0.241015) | 36878697 | 36866623 | 36866740 |
| JUL2024 (19.24.0.0.240716) | 36414915 | 36522340 | 36522439 |
| APR2024 (19.23.0.0.240416) | 36199232 | 36209492 | 36209493 |
| JAN2024 (19.22.0.0.240116) | 35926646 | 36031426 | 36031453 |
| OCT2023 (19.21.0.0.231017) | 35648110 | 35742413 | 35742441 |
| JUL2023 (19.20.0.0.230718) | 35354406 | 35370174 | 35370167 |
| APR2023 (19.19.0.0.230418) | 35050341 | 35058163 | 35058172 |
| JAN2023 (19.18.0.0.230117) | 34786990 | 34773489 | 34773504 |
| OCT2022 (19.17.0.0.221018) | 34411846 | 34449114 | 34449117 |
| JUL2022 (19.16.0.0.220719) | 34086870 | 34160831 | 34160854 |
| APR2022 (19.15.0.0.220419) | 33808367 | 33859194 | 33859214 |
| JAN2022 (19.14.0.0.220118) | 33561310 | 33567270 | 33567274 |
| OCT2021 (19.13.0.0.211019) | 33192694 | 33248420 | 33248471 |
| JUL2021 (19.12.0.0.210720) | 32876380 | 32900021 | 32900083 |
| APR2021 (19.11.0.0.210420) | 32399816 | 32578972 | 32578973 |
| JAN2021 (19.10.0.0.210119) | 32067171 | 32126828 | 32126842 |
| OCT2020 (19.9.0.0.201020) | 31668882 | 31720396 | 31720429 |
| JUL2020 (19.8.0.0.200714) | 31219897 | 31326362 | 31326369 |
| APR2020 (19.7.0.0.200414) | 30805684 | 30783543 | 30783556 |
| JAN2020 (19.6.0.0.200114) | 30484981 | 30463595 | 30463609 |
| OCT2019 (19.5.0.0.191015) | 30128191 | 30133124 | 30133178 |
| JUL2019 (19.4.0.0.190716) | 29774421 | 29699079 | 29699097 |
| APR2019 (19.3.0.0.190416) | 29548437 | 29621253 | 29621299 |
最新的patch信息整合来自:Primary Note for Database Quarterly Release Updates KB106822
Patch_SCN快速解决ORA-600 2663故障
一个维保客户和我说他们测试库删除了日志文件导致库无法启动,让我帮忙看看
客户现场现况
1. 磁盘空间使用100%
[oracle@We1-db_Test ~]$ df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 3.9G 880K 3.9G 1% /run tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup /dev/vda1 40G 38G 92M 100% / tmpfs 783M 0 783M 0% /run/user/0
2. 数据库redo被删除了部分,而且是active状态的被删除
[oracle@We1-db_Test ~]$ ls -l /opt/app/oracle/oradata/orcl/redo0*
-rw-r----- 1 oracle oinstall 52429312 Jan 15 15:29 /opt/app/oracle/oradata/orcl/redo04.log
-rw-r----- 1 oracle oinstall 52429312 Jan 15 16:26 /opt/app/oracle/oradata/orcl/redo05.log
SQL> select group#,SEQUENCE#,STATUS FROM V$lOG;
GROUP# SEQUENCE# STATUS
---------- ---------- ----------------
1 8989 CURRENT
2 0 UNUSED
5 0 UNUSED
4 0 UNUSED
3 8988 ACTIVE
SQL> select member from v$logfile;
MEMBER
-----------------------------------------------------
/opt/app/oracle/oradata/orcl/redo03.log
/opt/app/oracle/oradata/orcl/redo02.log
/opt/app/oracle/oradata/orcl/redo01.log
/opt/app/oracle/oradata/orcl/redo04.log
/opt/app/oracle/oradata/orcl/redo05.log
基于当前情况,直接open库无望,但是空间不足问题需要先解决,不然恢复过程中创建redo空间不足依旧会报错卡死,所以先清理了监听和alert等日志,系统空闲了3G多空间,可以进行恢复操作
[oracle@We1-db_Test trace]$ df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 3.9G 880K 3.9G 1% /run tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup /dev/vda1 40G 34G 3.9G 90% / tmpfs 783M 0 783M 0% /run/user/0
恢复数据库
1. 由于active redo丢失,毫无疑问,直接强制拉库,使用_allow_resetlogs_corruption参数开干
SQL> startup mount pfile='/tmp/pfile';
ORACLE instance started.
Total System Global Area 2455228416 bytes
Fixed Size 2255712 bytes
Variable Size 905970848 bytes
Database Buffers 1526726656 bytes
Redo Buffers 20275200 bytes
Database mounted.
SQL> recover database until cancel;
ORA-00283: recovery session canceled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
SQL> recover database using backup controlfile;
ORA-00279: change 311982775 generated at 12/31/2025 17:35:11 needed for thread
1
ORA-00289: suggestion :
/opt/app/oracle/fast_recovery_area/ORCL/archivelog/2026_01_16/o1_mf_1_8988_%u_.a
rc
ORA-00280: change 311982775 for thread 1 is in sequence #8988
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00600: internal error code, arguments: [2663], [0], [311982792], [0],
[311982833], [], [], [], [], [], [], []
Process ID: 11917
Session ID: 576 Serial number: 3
alert日志报错
Fri Jan 16 21:25:31 2026 Assigning activation ID 1750515127 (0x6856bdb7) Thread 1 opened at log sequence 1 Current log# 1 seq# 1 mem# 0: /opt/app/oracle/oradata/orcl/redo01.log Successful open of redo thread 1 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Fri Jan 16 21:25:31 2026 SMON: enabling cache recovery Errors in file /opt/app/oracle/diag/rdbms/orcl/we1db/trace/we1db_ora_11917.trc (incident=81753): ORA-00600: internal error code, arguments: [2663], [0], [311982792], [0], [311982833], [], [] Incident details in: /opt/app/oracle/diag/rdbms/orcl/we1db/incident/incdir_81753/we1db_ora_11917_i81753.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Errors in file /opt/app/oracle/diag/rdbms/orcl/we1db/trace/we1db_ora_11917.trc: ORA-00600: internal error code, arguments: [2663], [0], [311982792], [0], [311982833], [], [] Errors in file /opt/app/oracle/diag/rdbms/orcl/we1db/trace/we1db_ora_11917.trc: ORA-00600: internal error code, arguments: [2663], [0], [311982792], [0], [311982833], [], [] Error 600 happened during db open, shutting down database USER (ospid: 11917): terminating the instance due to error 600 Instance terminated by USER, pid = 11917 ORA-1092 signalled during: alter database open resetlogs... opiodr aborting process unknown ospid (11917) as a result of ORA-1092 Fri Jan 16 21:25:33 2026 ORA-1092 : opitsk aborting process
不幸数据库遇到ORA-600 2663错误,这个故障在以前的文章中描述过,基本上和ORA-600 2662的处理思路类似,这里直接使用:Patch_SCN for Linux进行恢复
2. 使用Patch_SCN处理数据库SCN
SQL> startup nomount pfile='/tmp/pfile'; ORACLE instance started. Total System Global Area 2455228416 bytes Fixed Size 2255712 bytes Variable Size 905970848 bytes Database Buffers 1526726656 bytes Redo Buffers 20275200 bytes SQL>@rectl Control file created. SQL> recover database; Media recovery complete.
SQL> alter database open;
Database altered.
SQL> SELECT CURRENT_SCN FROM V$DATABASE;
CURRENT_SCN
----------------
322002903
到这里完成数据库open操作,后续逻辑导出完成恢复任务


加我微信(17813235971)
加我QQ(107644445)

