Page tree

This topic provides information about upgrading and performing post installation tasks for BMC PATROL for Oracle.

Preparing to upgrade and migrate

No matter what method you use for upgrading and migrating customizations, you must first perform the following tasks:

  • back up PATROL_HOME and PATROL_CACHE
  • remove PATROL for Oracle files from PATROL_CACHE

Note

Throughout this section, all references to PATROL_HOME represent $PATROL_HOME in UNIX and %PATROL_HOME% in Windows; all references to PATROL_CACHE represent $HOME/patrol in UNIX and %PATROL_CACHE% in Windows.

To back up the current installation

  1. Shut down any PATROL Agents, consoles, and related services that are currently running.
  2. Ensure that no one is accessing any PATROL files or directories.
  3. Perform a full backup of the following two directories where PATROL executables and data are typically stored:
    • PATROL_HOME for agent and console installation directories
    • PATROL_CACHE for the console working cache

To remove PATROL for Oracle files from PATROL_CACHE

Before you install, you must remove the current PATROL for Oracle files from the PATROL_CACHE directory for the console. If you do not, old product files in PATROL_CACHE are loaded instead of the newly installed files from PATROL_HOME

Remove all PATROL for Oracle files with the following naming patterns from PATROL_CACHE\knowledge and PATROL_CACHE\psl:

  • ORA*
  • OPS*

Note

If you are using History.km, do not delete ORACLE_history_loader.km.

Creating an installation package of the merged PATROL for Oracle

After you have migrated and merged your customizations, you must create an installation package that can be used with the installation utility.

To create an installation package of the merged PATROL for Oracle

  1. Copy the contents of the PATROL for Oracle CD to a hard drive on a server.
    This temporary directory can be deleted after you have successfully created an installable image.
  2.  Navigate to the packaged_results directory for the merged package and open the .ppf file. Note the file name that is listed in the first line of the .ppf file.
    For example, if pokckm/x.x.xx/030107-233044 is listed in the first line of the .ppf file, pokckm is the file name.
  3. Rename the packaged_results directory with the file name from the .ppf file in step 2.
  4. Copy the renamed directory to the Products directory of the PATROL for Oracle CD image that you copied onto the server. You are replacing the files there with the merged files that contain your customizations.
  5. Copy the PATROL for Oracle CD image to the target server from which you will be installing.

Post-upgrade task for existing instances

When you upgrade to the latest version of PATROL for Oracle, if your PATROL account was created by the SYS user, collectors go into the alarm state due to missing privileges. To prevent the collectors from going into the alarm state, create the Over The Top script. This script grants the necessary privileges to the PATROL account.

Before you begin

Before you create Over The Top script, you must have read, write, and execute permissions on the conf directory at the following location:

  • (Windows)*%PATROL_HOME%\oracle*
  • (UNIX)$PATROL_HOME/../oracle/

If you do not have the specified permissions or if you do not have the sufficient disk space to create the script, the product displays the following error message:

  • (Windows)
    Error in generating files at %PATROL_HOME%\oracle\ conf\OverTheTopFiles\< Agent-Port-Number >\ due to lack of disk space or directory permissions
  • (UNIX)
    Error in generating files at $PATROL_HOME/../oracle/ conf/OverTheTopFiles/< Agent-Port-Number >/ due to lack of disk space or directory permissions

To create Over The Top scripts for all SYS-configured instances that are enabled for monitoring

  1. Right-click the Oracle KM icon and choose KM Commands > Configuration > Create Over The Top Scripts.
    This command creates the following files:

    Operating system

    Files

    Windows

    • OverTheTopScript.bat
    • SysConfigSidList.txt
    • SqlGrantsScript.sql
    • ConfirmGrants.bat
    • Set_Environment.bat

    UNIX

    • OverTheTopScript.sh
    • SysConfigSidList.txt
    • SqlGrantsScript.sql

    Note

    BMC recommends that you do not modify the above files.

  2.        Log on to the PATROL Agent, and run the following script from the command prompt:
    On Windows:
    1. Enter the following command: 

      cd %PATROL_HOME%\oracle\conf\OverTheTopFiles\< Agent-Port-Number >\

      Note

      You must have write permission on the < Agent-Port-Number> directory.

    2. Enter the following command: OverTheTopScript.bat
    3. Press Enter.
      On UNIX:
    4. Enter the following command: 

      cd $PATROL_HOME/../oracle/conf/OverTheTopFiles/<Agent-Port-Number>/

      Note

      You must have write permission on the < Agent-Port-Number> directory.

    5. Enter the following command: ./OverTheTopScript.sh
    6. Press Enter.
      The script displays the following message:
      Setting Environment for Instance instanceName
      Do you really want to continue (y/n) :
  3.  Type Y or y or N or n on the following Do you really want to continue (y/n) : command prompt.
    If you type N or n, the script does not give the privileges to that instance. If you press Enter, the script defaults to Y and gives the privileges.
  4.  Enter the SYS user password.
  5. The script displays the next instance. Repeat step 3 to step 4 to execute the script for the next instance.

After you enter the SYS password in step 3, the following privileges are given to the PATROL account:

  • SELECT ON DBA_UNDO_EXTENTS
  • SELECT ON V_$RESOURCE_LIMIT
  • SELECT ON V_$ARCHIVE_DEST_STATUS
  • SELECT ON V_$RECOVERY_FILE_DEST (additional privilege only for an instance with Oracle version 10g or later)

If the instance is part of a RAC database, the SELECT ANY DICTIONARY privilege is revoked from the PATROL database monitoring user and the following RAC-specific privileges are granted to the user:

  • GV_$INSTANCE
  • GV_$SESSION
  • GV_$SESSION_WAIT
  • GV_$SESSTAT
  • GV_$LOCK

In addition, a log file, OverTheTopGrants.log, is created at the following location:

  • Windows )%PATROL_HOME%\oracle\conf\OverTheTopFiles* <Agent-Port-Number>*
  • (UNIX)$PATROL_HOME/../oracle/conf/OverTheTopFiles/ <Agent-Port-Number>/

This log file contains the information whether the script is executed for a particular instance. It also contains the history of operations performed during execution of the script.

  • No labels