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.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Operations Connector10.11

Administer > Policies > Database Policies > Troubleshooting Database Policies

Troubleshooting Database Policies

This section describes troubleshooting and limitations when working with Database policies.

General troubleshooting guidelines

To start troubleshooting, check the Operations Agent log fileslog files of the agent in the %OvDataDir%log directory (Windows systems) or the /var/opt/OV/log directory (Linux systems).
To investigate issues related to policy execution, first examine the %OvDataDir%log\System.txt file (Windows systems) or the /var/opt/OV/log/System.txt file (Linux systems).

The log files whose names start with the opr- prefix are generated by the OMi web console.

REST Web service listener policy file rollingDatabase policy file rolling

A database policy reads the following XML file:

Windows: %OvDataDir%\tmp\<policyID>.xml

Linux: /var/opt/OV/tmp/<policyID>.xml

The file contains the results of the Operations Connector database queries in an XML file format that database policies can evaluate. The file exists only for policies that integrate events.

To prevent the file from becoming too large, a new version of the file is created when its size reaches 100000 KB. The original file is renamed and stored as a backup file. By default, up to three backup files can be created.

When the XML file rolls, that is, a new version is created, but the policy has not completed reading all entries, the unread entries are lost and no events are created.

The following defaults are set:

Maximum file size: 100000 KB

If not all expected events arrive in OMi, increase the maximum file size to 1000000 KB.
Maximum number of backup files: 3

To change the defaults:

Open the following file:

<Operations Connector root directory>/groups/master.config
Change the following values as required:

_eventRollingMaxFileSizeInKB=100000

_eventRollingMaxBackup=3
Restart ovc:

ovc -restart

Metrics troubleshooting

See "Topology Troubleshooting" on page 1 for more information on troubleshooting and limitations when Operations Connector is enabled to report CIs and CIs relationships topology to OMi.

Send Help Center feedback