Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Words and Phrases
| Search for | Example | Results |
|---|---|---|
| A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
|
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Using Boolean Operators
| Search for | Operator | Example |
|---|---|---|
|
Two or more words in the same topic |
|
|
| Either word in a topic |
|
|
| Topics that do not contain a specific word or phrase |
|
|
| Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
| A combination of search types | ( ) parentheses |
|
Known Issues and Workarounds
Events from Cloud Control 12c are forwarded with a delay
Symptom
When Ops Connector for OEM is integrated with OEM Cloud Control 12c to collect events (alerts), these events reach Operations Connector with a noticeable delay.
Action
To resolve or alleviate the problem, log on to your Oracle Enterprise Manager Console, enable the Retry option in the Ops Connector for OEM configuration, and then set the expiration time to 1 hour. See the corresponding step in Setting Up Actions for Cloud Control 12c topic.
Metric output file contains strings ############## instead of actual values
Symptom
Identification of the root cause for missing metric values in OMi reveals the ############## strings in the output file instead of actual metric values. If logging of local metric records is enabled in the Operations Connector policy for OEM metrics, inspection of the Operations Connector's <OvDataDir>/log/OpC/opcmsglg file reveals there are related errors logged in it.
Action
The symptom indicates that the number of digits in some acquired metric values exceeds the preconfigured limit. Ops Connector for OEM by default allows up to 15 digits in whole parts of numbers that represent metric values. You can change this limit.
To increase the number of digits allowed in a metric value, proceed as follows:
-
Locate the applicable SQL query file. For more information, see Metric Integration SQL Query topic.
-
Open the SQL query file in a plain text editor.
-
To increase the number of the allowed digits in the whole part of the number to 20, change the line
to_char(em_metric_value_access(v.met_values, c.column_index), \
'999999999999990.99') AS metric_valueto
to_char(em_metric_value_access(v.met_values, c.column_index), \
'99999999999999999990.99') AS metric_valueTo allow more digits, add more
9characters to the99999999999999999990.99string in the same line. - Save the change.
Some expected metrics are not present in the metric output file
Symptom
Inspection of the metric output file for identifying the root cause of missing metric values in OMi reveals the metrics are also missing in the output file.
Action
The SQL query that Ops Connector for OEM uses does not collect all metrics that are available in OEM. The root cause might be a metric collection interval that is too small for your OEM-managed environment.
To increase the predefined metric collection interval, proceed as follows:
-
Open the metric database policy based on the OEM version.
-
In the
sourcesubsection, increase the value of thepolling intervaloption. It defines the time period (in seconds) of the intervals at which data is acquired from the OEM database. -
Save the change.
-
Restart the metric integration as described in Restarting the Services topic.
Before Contacting Software Support
If you cannot solve your issue, report it. Before contacting Software Support, ensure that:
-
You have performed the general checks. See General Troubleshooting Guidelines topic.
-
You have verified your problem is not described in this topic. See Known Issues and Workarounds topic.
-
You have collected relevant data that might be required to send to Software Support: a description of your problem, characteristics of your environment, related entries logged in the operating system event log or in the Ops Connector for OEM log files.
Software Support personnel will then provide you with further instructions. Among other things, you may be asked to change the Ops Connector for OEM logging severity level, to repeat or perform particular operations in your Ops Connector for OEM environment, and to collect specific data from your system and send them to Software Support.
To contact Software Support, see the web site at https://softwaresupport.softwaregrp.com.
Related topics
Setting Actions for OEM Cloud Control 12c or 13c
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to ovdoc-asm@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: