EM 12c : Diagnostic Incidents Created "java.util.regex.PatternSyntaxException: Dangling meta character '*' near index 0 *"

(Doc ID 2183432.1)

Last updated on SEPTEMBER 23, 2016

Applies to:

Enterprise Manager for Oracle Database - Version and later
Information in this document applies to any platform.


Very frequently Diagnostic Incidents (Problem) are being generated for a particular database target in the EM Console with the following stack:

Incident Id: 3153
Incident Source: SYSTEM
Create Time: Wed Aug 17 15:08:25 EDT 2016
Problem Key: java.util.regex.PatternSyntaxException:java.util.regex.Pattern:1724::oracle.sysman.gcagent.target.interaction.execution.ExecuteTask:2870
ECID: bd8afd3e-f149-8f10-d561247a
Error Message Id: OFM-99999
Context Values
threadName : GC.Executor.1790236 (oracle_database:ORCL:adr_alert_log_rollup)
TARGET_ID : oracle_database.ORCL
METRIC_NAME : adrAlertLogIncidentError
Stack Trace
java.util.regex.PatternSyntaxException: Dangling meta character '*' near index 0
at java.util.regex.Pattern.error(Pattern.java:1724)
at java.util.regex.Pattern.sequence(Pattern.java:1889)
at java.util.regex.Pattern.expr(Pattern.java:1763)
at java.util.regex.Pattern.compile(Pattern.java:1471)
at java.util.regex.Pattern.<init>(Pattern.java:1144)
at java.util.regex.Pattern.compile(Pattern.java:834)
at oracle.sysman.gcagent.target.interaction.execution.ExecuteTask.fastCompute(ExecuteTask.java:2870)
at oracle.sysman.gcagent.target.interaction.execution.ExecuteTask.fastCompute(ExecuteTask.java:2913)
at oracle.sysman.gcagent.target.interaction.execution.ExecuteTask.check_condition(ExecuteTask.java:2770)
at oracle.sysman.gcagent.target.interaction.execution.ExecuteTask.check_Thresholds(ExecuteTask.java:2525)
at oracle.sysman.gcagent.target.interaction.execution.ExecuteTask.ProcessResultSet(ExecuteTask.java:2105)
at oracle.sysman.gcagent.target.interaction.execution.ExecuteTask.runTask(ExecuteTask.java:4209)

-  The diagnostic incident is created for the Agent target, monitoring this database.


For this database target, the thresholds for the metrics under the Incident and 'Operational Error' have been modified and some of them have the warning / critical thresholds set to the regular expression: *

By default, the metrics under the Incident and 'Operational Error' collections have critical threshold set to the regular expression: .*


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