EM13c : Can't resolve a non-optional query descriptor property [log_file_absolute] (alert_log_file)
(Doc ID 2249304.1)
Last updated on APRIL 06, 2023
Applies to:
Enterprise Manager for Oracle Database - Version 13.1.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
In Enterprise Manager (EM) 13c Cloud Control, alertLog metric collection fails.
Trying to run the Metric Collection manually fails as below:
emctl control agent runCollection <TARGET_NAME>:oracle_database alert_log_rollup_11g
Oracle Enterprise Manager Cloud Control 13c Release 1
Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
EMD runCollection error:
alert_log_rollup_11g:alertLog:Can't resolve a non-optional query descriptor property [log_file_absolute] (alert_log_file)
alertLog:Can't resolve a non-optional query descriptor property [log_file_absolute] (alert_log_file)
alertLogStatus:Can't resolve a non-optional query descriptor property [log_file_absolute] (alert_log_file)
Oracle Enterprise Manager Cloud Control 13c Release 1
Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
EMD runCollection error:
alert_log_rollup_11g:alertLog:Can't resolve a non-optional query descriptor property [log_file_absolute] (alert_log_file)
alertLog:Can't resolve a non-optional query descriptor property [log_file_absolute] (alert_log_file)
alertLogStatus:Can't resolve a non-optional query descriptor property [log_file_absolute] (alert_log_file)
Error stack observed from <AGENT_INST>/sysman/logemagent_perl.trc file:
alertlog.pl: 2017-01-31 04:03:05,901: WARN: isAlertLogFileTruncated: Old signature content and size not available.
alertlog.pl: 2017-01-31 04:03:05,902: INFO: Alert log file was truncated since previous metric collection.
alertlog.pl: 2017-01-31 04:03:06,692: INFO: isAlertLogFileTruncated: Alert log file was not truncated since previous metric collection.
alertlog.pl: 2017-01-31 04:03:07,101: INFO: isAlertLogFileTruncated: Alert log file was not truncated since previous metric collection.
alertlog.pl: 2017-01-31 04:03:07,501: INFO: isAlertLogFileTruncated: Alert log file was not truncated since previous metric collection.
alertlog.pl: 2017-01-31 04:03:07,924: INFO: isAlertLogFileTruncated: Alert log file was not truncated since previous metric collection.
alertlog.pl: 2017-01-31 04:03:08,390: INFO: isAlertLogFileTruncated: Alert log file was not truncated since previous metric collection.
alertlog.pl: 2017-01-31 04:03:05,902: INFO: Alert log file was truncated since previous metric collection.
alertlog.pl: 2017-01-31 04:03:06,692: INFO: isAlertLogFileTruncated: Alert log file was not truncated since previous metric collection.
alertlog.pl: 2017-01-31 04:03:07,101: INFO: isAlertLogFileTruncated: Alert log file was not truncated since previous metric collection.
alertlog.pl: 2017-01-31 04:03:07,501: INFO: isAlertLogFileTruncated: Alert log file was not truncated since previous metric collection.
alertlog.pl: 2017-01-31 04:03:07,924: INFO: isAlertLogFileTruncated: Alert log file was not truncated since previous metric collection.
alertlog.pl: 2017-01-31 04:03:08,390: INFO: isAlertLogFileTruncated: Alert log file was not truncated since previous metric collection.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |