11gr2 with asm to asm,主备采用存储复制

Maclean Liu(刘相兵

Question:
11gr2 with asm to asm,主备采用存储复制

有做过11gR2(asm),  rac 到单机采用存储复制做DR实施的没？

Maclean Liu(刘相兵

Answer:

How to restore ASM based OCR after complete loss of the CRS diskgroup on Linux/Unix systems (Doc ID 1062983.1)




Migrate the product database to test server, the public ip need to change to a different subnet and the private ip need not to be modify.

to modify the public ip subnet and ip information in the OCR, need perform the following two command when the CRS is running:

% $ORA_CRS_HOME/bin/oifcfg delif -global eth0
% $ORA_CRS_HOME/bin/oifcfg setif -global eth0/10.2.166.0:public

but the GI in test server has been stopped, so it is can not perform the above commands.

Maclean Liu(刘相兵

ODM Data:

1. How to restore ASM based OCR after complete loss of the CRS diskgroup on Linux/Unix systems
   
2. 
   
3. Applies to:
   
4. Oracle Server - Enterprise Edition - Version: 11.2.0.1.0 to 11.2.0.2 - Release: 11.2 to 11.2
   
5. Information in this document applies to any platform.
   
6. Goal
   
7. It is not possible to directly restore a manual or automatic OCR backup if the OCR is located in an ASM disk group. This is caused by the fact that the command 'ocrconfig -restore' requires ASM to be up & running in order to restore an OCR backup to an ASM disk group. However, for ASM to be available, the CRS stack must have been successfully started. For the restore to succeed, the OCR also must not be in use (r/w), i.e. no CRS daemon must be running while the OCR is being restored.
   
8. 
   
9. A description of the general procedure to restore the OCR can be found in the  documentation, this document explains how to recover from a complete loss of the ASM disk group that held the OCR and Voting files in a 11gR2 Grid environment.
   
10. Solution
    
11. When using an ASM disk group for CRS there are typically 3 different types of files located in the disk group that potentially need to be restored/recreated:
    
12. 
    
13.     the Oracle Cluster Registry file (OCR)
    
14.     the Voting file(s)
    
15.     the shared SPFILE for the ASM instances
    
16. 
    
17. The following example assumes that the OCR was located in a single disk group used exclusively for CRS. The disk group has just one disk using external redundancy.
    
18. 
    
19. Since the CRS disk group has been lost the CRS stack will not be available on any node.
    
20. 
    
21. The following settings used in the example would need to be replaced according to the actual configuration:
    
22. 
    
23. GRID user:                       oragrid
    
24. GRID home:                       /u01/app/11.2.0/grid ($CRS_HOME)
    
25. ASM disk group name for OCR:     CRS
    
26. ASM/ASMLIB disk name:            ASMD40
    
27. Linux device name for ASM disk:  /dev/sdh1
    
28. Cluster name:                    rac_cluster1
    
29. Nodes:                           racnode1, racnode2
    
30. 
    
31. 
    
32. This document assumes that the name of the OCR diskgroup remains unchanged, however there may be a need to use a different diskgroup name, in which case the name of the OCR diskgroup would have to be modified in /etc/oracle/ocr.loc across all nodes prior to executing the following steps.
    
33. 
    
34. 1. Locate the latest automatic OCR backup
    
35. 
    
36. When using a non-shared CRS home, automatic OCR backups can be located on any node of the cluster, consequently all nodes need to be checked for the most recent backup:
    
37. 
    
38. $ ls -lrt $CRS_HOME/cdata/rac_cluster1/
    
39. -rw------- 1 root root 7331840 Mar 10 18:52 week.ocr
    
40. -rw------- 1 root root 7651328 Mar 26 01:33 week_.ocr
    
41. -rw------- 1 root root 7651328 Mar 29 01:33 day.ocr
    
42. -rw------- 1 root root 7651328 Mar 30 01:33 day_.ocr
    
43. -rw------- 1 root root 7651328 Mar 30 01:33 backup02.ocr
    
44. -rw------- 1 root root 7651328 Mar 30 05:33 backup01.ocr
    
45. -rw------- 1 root root 7651328 Mar 30 09:33 backup00.ocr
    
46. 
    
47. 2. Make sure the Grid Infrastructure is shutdown on all nodes
    
48. 
    
49. Given that the OCR diskgroup is missing, the GI stack will not be functional on any node, however there may still be various daemon processes running.  On each node shutdown the GI stack using the force (-f) option:
    
50. # $CRS_HOME/bin/crsctl stop crs -f
    
51. 
    
52. 
    
53. 3. Start the CRS stack in exclusive mode
    
54. 
    
55. On the node that has the most recent OCR backup, log on as root and start CRS in exclusive mode, this mode will allow ASM to start & stay up without the presence of a Voting disk and without the CRS daemon process (crsd.bin) running.
    
56. 
    
57. 11.2.0.1:
    
58. # $CRS_HOME/bin/crsctl start crs -excl
    
59. ...
    
60. CRS-2672: Attempting to start 'ora.asm' on 'racnode1'
    
61. CRS-2676: Start of 'ora.asm' on 'racnode1' succeeded
    
62. CRS-2672: Attempting to start 'ora.crsd' on 'racnode1'
    
63. CRS-2676: Start of 'ora.crsd' on 'racnode1' succeeded
    
64. 
    
65. Please note:
    
66. This document assumes that the CRS diskgroup was completely lost, in which  case the CRS daemon (resource ora.crsd) will terminate again due to the inaccessibility of the OCR - even if above message indicates that the start succeeded.
    
67. If this is not the case - i.e. if the CRS diskgroup is still present (but corrupt or incorrect) the CRS daemon needs to be shutdown manually using:
    
68. # $CRS_HOME/bin/crsctl stop res ora.crsd -init
    
69. 
    
70. otherwise the subsequent OCR restore will fail.
    
71. 
    
72. 11.2.0.2:
    
73. # $CRS_HOME/bin/crsctl start crs -excl -nocrs
    
74. CRS-4123: Oracle High Availability Services has been started.
    
75. ...
    
76. CRS-2672: Attempting to start 'ora.cluster_interconnect.haip' on 'auw2k3'
    
77. CRS-2672: Attempting to start 'ora.ctssd' on 'racnode1'
    
78. CRS-2676: Start of 'ora.drivers.acfs' on 'racnode1' succeeded
    
79. CRS-2676: Start of 'ora.ctssd' on 'racnode1' succeeded
    
80. CRS-2676: Start of 'ora.cluster_interconnect.haip' on 'racnode1' succeeded
    
81. CRS-2672: Attempting to start 'ora.asm' on 'racnode1'
    
82. CRS-2676: Start of 'ora.asm' on 'racnode1' succeeded
    
83. 
    
84. IMPORTANT:
    
85. A new option '-nocrs' has been introduced with  11.2.0.2, which prevents the start of the ora.crsd resource. It is vital that this option is specified, otherwise the failure to start the ora.crsd resource will tear down ora.cluster_interconnect.haip, which in turn will cause ASM to crash.
    
86. 
    
87. 
    
88. 4. Label the CRS disk for ASMLIB use
    
89. 
    
90. If using ASMLIB the disk to be used for the CRS disk group needs to stamped first, as user root do:
    
91. # /usr/sbin/oracleasm createdisk ASMD40 /dev/sdh1
    
92. Writing disk header: done
    
93. Instantiating disk: done
    
94. 
    
95. 
    
96. 5. Create the CRS diskgroup via sqlplus
    
97. 
    
98. The disk group can now be (re-)created via sqlplus from the grid user. The compatible.asm attribute must be set to 11.2 in order for the disk group to be used by CRS:
    
99. $ sqlplus / as sysasm
    
100. SQL*Plus: Release 11.2.0.1.0 Production on Tue Mar 30 11:47:24 2010
     
101. Copyright (c) 1982, 2009, Oracle. All rights reserved.
     
102. Connected to:
     
103. Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
     
104. With the Real Application Clusters and Automatic Storage Management options
     
105. 
     
106. SQL> create diskgroup CRS external redundancy disk 'ORCL:ASMD40' attribute 'COMPATIBLE.ASM' = '11.2';
     
107. 
     
108. Diskgroup created.
     
109. SQL> exit
     
110. 
     
111. 
     
112. 6. Restore the latest OCR backup
     
113. 
     
114. Now that the CRS disk group is created & mounted the OCR can be restored - must be done as the root user:
     
115. # cd $CRS_HOME/cdata/rac_cluster1/
     
116. # $CRS_HOME/bin/ocrconfig -restore backup00.ocr
     
117. 
     
118. 
     
119. 7. Start the CRS daemon on the current node (11.2.0.1 only !)
     
120. 
     
121. Now that the OCR has been restored the CRS daemon can be started, this is needed to recreate the Voting file. Skip this step for 11.2.0.2.0.
     
122. # $CRS_HOME/bin/crsctl start res ora.crsd -init
     
123. CRS-2672: Attempting to start 'ora.crsd' on 'racnode1'
     
124. CRS-2676: Start of 'ora.crsd' on 'racnode1' succeeded
     
125. 
     
126. 
     
127. 8. Recreate the Voting file
     
128. 
     
129. The Voting file needs to be initialized in the CRS disk group:
     
130. # $CRS_HOME/bin/crsctl replace votedisk +CRS
     
131. Successful addition of voting disk 00caa5b9c0f54f3abf5bd2a2609f09a9.
     
132. Successfully replaced voting disk group with +CRS.
     
133. CRS-4266: Voting file(s) successfully replaced
     
134. 
     
135. 
     
136. 9. Recreate the SPFILE for ASM (optional)
     
137. 
     
138. 
     
139. Please note:
     
140. 
     
141. If you are
     
142. - not using an  SPFILE for ASM
     
143. - not using a shared SPFILE for ASM
     
144. - using a shared SPFILE not stored in ASM (e.g. on cluster file system)
     
145. this step possibly should be skipped.
     
146. 
     
147. Also use extra care in regards to the asm_diskstring parameter as it impacts the discovery of the voting disks.
     
148. 
     
149. Please verify the previous settings using the ASM alert log.
     
150. 
     
151. Prepare a pfile (e.g. /tmp/asm_pfile.ora) with the ASM startup parameters - these may vary from the example below. If in doubt consult the ASM alert log  as the ASM instance startup should list all non-default parameter values. Please note the last startup of ASM (in step 2 via CRS start) will not have used an SPFILE, so a startup prior to the loss of the CRS disk group would need to be located.
     
152. *.asm_power_limit=1
     
153. *.diagnostic_dest='/u01/app/oragrid'
     
154. *.instance_type='asm'
     
155. *.large_pool_size=12M
     
156. *.remote_login_passwordfile='EXCLUSIVE'
     
157. Now the SPFILE can be created using this PFILE:
     
158. $ sqlplus / as sysasm
     
159. SQL*Plus: Release 11.2.0.1.0 Production on Tue Mar 30 11:52:39 2010
     
160. Copyright (c) 1982, 2009, Oracle. All rights reserved.
     
161. 
     
162. Connected to:
     
163. Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
     
164. With the Real Application Clusters and Automatic Storage Management options
     
165. 
     
166. SQL> create spfile='+CRS' from pfile='/tmp/asm_pfile.ora';
     
167. 
     
168. File created.
     
169. SQL> exit
     
170. 
     
171. 
     
172. 10. Shutdown CRS
     
173. 
     
174. Since CRS is running in exclusive mode, it needs to be shutdown  to allow CRS to run on all nodes again. Use of the force (-f) option may be required:
     
175. # $CRS_HOME/bin/crsctl stop crs -f
     
176. ...
     
177. CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'auw2k3' has completed
     
178. CRS-4133: Oracle High Availability Services has been stopped.
     
179. 
     
180. 
     
181. 11. Rescan ASM disks
     
182. 
     
183. If using ASMLIB rescan all ASM disks on each node as the root user:
     
184. # /usr/sbin/oracleasm scandisks
     
185. Reloading disk partitions: done
     
186. Cleaning any stale ASM disks...
     
187. Scanning system for ASM disks...
     
188. Instantiating disk "ASMD40"
     
189. 
     
190. 
     
191. 12. Start CRS
     
192. As the root user submit the CRS startup on all cluster nodes:
     
193. # $CRS_HOME/bin/crsctl start crs
     
194. CRS-4123: Oracle High Availability Services has been started.
     
195. 
     
196. 
     
197. 13. Verify CRS
     
198. 
     
199. To verify that CRS is fully functional again:
     
200. # $CRS_HOME/bin/crsctl check cluster -all
     
201. **************************************************************
     
202. racnode1:
     
203. CRS-4537: Cluster Ready Services is online
     
204. CRS-4529: Cluster Synchronization Services is online
     
205. CRS-4533: Event Manager is online
     
206. **************************************************************
     
207. racnode2:
     
208. CRS-4537: Cluster Ready Services is online
     
209. CRS-4529: Cluster Synchronization Services is online
     
210. CRS-4533: Event Manager is online
     
211. **************************************************************
     
212. 
     
213. # $CRS_HOME/bin/crsctl status resource -t
     
214. ...

复制代码

szkking

刚做完RAC到单机的存储复制容灾，用的HDS的HUR。

单机端正常打开，一切正常；

不过客户提个要求，要对比两个库到底差了多少多长时间的数据，因为HUR现在是30秒同步一次，加上
断开SI的时间。

客户提出要求要对比两个库到底差了多少时间数据。这个真的搞不出来。
只想了一个办法，建个测试表，用存储过程每秒一次插入时间戳数据这种方式测试。或者停机验证下在mount状态的数据文件的SCN号

有没有更好的办法验证数据是否一致？或者是从别的方向入手来验证数据是否一致？

szkking

期待回复啊

Maclean Liu(刘相兵

Oracle中比对2张表之间数据是否一致的几种方法 http://www.oracledatabase12g.com ... -tables-method.html