windows上面如何物理备份crs的ocr与voting disk

mfkqwyc86

windows上面如何物理备份crs的ocr与voting disk

Maclean Liu(刘相兵

1.

默认每4个小时 ocr会自动备份， 可以通过如下命令找出 备份文件

[grid@vrh2 ~]$ ocrconfig -showbackup

vrh2     2012/03/03 22:02:45     /g01/11.2.0/grid/cdata/vrh-cluster/backup00.ocr

vrh2     2012/03/03 18:02:45     /g01/11.2.0/grid/cdata/vrh-cluster/backup01.ocr

vrh2     2012/03/03 14:02:44     /g01/11.2.0/grid/cdata/vrh-cluster/backup02.ocr

vrh2     2012/03/02 03:09:35     /g01/11.2.0/grid/cdata/vrh-cluster/day.ocr

vrh2     2012/02/24 03:09:04     /g01/11.2.0/grid/cdata/vrh-cluster/week.ocr
PROT-25: Manual backups for the Oracle Cluster Registry are not available


还可以利用  ocrconfig  -export 导出ocr到文件


[grid@vrh2 ~]$ su - root
Password:

[root@vrh2 ~]# ocrconfig  -export new.ocr
[root@vrh2 ~]# file new.ocr
new.ocr: data


2. 在Unix/Linux上可以使用dd 备份votedisk

而在Windows上有 ocopy

C:\Users\Maclean.Liu>ocopy
OCOPY v2.0 - Copyright 1989-1993 Oracle Corp.  All rights reserved.
Usage:
    ocopy from_file [to_file [a | size_1 [size_n]]]
    ocopy -b from_file to_drive
    ocopy -r from_drive to_dir


How do I restore OCR from a backup? On Windows, can I use ocopy?
The only recommended way to restore an OCR from a backup is "ocrconfig -restore ". The ocopy command will not be able to perform the restore action for OCR.


    ocopy \\.\votedsk1 o:\backup\votedsk1.bak

Maclean Liu(刘相兵

"windows上面如何物理备份RAC 中 crs的ocr与voting disk?"

ODM Data:

1. OCR / Vote disk Maintenance Operations: (ADD/REMOVE/REPLACE/MOVE) [ID 428681.1]
   
2. 
   
3. Applies to:
   
4. Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.2.0.3 - Release: 10.2 to 11.2
   
5. Information in this document applies to any platform.
   
6. Goal
   
7. The goal of this note is to provide steps to add, remove, replace or move an Oracle Cluster Repository (OCR) or voting disk in Oracle Clusterware 10gR2, 11gR1 and 11gR2 environment. It will also provide steps to move OCR / voting and ASM devices from raw device to block device.
   
8. 
   
9. This article is intended for DBA and Support Engineers who need to modify, or move OCR and voting disks files, customers who have an existing clustered environment deployed on a storage array and might want to migrate to a new storage array with minimal downtime.
   
10. 
    
11. Typically, one would simply cp or dd the files once the new storage has been presented to the hosts. In this case, it is a little more difficult because:
    
12. 
    
13. 1. The Oracle Clusterware has the OCR and voting disks open and is actively using them. (Both primary and mirrors)
    
14. 2. There is an API provided for this function (ocrconfig, and crsctl), which is the appropriate interface than typical cp and/or dd commands.
    
15. 
    
16. It is highly recommended to take a backup of the voting disk, and OCR device before making any changes.
    
17. 
    
18. Oracle Cluster Registry (OCR) and Voting Disk Additional clarifications
    
19. 
    
20. The following steps assume the cluster is setup using Oracle redundancy with 3 voting disks and 2 OCR.
    
21. 
    
22. 
    
23. Solution
    
24. ADD/REMOVE/REPLACE/MOVE OCR Device
    
25. Note: You must be logged in as the root user, because root owns the OCR files. "crsctl -replace" command can only be issued when CRS is running, otherwise "PROT-1: Failed to initialize ocrconfig" will occur.
    
26. 
    
27. 
    
28. Make sure there is a recent copy of the OCR file before making any changes:
    
29. 
    
30.     ocrconfig -showbackup
    
31. 
    
32. If there is not a recent backup copy of the OCR file, an export can be taken for the current OCR file. Use the following command to generate an export of the online OCR file:
    
33. 
    
34. In 10.2
    
35. 
    
36.     # ocrconfig -export <OCR export_filename> -s online
    
37. 
    
38. In 11.1 and 11.2
    
39. 
    
40.     # ocrconfig -manualbackup
    
41.     node1 2008/08/06 06:11:58 /crs/cdata/crs/backup_20080807_003158.ocr
    
42. 
    
43. If you need to recover using this file, the following command can be used:
    
44. 
    
45. # ocrconfig -import <OCR export_filename>
    
46. 
    
47. From 11.2+, please also refer How to restore ASM based OCR after complete loss of the CRS diskgroup on Linux/Unix systems Document 1062983.1
    
48. 
    
49. To see whether OCR is healthy, run an ocrcheck, which should return with like below.
    
50. 
    
51.     # ocrcheck
    
52.     Status of Oracle Cluster Registry is as follows :
    
53.     Version : 2
    
54.     Total space (kbytes) : 497928
    
55.     Used space (kbytes) : 312
    
56.     Available space (kbytes) : 497616
    
57.     ID : 576761409
    
58.     Device/File Name : /dev/raw/raw1
    
59.     Device/File integrity check succeeded
    
60.     Device/File Name : /dev/raw/raw2
    
61.     Device/File integrity check succeeded
    
62. 
    
63.     Cluster registry integrity check succeeded
    
64. 
    
65.     For 11.2+, ocrcheck as root user should also show:
    
66. 
    
67.     Logical corruption check succeeded
    
68. 
    
69. 1. To add an OCRMIRROR device when only OCR device is defined:
    
70. 
    
71. To add an OCR mirror device, provide the full path including file name.
    
72. 10.2 and 11.1:
    
73. 
    
74.     # ocrconfig -replace ocrmirror <filename>
    
75. 
    
76. 11.2+: From 11.2 onwards, upto 4 ocrmirrors can be added
    
77. 
    
78.     # ocrconfig -add <filename>
    
79. 
    
80. 
    
81. 2. To remove an OCR device:
    
82. 
    
83. To remove an OCR device:
    
84. 10.2 and 11.1:
    
85. 
    
86.     # ocrconfig -replace ocr
    
87. 
    
88. 11.2+:
    
89. 
    
90.     # ocrconfig -delete <filename>
    
91. 
    
92. 
    
93.     * Once an OCR device is removed, ocrmirror device automatically changes to be OCR device.
    
94.     * It is not allowed to remove OCR device if only 1 OCR device is defined, the command will return PROT-16.
    
95. 
    
96. 
    
97. To remove an OCR mirror device:
    
98. 10.2 and 11.1:
    
99. 
    
100.     # ocrconfig -replace ocrmirror
     
101. 
     
102. 11.2+:
     
103. 
     
104.     # ocrconfig -delete <ocrmirror filename>
     
105. 
     
106. 
     
107. After removal, the old OCR/OCRMIRROR can be deleted if they are on cluster filesystem.
     
108. 
     
109. 
     
110. 3. To replace or move the location of an OCR device:
     
111. 
     
112. Note. 1. An ocrmirror must be in place before trying to replace the OCR device. The ocrconfig will fail with PROT-16, if there is no ocrmirror.
     
113. 2. If an OCR device is replaced with a device of a different size, the size of the new device will not be reflected until the clusterware is restarted.
     
114. 3. If OCR is on cluster file system, the new OCR or OCRMIRROR file must be touched first before replace command can be issued. Otherwise PROT-21: Invalid parameter will occur.
     
115. 
     
116. 10.2 and 11.1:
     
117. To replace the OCR device with <filename>, provide the full path including file name.
     
118. 
     
119.     # ocrconfig -replace ocr <filename>
     
120. 
     
121. To replace the OCR mirror device with <filename>, provide the full path including file name.
     
122. 
     
123.     # ocrconfig -replace ocrmirror <filename>
     
124. 
     
125. 11.2:
     
126. The command is same for replace either OCR or OCRMIRRORs:
     
127. 
     
128. # ocrconfig -replace <current filename> -replacement <new filename>
     
129. eg:
     
130. # ocrconfig -replace /cluster_file/ocr.dat -replacement +OCRVOTE
     
131. 
     
132. Example Moving OCR from Raw Device to Block Device(pre 11.2)
     
133. 
     
134. The OCR disk must be owned by root, in the oinstall group, and must have permissions set to 640. Provide at least 100 MB disk space for the OCR.
     
135. 
     
136. In this example the OCR files will be on the following devices:
     
137. 
     
138.     /dev/raw/raw1
     
139.     /dev/raw/raw2
     
140. 
     
141. For moving the OCR  from raw device to block device there are two different ways. One, which requires a full cluster outage, and one with no outage. The offline method is recommended for 10.2 and earlier since a cluster outage is required anyways due to an Oracle bug, which prevents online addition and deletion of voting files. This bug is fixed in 11.1, so either online or offline method can be employed in 11.1 onwards.
     
142. 
     
143. Method 1 (Online)
     
144. 
     
145. If there are additional block devices of same or larger size available, one can perform 'ocrconfig -replace'.
     
146. 
     
147. PROS: No cluster outage required. Run 2 commands and changes are reflected across the entire cluster.
     
148. 
     
149. CONS: Need temporary additional block devices with 256MB in size. One can reclaim the storage pointed by the raw devices when the operation completes.
     
150. 
     
151. On one node as root run:
     
152. 
     
153. 
     
154.     # ocrconfig -replace ocr /dev/sdb1
     
155.     # ocrconfig -replace ocrmirror /dev/sdc1
     
156. 
     
157. For every ocrconfig or ocrcheck command a trace file to $CRS_Home/log/<hostname>/client directory is written. Below an example from the successful ocrconfig -replace ocr command.
     
158. 
     
159. Oracle Database 10g CRS Release 10.2.0.4.0 Production Copyright 1996, 2008 Oracle. All rights reserved.
     
160. 2008-08-06 07:07:10.424: [ OCRCONF][3086866112]ocrconfig starts...
     
161. 2008-08-06 07:07:11.328: [ OCRCONF][3086866112]Successfully replaced OCR and set block 0
     
162. 2008-08-06 07:07:11.328: [ OCRCONF][3086866112]Exiting [status=success]...
     
163. 
     
164. 
     
165. Now run ocrcheck to verify if the OCR is pointing to the block device and no error is returned.
     
166. Status of Oracle Cluster Registry is as follows :
     
167. 
     
168. 
     
169.     Version : 2
     
170.     Total space (kbytes) : 497776
     
171.     Used space (kbytes) : 3844
     
172.     Available space (kbytes) : 493932
     
173.     ID : 576761409
     
174.     Device/File Name : /dev/sdb1
     
175.     Device/File integrity check succeeded
     
176.     Device/File Name : /dev/sdc2
     
177.     Device/File integrity check succeeded
     
178. 
     
179.     Cluster registry integrity check succeeded
     
180. 
     
181. Method 2 (Offline)
     
182. 
     
183. In place method when additional storage is not available, but this requires cluster downtime.
     
184. 
     
185. Below the existing mapping from the raw bindings to the block devices, is defined in /etc/sysconfig/rawdevices
     
186. 
     
187. 
     
188.     /dev/raw/raw1 /dev/sdb1
     
189.     /dev/raw/raw2 /dev/sdc1
     
190. 
     
191.     # raw -qa
     
192.     /dev/raw/raw1: bound to major 8, minor 17
     
193.     /dev/raw/raw2: bound to major 8, minor 33
     
194. 
     
195.     # ls /dev/raw/raw*
     
196.     crw-r----- 1 root oinstall 162, 1 Jul 24 10:39 /dev/raw/raw1
     
197.     crw-r----- 1 root oinstall 162, 2 Jul 24 10:39 /dev/raw/raw2
     
198. 
     
199.     # ls -ltra /dev/*
     
200.     brw-r----- 1 root oinstall 8, 17 Jul 24 10:39 /dev/sdb1
     
201.     brw-r----- 1 root oinstall 8, 33 Jul 24 10:39 /dev/sdc1
     
202. 
     
203. 
     
204. 1. Shutdown Oracle Clusterware on all nodes using "crsctl stop crs" as root.
     
205. 
     
206. 2. On all nodes run the following commands as root:
     
207. 
     
208.     # ocrconfig -repair ocr /dev/sdb1
     
209.     # ocrconfig -repair ocrmirror /dev/sdc1
     
210. 
     
211. 3. On one node as root run:
     
212. 
     
213.     # ocrconfig -overwrite
     
214. 
     
215. In the $CRS_Home/log/<hostname>/client directory there is a trace file from "ocrconfig -overwrite" like ocrconfig_<pid>.log which should exit with status=success like below:
     
216. 
     
217.     cat /crs/log/node1/client/ocrconfig_20022.log
     
218. 
     
219.     Oracle Database 10g CRS Release 10.2.0.4.0 Production Copyright 1996, 2008 Oracle. All rights reserved.
     
220.     2008-08-06 06:41:29.736: [ OCRCONF][3086866112]ocrconfig starts...
     
221.     2008-08-06 06:41:31.535: [ OCRCONF][3086866112]Successfully overwrote OCR configuration on disk
     
222.     2008-08-06 06:41:31.535: [ OCRCONF][3086866112]Exiting [status=success]...
     
223. 
     
224. As a verification step run ocrcheck on all nodes and the Device/File Name should reflect the block devices replacing the raw devices:
     
225. 
     
226.     # ocrcheck
     
227.     Status of Oracle Cluster Registry is as follows :
     
228.     Version : 2
     
229.     Total space (kbytes) : 497776
     
230.     Used space (kbytes) : 3844
     
231.     Available space (kbytes) : 493932
     
232.     ID : 576761409
     
233.     Device/File Name : /dev/sdb1
     
234.     Device/File integrity check succeeded
     
235.     Device/File Name : /dev/sdc1
     
236.     Device/File integrity check succeeded
     
237. 
     
238.     Cluster registry integrity check succeeded
     
239. 
     
240. Example of adding an OCR device file on raw device (Pre 11.2)
     
241. 
     
242. If you have upgraded your environment from a previous version, where you only had one OCR device file, you can use the following step to add an OCRMIRROR file.
     
243. 
     
244. Add /dev/raw/raw2 as OCR mirror device
     
245. 
     
246.     # ocrconfig -replace ocrmirror /dev/raw/raw2
     
247. 
     
248. Example of adding/replacing OCR/OCRMIRROR on cluster file system (per 11.2)
     
249. 
     
250. The new OCR/OCRMIRROR file on the cluster filesystem must exist before add/replace can happen. For example, the new OCR and OCRMIRROR will be located under:
     
251. /cluster_fs/OCR/newocr.dat
     
252. /cluster_fs/OCR/newocrm.dat
     
253. 
     
254. As root user:
     
255. # touch /cluster_fs/OCR/newocr.dat
     
256. # touch /cluster_fs/OCR/newocrm.dat
     
257. # chown root:oinstall /cluster_fs/OCR/newocr.dat
     
258. # chown root:oinstall /cluster_fs/OCR/newocrm.dat
     
259. # chmod 640 /cluster_fs/OCR/newocr.dat
     
260. # chmod 640 /cluster_fs/OCR/newocrm.dat
     
261. 
     
262. To add OCRMIRROR:
     
263. # ocrconfig -replace ocrmirror /cluster_fs/OCR/newocrm.dat
     
264. 
     
265. To replace OCR or OCRMIRROR:
     
266. # ocrconfig -replace ocr /cluster_fs/OCR/newocr.dat
     
267. # ocrconfig -replace ocrmirror /cluster_fs/OCR/newocrm.dat
     
268. 
     
269. 
     
270. ADD/DELETE/MOVE Voting Disk
     
271. Note: 1. crsctl votedisk commands must be run as root
     
272. 2 .If the new voting disk is on cluster file system, then it needs to be touched with proper ownership and permission before they can be added.
     
273. 3. If the old voting disk is on cluster file system, it needs to be deleted manually after crsctl delete css votedisk command.
     
274. 4. The voting disk must be owned by the oracle user, in the oinstall group, and must have permissions set to 644. In 10g provide at least 20 MB disk space for the voting disk. In 11g provide at least 280 MB disk space for the voting disk.
     
275. 
     
276. 
     
277. 10.2
     
278. 
     
279. Shutdown the Oracle Clusterware (crsctl stop crs as root) on all nodes before making any modification to the voting disk. Determine the current voting disk location using:
     
280. crsctl query css votedisk
     
281. 
     
282. 1. To add a Voting Disk, provide the full path including file name:
     
283. 
     
284.     # crsctl add css votedisk <VOTEDISK_LOCATION> -force
     
285. 
     
286. 2. To delete a Voting Disk, provide the full path including file name:
     
287. 
     
288.     # crsctl delete css votedisk <VOTEDISK_LOCATION> -force
     
289. 
     
290. 3. To move a Voting Disk, provide the full path including file name:
     
291. 
     
292.     # crsctl add css votedisk <NEW_LOCATION> -force
     
293.     # crsctl delete css votedisk <OLD_LOCATION> -force
     
294. 
     
295. After modifying the voting disk, start the Oracle Clusterware stack on all nodes
     
296. 
     
297.     # crsctl start crs
     
298. 
     
299. Verify the voting disk location using
     
300. 
     
301.     # crsctl query css votedisk
     
302. 
     
303. 
     
304. 11.1
     
305. 
     
306. Starting with 11.1.0.6, the below commands can be performed online.
     
307. 
     
308. 1. To add a Voting Disk, provide the full path including file name:
     
309. 
     
310. # crsctl add css votedisk <VOTEDISK_LOCATION>
     
311. 
     
312. 
     
313. 2. To delete a Voting Disk, provide the full path including file name:
     
314. 
     
315. # crsctl delete css votedisk <VOTEDISK_LOCATION>
     
316. 
     
317. 3. To move a Voting Disk, provide the full path including file name:
     
318. 
     
319. # crsctl add css votedisk <NEW_LOCATION>
     
320. # crsctl delete css votedisk <OLD_LOCATION>
     
321. 
     
322. Verify the voting disk location using:
     
323. # crsctl query css votedisk
     
324. 
     
325. 11.2+:
     
326. From 11.2, votedisk can be stored on either ASM diskgroup or cluster file systems. The following commands can only be executed when GI is running either in cluster mode or exclusive mode. As grid user:
     
327. 
     
328. 1. To add a Voting Disk
     
329. a. When votedisk is on cluster file system:
     
330. $ crsctl add css votedisk <VOTEDISK_LOCATION/filename>
     
331. 
     
332. b. When votedisk is on ASM diskgroup, no add option available. The number of votedisk is determined by the diskgroup redundancy. If more copy of votedisk is desired, one can move votedisk to a diskgroup with higher redundancy.
     
333. 
     
334. 2. To delete a Voting Disk
     
335. a. When votedisk is on cluster file system:
     
336. $ crsctl delete css votedisk <VOTEDISK_LOCATION/filename>
     
337. 
     
338. b. When votedisk is on ASM, no delete option available, one can only replace the existing votedisk group with another ASM diskgroup
     
339. 
     
340. 3. To move a Voting Disk
     
341. a. When votedisk is on cluster file system:
     
342. $ crsctl add css votedisk <NEW VOTEDISK_LOCATION/filename>
     
343. $ crsctl delete css votedisk <OLD VOTEDISK_LOCATION/filename>
     
344. 
     
345. b. When votedisk is on ASM or moving votedisk between cluster file system and ASM diskgroup
     
346. 
     
347. $ crsctl replace votedisk <+diskgroup>|<vdisk>
     
348. 
     
349. eg:
     
350. move from ASM to cluster file system:
     
351. $ crsctl replace votedisk /shared/vote.dat
     
352. Now formatting voting disk: /shared/vote.dat.
     
353. CRS-4256: Updating the profile
     
354. Successful addition of voting disk 32ff90ab38a04f65bf0c428c8fea9721.
     
355. Successful deletion of voting disk 3d34623f09b64f9dbfa44fabf455513e.
     
356. Successful deletion of voting disk 7043c38000a24f1abf36473ca7e9cd9e.
     
357. Successful deletion of voting disk 18de241007df4f9cbf3fbb4193f0ecb4.
     
358. CRS-4256: Updating the profile
     
359. CRS-4266: Voting file(s) successfully replaced
     
360. 
     
361. move from an ASM diskgroup +CRS to ASM diskgroup +OCRVOTE:
     
362. $ crsctl replace votedisk +OCRVOTE
     
363. CRS-4256: Updating the profile
     
364. Successful addition of voting disk 3d34623f09b64f9dbfa44fabf455513e.
     
365. Successful addition of voting disk 7043c38000a24f1abf36473ca7e9cd9e.
     
366. Successful addition of voting disk 18de241007df4f9cbf3fbb4193f0ecb4.
     
367. Successful deletion of voting disk a32c9b158e644fabbfdcc239c76f22a0.
     
368. Successfully replaced voting disk group with +CRS.
     
369. CRS-4256: Updating the profile
     
370. CRS-4266: Voting file(s) successfully replaced
     
371. 
     
372. 
     
373. 4. To verify:
     
374. $ crsctl query css votedisk
     
375. 
     
376. 
     
377. EXAMPLE MOVING VOTING DISK FROM RAW DEVICE to BLOCK DEVICE(Pre 11.2)
     
378. 
     
379. In this example the voting disks will be on the following devices:
     
380. 
     
381.     /dev/raw/raw4
     
382.     /dev/raw/raw5
     
383.     /dev/raw/raw6
     
384. 
     
385. Backup Voting before starting any modification.
     
386. 
     
387. To determine the configured voting devices run "crsctl query css votedisk"
     
388. 
     
389. 
     
390.     # crsctl query css votedisk
     
391.     0. 0 /dev/raw/raw4
     
392.     1. 0 /dev/raw/raw5
     
393.     2. 0 /dev/raw/raw6
     
394.     located 3 votedisk(s).
     
395. 
     
396. Backup Voting
     
397. 
     
398. Take a backup of all voting disk:
     
399. 
     
400.     $ dd if=voting_disk_name of=backup_file_name
     
401. 
     
402. For Windows:
     
403. 
     
404.     ocopy \\.\votedsk1 o:\backup\votedsk1.bak
     
405. 
     
406. 
     
407. Moving Voting Device from RAW Device to Block Device
     
408. 
     
409. 1) Run crsctl query css votedisk to determine the current voting disks:
     
410. 
     
411.     # crsctl query css votedisk
     
412.     0. 0 /dev/raw/raw4
     
413.     1. 0 /dev/raw/raw5
     
414.     2. 0 /dev/raw/raw6
     
415.     located 3 votedisk(s).
     
416. 
     
417. 2) Shutdown Oracle Clusterware on all nodes using "crsctl stop crs" as root.
     
418. 
     
419. Note: This step is only required for 10g CRS. For 11.1 this is an online operation and no cluster outage is required.
     
420. 
     
421. 
     
422. 3) Perform add new voting disk and delete old voting disk. Please note, it is not allowed to delete the last defined voting disk without adding a new one first. Perform the below commands on one node only:
     
423. 
     
424.     # crsctl delete css votedisk /dev/raw/raw4 -force
     
425.     # crsctl add css votedisk /dev/vote1 -force
     
426.     # crsctl delete css votedisk /dev/raw/raw5 -force
     
427.     # crsctl delete css votedisk /dev/raw/raw6 -force
     
428.     # crsctl add css votedisk /dev/vote2 -force
     
429.     # crsctl add css votedisk /dev/vote3 -force
     
430. 
     
431. 
     
432. 4) Verify with crsctl query css votedisk:
     
433. 
     
434.     # crsctl query css votedisk
     
435.     0. 0 /dev/vote1
     
436.     1. 0 /dev/vote2
     
437.     2. 0 /dev/vote3
     
438.     located 3 votedisk(s).
     
439. 
     
440. 5) After this the Oracle Clusterware stack can be restarted with "crsctl start crs" as root. (Only required for 10g CRS)
     
441. 
     
442. Monitoring the cluster_alert.log in $CRS_HOME/log/<hostname>/alertnode.log the new configured voting disks should be online:
     
443. 
     
444. 2008-08-06 07:41:55.029
     
445. [cssd(31750)]CRS-1605:CSSD voting file is online: /dev/vote1. Details in /crs/log/node1/cssd/ocssd.log.
     
446. 2008-08-06 07:41:55.038
     
447. [cssd(31750)]CRS-1605:CSSD voting file is online: /dev/vote2. Details in /crs/log/node1/cssd/ocssd.log.
     
448. 2008-08-06 07:41:55.058
     
449. [cssd(31750)]CRS-1605:CSSD voting file is online: /dev/vote3. Details in /crs/log/node1/cssd/ocssd.log.
     
450. [cssd(31750)]CRS-1601:CSSD Reconfiguration complete. Active nodes are node1 node2 .
     
451. 
     
452. 
     
453. References
     
454. NOTE:1062983.1 - How to restore ASM based OCR after complete loss of the CRS diskgroup on Linux/Unix systems
     
455. NOTE:390880.1 - OCR Corruption after Adding/Removing voting disk to a cluster when CRS stack is running
     
456. NOTE:866102.1 - Renaming OCR Using "ocrconfig -overwrite" Fails

复制代码