"No data was found for registration ID" error in DB2 or Oracle agent logs (4310557)

Chatee ahora con Soporte

Obtener ayuda en vivo
Completar registro

Iniciar sesión

Solicitar precios

Comuníquese con Ventas

Regresar

Comentarios enviados

¿Este artículo solucionó su problema?

Seleccionar calificación

Título

"No data was found for registration ID" error in DB2 or Oracle agent logs
Descripción

Messages similar to the following appear after starting a DB2 agent

ECHO <DB_DB2/5.6.10.3/DB_DB2/MYHOST-MYINSTANCE-agent> ERROR [MYHOST-MYINSTANCE-lowPriorityPool-2-[DB2_Host_Properties]] com.quest.qsi.fason.core.collection.processor.InstanceProcessor - Failed to run DB2HostPropertiesRamHostProcessor processor of DB2_Host_Properties collection.

java.lang.RuntimeException: Failed to execute collection [DB2_Host_Properties], reason=No data was found for registration ID 35

or

ERROR [RAC-INSTANCE-lowPriorityPool-1-[DBO_OS_General_Network][]] com.quest.qsi.fason.oracle.collection.processor.DBOInstanceProcessor - Failed to run DBOGeneralNetworkProcessor processor of DBO_OS_General_Network collection of HOSTNAME-INSTANCENAME instance.

java.lang.RuntimeException: Failed to execute collection [DBO_OS_General_Network], reason=No data was found for registration ID 28
Causa

CAUSE 1

This error can occur when it takes a long time for the OS collector to start collecting the data for the first time. It can happen in slow environments. The agent misses one cycle of the OS collection, but the next cycle the agent gets the data normally.

CAUSE 2

The Single OS collector is enabled in the Agent Properties of a DB2 or Oracle agent.
Resolución
RESOLUTION 1 (recommended)

It takes some time for the agent to start running all collections, the agent is waiting to get the results from the OS collector before running additional collections. This is working as designed.

RESOLUTION 2
1. Navigate to Administration | Agents | Agent Status
2. In the Agent status view, select the DB2 or Oracle agent not displaying the metrics.
3. Click on the Edit Properties button at the bottom of the screen.
4. Select the link to modify properties only for that agent.
5. Under OS Monitored Connection Profile (Unix), change the "Use Single OS Collector" to FALSE
6. Click the Save button
7. Deactivate the database agent
8. Activate the database agent
Note: Making this change will increase the number of OS connections made from the FglAM to the host when multiple database agents of the same type are monitoring the same host.

Comentarios enviados

¿Este artículo solucionó su problema?

Seleccionar calificación

Solicitar un artículo KB

Contenido recomendado

Producto(s):: Foglight
7.1.0, 6.3.0, 6.1.0, 6.0.0, 5.9.8, 5.9.7, 5.9.5, 5.9.4, 5.9.3, 5.9.2, 5.7.5; Foglight for Databases
7.1.0, 6.3.0, 6.1.0, 6.0.0, 5.9.7, 5.9.5, 5.9.4, 5.9.3, 5.9.2

Tema(s):: Troubleshooting

Historial del artículo:: Creado el: 11/28/2014
Última actualización: 12/14/2023

Buscar todos los artículos

Seleccione su producto:

Con el fin de ofrecerle un mejor servicio, complete el campo Motivo del chat:

Soluciones recomendadas para su problema

"No data was found for registration ID" error in DB2 or Oracle agent logs (4310557)

Título

Descripción

Causa

Resolución

Leave a Comment