Exadata after disk replacement asm disk remain mount_status closed header_status candidate

One of physical disk on exadata cell was droped for replacement status, after engineer change physical disk with new disk in v$asm_disk view shown that mount_status is closed and header_status is candidate:

select g.NAME,
       d.disk_number dsk_num,
       d.mount_status,
       d.header_status,
       d.OS_MB,
       d.path
 from v$asm_disk d, v$asm_diskgroup g
 where
      d.GROUP_NUMBER=g.GROUP_NUMBER
      and d.disk_number = 26;
 

NAME           DSK_NUM MOUNT_STATUS HEADER_STATUS      OS_MB PATH
----------- ---------- ------------ ------------- ---------- ------------------------------------------------
RECO           26      CACHED       MEMBER            582080  o/192.168.10.17;192.168.10.18/RECO_FD_02_x81cel04
DATA           26      CLOSED       CANDIDATE         5217280 o/192.168.10.13;192.168.10.14/DATA_FD_02_x81cel02

Solution : The problem will be resolved when the disks are added to the relevant disk groups by using the PATH value in the above query.

Processes must be performed by connecting to the ASM instance as SYSASM.

First of all check if rebalnce process is not working and if not than add disk manually.

check asm rebalance is not working:

sqlplus / as sysasm

SQL*Plus: Release 19.0.0.0.0 - Production on Fri Aug 4 16:21:21 2023
Version 19.17.0.0.0

Copyright (c) 1982, 2022, Oracle.  All rights reserved.


Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.17.0.0.0

SQL> select * from v$asm_operation;

no rows selected

SQL>

add disk manually:

alter diskgroup DATA add disk 'o/192.168.10.13;192.168.10.14/DATA_FD_02_x81cel02' rebalance power 4;

you can check progress of rebalance againg in v$asm_operation.

After rebalance process finish its job disk statuses must be cached and member.

 

select g.NAME,
       d.disk_number dsk_num,
       d.mount_status,
       d.header_status,
       d.OS_MB,
       d.path
 from v$asm_disk d, v$asm_diskgroup g
 where
      d.GROUP_NUMBER=g.GROUP_NUMBER
      and d.disk_number = 26;
 

NAME           DSK_NUM MOUNT_STATUS HEADER_STATUS      OS_MB PATH
----------- ---------- ------------ ------------- ---------- ------------------------------------------------
RECO           26      CACHED       MEMBER            582080  o/192.168.10.17;192.168.10.18/RECO_FD_02_x81cel04
DATA           26      CACHED       MEMBER            5217280 o/192.168.10.13;192.168.10.14/DATA_FD_02_x81cel02

Exadata CELL-01514: Connect Error. Verify that Management Server is listening at the specified HTTP port: 8888

 Today we faced below problem while trying to connect cellcli on Exadata Storage Cell

"CELL-01514: Connect Error. Verify that Management Server is listening at the specified HTTP port: 8888"

[root@testcel01 ~]# cellcli -e list physicaldisk detail

CELL-01514: Connect Error. Verify that Management Server is listening at the specified HTTP port: 8888.
[root@testcel01 ~]#

Cell server is not running actually and we need to solve this problem.
To solve this problem, you need to start cell daemon:

[root@testcel01 ~]# service celld start
1: ERROR: Resource temporarily unavailable
rds-ping failed on 192.168.10.27
1: ERROR: Resource temporarily unavailable
rds-ping failed on 192.168.23.16
1: 90 usec
1: 134 usec

Starting the RS, CELLSRV, and MS services...
Getting the state of RS services... running
Starting CELLSRV services...
The STARTUP of CELLSRV services was successful.
Starting MS services...
The STARTUP of MS services was successful.
[root@testcel01 ~]# 
[root@testcel01 ~]#

Cell server daemon was started successful. You can check its status:

[root@testcel01 ~]# service celld status
rsStatus: running
msStatus: running
cellsrvStatus: running
[root@testcel01 ~]#