标签云
asm恢复 bbed bootstrap$ dul In Memory kcbzib_kcrsds_1 kccpb_sanity_check_2 MySQL恢复 ORA-00312 ORA-00607 ORA-00704 ORA-00742 ORA-01110 ORA-01555 ORA-01578 ORA-01595 ORA-08103 ORA-600 2131 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-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)
- 操作系统 (103)
- 数据库 (1,762)
- DB2 (22)
- MySQL (76)
- Oracle (1,604)
- Data Guard (52)
- EXADATA (8)
- GoldenGate (24)
- ORA-xxxxx (166)
- 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 监听 (28)
- Oracle备份恢复 (588)
- Oracle安装升级 (97)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (85)
- PostgreSQL (30)
- pdu工具 (6)
- PostgreSQL恢复 (9)
- SQL Server (32)
- SQL Server恢复 (13)
- TimesTen (7)
- 达梦数据库 (3)
- 达梦恢复 (1)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (39)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (22)
-
最近发表
- 解决一次硬件恢复之后数据文件0kb的故障恢复case
- Error in invoking target ‘libasmclntsh19.ohso libasmperl19.ohso client_sharedlib’问题处理
- ORA-01171: datafile N going offline due to error advancing checkpoint
- linux环境oracle数据库被文件系统勒索加密为.babyk扩展名溯源
- ORA-600 ksvworkmsgalloc: bad reaper
- ORA-600 krccfl_chunk故障处理
- Oracle Recovery Tools恢复案例总结—202505
- ORA-600 kddummy_blkchk 数据库循环重启
- 记录一次asm disk加入到vg通过恢复直接open库的案例
- CHECKDB 发现了 N 个分配错误和 M 个一致性错误
- 达梦数据库dm.ctl文件异常恢复
- Oracle Recovery Tools修复ORA-00742、ORA-600 ktbair2: illegal inheritance故障
- 可能是 tempdb 空间用尽或某个系统表不一致故障处理
- 11.2.0.4库中遇到ORA-600 kcratr_nab_less_than_odr报错
- [MY-013183] [InnoDB] Assertion failure故障处理
- Oracle 19c 202504补丁(RUs+OJVM)-19.27
- Oracle Recovery Tools修复ORA-600 6101/kdxlin:psno out of range故障
- pdu完美支持金仓数据库恢复(KingbaseES)
- 虚拟机故障引起ORA-00310 ORA-00334故障处理
- pg创建gbk字符集库
分类目录归档:数据库
差点被误操作的ORA-600 kcratr_nab_less_than_odr故障
晚上接到一个客户电话,数据库无法启动,咨询我的Oracle Recovery Tools工具的授权问题,我远程登录客户的环境进行查看故障,发现客户进行了一下操作导致最后open报ORA-01152错误
C:\Users\Administrator>sqlplus sys/sys as sysdba SQL*Plus: Release 11.2.0.1.0 Production on Tue Mar 18 22:43:24 2025 Copyright (c) 1982, 2010, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> startup mount ORACLE instance started. Total System Global Area 1603411968 bytes Fixed Size 2176168 bytes Variable Size 973081432 bytes Database Buffers 620756992 bytes Redo Buffers 7397376 bytes Database mounted. SQL> recover database; Media recovery complete. SQL> alter database open; alter database open * ERROR at line 1: ORA-00600: internal error code, arguments: [kcratr_nab_less_than_odr], [1], [27890], [1589], [1649], [], [], [], [], [], [], [] SQL> recover database; ORA-00283: 恢复会话因错误而取消 ORA-00264: 不要求恢复 SQL> alter database open; alter database open * ERROR at line 1: ORA-00600: internal error code, arguments: [kcratr_nab_less_than_odr], [1], [27890], [1589], [1649], [], [], [], [], [], [], [] SQL> recover database until cancel; ORA-10879: error signaled in parallel recovery slave ORA-01547: 警告: RECOVER 成功但 OPEN RESETLOGS 将出现如下错误 ORA-01152: 文件 1 没有从过旧的备份中还原 ORA-01110: 数据文件 1: 'D:\APP\ADMINISTRATOR\ORADATA\orcl\SYSTEM01.DBF' SQL> alter database open resetlogs; alter database open resetlogs * ERROR at line 1: ORA-01152: file 1 was not restored from a sufficiently old backup ORA-01110: data file 1: 'D:\APP\ADMINISTRATOR\ORADATA\orcl\SYSTEM01.DBF' SQL> RECOVER DATABASE USING BACKUP CONTROLFILE; ORA-00279: change 17384974762395 generated at 03/18/2025 18:30:34 needed for thread 1 ORA-00289: suggestion : D:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\orcl\ARCHIVELOG\2025_03_19\O1_MF_1_27 890_%U_.ARC ORA-00280: change 17384974762395 for thread 1 is in sequence #27890 Specify log: {<RET>=suggested | filename | AUTO | CANCEL} D\APP\ADMINISTRATOR\ORADATA\orcl\RED001.LOG ORA-00308: 无法打开归档日志 'D\APP\ADMINISTRATOR\ORADATA\orcl\RED001.LOG' ORA-27041: 无法打开文件 OSD-04002: 无法打开文件 O/S-Error: (OS 3) 系统找不到指定的路径。 Specify log: {<RET>=suggested | filename | AUTO | CANCEL} D:\app\Administrator\oradata\orcl\RED001.LOG ORA-00308: 无法打开归档日志 'D:\app\Administrator\oradata\orcl\RED001.LOG' ORA-27041: 无法打开文件 OSD-04002: 无法打开文件 O/S-Error: (OS 2) 系统找不到指定的文件。
最初数据库启动报ORA-600 kcratr_nab_less_than_odr错误(这个是一个非常典型的错误,早期写过处理方法:ORA-600 kcratr_nab_less_than_odr故障解决),客户处理故障思路不太清晰,使用了recover database until cancel和alter database open resetlogs等不当操作,导致数据库没有open成功.然后希望使用我的Oracle Recovery Tools小工具进行修复,但是根据我的判断,这个故障还用不上该工具,直接可以open库.对其进行ctl重建并open库
SQL> alter database backup controlfile to trace as 'd:/ctl.txt'; Database altered. SQL> create pfile='d:/pfile.txt' from spfile; File created. SQL> shutdown immediate; ORA-01109: database not open Database dismounted. ORACLE instance shut down. SQL> startup nomount; ORACLE instance started. Total System Global Area 1603411968 bytes Fixed Size 2176168 bytes Variable Size 973081432 bytes Database Buffers 620756992 bytes Redo Buffers 7397376 bytes SQL> @d:/xifenfei/rectl.sql Control file created. SQL> SQL> SQL> recover database; Media recovery complete. SQL> alter database open; Database altered.
在open之后,数据库报ORA-600 4194错误
Wed Mar 19 01:51:12 2025 alter database open Beginning crash recovery of 1 threads parallel recovery started with 23 processes Started redo scan Completed redo scan read 793 KB redo, 0 data blocks need recovery Started redo application at Thread 1: logseq 27890, block 2, scn 17384974741793 Recovery of Online Redo Log: Thread 1 Group 4 Seq 27890 Reading mem 0 Mem# 0: D:\APP\ADMINISTRATOR\ORADATA\orcl\REDO04.LOG Completed redo application of 0.00MB Completed crash recovery at Thread 1: logseq 27890, block 1589, scn 17384974762395 0 data blocks read, 0 data blocks written, 793 redo k-bytes read Wed Mar 19 01:51:14 2025 Thread 1 advanced to log sequence 27891 (thread open) Thread 1 opened at log sequence 27891 Current log# 2 seq# 27891 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\orcl\REDO02.LOG Successful open of redo thread 1 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Wed Mar 19 01:51:14 2025 SMON: enabling cache recovery Successfully onlined Undo Tablespace 2. Dictionary check beginning Tablespace 'TEMP' #3 found in data dictionary, but not in the controlfile. Adding to controlfile. Tablespace 'TEMP1' #11 found in data dictionary, but not in the controlfile. Adding to controlfile. Dictionary check complete Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed SMON: enabling tx recovery ********************************************************************* WARNING: The following temporary tablespaces contain no files. This condition can occur when a backup controlfile has been restored. It may be necessary to add files to these tablespaces. That can be done using the SQL statement: ALTER TABLESPACE <tablespace_name> ADD TEMPFILE Alternatively, if these temporary tablespaces are no longer needed, then they can be dropped. Empty temporary tablespace: TEMP Empty temporary tablespace: TEMP1 ********************************************************************* Database Characterset is ZHS16GBK No Resource Manager plan active Errors in file d:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_smon_4084.trc (incident=158542): ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] Incident details in: d:\app\administrator\diag\rdbms\orcl\orcl\incident\incdir_158542\orcl_smon_4084_i158542.trc Wed Mar 19 01:51:26 2025 Trace dumping is performing id=[cdmp_20250319015126] Wed Mar 19 01:51:31 2025 Sweep [inc][158542]: completed Sweep [inc2][158542]: completed Wed Mar 19 01:51:35 2025 Doing block recovery for file 3 block 1415 Resuming block recovery (PMON) for file 3 block 1415 Block recovery from logseq 27891, block 86 to scn 17384974782720 Recovery of Online Redo Log: Thread 1 Group 2 Seq 27891 Reading mem 0 Mem# 0: D:\APP\ADMINISTRATOR\ORADATA\orcl\REDO02.LOG Block recovery stopped at EOT rba 27891.87.16 Block recovery completed at rba 27891.87.16, scn 4047.3242135803 Doing block recovery for file 3 block 264 Resuming block recovery (PMON) for file 3 block 264 Block recovery from logseq 27891, block 86 to scn 17384974782714 Recovery of Online Redo Log: Thread 1 Group 2 Seq 27891 Reading mem 0 Mem# 0: D:\APP\ADMINISTRATOR\ORADATA\orcl\REDO02.LOG Block recovery completed at rba 27891.87.16, scn 4047.3242135803 Errors in file d:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_smon_4084.trc: ORA-01595: 释放区 (2) 回退段 (12) 时出错 ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] Wed Mar 19 01:51:36 2025 Errors in file d:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_ora_5680.trc (incident=158590): ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], [] Incident details in: d:\app\administrator\diag\rdbms\orcl\orcl\incident\incdir_158590\orcl_ora_5680_i158590.trc
数据库open成功,但是后台报ORA-01595/ORA-600 4194错误,这个问题比较常见,直接处理异常undo即可恢复.
win平台19c 打patch遭遇2个小问题汇总
在给19c的库打ru patch的过程中遇到两个错误,进行记录,以供以后遇到类似错误参考:
UtilSession 失败: oracle/cluster/install/InstallException
C:\Users\Administrator>F:\updatecode\WINDOWS.X64_193000_db_home\opatch\opatch apply F:\oracle_patch\37486199 Oracle 临时补丁程序安装程序版本 12.2.0.1.45 版权所有 (c) 2025, Oracle Corporation。保留所有权利。 Oracle 主目录 :F:\updatecode\WINDOWS.X64_193000_db_home 主产品清单:C:\Program Files\Oracle\Inventory 来自 : OPatch 版本 :12.2.0.1.45 OUI 版本 :12.2.0.7.0 日志文件位置:F:\updatecode\WINDOWS.X64_193000_db_home\cfgtoollogs\opatch\opatch2025-03-17_18-19-56下午_1.log Verifying environment and performing prerequisite checks... UtilSession 失败: oracle/cluster/install/InstallException Log file location: F:\updatecode\WINDOWS.X64_193000_db_home\cfgtoollogs\opatch\opatch2025-03-17_18-19-56下午_1.log OPatch failed with error code = 73
对应的日志错误部分
[2025-3-17 18:19:57] [INFO] CAS Dynamic Loading : [2025-3-17 18:19:57] [INFO] CUP_LOG: Trying to load HomeOperations object [2025-3-17 18:19:57] [INFO] CUP_LOG: HomeOperations object created. CUP1.0 is enabled [2025-3-17 18:19:57] [INFO] OPatch invoked as follows: 'apply F:\oracle_patch\37486199 ' [2025-3-17 18:19:57] [INFO] Runtime args: [-DOPatch.ORACLE_HOME=F:\updatecode\WINDOWS.X64_193000_db_home, -DOPatch.DEBUG=false, -DOPatch.RUNNING_DIR=F:\updatecode\WINDOWS.X64_193000_db_home\OPatch, -DOPatch.MW_HOME=, -DOPatch.WL_HOME=, -DOPatch.COMMON_COMPONENTS_HOME=, -DOPatch.OUI_LOCATION=, -DOPatch.FMW_COMPONENT_HOME=, -DOPatch.WEBLOGIC_CLASSPATH=, -DOPatch.OPATCH_CLASSPATH=] [2025-3-17 18:19:57] [INFO] Heap in use : 120 MB Total memory: 1917 MB Free memory : 1796 MB Max memory : 27305 MB [2025-3-17 18:19:57] [INFO] Oracle 主目录 : F:\updatecode\WINDOWS.X64_193000_db_home 主产品清单: C:\Program Files\Oracle\Inventory 从 : OPatch 版本 : 12.2.0.1.45 OUI 版本 : 12.2.0.7.0 OUI 位置 : F:\updatecode\WINDOWS.X64_193000_db_home\oui 日志文件位置 : F:\updatecode\WINDOWS.X64_193000_db_home\cfgtoollogs\opatch\opatch2025-03-17_18-19-56下午_1.log [2025-3-17 18:19:57] [INFO] Patch history file: F:\updatecode\WINDOWS.X64_193000_db_home\cfgtoollogs\opatch\opatch_history.txt [2025-3-17 18:19:59] [INFO] [OPSR-TIME] Loading raw inventory [2025-3-17 18:20:00] [INFO] [OPSR-MEMORY] Loaded all components from inventory. Heap memory in use: 150 (MB) [2025-3-17 18:20:00] [INFO] [OPSR-MEMORY] Loaded all one offs from inventory. Heap memory in use: 160 (MB) [2025-3-17 18:20:00] [INFO] [OPSR-TIME] Raw inventory loaded successfully [2025-3-17 18:20:00] [INFO] NApply::no CAS enabled, OPatch runs with legacy process. [2025-3-17 18:20:00] [INFO] Verifying environment and performing prerequisite checks... [2025-3-17 18:20:00] [INFO] [OPSR-TIME] Running prerequisite checks [2025-3-17 18:20:00] [INFO] opatch-external.jar is in F:\updatecode\WINDOWS.X64_193000_db_home\OPatch\jlib\opatch-external.jar [2025-3-17 18:20:00] [SEVERE] OUI-67073:UtilSession 失败: oracle/cluster/install/InstallException [2025-3-17 18:20:00] [INFO] Finishing UtilSession at Mon Mar 17 18:20:00 CST 2025 [2025-3-17 18:20:00] [INFO] 堆栈说明: java.lang.RuntimeException: oracle/cluster/install/InstallException at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671) at java.lang.Class.getConstructor0(Class.java:3075) at java.lang.Class.getConstructor(Class.java:1825) at oracle.opatch.OPatchExternalFactory.getRac(OPatchExternalFactory.java:158) at oracle.opatch.napplyhelper.EnvValidation.validateConnectStringNodes(EnvValidation.java:104) at oracle.opatch.napplyhelper.EnvValidation.checkConnectString(EnvValidation.java:92) at oracle.opatch.napplyhelper.EnvValidation.validate(EnvValidation.java:64) at oracle.opatch.opatchutil.NApply.legacy_process(NApply.java:530) at oracle.opatch.opatchutil.NApply.legacy_process(NApply.java:374) at oracle.opatch.opatchutil.NApply.process(NApply.java:354) at oracle.opatch.opatchutil.OUSession.napply(OUSession.java:1143) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at oracle.opatch.UtilSession.process(UtilSession.java:355) at oracle.opatch.OPatchSession.process(OPatchSession.java:2640) at oracle.opatch.OPatch.process(OPatch.java:888) at oracle.opatch.OPatch.main(OPatch.java:945) Caused by: java.lang.NoClassDefFoundError: oracle/cluster/install/InstallException ... 20 more Caused by: java.lang.ClassNotFoundException: oracle.cluster.install.InstallException at java.net.URLClassLoader.findClass(URLClassLoader.java:387) at java.lang.ClassLoader.loadClass(ClassLoader.java:418) at java.lang.ClassLoader.loadClass(ClassLoader.java:351) ... 20 more
通过mos给出来的文档:Windows:opatch file with error: [SEVERE] OUI-67073:UtilSession failed: oracle/cluster/install/InstallException (Doc ID 3020534.1),可能是由于%ORACLE_HOME%\oui\jlib\srvm.jar 文件异常导致该问题,查看打patch机器,发现该文件丢失[丢失原因未知],从37486199的patch文件中拷贝该文件到数据库对应目录,后续没有再报该错误
然后提示Prerequisite check “CheckActiveFilesAndExecutables” failed.错误
注意参考:win平台 UtilSession 失败: Prerequisite check “CheckActiveFilesAndExecutables” failed. 处理没有解决问题(因为文件本身没有被占用)
F:\oracle_patch\37486199>F:\updatecode\WINDOWS.X64_193000_db_home\opatch\opatch apply Oracle 临时补丁程序安装程序版本 12.2.0.1.45 版权所有 (c) 2025, Oracle Corporation。保留所有权利。 Oracle 主目录 :F:\updatecode\WINDOWS.X64_193000_db_home 主产品清单:C:\Program Files\Oracle\Inventory 来自 : OPatch 版本 :12.2.0.1.45 OUI 版本 :12.2.0.7.0 日志文件位置:F:\updatecode\WINDOWS.X64_193000_db_home\cfgtoollogs\opatch\opatch2025-03-17_18-34-40下午_1.log Verifying environment and performing prerequisite checks... Prerequisite check "CheckActiveFilesAndExecutables" failed. The details are: Following active files/executables/libs are used by ORACLE_HOME :F:\updatecode\WINDOWS.X64_193000_db_home F:\updatecode\WINDOWS.X64_193000_db_home\bin\oravssmsgus.dll F:\updatecode\WINDOWS.X64_193000_db_home\bin\ORAEVRUS19.dll UtilSession 失败: Prerequisite check "CheckActiveFilesAndExecutables" failed. Log file location: F:\updatecode\WINDOWS.X64_193000_db_home\cfgtoollogs\opatch\opatch2025-03-17_18-34-40下午_1.log OPatch failed with error code = 73
通过命令分析确认oravssmsgus.ddl和ORAEVRUS19.dll动态库没有被其他程序占用
F:\oracle_patch\37486199>tasklist /M ora* 信息: 没有运行的任务匹配指定标准。 F:\oracle_patch\37486199>tasklist /M ORA* 信息: 没有运行的任务匹配指定标准。
对于这种情况,根据mos文档:Database Release Update Bundle Windows Patch (XXX) Error”UtilSession failed: Prerequisite check “CheckActiveFilesAndExecutables” failed.” (Doc ID 3046640.1)建议,把对一个文件重命名
F:\updatecode\WINDOWS.X64_193000_db_home\bin>dir *bak.dll 驱动器 F 中的卷是 安全区 卷的序列号是 4407-E854 F:\updatecode\WINDOWS.X64_193000_db_home\bin 的目录 2022-07-28 17:35 4,096 ORAEVRUS19-bak.dll 2022-07-28 17:35 100,352 oravssmsgus-bak.dll 2 个文件 104,448 字节 0 个目录 680,382,025,728 可用字节
后续打patch操作一切正常,没有再出现其他问题.
pg单个数据库目录恢复-pdu恢复单个数据库目录数据
在某些情况下,无法获取pg完整的PGDATA目录中的所有数据库文件目录和文件,只能恢复出来一个数据库目录,对于这种情况,可以通过pdu进行直接恢复,比如有一个目录16805
[postgres@localhost 16805]$ pwd /tmp/16805 [postgres@localhost 16805]$ ls 112 16841 2613 2682 3079 3596 4159 113 174 2615 2683 3079_fsm 3597 4160 1247 175 2615_fsm 2684 3079_vm 3598 4163 1247_fsm 2187 2615_vm 2685 3080 3599 4164 1247_vm 2224 2616 2686 3081 3600 4165 1249 2228 2616_fsm 2687 3085 3600_fsm 4166 1249_fsm 2328 2616_vm 2688 3118 3600_vm 4167 1249_vm 2336 2617 2689 3119 3601 4168 1255 2337 2617_fsm 2690 3164 3601_fsm 4169 1255_fsm 2579 2617_vm 2691 3256 3601_vm 4170 1255_vm 2600 2618 2692 3257 3602 4171 1259 2600_fsm 2618_fsm 2693 3258 3602_fsm 4172 1259_fsm 2600_vm 2618_vm 2696 3350 3602_vm 4173 1259_vm 2601 2619 2699 3351 3603 4174 13362 2601_fsm 2619_fsm 2701 3379 3603_fsm 5002 13362_fsm 2601_vm 2619_vm 2702 3380 3603_vm 548 13362_vm 2602 2620 2703 3381 3604 549 13365 2602_fsm 2650 2704 3394 3605 6102 13366 2602_vm 2651 2753 3394_fsm 3606 6104 13367 2603 2652 2753_fsm 3394_vm 3607 6106 13367_fsm 2603_fsm 2653 2753_vm 3395 3608 6110 13367_vm 2603_vm 2654 2754 3429 3609 6111 13370 2604 2655 2755 3430 3712 6112 13371 2605 2656 2756 3431 3764 6113 13372 2605_fsm 2657 2757 3433 3764_fsm 6116 13372_fsm 2605_vm 2658 2830 3439 3764_vm 6117 13372_vm 2606 2659 2831 3440 3766 6175 13375 2606_fsm 2660 2832 3455 3767 6176 13376 2606_vm 2661 2833 3456 3997 6228 13377 2607 2662 2834 3456_fsm 4143 6229 13377_fsm 2607_fsm 2663 2835 3456_vm 4144 6237 13377_vm 2607_vm 2664 2836 3466 4145 6238 13380 2608 2665 2836_fsm 3467 4146 6239 13381 2608_fsm 2666 2836_vm 3468 4147 826 1417 2608_vm 2667 2837 3501 4148 827 1418 2609 2668 2838 3502 4149 828 16806 2609_fsm 2669 2838_fsm 3503 4150 pg_filenode.map 16806_fsm 2609_vm 2670 2838_vm 3534 4151 pg_internal.init 16806_vm 2610 2673 2839 3541 4152 PG_VERSION 16809 2610_fsm 2674 2840 3541_fsm 4153 16810 2610_vm 2675 2840_fsm 3541_vm 4154 16833 2611 2678 2840_vm 3542 4155 16833_fsm 2612 2679 2841 3574 4156 16833_vm 2612_fsm 2680 2995 3575 4157 16840 2612_vm 2681 2996 3576 4158 [postgres@localhost 16805]$
利用pdu进行恢复
PDU.public=# restore db xifenfei /tmp/16805; -pg_schema:</tmp/16805/2615> -pg_class:</tmp/16805/1259>,共86行 -pg_attribute:</tmp/16805/1249>,共3274行 模式: -->public,2张表 PDU.public=# use xifenfei; |----------------------------------------| | 模式 | 表数量 | |----------------------------------------| | public | 2 | |----------------------------------------| xifenfei.public=# set public; |--------------------------------------------------| | 表名 | 表大小 | |--------------------------------------------------| | t_cas_paymentbill | 8.24 MB | | t_auth | 80.00 KB | |--------------------------------------------------| 仅显示表大小排名前 2 的表名 xifenfei.public=# \dt; |--------------------------------------------------| | 表名 | 表大小 | |--------------------------------------------------| | t_cas_paymentbill | 8.24 MB | | t_auth | 80.00 KB | |--------------------------------------------------| 共计 2 张表 xifenfei.public=# unload sch public; 正在解析表 <t_cas_paymentbill>. 已解析数据页: 1055, 已解析数据: 9636 条 表名<t_cas_paymentbill>-</tmp/16805//16806> 解析完成, 1055 个数据页 ,共计 9636 条数据. 成功 9636 条; 失败【0】条 COPY文件路径为:<xifenfei/public/t_cas_paymentbill.csv> 正在解析表 <t_auth>. 已解析数据页: 10, 已解析数据: 129 条 表名<t_auth>-</tmp/16805//16833> 解析完成, 10 个数据页 ,共计 129 条数据. 成功 129 条; 失败【0】条 COPY文件路径为:<xifenfei/public/t_auth.csv> 模式<public>共 2 张表。成功:2, 失败【0】 日志路径:log/log/xifenfei_unload_schema_public_err.txt COPY命令导出完成, 文件路径: xifenfei/COPY/public_copy.sql,共找到2个csv文件 DDL导出完成. 文件路径: xifenfei/DDL/public_ddl.sql, 共计 2 张表 xifenfei.public=# xifenfei.public=# unload ddl; DDL导出完成. 文件路径: xifenfei/DDL/public_ddl.sql, 共计 2 张表
通过pdu解析和恢复,该目录中一共两个业务表,均正常恢复出来,创建新库,导入数据测试
postgres=# create database xifenfei; CREATE DATABASE postgres=# \c xifenfei; You are now connected to database "xifenfei" as user "postgres". xifenfei=# \i /data/tools/pdu/xifenfei/DDL/public_ddl.sql psql:/data/tools/pdu/xifenfei/DDL/public_ddl.sql:1: ERROR: schema "public" already exists SET CREATE TABLE CREATE TABLE xifenfei=# \i /data/tools/pdu/xifenfei/COPY/public_copy.sql SET COPY 9636 COPY 129 xifenfei=# select count(1) from t_auth; count ------- 129 (1 row) xifenfei=# select count(1) from t_cas_paymentbill; count ------- 9636 (1 row)