-
Title
Failed to run DBOVirtualizationProcessor processor of DBO_Virtualization collection of Oracle -
Description
The following errors can be received for Oracle databases:Oracle - Collection Status DBO_Virtualization Failed with the exception: A failure happened due to the following reason : Failed to execute collection [DBO_Virtualization], reason=VM not found.
Oracle - Collection Status. DBO_Virtualization Failed with the exception: java.lang.RuntimeException: Failed to execute collection [DBO_Virtualization], reason=Connection to the VMWare could not be established.
-
Cause
CAUSE 1
DNS entry for host is not found on the ESX server when the database agent performs a query.
CAUSE 2
The database agent is not able to reach the ESX server.
-
Resolution
RESOLUTION 1
The agent queries the ESX server host for its DNS entry.
When this property cannot be found, it pops up with the message "host name null" / VM... not found".
Normally when the VM (virtual machine) is turned on, host and DNS entry are synced, but it is possible that each site has its own net policies regarding DNS and DNS sync.Please make sure ESX server reports DNS entry for the host and the DB agent will follow.
RESOLUTION 2
Verify that there is connectivity between the Foglight Agent Manager (FglAM) where the database agent is hosted and the vCenter. Use ping (or other appropriate tools) as a method to verify that name resolves and can connect.