Issues related to the VCS database agents
This section describes the known issues about VCS database agents.
Related information
Cluster Server known issues
VCS ASMDG resource status does not match the Oracle ASMDG resource status (3962416)ASMDG agent does not go offline if the management DB is running on the same (3856460)ASMDG on a particular does not go offline if its instances is being used by other database instances (3856450)Sometimes ASMDG reports as offline instead of faulted (3856454)Netlsnr agent monitoring can't detect tnslsnr running on Solaris if the entire process name exceeds 79 charactersThe ASMInstAgent does not support having pfile/spfile for the ASM Instance on the ASM diskgroupsVCS agent for ASM- Health check monitoring is not supported for ASMInst agentNOFAILOVER action specified for certain Oracle errorsASMInstance resource monitoring offline resource configured with OHASD as application resource logs error messages in VCS logsOracle agent fails to offline pluggable database (PDB) resource with PDB in backup modeClean succeeds for PDB even as PDB staus is UNABLE to OFFLINESecond level monitoring fails if user and table names are identicalMonitor entry point times out for Oracle PDB resources when CDB is moved to suspended state in Oracle 12.1.0.2Oracle agent fails to come online and monitor Oracle instance if threaded_execution parameter is set to true (3644425)