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.

Configuring an ASM instance


The following section helps you to configure an Automatic Storage Management (ASM) instance for monitoring: 

Note

  • The ASM monitoring feature of BMC PATROL for Oracle does not support auto configuration, but you can configure the ASM instance using the PCM rule sets method. 
  • Batch configuration is also supported besides the rule set. For more information, see PATROL Configuration Manager rule sets for Oracle_ASM KM
  • You can also configure by using BMC ProactiveNet Performance Management Central Monitoring Administration console. For more information, click here.
  • Make sure the account used for configuring an ASM instance has SYS or has SYSASM privileges.

To configure an ASM instance

Click to view a short video on how to configure an Oracle ASM instance for monitoring in a PATROL environment.

icon-play.png https://youtu.be/Wf4kPTtd0Bk

Note

Verify that the PATROL console user has the privilege to execute SQL*Plus commands.

  1. Choose the ORACLE_ASM > ASM Instance Configure menu command from the host.
     The ASM Instance Configure dialog box appears.
  2. In the ASM Instance name field, enter the ASM instance name with a "+" prefix.
  3. In the ASM Home field, type the name of the ASM instance home directory.
  4. In the Username field, type the user name:
    • Choose one of the following methods to enter the user name:
      • Keep the user name as SYS.
      • Enter an existing NON SYS user with SYSASM privileges.
      • Keep the user name as NON- SYS and select the Create ASM Monitoring Account check box to create a new user with SYSASM privilege.
  5. In the Password field, type the password for the user.

    Note

    Do not append 'as sysdba*'* or 'as sysasm*'* to the password.

    If the database user password contains special characters, specify the password within the double quotes. Example: “%BMC$"

  6. Click Apply.
     If you selected Create ASM Monitoring Account check box for the SYS user on Oracle database 11 g version, the ASM Instance Configure dialog box appears. For more information about ASM Instance Configure dialog box, see To monitor an ASM Instance for Oracle 11g or later
  7. Click Exit.

To monitor an ASM Instance for Oracle 11g or later

  1. In the Username field, type the ASM database monitoring user to be created with SYSASM privilege.
  2. In the Password field, type the password.

    Note

    If Username already exists in the ASM instance, the password associated with the user name is changed to the one that you type in the Password field.

  3. Click Apply.
  4. Click Exit.

Batch Configuration for ASM instance

You can perform the batch configuration by creating a text file outside Oracle KM, or by using Global configuration from CMA.

The following describes how to perform batch configuration:

Batch configuration uses a configuration file that you can create outside of PATROL, after this file has been created, The discovery scans for the configuration file. After it finds the file, it automatically starts the configuration process, using the information in the configuration file.

The configuration file contains the settings for all the instances that you want to configure. When discovery process runs, all the instances defined in the configuration file are configured at one time.

You can create a file as the following:

  • create a text file in a text editor, using the ASM_batch_conf_sample.wri file as a template

To create a batch configuration file from OS prompt:

  1. Open the ASM_batch_conf_sample.wri file, from the $PATROL_HOME/../oracle/conf directory for UNIX and the %PATROL_HOME%\oracle\conf directory for Microsoft Windows.
  2. Edit the SID and the keyword values to reflect the instances you want to configure.
  3. Save the file as ASM_batch_conf<port_number>.txt, in a text only format.

Note

You can add any number of instances. Each instance has its own configuration data.

The discovery searches for this file, and when found, starts processing the file to configure the instances on that PATROL agent port. The file name is changed to ASM_batch_conf<port_number>.done when processing is completed.

Note

It is recommended to clear the text as it contains password.

 

To check if there is an error or success, you can check the following log files that exists on $PATROL_HOME/../oracle/conf directory for UNIX and the %PATROL_HOME%\oracle\conf directory for Microsoft Windows:

ASMBatchConfig<port_number>.log

ASMConfig<port_number>.log 

info

You can also perform the batch configuration in CMA. Click to see more on Oracle-ASM-Global-Configuration.

PCM configuration for ASM instance

You have an option to configure instance using PCM.(Patrol Configuration Management)

The product creates the ASMConfig.cfg file at the $PATROL_HOME/../oracle/rulesets directory for UNIX and the %PATROL_HOME%\oracle\rulesets directory for Microsoft Windows.

When you apply the rule set to the configured Agent, the Agent automatically configures all the instances for which the rule sets have been created.

For the details of the configuration, you can see the ASMConfig{Agentport-no}.log file that is created at the $PATROL_HOME/../oracle/conf directory for UNIX and the %PATROL_HOME%\oracle\conf directory for Microsoft Windows.

Note

You can add any number of instances. Each instance has its own configuration data.

Related topics

Monitoring-ASM-instances

Solving-RAC-ASM-and-DataGuard-configuration-failure

 

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