OC4J Targets Goes Into Metric Collection Error "Response metric failed to run on schedule - likely due to validIf" (Doc ID 1604759.1)

Last updated on SEPTEMBER 03, 2021

Applies to:

Symptoms

In Cloud Control 12c R3 Oracle Application Server Target OC4J  goes to metric collection errors after blackout.

gcagent.log

2013-11-26 09:01:06,840 [13523:6D5A2983] WARN - Found a row with more columns than declared for the metric for TargetID = oif.test.<DOMAIN>_BC4J, Metric = Response
Row = *** row contents suppressed ***
2013-11-26 09:01:12,820 [8463:2311CBDF:GC.SysExecutor.36 (CollectionManager.ResponseChecker)] WARN - Response metric for target oc4j.oif.test.<DOMAIN>_home being placed in metric collection error due to Response metric failed to run on schedule - likely due to validIf
2013-11-26 09:01:12,821 [8463:2311CBDF] WARN - Response metric for target oc4j.oif.test.<DOMAIN>_OC4J_FED being placed in metric collection error due to Response metric failed to run on schedule - likely due to validIf
2013-11-26 09:01:12,822 [8463:2311CBDF] WARN - Response metric for target oracle_apache.oif.test.<DOMAIN>_HTTP Server being placed in metric collection error due to Response metric failed to run on schedule - likely due to validIf
2013-11-26 09:01:32,080 [8460:8670C8F9:GC.SysExecutor.34 (Ping OMS)] INFO - attempting another heartbeat

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.