Writer instructions

Page title

For most spaces, this page must be titled Space announcements.

For spaces with localized content, this page must be titled Space announcements l10n.

Purpose

Provide an announcement banner on every page of your space.

Location

Move this page outside of your home branch.

Guidelines

Announcement Support for this product will end on December 22, 2025. To monitor Oracle databases, we recommend that you use PATROL for Oracle Enterprise Database.

Agent configuration variables


The following table lists and describes variables that are set in the PATROL Agent for PATROL for Oracle. Use the agent configuration utility to view these variables. Some variables are created for internal use only. These variables are used by PATROL for Oracle and alteration of these variables harms the operation of PATROL for Oracle.

Warning

Do not change variables that are designated For internal use only; do not modify or delete. Modification or deletion of these variables harms the operation of PATROL for Oracle.

When changing variables, follow these guidelines:

  • Make sure that you are aware of the implications before changing a variable.
  • Create a record of the original setting for a variable before you change it.
  • If you use the PATROL Configuration Manager to change variables, make sure that the Backup Agents Before Apply option remains selected.

For more information, see Using PATROL Configuration Manager to modify and migrate configuration and the PATROL Configuration Manager User Guide.

Note

From PATROL for Oracle version 9.1.00 and 9.1.10, all pconfig variables for which each string was separated by a new line will be separated by the pipe character (|) and for Oracle versions 9.5.00 onwards, all pconfig variables for which each string was separated by a new line be separated by the comma (,).

  

 pconfig variables set by PATROL for Oracle

Note

The ANYINST designation allows you to apply these changes to any instance without adding specific instance name.


Values for these variables are selected by users in the Users Excluded dialog box. You can change this variable by using the Exclusion > User Exclusion menu command in the AVAILABILITY menu.

The Tablespace can be excluded according to few strategies TS Names, RegEx to filter TS names, according to TS types.

The default categories are AVAILABILITY and COLLECTORS. You can select some or none of the other categories by using Configuration > Advanced > Instance Configuration from the ORACLE menu.

You can change this variable by selecting Configuration > Advanced > Monitoring Enable/Disable from the ORACLE menu.

Warning

If you update this variable with PATROL Configuration Manager, you must reinitialize the agent.

Also, if the variable does not exist, failover monitoring is not active for the instance. You can change this variable by selecting the Failover Monitoring > Configure menu command from the ORACLE_INSTANCE menu, filling in all fields, and clicking Accept.

You can change this variable by using the User Monitoring > Problem User Settings menu command from a USERS instance menu.

For example, if you set a blackout period on a server called Oracle1 for Monday, starting at 1:00 a.m., and lasting for 60 minutes, the following value would display for this variable:

Oracle1 Monday 3600 60

See also Modifying the blackout configuration variable.

Warning

Blackout periods set by using PATROL Configuration Manager are not verified.

You can change this variable by using the Debug command from the ORACLE menu.

You can change this variable by using the Debug command from the ORACLE menu.

This pconfig variable must be created and set with an appropriate Oracle hint only when you have performance issues for the LockConflicts parameter.

Default value: 0

Default value: 0

 
Because PATROL for Oracle ® connects directly to your production databases, BMC recommends that communication between tiers of the product, especially if any tier lies outside your internal network, be handled through virtual private networking (VPN) connections for the strongest security. This appendix provides information about setting up those communications in your environment.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*