在有些场景下，RAC环境中如果主机出现问题，比如硬件故障等，不能启动，我们需要尽快存储上的启动
数据库，恢复业务，那么就需要迁移以前的RAC环境到新的主机环境下，我测试了11.2和12.1的RAC，恢复过程还是很快的，基本上就是安装软件的过程，如果真实场景恢复业务，有两种
方法： 1，按照我这里的
方法重新安装主机，恢复RAC和
数据库 2，如果之前有可用的操作系统的备份（比如NBU备份了OS），那么直接使用NBU还原即可 . 我这里测试的是
方法1，重新安装11204的GI（Grid Infrastructure）和ORACLE RDBMS软件，然后识别老存储。 测试环境：单节点RAC,操作系统是OEL Linux 6.6,
数据库版本是11.2.0.4 首先，因为存储使用的是11204的ASM，测试过程只安装11204的GI（Grid Infrastructure）软件，不用OUI配置GI。 [root@lunar5 ~]# /u01/app/oraInventory/orainstRoot.sh Changing permissions of /u01/app/oraInventory. Adding read,write permissions for group. Removing read,write,execute permissions for world. Changing groupname of /u01/app/oraInventory to oinstall. The execution of the script is complete. [root@lunar5 ~]# 执行root.sh： [root@lunar5 ~]# /u01/app/11.2.0.4/grid/root.sh Performing root user operation for Oracle 11g The following environment variables are set as: ORACLE_OWNER= grid ORACLE_HOME= /u01/app/11.2.0.4/grid Enter the full pathname of the local bin directory: [/usr/local/bin]: The contents of "dbhome" have not changed. No need to overwrite. The contents of "oraenv" have not changed. No need to overwrite. The contents of "coraenv" have not changed. No need to overwrite. Creating /etc/oratab file... Entries will be added to the /etc/oratab file as needed by Database Configuration Assistant when a database is created Finished running generic part of root script. Now product-specific root actions will be performed. Using configuration parameter file: /u01/app/11.2.0.4/grid/crs/install/crsconfig_params Creating trace directory User ignored Prerequisites during installation Installing Trace File Analyzer OLR initialization - successful root wallet root wallet cert root cert export peer wallet profile reader wallet pa wallet peer wallet keys pa wallet keys peer cert request pa cert request peer cert pa cert peer root cert TP profile reader root cert TP pa root cert TP peer pa cert TP pa peer cert TP profile reader pa cert TP profile reader peer cert TP peer user cert pa user cert Adding Clusterware entries to upstart CRS-2672: Attempting to start 'ora.mdnsd' on 'lunar5' CRS-2676: Start of 'ora.mdnsd' on 'lunar5' succeeded CRS-2672: Attempting to start 'ora.gpnpd' on 'lunar5' CRS-2676: Start of 'ora.gpnpd' on 'lunar5' succeeded CRS-2672: Attempting to start 'ora.cssdmonitor' on 'lunar5' CRS-2672: Attempting to start 'ora.gipcd' on 'lunar5' CRS-2676: Start of 'ora.cssdmonitor' on 'lunar5' succeeded CRS-2676: Start of 'ora.gipcd' on 'lunar5' succeeded CRS-2672: Attempting to start 'ora.cssd' on 'lunar5' CRS-2672: Attempting to start 'ora.diskmon' on 'lunar5' CRS-2676: Start of 'ora.diskmon' on 'lunar5' succeeded CRS-2676: Start of 'ora.cssd' on 'lunar5' succeeded ASM created and started successfully. Disk Group TEMPDG created successfully. clscfg: -install mode specified Successfully accumulated necessary OCR keys. Creating OCR keys for user 'root',privgrp 'root'.. Operation successful. CRS-4256: Updating the profile Successful addition of voting disk 381226346c054f62bf5f219ee16d7e25. Successfully replaced voting disk group with +TEMPDG. CRS-4256: Updating the profile CRS-4266: Voting file(s) successfully replaced ## STATE File Universal Id File Name Disk group -- ----- ----------------- --------- --------- 1. ONLINE 381226346c054f62bf5f219ee16d7e25 (/dev/asm-diski) [TEMPDG] Located 1 voting disk(s). CRS-2672: Attempting to start 'ora.asm' on 'lunar5' CRS-2676: Start of 'ora.asm' on 'lunar5' succeeded CRS-2672: Attempting to start 'ora.TEMPDG.dg' on 'lunar5' CRS-2676: Start of 'ora.TEMPDG.dg' on 'lunar5' succeeded Configure Oracle Grid Infrastructure for a Cluster ... succeeded [root@lunar5 ~]# 相应的checkpoint
文件内容： [root@lunar5 ~]# ll /u01/app/grid/Clusterware/ckptGridHA_lunar5.xml -rw-r--r-- 1 grid oinstall 4176 Feb 15 19:31 /u01/app/grid/Clusterware/ckptGridHA_lunar5.xml [root@lunar5 ~]# [root@lunar5 ~]# tail /u01/app/grid/Clusterware/ckptGridHA_lunar5.xml <CHECKPOINT LEVEL="MAJOR" NAME="ROOTCRS_OSDSETUP" DESC="ROOTCRS_OSDSETUP" STATE="SUCCESS"/> <CHECKPOINT LEVEL="MAJOR" NAME="ROOTCRS_ONETIME" DESC="ROOTCRS_ONETIME" STATE="SUCCESS"/> <CHECKPOINT LEVEL="MAJOR" NAME="ROOTCRS_OLR" DESC="ROOTCRS_OLR" STATE="SUCCESS"/> <CHECKPOINT LEVEL="MAJOR" NAME="ROOTCRS_GPNPSETUP" DESC="ROOTCRS_GPNPSETUP" STATE="SUCCESS"/> <CHECKPOINT LEVEL="MAJOR" NAME="ROOTCRS_OHASD" DESC="ROOTCRS_OHASD" STATE="SUCCESS"/> <CHECKPOINT LEVEL="MAJOR" NAME="ROOTCRS_INITRES" DESC="ROOTCRS_INITRES" STATE="SUCCESS"/> <CHECKPOINT LEVEL="MAJOR" NAME="ROOTCRS_ACFSINST" DESC="ROOTCRS_ACFSINST" STATE="SUCCESS"/> <CHECKPOINT LEVEL="MAJOR" NAME="ROOTCRS_BOOTCFG" DESC="ROOTCRS_BOOTCFG" STATE="SUCCESS"/> <CHECKPOINT LEVEL="MAJOR" NAME="ROOTCRS_NODECONFIG" DESC="ROOTCRS_NODECONFIG" STATE="SUCCESS"/> </CHECKPOINTS> [root@lunar5 ~]# 这里看到“DESC=”ROOTCRS_NODECONFIG” STATE=”SUCCESS””表示GI已经配置完成。 图形界面点击ok，继续执行其余配置,配置完成后，再次检查checkpoint
文件： [root@lunar5 ~]# ll /u01/app/grid/Clusterware/ckptGridHA_lunar5.xml -rw-r--r-- 1 grid oinstall 4176 Feb 15 19:31 /u01/app/grid/Clusterware/ckptGridHA_lunar5.xml [root@lunar5 ~]# cd /u01/app/grid/Clusterware/ [root@lunar5 Clusterware]# ll total 8 -rw-r--r-- 1 grid oinstall 4176 Feb 15 19:31 ckptGridHA_lunar5.xml [root@lunar5 Clusterware]# 这里看到，checkpoint
文件的日期没有变化，说明checkpoint
文件是执行root.sh的时候才有用的，也就是这个过程是11.2中为了方便客户，
增加了root.sh的失败后继续配置二设计的，非常体贴的
功能。在12.2中，该
功能更加方便，他将会只管的告诉你当前配置的检查点情况，如果有些步骤失败后，oracle会
自动清除老的配置，以便可以失败安装后不用重装，而是纠正
错误后继续配置，类似“断点续传”那种意思。 . 比如，下面是12.2beta上安装RAC时执行root.sh的过程： [root@lunar1 ~]# /stage/root.sh Performing root user operation. The following environment variables are set as: ORACLE_OWNER= grid ORACLE_HOME= /stage Enter the full pathname of the local bin directory: [/usr/local/bin]: The contents of "dbhome" have not changed. No need to overwrite. The contents of "oraenv" have not changed. No need to overwrite. The contents of "coraenv" have not changed. No need to overwrite. Entries will be added to the /etc/oratab file as needed by Database Configuration Assistant when a database is created Finished running generic part of root script. Now product-specific root actions will be performed. Relinking oracle with rac_on option Using configuration parameter file: /stage/crs/install/crsconfig_params The log of current session can be found at: /u01/app/grid/crsdata/lunar1/crsconfig/rootcrs_lunar1_2016-01-24_12-44-34AM.log 2016/01/24 12:44:34 CLSRSC-46: Error: '/stage/crs/install/ParentDirPerm_lunar1.txt' does not exist 2016/01/24 12:44:34 CLSRSC-46: Error: '/stage/crs/install/ParentDirPerm_lunar1.txt' does not exist 2016/01/24 12:44:35 CLSRSC-594: Executing installation step 1 of 19: 'SetupTFA'. 2016/01/24 12:44:35 CLSRSC-4001: Installing Oracle Trace File Analyzer (TFA) Collector. 2016/01/24 12:44:35 CLSRSC-4002: Successfully installed Oracle Trace File Analyzer (TFA) Collector. 2016/01/24 12:44:35 CLSRSC-594: Executing installation step 2 of 19: 'ValidateEnv'. 2016/01/24 12:44:37 CLSRSC-363: User ignored prerequisites during installation 2016/01/24 12:44:37 CLSRSC-594: Executing installation step 3 of 19: 'CheckFirstNode'. 2016/01/24 12:44:38 CLSRSC-594: Executing installation step 4 of 19: 'GenSiteGUIDs'. 2016/01/24 12:44:39 CLSRSC-594: Executing installation step 5 of 19: 'SaveParamFile'. 2016/01/24 12:44:40 CLSRSC-594: Executing installation step 6 of 19: 'SetupOSD'. 2016/01/24 12:44:41 CLSRSC-594: Executing installation step 7 of 19: 'CheckCRSConfig'. 2016/01/24 12:44:41 CLSRSC-594: Executing installation step 8 of 19: 'SetupLocalGPNP'. 2016/01/24 12:44:42 CLSRSC-594: Executing installation step 9 of 19: 'ConfigOLR'. 2016/01/24 12:44:43 CLSRSC-594: Executing installation step 10 of 19: 'ConfigCHMOS'. 2016/01/24 12:45:30 CLSRSC-594: Executing installation step 11 of 19: 'CreateOHASD'. 2016/01/24 12:45:31 CLSRSC-594: Executing installation step 12 of 19: 'ConfigOHASD'. 2016/01/24 12:45:46 CLSRSC-330: Adding Clusterware entries to file 'oracle-ohasd.service' 2016/01/24 12:46:08 CLSRSC-594: Executing installation step 13 of 19: 'InstallAFD'. 2016/01/24 12:46:11 CLSRSC-594: Executing installation step 14 of 19: 'InstallACFS'. 2016/01/24 12:46:11 CLSRSC-594: Executing installation step 15 of 19: 'InstallKA'. 2016/01/24 12:46:14 CLSRSC-594: Executing installation step 16 of 19: 'InitConfig'. CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'lunar1' CRS-2673: Attempting to stop 'ora.mdnsd' on 'lunar1' CRS-2673: Attempting to stop 'ora.gpnpd' on 'lunar1' CRS-2677: Stop of 'ora.mdnsd' on 'lunar1' succeeded CRS-2677: Stop of 'ora.gpnpd' on 'lunar1' succeeded CRS-2673: Attempting to stop 'ora.evmd' on 'lunar1' CRS-2677: Stop of 'ora.evmd' on 'lunar1' succeeded CRS-2673: Attempting to stop 'ora.gipcd' on 'lunar1' CRS-2677: Stop of 'ora.gipcd' on 'lunar1' succeeded CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'lunar1' has completed CRS-4133: Oracle High Availability Services has been stopped. 2016/01/24 12:46:23 CLSRSC-594: Executing installation step 17 of 19: 'StartCluster'. CRS-4123: Starting Oracle High Availability Services-managed resources CRS-2672: Attempting to start 'ora.mdnsd' on 'lunar1' CRS-2672: Attempting to start 'ora.evmd' on 'lunar1' CRS-2676: Start of 'ora.mdnsd' on 'lunar1' succeeded CRS-2676: Start of 'ora.evmd' on 'lunar1' succeeded CRS-2672: Attempting to start 'ora.gpnpd' on 'lunar1' CRS-2676: Start of 'ora.gpnpd' on 'lunar1' succeeded CRS-2672: Attempting to start 'ora.gipcd' on 'lunar1' CRS-2676: Start of 'ora.gipcd' on 'lunar1' succeeded CRS-2672: Attempting to start 'ora.cssdmonitor' on 'lunar1' CRS-2676: Start of 'ora.cssdmonitor' on 'lunar1' succeeded CRS-2672: Attempting to start 'ora.cssd' on 'lunar1' CRS-2672: Attempting to start 'ora.diskmon' on 'lunar1' CRS-2676: Start of 'ora.diskmon' on 'lunar1' succeeded CRS-2676: Start of 'ora.cssd' on 'lunar1' succeeded CRS-2672: Attempting to start 'ora.cluster_interconnect.haip' on 'lunar1' CRS-2672: Attempting to start 'ora.ctssd' on 'lunar1' CRS-2676: Start of 'ora.ctssd' on 'lunar1' succeeded CRS-2676: Start of 'ora.cluster_interconnect.haip' on 'lunar1' succeeded CRS-2672: Attempting to start 'ora.asm' on 'lunar1' CRS-2676: Start of 'ora.asm' on 'lunar1' succeeded CRS-2672: Attempting to start 'ora.storage' on 'lunar1' CRS-2676: Start of 'ora.storage' on 'lunar1' succeeded CRS-2672: Attempting to start 'ora.crf' on 'lunar1' CRS-2676: Start of 'ora.crf' on 'lunar1' succeeded CRS-2672: Attempting to start 'ora.crsd' on 'lunar1' CRS-2676: Start of 'ora.crsd' on 'lunar1' succeeded CRS-6023: Starting Oracle Cluster Ready Services-managed resources CRS-6017: Processing resource auto-start for servers: lunar1 CRS-6016: Resource auto-start has completed for server lunar1 CRS-6024: Completed start of Oracle Cluster Ready Services-managed resources CRS-4123: Oracle High Availability Services has been started. 2016/01/24 12:47:34 CLSRSC-343: Successfully started Oracle Clusterware stack 2016/01/24 12:47:34 CLSRSC-594: Executing installation step 18 of 19: 'ConfigNode'. CRS-2672: Attempting to start 'ora.ASMNET1LSNR_ASM.lsnr' on 'lunar1' CRS-2676: Start of 'ora.ASMNET1LSNR_ASM.lsnr' on 'lunar1' succeeded CRS-2672: Attempting to start 'ora.asm' on 'lunar1' CRS-2676: Start of 'ora.asm' on 'lunar1' succeeded CRS-2672: Attempting to start 'ora.CRSDG.dg' on 'lunar1' CRS-2676: Start of 'ora.CRSDG.dg' on 'lunar1' succeeded 2016/01/24 12:48:43 CLSRSC-594: Executing installation step 19 of 19: 'PostConfig'. 2016/01/24 12:49:04 CLSRSC-325: Configure Oracle Grid Infrastructure for a Cluster ... succeeded [root@lunar1 ~]# 可以看到，这个过程比12.2以前的RAC执行root.sh的
提示更加清晰了。 好吧，回到我们的环境中，继续检查老的asm磁盘组 [grid@lunar5 ~]$ kfod disks=all ds=true cluster=true status=true -------------------------------------------------------------------------------- Disk Size Header Path Disk Group User Group ================================================================================ 1: 512 Mb MEMBER /dev/asm-diskb DATADG1 grid asmadmin 2: 512 Mb MEMBER /dev/asm-diskc DATADG1 grid asmadmin 3: 512 Mb MEMBER /dev/asm-diskd DATADG1 grid asmadmin 4: 1024 Mb MEMBER /dev/asm-diske CRSDG grid asmadmin 5: 1024 Mb MEMBER /dev/asm-diskf CRSDG grid asmadmin 6: 1024 Mb MEMBER /dev/asm-diskg CRSDG grid asmadmin 7: 5120 Mb MEMBER /dev/asm-diskh DATADG2 grid asmadmin 8: 3072 Mb MEMBER /dev/asm-diski TEMPDG grid asmadmin -------------------------------------------------------------------------------- ORACLE_SID ORACLE_HOME HOST_NAME ================================================================================ +ASM1 /u01/app/11.2.0.4/grid lunar5 [grid@lunar5 ~]$ 将上述磁盘组
添加到ASM启动磁盘组的列表中： [grid@lunar5 ~]$ ss
sql*Plus: Release 11.2.0.4.0 Production on Mon Feb 15 21:31:29 2016 Copyright (c) 1982,2013,Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Real Application Clusters and Automatic Storage Management options
sql> show parameter asm NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ asm_diskgroups string asm_diskstring string /dev/asm* asm_power_limit integer 1 asm_preferred_read_failure_groups string
sql> alter system set asm_diskgroups='TEMPDG','CRSDG','DATADG1','DATADG2' scope=both; System altered.
sql> 对新
添加的磁盘组执行mount和dismount后，这些磁盘组就会
自动添加到ocr中： [root@lunar5 ~]# crsctl status res -t -------------------------------------------------------------------------------- NAME TARGET STATE SERVER STATE_DETAILS -------------------------------------------------------------------------------- Local Resources -------------------------------------------------------------------------------- ora.CRSDG.dg ONLINE ONLINE lunar5 ora.DATADG1.dg ONLINE ONLINE lunar5 ora.DATADG2.dg ONLINE ONLINE lunar5 ora.LISTENER.lsnr ONLINE ONLINE lunar5 ora.TEMPDG.dg ONLINE ONLINE lunar5 ora.asm ONLINE ONLINE lunar5 Started ora.gsd OFFLINE OFFLINE lunar5 ora.net1.network ONLINE ONLINE lunar5 ora.ons ONLINE ONLINE lunar5 -------------------------------------------------------------------------------- Cluster Resources -------------------------------------------------------------------------------- ora.LISTENER_SCAN1.lsnr 1 ONLINE ONLINE lunar5 ora.cvu 1 ONLINE ONLINE lunar5 ora.lunar5.vip 1 ONLINE ONLINE lunar5 ora.oc4j 1 ONLINE ONLINE lunar5 ora.scan1.vip 1 ONLINE ONLINE lunar5 [root@lunar5 ~]# 检查ASM磁盘组中的
内容（比如包含哪些
数据库），因为ASM是采用OMF的，因此大部分情况下，通过磁盘组的目录结构就可以看出来这个存储中以前包含哪些
数据库和其他相关信息： ASMCMD> lsdg State Type Rebal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name MOUNTED NORMAL N 512 4096 1048576 3072 2769 1024 872 0 N CRSDG/ MOUNTED NORMAL N 512 4096 1048576 1536 1251 512 369 0 N DATADG1/ MOUNTED EXTERN N 512 4096 1048576 5120 3386 0 3386 0 N DATADG2/ MOUNTED EXTERN N 512 4096 1048576 3072 2719 0 2719 0 Y TEMPDG/ ASMCMD> cd +crsdg ASMCMD> ls ASMCMD> cd +datadg1 ASMCMD> ls ASMCMD> cd +datadg2 ASMCMD> ls LUNAR/ ASMCMD> 这里看到，该存储中，包含了一个
数据库，crsdg中的信息已经被我
删除了，因此，没有老的ocr和voting disk
文件了 现在，已经确定只有datadg2上面有数据，因此可以重组磁盘组，以便合理利用空间（后续我要用这个vm做很多其他测试）： ASMCMD> lsdg State Type Rebal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name MOUNTED NORMAL N 512 4096 4194304 1536 1296 512 392 0 N DATADG1/ MOUNTED EXTERN N 512 4096 1048576 5120 3386 0 3386 0 N DATADG2/ MOUNTED EXTERN N 512 4096 1048576 3072
3016 0
3016 0 N DATADG3/ MOUNTED EXTERN N 512 4096 1048576 3072 2719 0 2719 0 Y TEMPDG/ ASMCMD> 使用kfod查看： [grid@lunar5 ~]$ kfod disks=all ds=true cluster=true status=true -------------------------------------------------------------------------------- Disk Size Header Path Disk Group User Group ================================================================================ 1: 512 Mb MEMBER /dev/asm-diskb DATADG1 grid asmadmin 2: 512 Mb MEMBER /dev/asm-diskc DATADG1 grid asmadmin 3: 512 Mb MEMBER /dev/asm-diskd DATADG1 grid asmadmin 4: 1024 Mb MEMBER /dev/asm-diske DATADG3 grid asmadmin 5: 1024 Mb MEMBER /dev/asm-diskf DATADG3 grid asmadmin 6: 1024 Mb MEMBER /dev/asm-diskg DATADG3 grid asmadmin 7: 5120 Mb MEMBER /dev/asm-diskh DATADG2 grid asmadmin 8: 3072 Mb MEMBER /dev/asm-diski TEMPDG grid asmadmin -------------------------------------------------------------------------------- ORACLE_SID ORACLE_HOME HOST_NAME ================================================================================ +ASM1 /u01/app/11.2.0.4/grid lunar5 [grid@lunar5 ~]$ 确认当前的crs状态都是正常的： [root@lunar5 ~]# crsctl status res -t ——————————————————————————– NAME TARGET STATE SERVER STATE_DETAILS ——————————————————————————– Local Resources ——————————————————————————– ora.DATADG1.dg ONLINE ONLINE lunar5 ora.DATADG2.dg ONLINE ONLINE lunar5 ora.DATADG3.dg ONLINE ONLINE lunar5 ora.LISTENER.lsnr ONLINE ONLINE lunar5 ora.TEMPDG.dg ONLINE ONLINE lunar5 ora.asm ONLINE ONLINE lunar5 Started ora.gsd OFFLINE OFFLINE lunar5 ora.net1.network ONLINE ONLINE lunar5 ora.ons ONLINE ONLINE lunar5 ——————————————————————————– Cluster Resources ——————————————————————————– ora.LISTENER_SCAN1.lsnr 1 ONLINE ONLINE lunar5 ora.cvu 1 ONLINE ONLINE lunar5 ora.lunar5.vip 1 ONLINE ONLINE lunar5 ora.oc4j 1 ONLINE ONLINE lunar5 ora.scan1.vip 1 ONLINE ONLINE lunar5 [root@lunar5 ~]# 至此老存储的ASM磁盘组已经在新的主机上可以识别了。 假设原来的主机已经完全不能启动了（比如硬件故障等），只能在存储上的ASM中查找
数据库使用的参数
文件： [grid@lunar5 ~]$ ss
sql*Plus: Release 11.2.0.4.0 Production on Mon Feb 15 21:48:15 2016 Copyright (c) 1982,Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Real Application Clusters and Automatic Storage Management options SYS@+ASM1>col name for a55 SYS@+ASM1>col type for a25 SYS@+ASM1>SELECT f.group_number,f.file_number,a.name name,f.type type 2 FROM v$asm_file f,v$asm_alias a 3 WHERE f.group_number=a.group_number and f.file_number=a.file_number 4 and f.type='PARAMETERFILE' 5 ORDER BY 1,2; GROUP_NUMBER FILE_NUMBER NAME TYPE ---------------- ---------------- ------------------------------------------------------- ------------------------- 2 272 spfile.272.892409049 PARAMETERFILE 2 272 spfilelunar.ora PARAMETERFILE Elapsed: 00:00:00.09 SYS@+ASM1> 这里看到，
数据库使用的参数
文件是spfilelunar.ora，它是spfile.272.892409049的别名
文件。 我们在ASM中查看一下： ASMCMD> pwd +datadg2/lunar ASMCMD> ls -l Type Redund Striped Time Sys Name Y ARCHIVELOG/ Y CONTROLFILE/ Y DATAFILE/ Y ONLINELOG/ Y PARAMETERFILE/ Y TEMPFILE/ N spfilelunar.ora => +DATADG2/LUNAR/PARAMETERFILE/spfile.272.892409049 ASMCMD> 我们将这个
文件复制到
文件系统，然后查看该
文件内容，以便确定是否为我们需要使用的
数据库的参数
文件： 1 ASMCMD> cp +DATADG2/LUNAR/PARAMETERFILE/spfile.272.892409049 /tmp/lunar.db.spfile copying +DATADG2/LUNAR/PARAMETERFILE/spfile.272.892409049 -> /tmp/lunar.db.spfile ASMCMD> 检查
数据库的spfile的
内容： [root@lunar5 ~]# ll /tmp/lunar.db.spfile -rw-r----- 1 grid oinstall 2560 Feb 15 21:51 /tmp/lunar.db.spfile [root@lunar5 ~]# strings /tmp/lunar.db.spfile *.audit_file_dest='/u01/app/oracle/admin/lunar/adump' *.audit_trail='db' *.cluster_database=true *.compatible='11.2.0.4.0' *.control_files='+DATADG2/lunar/controlfile/current.256.892408309','+DATADG2/lunar/controlfile/current.257.892408311' *.db_block_size=8192 *.db_cache_size=157286400 *.db_create_file_dest='+DATADG2' *.db_domain='' *.db_name='lunar' *.db_recovery_file_dest='+DATADG2' *.db_recovery_file_dest_size=4194304000 *.diagnostic_dest='/u01/app/oracle' lunar2.instance_number= lunar1.instance_number=1 *.java_pool_size=31457280 *.large_pool_size=31457280 *.log_archive_format='%t_%s_%r.dbf' *.open_cursors=300 *.pga_aggregate_target=228589568 *.processes=150 *.remote_listener='lunar-scan:1521' *.remote_login_passwordfile='exclusive' *.shared_pool_size=419430400 lunar2.thread=2 lunar1.thread=1 lunar2.undo_tablespace='UNDOTBS2' lunar1.undo_tablespace='UNDOTBS1' [root@lunar5 ~]# 这里确定的，该
文件+datadg2/lunar/spfilelunar.ora（也就是+DATADG2/LUNAR/PARAMETERFILE/spfile.272.892409049）就是我们需要使用的
数据库参数
文件。 安装Oracle 11.2.0.4
数据库软件，然
后执行root.sh，这个没有特别的东西，略。 之后，我们需要
修改ORACLE RDBMS的oracle二进制
文件的权限，让oracle
数据库进程可以
获取ASM磁盘组。 [root@lunar5 ~]# su - grid [grid@lunar5 ~]$ $ORACLE_HOME/bin/setasmgidwrap o=/u01/app/oracle/product/11.2.0.4/dbhome_1/bin/oracle [grid@lunar5 ~]$ ll /u01/app/oracle/product/11.2.0.4/dbhome_1/bin/oracle -rwsr-s--x 1 oracle asmadmin 239626689 Feb 15 22:09 /u01/app/oracle/product/11.2.0.4/dbhome_1/bin/oracle [grid@lunar5 ~]$ 注意，这里的/u01/app/oracle/product/11.2.0.4/dbhome_1/bin/oracle就是安装ORACLE RDBMS的ORACLE_HOME。 然后，将
数据库添加到CRS中，启动
数据库： [oracle@lunar5 ~]$ srvctl add database -d lunar -n lunar5 -o $ORACLE_HOME -p +DATADG2/LUNAR/PARAMETERFILE/spfile.272.892409049 -s OPEN -y AUTOMATIC -a "TEMPDG,DATADG1,DATADG2,DATADG3" -t IMMEDIATE [oracle@lunar5 ~]$ 检查
数据库在ocr中的配置： [oracle@lunar5 ~]$ srvctl config database -d lunar Database unique name: lunar Database name: lunar5 Oracle home: /u01/app/oracle/product/11.2.0.4/dbhome_1 Oracle user: oracle Spfile: +DATADG2/LUNAR/PARAMETERFILE/spfile.272.892409049 Domain: Start options: open Stop options: immediate Database role: PRIMARY Management policy: AUTOMATIC Server pools: lunar Database instances: Disk Groups: TEMPDG,DATADG3 Mount point paths: Services: Type: RAC Database is administrator managed [oracle@lunar5 ~]$ 启动
数据库： [oracle@lunar5 ~]$ srvctl start database -d lunar [oracle@lunar5 ~]$ 检查crs的状态： [root@lunar5 ~]# crsctl status res -t -------------------------------------------------------------------------------- NAME TARGET STATE SERVER STATE_DETAILS -------------------------------------------------------------------------------- Local Resources -------------------------------------------------------------------------------- ora.DATADG1.dg ONLINE ONLINE lunar5 ora.DATADG2.dg ONLINE ONLINE lunar5 ora.DATADG3.dg ONLINE ONLINE lunar5 ora.LISTENER.lsnr ONLINE ONLINE lunar5 ora.TEMPDG.dg ONLINE ONLINE lunar5 ora.asm ONLINE ONLINE lunar5 Started ora.gsd OFFLINE OFFLINE lunar5 ora.net1.network ONLINE ONLINE lunar5 ora.ons ONLINE ONLINE lunar5 -------------------------------------------------------------------------------- Cluster Resources -------------------------------------------------------------------------------- ora.LISTENER_SCAN1.lsnr 1 ONLINE ONLINE lunar5 ora.cvu 1 ONLINE ONLINE lunar5 ora.lunar.db 1 ONLINE ONLINE lunar5 Open ora.lunar5.vip 1 ONLINE ONLINE lunar5 ora.oc4j 1 ONLINE ONLINE lunar5 ora.scan1.vip 1 ONLINE ONLINE lunar5 [root@lunar5 ~]# 至此，整个使用新主机识别老存储的RAC（主要是识别ASM）就完成了。如果是
文件系统的环境，比这个简单很多，ASM的全部可以省略了。
原文链接：https://www.f2er.com/oracle/213508.html
