标签云
asm恢复 bbed bootstrap$ dul 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 2131 ORA-600 2662 ORA-600 2663 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)
- 操作系统 (102)
- 数据库 (1,678)
- DB2 (22)
- MySQL (73)
- Oracle (1,540)
- Data Guard (52)
- EXADATA (8)
- GoldenGate (24)
- ORA-xxxxx (159)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (14)
- ORACLE 21C (3)
- Oracle 23ai (7)
- Oracle ASM (67)
- Oracle Bug (8)
- Oracle RAC (52)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (28)
- Oracle备份恢复 (563)
- Oracle安装升级 (92)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (79)
- PostgreSQL (18)
- PostgreSQL恢复 (6)
- SQL Server (27)
- SQL Server恢复 (8)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (37)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (20)
-
最近发表
- .wstop扩展名勒索数据库恢复
- Oracle Recovery Tools工具一键解决ORA-00376 ORA-01110故障(文件offline)
- OGG-02771 Input trail file format RELEASE 19.1 is different from previous trail file form at RELEASE 11.2.
- OGG-02246 Source redo compatibility level 19.0.0 requires trail FORMAT 12.2 or higher
- GoldenGate 19安装和打patch
- dd破坏asm磁盘头恢复
- 删除asmlib磁盘导致磁盘组故障恢复
- Kylin Linux 安装19c
- ORA-600 krse_arc_complete.4
- Oracle 19c 202410补丁(RUs+OJVM)
- ntfs MFT损坏(ntfs文件系统故障)导致oracle异常恢复
- .mkp扩展名oracle数据文件加密恢复
- 清空redo,导致ORA-27048: skgfifi: file header information is invalid
- A_H_README_TO_RECOVER勒索恢复
- 通过alert日志分析客户自行对一个数据库恢复的来龙去脉和点评
- ORA-12514: TNS: 监听进程不能解析在连接描述符中给出的SERVICE_NAME
- ORA-01092 ORA-00604 ORA-01558故障处理
- ORA-65088: database open should be retried
- Oracle 19c异常恢复—ORA-01209/ORA-65088
- ORA-600 16703故障再现
标签归档:ORA-01595
ORA-01595/ORA-600 4194处理
又一个客户由于服务器断电,导致oracle无法正常启动报ORA-600 4194错误
Sat Jan 20 13:45:22 2024 ALTER DATABASE OPEN Beginning crash recovery of 1 threads parallel recovery started with 32 processes Started redo scan Completed redo scan read 31 KB redo, 5 data blocks need recovery Started redo application at Thread 1: logseq 9, block 3 Recovery of Online Redo Log: Thread 1 Group 3 Seq 9 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\xff\REDO03.LOG Completed redo application of 0.02MB Completed crash recovery at Thread 1: logseq 9, block 66, scn 81924188 5 data blocks read, 5 data blocks written, 31 redo k-bytes read Thread 1 advanced to log sequence 10 (thread open) Thread 1 opened at log sequence 10 Current log# 1 seq# 10 mem# 0: D:\ORACLE\ORADATA\xff\REDO01.LOG Successful open of redo thread 1 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set SMON: enabling cache recovery Successfully onlined Undo Tablespace 2. Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed SMON: enabling tx recovery Database Characterset is AL32UTF8 No Resource Manager plan active Errors in file d:\oracle\diag\rdbms\xff\xff\trace\xff_smon_5164.trc (incident=384222): ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] Incident details in: d:\oracle\diag\rdbms\xff\xff\incident\incdir_384222\xff_smon_5164_i384222.trc Errors in file d:\oracle\diag\rdbms\xff\xff\trace\xff_ora_6832.trc (incident=384270): ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] Incident details in: d:\oracle\diag\rdbms\xff\xff\incident\incdir_384270\xff_ora_6832_i384270.trc Doing block recovery for file 3 block 207 Resuming block recovery (PMON) for file 3 block 207 Block recovery from logseq 10, block 64 to scn 81924393 Recovery of Online Redo Log: Thread 1 Group 1 Seq 10 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\xff\REDO01.LOG Block recovery stopped at EOT rba 10.66.16 Block recovery completed at rba 10.66.16, scn 0.81924391 Doing block recovery for file 3 block 160 Resuming block recovery (PMON) for file 3 block 160 Block recovery from logseq 10, block 64 to scn 81924389 Recovery of Online Redo Log: Thread 1 Group 1 Seq 10 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\xff\REDO01.LOG Block recovery completed at rba 10.64.16, scn 0.81924390 Errors in file d:\oracle\diag\rdbms\xff\xff\trace\xff_smon_5164.trc: ORA-01595: 释放区 (2) 回退段 (3) 时出错 ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] Trace dumping is performing id=[cdmp_20240120134525] Doing block recovery for file 3 block 3857 Resuming block recovery (PMON) for file 3 block 3857 Block recovery from logseq 10, block 64 to scn 81924396 Recovery of Online Redo Log: Thread 1 Group 1 Seq 10 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\xff\REDO01.LOG Block recovery stopped at EOT rba 10.66.16 Block recovery completed at rba 10.66.16, scn 0.81924391 Doing block recovery for file 3 block 272 Resuming block recovery (PMON) for file 3 block 272 Block recovery from logseq 10, block 64 to scn 81924390 Recovery of Online Redo Log: Thread 1 Group 1 Seq 10 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\xff\REDO01.LOG Block recovery completed at rba 10.66.16, scn 0.81924391 replication_dependency_tracking turned off (no async multimaster replication found) Starting background process QMNC Sat Jan 20 13:45:26 2024 QMNC started with pid=56, OS id=8052 Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0x66F8B134] [PC:0x93C7D88, kgegpa()+38] Dump file d:\oracle\diag\rdbms\xff\xff\trace\alert_xff.log Doing block recovery for file 3 block 3857 Resuming block recovery (PMON) for file 3 block 3857 Block recovery from logseq 10, block 64 to scn 81924396 Recovery of Online Redo Log: Thread 1 Group 1 Seq 10 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\xff\REDO01.LOG Block recovery completed at rba 10.66.16, scn 0.81924399 Errors in file d:\oracle\diag\rdbms\xff\xff\trace\xff_mmon_7876.trc (incident=396089): ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-06512: 在 "SYS.DBMS_HA_ALERTS_PRVT", line 310 ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], Doing block recovery for file 3 block 3857 Resuming block recovery (PMON) for file 3 block 3857 Block recovery from logseq 10, block 64 to scn 81924396 Recovery of Online Redo Log: Thread 1 Group 1 Seq 10 Reading mem 0 Mem# 0: D:\ORACLE\ORADATA\xff\REDO01.LOG Block recovery completed at rba 10.66.16, scn 0.81924399 Errors in file d:\oracle\diag\rdbms\xff\xff\trace\xff_pmon_8876.trc (incident=384102): ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] Sat Jan 20 13:45:39 2024 Errors in file d:\oracle\diag\rdbms\xff\xff\trace\xff_pmon_8876.trc: ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [], [], [] PMON (ospid: 8876): terminating the instance due to error 472 Instance terminated by PMON, pid = 8876
这个故障比较简单,由于undo回滚异常导致,对异常的undo进行处理,数据库正常open,重建undo表空间导出数据,完成本次恢复工作
又一例ORA-600 kcratr_nab_less_than_odr
数据库启动报错ORA-600 kcratr_nab_less_than_odr
alter database open Sat Jul 23 21:38:32 2022 Beginning crash recovery of 1 threads parallel recovery started with 19 processes Sat Jul 23 21:38:33 2022 Started redo scan Sat Jul 23 21:38:33 2022 Completed redo scan read 244 KB redo, 64 data blocks need recovery Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl12c\orcl12c\trace\orcl12c_ora_5748.trc (incident=309845): ORA-00600: ??????, ??: [kcratr_nab_less_than_odr], [1], [10343], [67442], [67454], [], [], [], [], [], [], [] Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Sat Jul 23 21:38:34 2022 Slave encountered ORA-10388 exception during crash recovery Sat Jul 23 21:38:34 2022 Slave encountered ORA-10388 exception during crash recovery Sat Jul 23 21:38:34 2022 Slave encountered ORA-10388 exception during crash recovery Sat Jul 23 21:38:34 2022 Slave encountered ORA-10388 exception during crash recovery Sat Jul 23 21:38:34 2022 Slave encountered ORA-10388 exception during crash recovery Sat Jul 23 21:38:34 2022 Slave encountered ORA-10388 exception during crash recovery Sat Jul 23 21:38:34 2022 Slave encountered ORA-10388 exception during crash recovery Sat Jul 23 21:38:34 2022 Slave encountered ORA-10388 exception during crash recovery Sat Jul 23 21:38:34 2022 Slave encountered ORA-10388 exception during crash recovery Sat Jul 23 21:38:34 2022 Slave encountered ORA-10388 exception during crash recovery Sat Jul 23 21:38:34 2022 Slave encountered ORA-10388 exception during crash recovery Sat Jul 23 21:38:34 2022 Slave encountered ORA-10388 exception during crash recovery Sat Jul 23 21:38:34 2022 Slave encountered ORA-10388 exception during crash recovery Sat Jul 23 21:38:34 2022 Slave encountered ORA-10388 exception during crash recovery Sat Jul 23 21:38:34 2022 Slave encountered ORA-10388 exception during crash recovery Sat Jul 23 21:38:34 2022 Slave encountered ORA-10388 exception during crash recovery Sat Jul 23 21:38:34 2022 Slave encountered ORA-10388 exception during crash recovery Sat Jul 23 21:38:34 2022 Slave encountered ORA-10388 exception during crash recovery Sat Jul 23 21:38:34 2022 Slave encountered ORA-10388 exception during crash recovery Sat Jul 23 21:38:38 2022 Aborting crash recovery due to error 600 Sat Jul 23 21:38:38 2022 Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl12c\orcl12c\trace\orcl12c_ora_5748.trc: ORA-00600: ??????, ??: [kcratr_nab_less_than_odr], [1], [10343], [67442], [67454], [], [], [], [], [], [], [] Sat Jul 23 21:38:39 2022 Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl12c\orcl12c\trace\orcl12c_ora_5748.trc: ORA-00600: ??????, ??: [kcratr_nab_less_than_odr], [1], [10343], [67442], [67454], [], [], [], [], [], [], [] ORA-600 signalled during: alter database open...
这个错误比较简单,参考:
12c启动报kcratr_nab_less_than_odr
ORA-600 kcratr_nab_less_than_odr故障解决
解决该问题之后,数据库启动报ORA-600 4194错误
Mon Jul 25 12:18:04 2022 SMON: enabling tx recovery Starting background process SMCO Mon Jul 25 12:18:05 2022 SMCO started with pid=26, OS id=8164 Mon Jul 25 12:18:06 2022 Database Characterset is ZHS16GBK ORA-00600: ??????, ??: [4194], [46], [44], [], [], [], [], [], [], [], [], [] Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Mon Jul 25 12:18:14 2022 Doing block recovery for file 5 block 1267 Mon Jul 25 12:18:14 2022 Resuming block recovery (PMON) for file 5 block 1267 Block recovery from logseq 1, block 67 to scn 217083444 Mon Jul 25 12:18:15 2022 Recovery of Online Redo Log: Thread 1 Group 1 Seq 1 Reading mem 0 Mem# 0: D:\APP\ADMINISTRATOR\ORADATA\ORCL12C\REDO01.LOG Block recovery stopped at EOT rba 1.68.16 Block recovery completed at rba 1.68.16, scn 0.217083444 Doing block recovery for file 5 block 272 Resuming block recovery (PMON) for file 5 block 272 Block recovery from logseq 1, block 67 to scn 217083443 Mon Jul 25 12:18:18 2022 Recovery of Online Redo Log: Thread 1 Group 1 Seq 1 Reading mem 0 Mem# 0: D:\APP\ADMINISTRATOR\ORADATA\ORCL12C\REDO01.LOG Block recovery completed at rba 1.68.16, scn 0.217083444 Mon Jul 25 12:18:19 2022 Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl12c\orcl12c\trace\orcl12c_smon_7100.trc: ORA-01595: 释放区 (5) 回退段 (10) 时出错 ORA-00600: ??????, ??: [4194], [46], [44], [], [], [], [], [], [], [], [], [] Mon Jul 25 12:18:19 2022 No Resource Manager plan active Mon Jul 25 12:18:23 2022 Sweep [inc][317000]: completed Sweep [inc2][317000]: completed Starting background process FBDA Mon Jul 25 12:18:40 2022 FBDA started with pid=28, OS id=7828 Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl12c\orcl12c\trace\orcl12c_ora_5804.trc (incident=317056): ORA-00600: 内部错误代码, 参数: [4194], [46], [44], [], [], [], [], [], [], [], [], [] Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Mon Jul 25 12:18:53 2022 Doing block recovery for file 5 block 1267 Resuming block recovery (PMON) for file 5 block 1267 Block recovery from logseq 1, block 67 to scn 217083444 Mon Jul 25 12:18:53 2022 Recovery of Online Redo Log: Thread 1 Group 1 Seq 1 Reading mem 0 Mem# 0: D:\APP\ADMINISTRATOR\ORADATA\ORCL12C\REDO01.LOG Block recovery completed at rba 1.68.16, scn 0.217083454 Doing block recovery for file 5 block 272 Resuming block recovery (PMON) for file 5 block 272 Block recovery from logseq 1, block 67 to scn 217083454 Mon Jul 25 12:18:54 2022 Recovery of Online Redo Log: Thread 1 Group 1 Seq 1 Reading mem 0 Mem# 0: D:\APP\ADMINISTRATOR\ORADATA\ORCL12C\REDO01.LOG Block recovery completed at rba 1.69.16, scn 0.217083455 Mon Jul 25 12:18:55 2022 Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl12c\orcl12c\trace\orcl12c_ora_5804.trc: ORA-00600: 内部错误代码, 参数: [4194], [46], [44], [], [], [], [], [], [], [], [], [] Mon Jul 25 12:18:55 2022 Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl12c\orcl12c\trace\orcl12c_ora_5804.trc: ORA-00600: 内部错误代码, 参数: [4194], [46], [44], [], [], [], [], [], [], [], [], [] Error 600 happened during db open, shutting down database USER (ospid: 5804): terminating the instance due to error 600 Mon Jul 25 12:19:07 2022 Instance terminated by USER, pid = 5804 ORA-1092 signalled during: alter database open resetlogs...
该错误也比较简单,对异常undo段进行处理即可,参考类似操作:How to resolve ORA-600 [4194] errors
ORA-00333 ORA-01595 恢复
客户反馈数据库异常,查看日志发现asm和db均发生hang住情况(由于环境原因部分日志没有拷贝出来),基于现有情况,无法直接恢复,通过一些工具把asm磁盘组中的数据文件拷贝到文件系统,经过检测无坏块
修改相关路径,尝试recover库
Tue Jul 05 15:05:54 2022 ALTER DATABASE RECOVER datafile 1 Media Recovery Start Serial Media Recovery started Recovery of Online Redo Log: Thread 2 Group 4 Seq 29973 Reading mem 0 Mem# 0: E:\ORADATA\GROUP_4.266.822672441 Recovery of Online Redo Log: Thread 1 Group 2 Seq 38422 Reading mem 0 Mem# 0: E:\ORADATA\GROUP_2.262.822672137 Incomplete read from log member 'E:\ORADATA\GROUP_2.262.822672137'. Trying next member. Media Recovery failed with error 333 ORA-283 signalled during: ALTER DATABASE RECOVER datafile 1 ...
错误信息比较明显,在读入redo进行恢复的时候遭遇“ORA-00333: 重做日志读取块 11557 计数 731 出错”错误,从而无法继续恢复.这次故障运气比较好,通过分析v$datafile和v$datafile_header关系
进行一些操作,绕过redo block 11557,顺利recover成功,并且open库
ALTER DATABASE RECOVER database Media Recovery Start started logmerger process Tue Jul 05 15:17:46 2022 Parallel Media Recovery started with 32 slaves Tue Jul 05 15:17:46 2022 Recovery of Online Redo Log: Thread 2 Group 4 Seq 29973 Reading mem 0 Mem# 0: E:\ORADATA\GROUP_4.266.822672441 Recovery of Online Redo Log: Thread 1 Group 2 Seq 38422 Reading mem 0 Mem# 0: E:\ORADATA\GROUP_2.262.822672137 Completed: ALTER DATABASE RECOVER database
通过分析alert日志发现有ORA-600 4194错误
QMNC started with pid=58, OS id=15980 LOGSTDBY: Validating controlfile with logical metadata LOGSTDBY: Validation complete Tue Jul 05 15:18:24 2022 Tue Jul 05 15:18:24 2022 Block recovery from logseq 38423, block 152 to scn 16218380250500 Recovery of Online Redo Log: Thread 1 Group 1 Seq 38423 Reading mem 0 Mem# 0: E:\ORADATA\GROUP_1.261.822672135 Block recovery stopped at EOT rba 38423.154.16 Block recovery completed at rba 38423.154.16, scn 3776.583740804 Block recovery from logseq 38423, block 152 to scn 16218380250497 Recovery of Online Redo Log: Thread 1 Group 1 Seq 38423 Reading mem 0 Mem# 0: E:\ORADATA\GROUP_1.261.822672135 Block recovery completed at rba 38423.154.16, scn 3776.583740804 Errors in file F:\APP\ADMINISTRATOR\diag\rdbms\xff\xff1\trace\xff1_smon_5660.trc: ORA-01595: 释放区 (2) 回退段 (8) 时出错 ORA-00600: 内部错误代码, 参数: [4194], [], [ Completed: alter database open
这比较简单,对于异常的undo进行处理即可,然后使用hcheck检查字典一致性
SQL> @e:/oradata/txt/11.txt HCheck Version 07MAY18 on 05-7月 -2022 16:30:18 ---------------------------------------------- Catalog Version 11.2.0.3.0 (1102000300) db_name: xff Catalog Fixed Procedure Name Version Vs Release Timestamp Result ------------------------------ ... ---------- -- ---------- -------------- ------ .- LobNotInObj ... 1102000300 <= *All Rel* 07/05 16:30:18 PASS .- MissingOIDOnObjCol ... 1102000300 <= *All Rel* 07/05 16:30:19 PASS .- SourceNotInObj ... 1102000300 <= *All Rel* 07/05 16:30:19 PASS .- OversizedFiles ... 1102000300 <= *All Rel* 07/05 16:30:19 PASS .- PoorDefaultStorage ... 1102000300 <= *All Rel* 07/05 16:30:19 PASS .- PoorStorage ... 1102000300 <= *All Rel* 07/05 16:30:19 PASS .- TabPartCountMismatch ... 1102000300 <= *All Rel* 07/05 16:30:20 PASS .- OrphanedTabComPart ... 1102000300 <= *All Rel* 07/05 16:30:20 PASS .- MissingSum$ ... 1102000300 <= *All Rel* 07/05 16:30:20 PASS .- MissingDir$ ... 1102000300 <= *All Rel* 07/05 16:30:20 PASS .- DuplicateDataobj ... 1102000300 <= *All Rel* 07/05 16:30:20 PASS .- ObjSynMissing ... 1102000300 <= *All Rel* 07/05 16:30:20 PASS .- ObjSeqMissing ... 1102000300 <= *All Rel* 07/05 16:30:21 PASS .- OrphanedUndo ... 1102000300 <= *All Rel* 07/05 16:30:21 PASS .- OrphanedIndex ... 1102000300 <= *All Rel* 07/05 16:30:21 PASS .- OrphanedIndexPartition ... 1102000300 <= *All Rel* 07/05 16:30:21 PASS .- OrphanedIndexSubPartition ... 1102000300 <= *All Rel* 07/05 16:30:21 PASS .- OrphanedTable ... 1102000300 <= *All Rel* 07/05 16:30:21 PASS .- OrphanedTablePartition ... 1102000300 <= *All Rel* 07/05 16:30:21 PASS .- OrphanedTableSubPartition ... 1102000300 <= *All Rel* 07/05 16:30:21 PASS .- MissingPartCol ... 1102000300 <= *All Rel* 07/05 16:30:21 PASS .- OrphanedSeg$ ... 1102000300 <= *All Rel* 07/05 16:30:21 PASS .- OrphanedIndPartObj# ... 1102000300 <= *All Rel* 07/05 16:30:21 PASS .- DuplicateBlockUse ... 1102000300 <= *All Rel* 07/05 16:30:21 PASS .- FetUet ... 1102000300 <= *All Rel* 07/05 16:30:21 PASS .- Uet0Check ... 1102000300 <= *All Rel* 07/05 16:30:21 PASS .- SeglessUET ... 1102000300 <= *All Rel* 07/05 16:30:21 PASS .- BadInd$ ... 1102000300 <= *All Rel* 07/05 16:30:21 PASS .- BadTab$ ... 1102000300 <= *All Rel* 07/05 16:30:22 PASS .- BadIcolDepCnt ... 1102000300 <= *All Rel* 07/05 16:30:22 PASS .- ObjIndDobj ... 1102000300 <= *All Rel* 07/05 16:30:22 PASS .- TrgAfterUpgrade ... 1102000300 <= *All Rel* 07/05 16:30:22 PASS .- ObjType0 ... 1102000300 <= *All Rel* 07/05 16:30:22 PASS .- BadOwner ... 1102000300 <= *All Rel* 07/05 16:30:22 PASS .- StmtAuditOnCommit ... 1102000300 <= *All Rel* 07/05 16:30:22 PASS .- BadPublicObjects ... 1102000300 <= *All Rel* 07/05 16:30:22 PASS .- BadSegFreelist ... 1102000300 <= *All Rel* 07/05 16:30:22 PASS .- BadDepends ... 1102000300 <= *All Rel* 07/05 16:30:22 PASS .- CheckDual ... 1102000300 <= *All Rel* 07/05 16:30:23 PASS .- ObjectNames ... 1102000300 <= *All Rel* 07/05 16:30:23 WARN HCKW-0018: OBJECT name clashes with SCHEMA name (Doc ID 2363142.1) Schema=BSHRP INDEX=XFF.XFF .- BadCboHiLo ... 1102000300 <= *All Rel* 07/05 16:30:23 PASS .- ChkIotTs ... 1102000300 <= *All Rel* 07/05 16:30:24 PASS .- NoSegmentIndex ... 1102000300 <= *All Rel* 07/05 16:30:24 PASS .- BadNextObject ... 1102000300 <= *All Rel* 07/05 16:30:24 PASS .- DroppedROTS ... 1102000300 <= *All Rel* 07/05 16:30:24 PASS .- FilBlkZero ... 1102000300 <= *All Rel* 07/05 16:30:24 PASS .- DbmsSchemaCopy ... 1102000300 <= *All Rel* 07/05 16:30:24 PASS .- OrphanedObjError ... 1102000300 > 1102000000 07/05 16:30:24 PASS .- ObjNotLob ... 1102000300 <= *All Rel* 07/05 16:30:24 PASS .- MaxControlfSeq ... 1102000300 <= *All Rel* 07/05 16:30:24 PASS .- SegNotInDeferredStg ... 1102000300 > 1102000000 07/05 16:30:25 PASS .- SystemNotRfile1 ... 1102000300 > 902000000 07/05 16:30:25 PASS .- DictOwnNonDefaultSYSTEM ... 1102000300 <= *All Rel* 07/05 16:30:25 PASS .- OrphanTrigger ... 1102000300 <= *All Rel* 07/05 16:30:25 PASS .- ObjNotTrigger ... 1102000300 <= *All Rel* 07/05 16:30:25 PASS --------------------------------------- 05-7月 -2022 16:30:25 Elapsed: 7 secs --------------------------------------- Found 0 potential problem(s) and 1 warning(s) Contact Oracle Support with the output and trace file to check if the above needs attention or not PL/SQL 过程已成功完成。
有一个SCHEMA和对象名一样,这个不影响属于正常情况(客户创建了一个用户叫做XFF,然后有创建了一个XFF的对象),该数据库恢复至此基本上晚上,业务可以直接运行,不用做逻辑迁移