AMDU数据恢复的方法是什么-创新互联
这篇文章主要介绍“AMDU数据恢复的方法是什么”，在日常操作中，相信很多人在AMDU数据恢复的方法是什么问题上存在疑惑，小编查阅了各式资料，整理出简单好用的操作方法，希望对大家解答”AMDU数据恢复的方法是什么”的疑惑有所帮助！接下来，请跟着小编一起来学习吧！
A.M.D.U数据恢复
客户环境：
操作系统：RedHat Enterprise AS Linux 4.6 x64
数据库DB：Oracle Enterprise Database 10g(10.2.0.4) no psu
集群系统：Oracle Real Application Cluster 10g(10.2.0.4) no psu
问题背景：
在一个寂静的夜晚被一阵急促的电话铃声吵醒，打来电话的是我的老朋友J，他告知我说数据库起不来了，业务全部中断，存储狂扇，频繁的告警亮灯，寻求我的紧急帮助。我首先安慰老朋友J，说这个可能是存储有问题，比较棘手，还是有修复的可能。J听到我这么一说长舒了一口气，缓缓的吐了几个字说：“吴哥，你得帮帮我！”我说没问题，随即梦醒打了个飞的直奔故障现场。了解到了客户环境：比想象中的更为复杂，上线后就没有任何备份，是一个部署在RHEL4.6环境下的10g(10.2.0.4)的RAC，用的是8盘位DFT低端SAS存储。
问题分析：
在了解到问题环境之后需要对问题进行进一步的分析和解决，思考了半个小时，CRS服务无法启动，没有数据库备份无法恢复；10gRAC ASM无法mount，内部视图无法查询，磁盘组无法正常加载，给数据恢复带来诸多不便......，看来常规方法是不行了，只能考虑一些非常规的数据恢复方法：DUL? AUL? ODU? 这几个工具一直在大脑中回荡，后来冷静思考，咨询了行业里面的牛人，告诉我说通过11g下的AMDU可以在磁盘组加载之前将ASM元数据抽出来，用于诊断及起库open，之后再重做RAC恢复数据即可。且该工具可以向后兼容，引入到10g中。
说完就干～！
处理过程：
1.1.基础环境准备
在Oracle官网下载最新的AMDU工具，在任意节点挂载外置移动硬盘，上传到挂载外置移动硬盘的节点上，进去后赋予oracle:oinstall权限并用oracle用户解压，配置参数文件amdu_par，包含如下内容：
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:`pwd`
export PATH=$PATH:`pwd`
1.2. 初始化amdu工具
用oracle用户执行如下命令，将自动生成一个以时间命名的目录，其下的报告
文件记录了磁盘组的相关信息。
./amdu amdu_2019_03_30_12_26_32
该报告的主要信息如下：
-*-amdu-*- ******************************* AMDU Settings ******************************** ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1 System name:Linux Node name: rac1 Release: 2.6.9-78.ELlargesmp Version: #1 SMP Wed Jul 9 16:03:59 EDT 2008 Machine:x86_64 amdu run: 30-MAR-19 12:26:32 Endianess: 1 --------------------------------- Operations --------------------------------- ------------------------------- Disk Selection ------------------------------- -diskstring '' ------------------------------ Reading Control ------------------------------- ------------------------------- Output Control ------------------------------- ********************************* DISCOVERY ********************************** ----------------------------- DISK REPORT N0001 ------------------------------ Disk Path: /dev/raw/raw1 Unique Disk ID: Disk Label: Physical Sector Size: 512 bytes Disk Size: 199 megabytes ** NOT A VALID ASM DISK HEADER. BAD VALUE IN FIELD blksize_kfdhdb ** ----------------------------- DISK REPORT N0002 ------------------------------ Disk Path: /dev/raw/raw2 Unique Disk ID: Disk Label: Physical Sector Size: 512 bytes Disk Size: 299 megabytes ** NOT A VALID ASM DISK HEADER. BAD VALUE IN FIELD blksize_kfdhdb ** ----------------------------- DISK REPORT N0003 ------------------------------ Disk Path: ORCL:VOL1 Unique Disk ID: Disk Label: VOL1 Physical Sector Size: 512 bytes Disk Size: 2047997 megabytes Group Name: ORADATA_DG1 Disk Name: VOL1 Failure Group Name: VOL1 Disk Number: 0 Header Status: 3 Disk Creation Time: 2011/01/04 15:51:21.126000 Last Mount Time: 2019/03/30 13:15:19.625000 Compatibility Version: 0x0a100000 Disk Sector Size: 512 bytes Disk size in AUs: 2047997 AUs Group Redundancy: 1 Metadata Block Size: 4096 bytes ---------元数据块大小，4KB AU Size: 1048576 bytes -------------AU大小：1MB Stride: 113792 AUs Group Creation Time: 2011/01/04 15:51:21.013000 File 1 Block 1 location: AU 2 ---------文件使用，从AU 2 开始 ----------------------------- DISK REPORT N0004 ------------------------------ Disk Path: ORCL:VOL2 Unique Disk ID: Disk Label: VOL2 Physical Sector Size: 512 bytes Disk Size: 2047997 megabytes Group Name: ORADATA_DG2 Disk Name: VOL2 Failure Group Name: VOL2 Disk Number: 0 Header Status: 3 Disk Creation Time: 2011/01/04 15:51:43.512000 Last Mount Time: 2019/03/30 13:15:19.851000 Compatibility Version: 0x0a100000 Disk Sector Size: 512 bytes Disk size in AUs: 2047997 AUs Group Redundancy: 1 Metadata Block Size: 4096 bytes ----------元数据块大小，4KB AU Size: 1048576 bytes --------------AU大小：1MB Stride: 113792 AUs Group Creation Time: 2011/01/04 15:51:43.370000 File 1 Block 1 location: AU 2 ---------文件使用，从AU 2 开始 ----------------------------- DISK REPORT N0005 ------------------------------ Disk Path: ORCL:VOL3 Unique Disk ID: Disk Label: VOL3 Physical Sector Size: 512 bytes Disk Size: 2047997 megabytes Group Name: ORADATA_DG3 Disk Name: VOL3 Failure Group Name: VOL3 Disk Number: 0 Header Status: 3 Disk Creation Time: 2011/01/04 15:52:05.086000 Last Mount Time: 2019/03/30 13:15:20.093000 Compatibility Version: 0x0a100000 Disk Sector Size: 512 bytes Disk size in AUs: 2047997 AUs Group Redundancy: 1 Metadata Block Size: 4096 bytes ---------元数据块大小，4KB AU Size: 1048576 bytes --------------AU大小：1MB Stride: 113792 AUs Group Creation Time: 2011/01/04 15:52:04.949000 File 1 Block 1 location: AU 2 ---------文件使用，从AU 2 开始 ----------------------------- DISK REPORT N0006 ------------------------------ Disk Path: ORCL:VOL4 Unique Disk ID: Disk Label: VOL4 Physical Sector Size: 512 bytes Disk Size: 1484867 megabytes Group Name: RECOVER_DG Disk Name: VOL4 Failure Group Name: VOL4 Disk Number: 0 Header Status: 3 Disk Creation Time: 2011/01/04 15:52:31.026000 Last Mount Time: 2019/03/30 13:15:20.336000 Compatibility Version: 0x0a100000 Disk Sector Size: 512 bytes Disk size in AUs: 1484867 AUs Group Redundancy: 1 Metadata Block Size: 4096 bytes AU Size: 1048576 bytes ----元数据块大小，4KB Stride: 113792 AUs --------AU 大小：1MB Group Creation Time: 2011/01/04 15:52:30.929000 File 1 Block 1 location: AU 2 ---------文件使用，从AU 2 开始 ******************************* END OF REPORT ********************************
1.3.抽取控制文件
由于磁盘组不能Mount，控制文件也无法访问，因此需要首先分析数据库的文件分布情况，进而通过文件的ASM 存储序号来进行文件抽取，通过告警日志，可以找到数据库的控制文件信息。如下所示，控制文件的ASM 文件号是270。
grep control_file $ORACLE_BASE/admin/$ORACLE_SID/bdump/alert_$ORACLE_SID.log control_files = "+ORADATA_DG1/ORADB/CONTROLFILE/Current.260.739555035" .......... [oracle@rac1 amdu_2019_03_30_12_26_32]$ amdu -diskstring '/dev/oracleasm/disks/VOL*' -extract ORADATA_DG1.260 amdu_2019_03_30_12_29_43/
1.4. 通过控制文件获取RedoLog 和DataFile
取得控制文件之后，可以通过控制文件内容获得数据库的数据文件及日志文件分布情况。以下是从控制文件中获得的信息输出。
[root@rac1 ~]# strings ORADATA_DG1_260.f |grep -v archivelog |grep -v oracle/ |grep ORAD| sort +ORADATA_DG1/oradb/idx_jsnet.dbf +ORADATA_DG1/oradb/idx_jsnet.dbf +ORADATA_DG1/oradb/idx_jsnet.ora +ORADATA_DG1/oradb/idx_jsnet.ora +ORADATA_DG1/oradb/redo01.log +ORADATA_DG1/oradb/redo01.log +ORADATA_DG1/oradb/redo02.log +ORADATA_DG1/oradb/redo02.log +ORADATA_DG1/oradb/redo03.log +ORADATA_DG1/oradb/redo03.log +ORADATA_DG1/oradb/redo04.log +ORADATA_DG1/oradb/redo04.log +ORADATA_DG1/oradb/sysaux01.dbf +ORADATA_DG1/oradb/sysaux01.dbf +ORADATA_DG1/oradb/system01.dbf +ORADATA_DG1/oradb/system01.dbf +ORADATA_DG1/oradb/tbs_jsnet.dbf +ORADATA_DG1/oradb/tbs_jsnet.dbf +ORADATA_DG1/oradb/tbs_jsnet.dbf +ORADATA_DG1/oradb/tbs_jsnet.dbf +ORADATA_DG1/oradb/temp01.dbf +ORADATA_DG1/oradb/temp01.dbf +ORADATA_DG1/oradb/undotbs01.dbf +ORADATA_DG1/oradb/undotbs01.dbf +ORADATA_DG1/oradb/undotbs02.dbf +ORADATA_DG1/oradb/undotbs02.dbf +ORADATA_DG1/oradb/users01.dbf +ORADATA_DG1/oradb/users01.dbf
1.5. 恢复文件
根据控制文件中的文件分布信息，可以通过amdu工具将所有文件提取出来，根据以数据文件和日志文件信息，创建如下脚本以抽取对应的日志文件和数据文件。
先恢复RedoLog File:
[oracle@rac1 amdu_2019_03_30_12_26_32]$ amdu -diskstring '/dev/oracleasm/disks/VOL*' -extract ORADATA_DG1.263 amdu_2019_03_30_12_32_38/ [oracle@rac1 amdu_2019_03_30_12_26_32]$ amdu -diskstring '/dev/oracleasm/disks/VOL*' -extract ORADATA_DG1.264 amdu_2019_03_30_12_33_12/ [oracle@rac1 amdu_2019_03_30_12_26_32]$ amdu -diskstring '/dev/oracleasm/disks/VOL*' -extract ORADATA_DG1.267 amdu_2019_03_30_12_34_11/ [oracle@rac1 amdu_2019_03_30_12_26_32]$ amdu -diskstring '/dev/oracleasm/disks/VOL*' -extract ORADATA_DG1.268 amdu_2019_03_30_12_34_22/
再恢复数据文件：
IDX_JSNET.ora: [oracle@rac1 amdu_2019_03_30_12_26_32]$ amdu -diskstring '/dev/oracleasm/disks/VOL*' -extract ORADATA_DG1.276 amdu_2019_03_30_12_38_42/ IDX_JSNET: [oracle@rac1 amdu_2019_03_30_12_26_32]$ amdu -diskstring '/dev/oracleasm/disks/VOL*' -extract ORADATA_DG1.298 TBS_JSNET: [oracle@rac1 amdu_2019_03_30_12_26_32]$ amdu -diskstring '/dev/oracleasm/disks/VOL*' -extract ORADATA_DG1.277 SYSAUX: [oracle@rac1 amdu_2019_03_30_12_26_32]$ amdu -diskstring '/dev/oracleasm/disks/VOL*' -extract ORADATA_DG1.257 SYSTEM: [oracle@rac1 amdu_2019_03_30_12_26_32]$ amdu -diskstring '/dev/oracleasm/disks/VOL*' -extract ORADATA_DG1.256 TEMP: [oracle@rac1 amdu_2019_03_30_12_26_32]$ amdu -diskstring '/dev/oracleasm/disks/VOL*' -extract ORADATA_DG1.265 UNDOTBS1: [oracle@rac1 amdu_2019_03_30_12_26_32]$ amdu -diskstring '/dev/oracleasm/disks/VOL*' -extract ORADATA_DG1.258 UNDOTBS2: [oracle@rac1 amdu_2019_03_30_12_26_32]$ amdu -diskstring '/dev/oracleasm/disks/VOL*' -extract ORADATA_DG1.266 USER: [oracle@rac1 amdu_2019_03_30_12_26_32]$ amdu -diskstring '/dev/oracleasm/disks/VOL*' -extract ORADATA_DG1.259
1.6. 校验文件
到这里文件已经全部恢复出来了，途中未见报错，接下来需要用dbv对文件进行个校验，检查下是否有逻辑坏块：
[oracle@rac1 amdu_2019_03_30_12_26_32]$ dbv file=amdu_2019_03_30_12_ amdu_2019_03_30_12_29_43/ amdu_2019_03_30_12_33_12/ amdu_2019_03_30_12_38_42/ amdu_2019_03_30_12_43_30/ amdu_2019_03_30_12_29_56/ amdu_2019_03_30_12_34_11/ amdu_2019_03_30_12_40_08/ amdu_2019_03_30_12_44_47/ amdu_2019_03_30_12_30_07/ amdu_2019_03_30_12_34_22/ amdu_2019_03_30_12_40_45/ amdu_2019_03_30_12_32_38/ amdu_2019_03_30_12_37_22/ amdu_2019_03_30_12_42_13/ [oracle@rac1 amdu_2019_03_30_12_26_32]$ dbv file=amdu_2019_03_30_12_38_42/ORADATA_DG1_276.f DBVERIFY: Release 10.2.0.4.0 - Production on Sat Mar 30 14:00:33 2019 Copyright (c) 1982, 2007, Oracle. All rights reserved. DBVERIFY - Verification starting : FILE = amdu_2019_03_30_12_38_42/ORADATA_DG1_276.f DBVERIFY - Verification complete Total Pages Examined : 25600 Total Pages Processed (Data) : 0 Total Pages Failing (Data) : 0 Total Pages Processed (Index): 0 Total Pages Failing (Index): 0 Total Pages Processed (Other): 8 Total Pages Processed (Seg) : 0 Total Pages Failing (Seg) : 0 Total Pages Empty : 25592 Total Pages Marked Corrupt : 0 Total Pages Influx : 0 Highest block SCN : 753000 (0.753000) [oracle@rac1 amdu_2019_03_30_12_26_32]$ dbv file=amdu_2019_03_30_12_40_08/ORADATA_DG1_298.f DBVERIFY: Release 10.2.0.4.0 - Production on Sat Mar 30 14:00:53 2019 Copyright (c) 1982, 2007, Oracle. All rights reserved. DBVERIFY - Verification starting : FILE = amdu_2019_03_30_12_40_08/ORADATA_DG1_298.f DBVERIFY - Verification complete Total Pages Examined : 32000 Total Pages Processed (Data) : 0 Total Pages Failing (Data) : 0 Total Pages Processed (Index): 28786 Total Pages Failing (Index): 0 Total Pages Processed (Other): 1062 Total Pages Processed (Seg) : 0 Total Pages Failing (Seg) : 0 Total Pages Empty : 2152 Total Pages Marked Corrupt : 0 Total Pages Influx : 0 Highest block SCN : 697113994 (0.697113994) [oracle@rac1 amdu_2019_03_30_12_26_32]$ dbv file=amdu_2019_03_30_12_40_45/ORADATA_DG1_277.f DBVERIFY: Release 10.2.0.4.0 - Production on Sat Mar 30 14:01:09 2019 Copyright (c) 1982, 2007, Oracle. All rights reserved. DBVERIFY - Verification starting : FILE = amdu_2019_03_30_12_40_45/ORADATA_DG1_277.f DBVERIFY - Verification complete Total Pages Examined : 101120 Total Pages Processed (Data) : 95455 Total Pages Failing (Data) : 0 Total Pages Processed (Index): 353 Total Pages Failing (Index): 0 Total Pages Processed (Other): 3290 Total Pages Processed (Seg) : 0 Total Pages Failing (Seg) : 0 Total Pages Empty : 2022 Total Pages Marked Corrupt : 0 Total Pages Influx : 0 Highest block SCN : 697223552 (0.697223552) [oracle@rac1 amdu_2019_03_30_12_26_32]$ dbv file=amdu_2019_03_30_12_42_13/ORADATA_DG1_257.f DBVERIFY: Release 10.2.0.4.0 - Production on Sat Mar 30 14:01:17 2019 Copyright (c) 1982, 2007, Oracle. All rights reserved. DBVERIFY - Verification starting : FILE = amdu_2019_03_30_12_42_13/ORADATA_DG1_257.f DBVERIFY - Verification complete Total Pages Examined : 107520 Total Pages Processed (Data) : 41691 Total Pages Failing (Data) : 0 Total Pages Processed (Index): 33473 Total Pages Failing (Index): 0 Total Pages Processed (Other): 18814 Total Pages Processed (Seg) : 0 Total Pages Failing (Seg) : 0 Total Pages Empty : 13542 Total Pages Marked Corrupt : 0 Total Pages Influx : 0 Highest block SCN : 697247738 (0.697247738) [oracle@rac1 amdu_2019_03_30_12_26_32]$ dbv file=amdu_2019_03_30_12_43_30/ORADATA_DG1_256.f DBVERIFY: Release 10.2.0.4.0 - Production on Sat Mar 30 14:01:59 2019 Copyright (c) 1982, 2007, Oracle. All rights reserved. DBVERIFY - Verification starting : FILE = amdu_2019_03_30_12_43_30/ORADATA_DG1_256.f DBVERIFY - Verification complete Total Pages Examined : 64000 Total Pages Processed (Data) : 38706 Total Pages Failing (Data) : 0 Total Pages Processed (Index): 7385 Total Pages Failing (Index): 0 Total Pages Processed (Other): 2067 Total Pages Processed (Seg) : 0 Total Pages Failing (Seg) : 0 Total Pages Empty : 15842 Total Pages Marked Corrupt : 0 Total Pages Influx : 0 Highest block SCN : 697247727 (0.697247727) [oracle@rac1 amdu_2019_03_30_12_26_32]$ dbv file=amdu_2019_03_30_12_44_47/ORADATA_DG1_265.f DBVERIFY: Release 10.2.0.4.0 - Production on Sat Mar 30 14:02:25 2019 Copyright (c) 1982, 2007, Oracle. All rights reserved. DBVERIFY: Skipping temporary file amdu_2019_03_30_12_44_47/ORADATA_DG1_265.f [oracle@rac1 amdu_2019_03_30_12_26_32]$ dbv file=amdu_2019_03_30_13_10_37/ORADATA_DG1_258.f DBVERIFY: Release 10.2.0.4.0 - Production on Sat Mar 30 14:03:18 2019 Copyright (c) 1982, 2007, Oracle. All rights reserved. DBVERIFY - Verification starting : FILE = amdu_2019_03_30_13_10_37/ORADATA_DG1_258.f DBVERIFY - Verification complete Total Pages Examined : 23680 Total Pages Processed (Data) : 0 Total Pages Failing (Data) : 0 Total Pages Processed (Index): 0 Total Pages Failing (Index): 0 Total Pages Processed (Other): 23432 Total Pages Processed (Seg) : 0 Total Pages Failing (Seg) : 0 Total Pages Empty : 248 Total Pages Marked Corrupt : 0 Total Pages Influx : 0 Highest block SCN : 667630094 (0.667630094) [oracle@rac1 amdu_2019_03_30_12_26_32]$ dbv file=amdu_2019_03_30_13_14_27/ORADATA_DG1_266.f DBVERIFY: Release 10.2.0.4.0 - Production on Sat Mar 30 14:03:43 2019 Copyright (c) 1982, 2007, Oracle. All rights reserved. DBVERIFY - Verification starting : FILE = amdu_2019_03_30_13_14_27/ORADATA_DG1_266.f DBVERIFY - Verification complete Total Pages Examined : 27080 Total Pages Processed (Data) : 0 Total Pages Failing (Data) : 0 Total Pages Processed (Index): 0 Total Pages Failing (Index): 0 Total Pages Processed (Other): 27080 Total Pages Processed (Seg) : 0 Total Pages Failing (Seg) : 0 Total Pages Empty : 0 Total Pages Marked Corrupt : 0 Total Pages Influx : 0 Highest block SCN : 697247738 (0.697247738) [oracle@rac1 amdu_2019_03_30_12_26_32]$ dbv file=amdu_2019_03_30_13_15_29/ORADATA_DG1_259.f DBVERIFY: Release 10.2.0.4.0 - Production on Sat Mar 30 14:04:03 2019 Copyright (c) 1982, 2007, Oracle. All rights reserved. DBVERIFY - Verification starting : FILE = amdu_2019_03_30_13_15_29/ORADATA_DG1_259.f DBVERIFY - Verification complete Total Pages Examined : 640 Total Pages Processed (Data) : 15 Total Pages Failing (Data) : 0 Total Pages Processed (Index): 2 Total Pages Failing (Index): 0 Total Pages Processed (Other): 593 Total Pages Processed (Seg) : 0 Total Pages Failing (Seg) : 0 Total Pages Empty : 30 Total Pages Marked Corrupt : 0 Total Pages Influx : 0 Highest block SCN : 598900 (0.598900)
1.7. 验证数据库版本及补丁信息
[oracle@rac1 amdu_2019_03_30_12_26_32]$ $ORACLE_HOME/OPatch/opatch lsinv Invoking OPatch 10.2.0.4.2 Oracle Interim Patch Installer version 10.2.0.4.2 Copyright (c) 2007, Oracle Corporation. All rights reserved. Oracle Home : /u01/app/oracle/product/10.2.0/db_1 Central Inventory : /u01/app/oraInventory from : /etc/oraInst.loc OPatch version : 10.2.0.4.2 OUI version : 10.2.0.4.0 OUI location : /u01/app/oracle/product/10.2.0/db_1/oui Log file location : /u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatc h3019-03-30_13-56-47PM.log Lsinventory Output file location : /u01/app/oracle/product/10.2.0/db_1/cfgtoollo gs/opatch/lsinv/lsinventory2019-03-30_13-56-47PM.txt -------------------------------------------------------------------------------- Installed Top-level Products (3): Oracle Database 10g 10.2.0.1.0 Oracle Database 10g Products 10.2.0.1.0 Oracle Database 10g Release 2 Patch Set 3 10.2.0.4.0 There are 3 products installed in this Oracle Home. There are no Interim patches installed in this Oracle Home. Rac system comprising of multiple nodes Local node = rac1 Remote node = rac2 -------------------------------------------------------------------------------- OPatch succeeded.
2、构建新的环境
2.1. 安装相同版本数据库
不要建库，只需安装数据库软件即可。
过程(略)
2.2. 创建数据库启动参数文件
编辑好参数文件，将数据库启动到nomount状态:
[oracle@rac1 dbs]$ cat initoradb.ora db_name=oradb db_files = 80 db_file_multiblock_read_count = 8 db_block_buffers = 100 shared_pool_size = 123232153 log_checkpoint_interval = 10000 processes = 50 parallel_max_servers = 5 log_buffer = 32768 max_dump_file_size = 10240 global_names = TRUE control_files = '/oracle/oradata/oradb/control01.ctl'
2.3. 将数据库启到nomount状态
[oracle@rac1 dbs]$ sqlplus / as sysdba SQL*Plus: Release 10.2.0.4.0 - Production on Sat Apr 6 12:47:26 2019 Copyright (c) 1982, 2007, Oracle. All Rights Reserved. Connected to an idle instance. SQL> startup nomount; ORACLE instance started. Total System Global Area 4294967296 bytes Fixed Size 2089472 bytes Variable Size 4269805056 bytes Database Buffers 8388608 bytes Redo Buffers 14684160 bytes
2.4. mount数据库
SQL> alter database mount; Database altered. SQL> select instance_name,status from gv$instance; INSTANCE_NAME STATUS ---------------- ------------ oradb MOUNTED
接下来就可以修改控制文件里面对应的数据文件及RedoLog的路径，并open数据库了。
2.5 修改路径
修改控制文件中的数据文件和RedoLog对应路径信息。
RedoLog File RENAME FILE:
alter database rename file '+ORADATA_DG1/oradb/redo02.log' to '/oracle/oradata/oradb/amdu_2019_03_30_12_33_12/ORADATA_DG1_264.f'; alter database rename file '+ORADATA_DG1/oradb/redo01.log' to '/oracle/oradata/oradb/amdu_2019_03_30_12_32_38/ORADATA_DG1_263.f'; alter database rename file '+ORADATA_DG1/oradb/redo03.log' to '/oracle/oradata/oradb/amdu_2019_03_30_12_34_11/ORADATA_DG1_267.f'; alter database rename file '+ORADATA_DG1/oradb/redo04.log' to '/oracle/oradata/oradb/amdu_2019_03_30_12_34_22/ORADATA_DG1_268.f'; ter database rename file '+ORADATA_DG1/oradb/users01.dbf' to '/oracle/oradata/oradb/amdu_2019_03_30_13_15_29/ORADATA_DG1_259.f'; alter database rename file '+ORADATA_DG1/oradb/sysaux01.dbf' to '/oracle/oradata/oradb/amdu_2019_03_30_12_42_13/ORADATA_DG1_257.f'; alter database rename file '+ORADATA_DG1/oradb/undotbs01.dbf' to '/oracle/oradata/oradb/amdu_2019_03_30_13_10_37/ORADATA_DG1_258.f'; alter database rename file '+ORADATA_DG1/oradb/system01.dbf' to '/oracle/oradata/oradb/amdu_2019_03_30_12_43_30/ORADATA_DG1_256.f'; alter database rename file '+ORADATA_DG1/oradb/undotbs02.dbf' to '/oracle/oradata/oradb/amdu_2019_03_30_13_14_27/ORADATA_DG1_266.f'; alter database rename file '+ORADATA_DG1/oradb/tbs_jsnet.dbf' to '/oracle/oradata/oradb/amdu_2019_03_30_12_40_45/ORADATA_DG1_277.f'; alter database rename file '+ORADATA_DG1/oradb/idx_jsnet.dbf' to '/oracle/oradata/oradb/amdu_2019_03_30_12_40_08/ORADATA_DG1_298.f';
Temp File RENAME FILE:
alter database rename file '+ORADATA_DG1/oradb/temp01.dbf' to '/oracle/oradata/oradb/amdu_2019_03_30_12_44_47/ORADATA_DG1_265.f';
3.启动数据库
[oracle@redhat5 ~]$ sqlplus / as sysdba SQL*Plus: Release 10.2.0.4.0 - Production on Sun Mar 31 03:50:55 2019 Copyright (c) 1982, 2007, Oracle. All Rights Reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> alter database open; alter database open * ERROR at line 1: ORA-00369: Current log of thread 1 not useable and other log being cleared ORA-00312: online log 1 thread 1: '/oracle/oradata/oradb/amdu_2019_03_30_12_32_38/ORADATA_DG1_263.f' SQL> alter database clear unarchived logfile group 1; Database altered. SQL> alter database open; Database altered. SQL> select instance_name,status from v$instance; INSTANCE_NAMESTATUS ---------------- ------------ oradb OPEN
4. 数据库业务方面确认
SQL> select username,default_tablespace from dba_users where account_status='OPEN'; USERNAME DEFAULT_TABLESPACE ------------------------------ ------------------------------ SYSTEM SYSTEM SYS SYSTEM SYSMAN SYSAUX DBSNMP SYSAUX MGMT_VIEW SYSTEM woo TBS_JSNET 6 rows selected. col OWNER format a8 col OBJECT_NAME format a25 select owner,object_name,status from dba_objects where owner='MAM42SYS'; OWNER OBJECT_NAME STATUS -------- ------------------------- ------- WOO WOO_NAVBONTMOL VALID WOO WOO_NAVTONTCOL VALID WOO WOO_NAV2GATIWN VALID
到此，关于“AMDU数据恢复的方法是什么”的学习就结束了，希望能够解决大家的疑惑。理论与实践的搭配能更好的帮助大家学习，快去试试吧！若想继续学习更多相关知识，请继续关注创新互联-成都网站建设公司网站，小编会继续努力为大家带来更多实用的文章！
新闻名称：AMDU数据恢复的方法是什么-创新互联
标题来源：http://hbruida.cn/article/djhiei.html
