Percebi que o agente e seus targets associados não estavam online no Oracle Enterprise Manager 13C:

Disparei a verificação do status via linha de comando para identificar alguma pista:
[user@hostname bin]$ ./emctl status agent
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved.
Na sessão “Blocked Reason” é evidenciado que há um problema:
Blocked Reason : Agent is out-of-sync with repository. This most likely means that the agent was reinstalled or recovered. Please contact an EM administrator to unblock the agent by performing an agent resync from the console.
Tentando o upload:
[user@hostname bin]$ ./emctl upload
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
EMD upload error:full upload has failed: The agent is blocked by the OMS. Agent is out-of-sync with repository. This most likely means that the agent was reinstalled or recovered. Please contact an EM administrator to unblock the agent by performing an agent resync from the console. (AGENT_BLOCKED)
Tentando o ping ao OMS:
[user@hostname bin]$ ./emctl pingOMS
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
EMD pingOMS error: The agent is blocked by the OMS. Agent is out-of-sync with repository. This most likely means that the agent was reinstalled or recovered. Please contact an EM administrator to unblock the agent by performing an agent resync from the console.
Diante disso, encontrei um Oracle Note reportando problema similar (“EM 12c, EM 13c: Enterprise Manager Cloud Control Agent is Blocked with Console Message: Agent is out-of-sync with repository. This most likely means Agent was reinstalled or recovered (Doc ID 1389227.1)”).

Para resolver: clicar em Configurar -> Gerenciar Cloud Control -> Agentes:

Após encontrar o agente, clicar em desbloquear:

Sim:

Sucesso:

Depois, clicar em Reinicializar:

Submeter:

Sucesso:

A partir disso, os targets associados já começam a ser normalizados:

Com isso, a comunicação com o OMS é resolvida:
[user@hostname bin]$ ./emctl pingOMS
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
EMD pingOMS completed successfully