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 |
Upgrading
Before you begin
It is recommended to back up PATROL_HOME and PATROL_CACHE directories. This is recommended in case you need to revert to an earlier version of the PATROL for Oracle Database.
- Ensure that no one is accessing the KM related PATROL files or directories.
- 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
- If you upgrade from an older version to 9.7.11.xx fix pack, you must login to the Oracle Database as a privileged user and grant the following privilege to the monitoring user.
grant select on dba_tablespace_usage_metrics to <Oracle monitoring user>
To upgrade the PATROL for Oracle Database in a PATROL environment
- Stop the PATROL Agent, the PATROL consoles, and any related services that are currently running
- Follow the typical installation instructions in Installing in a PATROL environment.
- Follow the instructions for post-upgrade task for existing instances.
To upgrade the PATROL for Oracle Database in a TrueSight environment
- Follow the process outlined in Installing using a TrueSight console.
- Follow the instructions for post-upgrade task for existing instances.
Post-upgrade task for existing instances
In case of remote monitoring, there is a need to modify Pconfig entry (if exists) "/OraNetConfig.javaHome". The new value must not contain the bin dir.
For example: /data/java/bin = /data/java
Restart the PATROL agent after changing this entry.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*