Exadata deletion: the process of adding a physical disk

Exadata introduces the concepts of lun, celldisk, and griddisk in the disk section. Here we will briefly introduce them. For example, after a physical hard disk is added to the Cell, the LUN will be automatically created, LUN

Exadata introduces the concepts of lun, celldisk, and griddisk in the disk section. Here we will briefly introduce them. For example, after a physical hard disk is added to the Cell, the LUN will be automatically created, LUN

Exadata introduces the concept of lun, celldisk, griddisk, Hong Kong server, and us server in the disk section. Here is a brief introduction, for example:

We can see that after a physical hard disk is added to the Cell, the LUN will be automatically created. The LUN corresponds to the creation of a celldisk, and one celldisk corresponds to one or more griddisks, griddisk can be provided to the ASM instance.

Here, I will mainly record the complete process of deleting and adding a running Exadata machine's disk.
(Here we emphasize that "CellCLI>" is all commands executed on cells, and "SQL>" is all commands executed on compute node (both database nodes)

1. First, determine the location of the LUN of the hard disk that I want to delete. The celldisk name can be queried using the following command:

2. query the griddisk information. You can find the disk name in asm and the name of diskgroup.
Through this command, we can also see that the celldisk corresponds to three griddisks.

3. query disk information through the ASM instance

4. Next we will start the delete operation. If you delete celldisk, you should first Delete the disk from the top level and from the ASM level.

5. During the deletion process, check the reblance progress through this command to ensure that the ASM disk deletion operation is complete, and then proceed to the next step.

6. After deleting the DBFS_DG_CD_03_DMORLCEL08 disk in ASM, run the griddisk command to query and find that the corresponding asmDiskName and asmDiskGroupName have no value.

7. Delete the griddisk and query it. No information about griddisk DBFS_DG_CD_03_DMORLCEL08 is found.

8. Continue to delete RECO_CD_03_dmorlcel08 and query

9. Continue to delete DATA_CD_03_DMORLCEL08 and query

10. Delete celldisk and query LUN Information

11. after the deletion is complete, we will start the adding process. In the actual troubleshooting, Exadata will not be properly created after the disk replacement is complete, celldisk and griddisk, we need to manually create celldisk and griddisk.

Before manual creation, we need to query the physicaldisk status and confirm that physicalSerial corresponds to the disk you replaced.

12. Create a celldisk. Based on the preceding information, confirm that the celldisk to be created matches the LUN accurately. Do not write an error in the server space.

14. First query a normal disk and confirm the information to be set later, such as name, size, and offset.

15. Create a griddisk

16. If the disk is not deleted, force needs to delete it again. However, in our test, the disk is deleted normally.

17. Add a disk

18. Run this command to check the progress of adding a disk.

SQL> select * from v $ asm_operation;

19. Finally, all completed statuses

Now, all the experiments have been completed. If you do not add them after changing the disk, refer to this experiment.

This article is from the blog "Little Dog's nest" and will not be reposted!