Last updated on MAY 16, 2014
Applies to:Enterprise Manager for Oracle Database - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 12.1]
Information in this document applies to any platform.
Certain security violations are reported as non-compliant in Enterprise Manager 12c Cloud Control. But other security violations (which are expected) are not flagged as non-compliant.
- The template "Oracle Certified-Enable Database Security Configuration Metrics" has been applied to the database from Enterprise/Monitoring/Monitoring Templates
- The "Basic Security Configuration for Oracle Database" compliance standard has been associated to the database.
When running the metric collections which collect the underlying data for the security compliances manually, it can be seen that oracle_security is able to collect and upload successfully. However oracle_security_inst gives the following error:-
[oracle@machine1 ~]$ emctl control agent runCollection orcl:oracle_database oracle_security_inst
Oracle Enterprise Manager Cloud Control 12c Release 3
Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved.
EMD runCollection error:
oracle_security_inst:Could not send some or all data over to repository: Failed to upload file: uploadXMLFiles skipped :: OMS version not checked yet. If this issue persists check trace files for ping to OMS related errors. (TIMEOUT)
Use the following syntax to run the collections manually
emctl control agent runCollection <dbname>:oracle_database oracle_security
emctl control agent runCollection <dbname>:oracle_database oracle_security_inst
The .../gc_inst/em/EMGC_OMS1/sysman/log/emoms.log contains a similar error message:
2014-01-14 14:42:41,397 [44459:GC.OnDemand.6 (oracle_database:orcl:Real-time collection oracle_security_inst)] ERROR - Collection item result upload failure oracle_database.orcl::oracle_security_inst
oracle.sysman.gcagent.target.interaction.execution.RTMUploadOnDemand$UploadOnDemandException: Could not send some or all data over to repository: Failed to upload file: xferFile failed with INVALID_CONFIG (TIMEOUT)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms