Set up the Oracle monitoring environment

This task describes how to set up the monitor environment before monitoring an Oracle Database server using the native LoadRunner Professional monitor.


  • If a problem occurs in setting up the Oracle environment, check the Oracle server to view the error messages.

  • The Oracle API call (olog() function) may fail when monitoring Oracle Database 12c or 19c. For a possible workaround, see this Oracle Communities discussion.

  1. Prerequisites

    • Ensure that the Oracle client libraries are installed on the Controller machine.

    • Verify that %OracleHome%\bin is included in the path environment variable. If it is not, add it.

    • Ensure that the registries are updated for the version of Oracle that you are using and that they have the following key: HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE

    • Verify that the Oracle server you want to monitor is up and running. Note that it is possible to monitor several Oracle Database servers concurrently.

    • Note: Only the 32-bit version of Oracle client should be installed on the Controller machine running the Oracle monitor.

  2. Configure the Oracle client/server connection

    Set the connection parameters so the Oracle client (Controller machine) can communicate with the Oracle server(s) you plan to monitor.

    On the Controller machine, set the following configuration parameter either by editing the tnsnames.ora file in a text editor, or using the Oracle service configuration tool (for example, Start > Programs > Oracle for Windows NT > Oracle Net8 Easy Config):

    • a new service name (TNS name) for the Oracle instance

    • TCP protocol

    • the host name (name of monitored server machine)

    • the port number (usually 1521)

    • the database SID (the default SID is ORCL)

    The following is an example of the contents of a tsnames.ora file:


       (ADDRESS = (PROTOCOL = TCP)(HOST = night)(PORT = 1521))
       (SID = ORCL)
  3. Connect to the monitored server machine and verify the connection

    1. Obtain a username and password for the service from your database administrator, and ensure that Controller has database administrator privileges for the Oracle V$ tables (V$SESSTAT, V$SYSSTAT, V$STATNAME, V$INSTANCE, V$SESSION).

    2. Verify connection with the Oracle server by performing tns ping from the Controller machine.

    3. Note: There may be a problem connecting if the Oracle server is behind a DMZ/firewall that limits its communication to application servers accessing it.

    4. Run SQL*Plus from Controller and attempt to log in to the Oracle server(s) with the desired username/password/server combination.

    5. Type SELECT * FROM V$SYSSTAT to verify that you can view the V$SYSSTAT table on the Oracle server. Use similar queries to verify that you can view the V$SESSTAT, V$SESSION, V$INSTANCE, V$STATNAME, and V$PROCESS tables on the server.

  4. Modify the monitoring sample rate (optional)

    To change the length of each monitoring sample (in seconds), edit the dat\monitors\vmon.cfg file in the LoadRunner Professional root folder. The default rate is 10 seconds.

    The minimum sampling rate for the Oracle Monitor is 10 seconds. If you set the sampling rate at less than 10 seconds, the Oracle Monitor continues to monitor at 10 second intervals.

  5. Configure the Oracle monitor from Controller

    For task details (beginning with step 2), see Configure monitors.

Back to top