When we install RAC, sometimes the incorrect ASM instance or LISTENER is installed due to various errors, or the CLUSTERWARE resource is added, but it does not really work, such:
The two nodes have created ASM1 and ASM2 instances respectively. The corresponding resource names are ora. RAC1.ASM1. asm and ora. RAC2.ASM2. asm, their statuses are all UNKONW, and three listeners are created for each node. The resource names are ora of Node 1 respectively. racw.listener.rac1.lsnr, ora. racw.listener1.rac1.lsnr, ora. racw.listener2.rac1.lsnr and ora of Node 2. RAC2_LISTENER.RAC2.lsnr, ora. RAC2_LISTENER2.RAC2.lsnr, ora. RAC2_LISTENER2.RAC2.lsnr, And the status is also UNKNOW. Obviously, these are incorrect resources, because an error is reported when crsctl start asm-n rac1 is executed, probably because during installation, not completed correctly, for example:
It cannot be deleted directly using srvctl.
Note: In srvctl remove usage, the object does not have a listener, and cannot be written as srvctl remove listener-n rac1 or srvctl remove ora. racw.listener.rac1.lsnr. You can check it with srvctl-h.
So how should we delete the above two types of resources correctly? There are two situations:
1. Delete the ASM instance (only list the deletion of ASM1, which can be pushed in the same way)
1. View Resources
Srvctl config asm-n rac1
2. log out of resources
Crs_unregister ora. rac1.ASM1. asm
3. log out of resources
Crs_unregister ora. rac1.ASM1. asm
Note that you cannot delete your ASM instance on this node. To delete a crs instance, stop the crs instance and then perform the delete operation on another node.
./Init. crs stop (linux only)
Crsctl stop crs (all)
Srvctl remove asm-n rac1-f
Ii. Delete LISTENER resources (CRS must be stopped before ASM is deleted)
1. View Resources
Srvctl config listener-n rac1
Srvctl config listener-n rac2
2. log out of resources
Crs_unregister ora. racw.listener.rac1.lsnr
3. Stop Resources
Crs_stop ora. racw.listener.rac1.lsnr
The following is an example of several operation diagrams.
The object to be deleted here is the ASM2 resource on node 2.
Stop CRS on node 2
Delete ASM2 on node 2.
In this case, we found that ASM2 has been deleted from the resource, and deleted in sequence. The correct results are shown in:
After that, we can use NETCA to recreate the listener and use DBCA to recreate the ASM instance ~ Very convenient.