Verifying installation requirements
Support for third-party products
To receive full support for a BMC product, you must have that product installed in a supported environment, as specified in the BMC product documentation. If a third-party vendor cancels support for one of its products (such as an operating system or subsystem), and that third-party product integrates or interacts with the BMC product you have licensed, you must upgrade to a supported version of that third-party product before BMC Customer Support can provide you with support for the affected BMC product. For further information, see
BMC's product support policy.
Verify that the target computer meets the requirements listed in the following table.
Note
To get complete compatibility information for BMC PATROL for Oracle Database, use the BMC Solution and Product Availability and Compatibility Utility on the Product Availability and Compatibility page.
Any information about UNIX ® in the following table applies to any supported versions of Linux ® unless otherwise specified.
System requirements for installing PATROL for Oracle Database
| Resource | Requirements | Comments |
|---|---|---|
| PATROL Agent and consoles | A PATROL Agent and one or more of the following consoles:
| PATROL Central consoles are not required, but a PATROL Agent is required for each monitored instance. |
| Supported Oracle databases |
| |
| OS accounts on Windows | If you are installing on Microsoft Windows, a PATROL Windows account | Use the following guidelines when setting up the PATROL Windows account:
|
| OS accounts on UNIX | If you are installing on UNIX, a PATROL UNIX account | Use the following guidelines when setting up the PATROL UNIX account:
|
| Oracle account | PATROL account for Oracle | Use one of the following accounts for the configuration process:
For more information, see Configuring instances for monitoring. |
| Other optional PATROL products |
| Distribution Server is required only if you plan to use it to distribute the KM. |
| The PATROL Configuration Manager and the PATROL KM for Event Management are required if you plan to modify PATROL for Oracle Database. See Using PATROL Configuration Manager to modify and migrate configuration | |
| Security | PATROL for Oracle Database operates in all PATROL security levels. | For more information about security, see Reviewing PATROL security. For information about installing with a firewall, see Firewall and port-forwarding considerations. |
| Ports | The installation utility might require you to specify the port number for agents | The default port number for agents is 3181. |
| Disk space needed to install | The following disk space is needed to install PATROL for Oracle Database on agents and console:
| These numbers are approximate and assume that you are installing PATROL for Oracle. |
| Disk space used after installation | The following disk space is needed to operate PATROL for Oracle Database on agents and console:
| These numbers are approximate and assume you are operating PATROL for Oracle Database. |
| Oracle database objects | Requires 10-15 MB available in the default tablespace and the default temporary tablespace. | For more information, see Configuring instances for monitoring. |
| Oracle database modes | If a database is in restricted mode, you must configure PATROL to monitor the database. | For more information, see Configuring instances for remote monitoring. |
| Other settings | SQL Snapshot CPU data retrieval | TIMED_STATISTICS = TRUE |
| Monitoring high CPU users | TIMED_STATISTICS = TRUE | |
| USRCpuSeconds parameter | TIMED_STATISTICS = TRUE | |
| PQO parameter settings | To monitor a parallel query option (PQO) environment, you must set the PQO parameters in the initialization file (init.ora) for a PQO environment. (The name of the init.ora file can vary. See initialization file.) | |
| MTS or shared server parameter settings | To monitor a multithreaded server (MTS) or shared server environment, you must set the MTS or shared server parameters in the init.ora file for a shared server environment. | |
| TNS_ADMIN | If the file is not in the default location, specify the location of the tnsname.ora file. The TNS_ADMIN environment variable is used to explicitly define the directory location for Oracle Net to resolve where to find its configuration files. TNS_ADMIN overrides the default Oracle Net location. For example, if TNS_ADMIN is set to ORACLE_HOME\test\admin, Oracle Net looks for its configuration files in ORACLE_HOME\test\admin to make a database connection or start other Oracle Networking products such as the Listener, Connection Manager, Names Server, and so on. PATROL for Oracle Database is unable to discover the listener if the value of the TNS_ADMIN environment variable contains ORACLE_HOME. | |
| $ORACLE_BASE environment variable | If you are using $ORACLE_BASE for the diagnostic_dest parameter, you must first set the $ORACLE_BASE environment variable to the appropriate value and then start the PATROL Agent. To resolve the actual value of the $ORACLE_BASE environment variable, set the path in the /OracleConfig.InstanceName.OracleBase pconfig variable to the correct ORACLE_BASE. Note This pconfig variable and environment variable setting is applicable only when diagnostic_dest = $ORACLE_BASE is set in the init.ora file. |
Note
BMC products are certified for use on supported operating system versions. BMC does not explicitly test for OS patches/updates that are released after a BMC product is released.
BMC products should work fine with minor updates to these supported operating systems. For assistance, please contact BMC Customer Support.
Comments
Log in or register to comment.