Problema

Ao tentar realizar um Move do GRID junto com o RDBMS no FPP, o processo falhou com o seguinte erro:

PRGO-1733 : No database in cluster "ORACLERESTART_lab03" is being moved.

Exemplo:

fppserver.dibiei.com: Audit ID: 3702
Job ID: 227
User: grid
Client: ORACLERESTART_lab03
Scheduled job command: "rhpctl move gihome -targetnode lab03 -sourcehome /u01/app/19.0.0/GI1924 -destwc WC_GI1925_lab03 -auto -dbhomes /u01/app/oracle/product/19.0.0.0/DB1924=WC_DB1925_lab03 -ignorewcpatches -cred dibiei_root -schedule NOW -eval"
Scheduled job execution start time: 2024-12-02T15:38:33-03. Equivalent local time: 2024-12-02 15:38:33
Current status: FAILED
Result file path: "/fpp/chkbase/scheduled/job-227-2024-12-02-15:38:34.log"
Job execution start time: 2024-12-02 15:38:35
Job execution end time: 2024-12-02 15:39:48
Job execution elapsed time: 1 minutes 12 seconds

Result file "/fpp/chkbase/scheduled/job-227-2024-12-02-15:38:34.log" contents:
fppserver.dibiei.com: Audit ID: 3701
fppserver.dibiei.com: Evaluation in progress for "move gihome" ...
fppserver.dibiei.com: verifying versions of Oracle homes ...
fppserver.dibiei.com: verifying owners of Oracle homes ...
fppserver.dibiei.com: verifying groups of Oracle homes ...
fppserver.dibiei.com: identifying patched working copies for databases being moved ...
fppserver.dibiei.com: PRGO-1774 : The evaluation revealed potential failure for command "move gihome".
PRGO-1733 : No database in cluster "ORACLERESTART_lab03" is being moved.

Mas o servidor tem 2 bancos de dados registrados no Grid:

[oracle@lab03 ~]$ srvctl config database
CDBTSSL
ORCL

[oracle@lab03 ~]$ srvctl config database -d CDBTSSL | grep home
Oracle home: /u01/app/oracle/product/19.0.0/DB1924
[oracle@lab03 ~]$
[oracle@lab03 ~]$ srvctl config database -d ORCL | grep home
Oracle home: /u01/app/oracle/product/19.0.0/DB1924

Causa

O caminho do Oracle Home informando no parâmetro -dbhomes (ou -sourcehome se for move database) é diferente do que é efetivamente usado no servidor:

Caminho informado no comando rhpctl possui 4 digitos no número da versão (19.0.0.0):

/u01/app/oracle/product/19.0.0.0/DB1924

Enquanto o que está sendo instalado no servidor tem apenas 3 dígitos (19.0.0):

/u01/app/oracle/product/19.0.0/DB1924

Solução

Neste caso é apenas um erro um de digitação nos parâmetros do comando rhpctl, basta ajustar corretamente e executar o comando novamente.

[grid@fppserver ~]$ export TARGET_NAME=lab03
[grid@fppserver ~]$ export NEW_RU="1925"
[grid@fppserver ~]$ export OLD_RU="1924"
[grid@fppserver ~]$ rhpctl move gihome \
>  -targetnode $TARGET_NAME \
>  -sourcehome /u01/app/19.0.0/GI${OLD_RU} \
>  -destwc "WC_GI${NEW_RU}_${TARGET_NAME}" \
>  -auto \
>  -dbhomes /u01/app/oracle/product/19.0.0/DB${OLD_RU}=WC_DB${NEW_RU}_${TARGET_NAME} \
>  -ignorewcpatches \
>  -cred dibiei_root \
>  -schedule NOW -eval
Operation "rhpctl move gihome" scheduled with the job ID "228".
[grid@fppserver ~]$
[grid@fppserver ~]$
[grid@fppserver ~]$ rhpctl query job -jobid 228 -brief
fppserver.dibiei.com: Audit ID: 3704
Job ID: 228
User: grid
Client: ORACLERESTART_lab03
Scheduled job command: "rhpctl move gihome -targetnode lab03 -sourcehome /u01/app/19.0.0/GI1924 -destwc WC_GI1925_lab03 -auto -dbhomes /u01/app/oracle/product/19.0.0/DB1924=WC_DB1925_lab03 -ignorewcpatches -cred dibiei_root -schedule NOW -eval"
Scheduled job execution start time: 2024-12-02T15:53:53-03. Equivalent local time: 2024-12-02 15:53:53
Current status: SUCCEEDED
Result file path: "/fpp/chkbase/scheduled/job-228-2024-12-02-15:54:04.log"
Job execution start time: 2024-12-02 15:54:05
Job execution end time: 2024-12-02 15:55:50
Job execution elapsed time: 1 minutes 44 seconds

Essa é uma das grandes vantagens de ter uma opção “dry-run” como o FPP oferece com o parâmetro -eval, poder detectar esse tipo de erro antes de janela de manutenção.