Configuring History Loader in a PATROL environment

Configure the History Loader component for your RDBMS. History Loader configuration is different for each RDBMS, so read the appropriate section for your RDBMS.

Configuring DB2 History Loaders

You must configure each History Loader to receive PATROL history data. This task must be performed on each DB2 History Loader computer.

Before you begin

You must have performed the steps documented in the Create an Account and Database topic.

To Configure DB2 History Loader

1. Access the DB2 History Loader application class menu. For more information, see Accessing KM Commands and InfoBoxes.
2. Choose the Configure menu command. 
   The Configure DB2 History Loader dialog box is displayed as shown below.
   
3. Enter the following information:

   • DB2 computer instance name

     The DB2 home directory must contain the DB2 executable files. For example, if opt/ibm/db2/V10.5 is your home directoy, V10.5 folder must contain DB2 executable files.

   • DB2 database name

   • user name of the database server

   • password of the database server

4. Click Accept.

5. Reinitialize your connection to the PATROL Agent to reflect the configuration changes you made.

6. Right-click on your History Loader instance and run the Create Database Objects knowledge module command.

Configuring Microsoft SQL Server History Loaders

You must configure each History Loader to receive PATROL history data. This task must be performed for each Microsoft SQL Server History Loader computer.

Before you begin

You must have performed the steps documented in the Create an Account and Database topic.

To Configure MS SQL Server History Loader

1. Access the Microsoft SQL Server History Loader application class menu. For more information, see Accessing KM Commands and InfoBoxes.
2. Access the Microsoft SQL Server History Loader application class menu and choose the Configure menu command.
3. The Configure MSSQL History Loader dialog box is displayed as shown below.
   
4. Enter the following information:

   • MSSQLSERVER home directory

     Note

     The MSSQLSERVER home directory must contain OSQL.exe and sqlldr.exe files. For example, if C:\Program Files\Microsoft SQL Server\100\Tools is your home directoy, Tools folder must contain OSQL.exe and sqlldr.exe executable files.

   • Server name

   • Database name

   • user name of the database server

   • password of the database server

5. Click Accept.

6. Reinitialize your connection to the PATROL Agent to reflect the configuration changes you made.

7. Right-click on your History Loader instance and run the Create Database Objects knowledge module command.  

Configuring Oracle Server History Loaders 

You must configure each History Loader to receive PATROL history data. This task must be performed for each Oracle Server History Loader computer.

Before you begin

You must have performed the steps documented in the Create an Account and Database topic.

To Configure Oracle History Loader

1. Access the Oracle Server History Loader application class menu. For more information, see Accessing KM Commands and InfoBoxes.
2. Access the Oracle Server History Loader application class menu and choose the Configure menu command.
   The Configure Oracle History Loader dialog box is displayed as shown below.
   
3. Enter the following information:
   

   • ORACLE_HOME

     The Oracle home directory must contain the sqlplus executable files. For example, if home/app/oracle/product/12.1.0/dbhome_1 is your home directoy, dbhome_1 folder must contain the sqlplus executable files.

   • ORACLE_SID

   • user name of the database server

   • password of the database server

4. Click Accept.
5. Reinitialize your connection to the PATROL Agent to reflect the configuration changes you made.
6. Right-click on your History Loader instance and run the Create Database Objects knowledge module command.

Setting the PATROL HL KM to use remote database instance (Oracle only)

Before you begin

Ensure the following prerequisites are met on the host that is running PATROL Agent.

• Oracle instant client-sqlplus must be installed. The version of the Oracle instant client-sqlplus must be same as the monitored Oracle database.
• Oracle instant client-basic must be installed. The version of the Oracle instant client-basic must be same as the monitored Oracle database.
• Perform custom installation of Oracle database and install sqlldr.

The custom installation is required to get the sqlldr and message files on the same location of Oracle instant client.

To Set the TNS entry of the monitored Oracle database

1. In the PATROL admin home directory, create tnsname.ora file.

2. Add the following settings to the user environment (by using .profile, .bashrc, .kshrc):

   TNS_ADMIN=<path of home directory>
   export TNS_ADMIN
   TWO_TASK=<SID name on targeted database>
   export TWO_TASK
   ORACLE_HOME=<Oracle tools install on the local host of PATROL agent>
   export ORACLE_HOME
   ORACLE_LIB=$ORACLE_HOME/lib
   export ORACLE_LIB

3. Perform the following tests on the PATROL Agent host to verify if the set up is working as expected:
   • $ sqlplus <DBUSER>/<DBPASSWORD>@<ORACLE SID>
     Connected to the database on the remote host message implies the set up is completed successfully. 
   • $ sqlldr
     Control= message prompt implies the set up is completed successfully. 

From this step onwards, the KM configuration is same as the local installation of Oracle database. Follow the steps described in Configuring Oracle Server History Loaders to complete the KM configuration.

Selecting the Rollback Segment (Oracle Only)

You can specify the rollback segment for the Oracle History Loader database. Specifying the rollback segment is useful when you need more space for loading history data. This task is optional.

To Select the Rollback Segment

1. Access the Oracle Server History Loader application class menu. For more information, see Accessing KM Commands and InfoBoxes.
2. Choose the Utilities > Rollback Segment menu command.

The Rollback Selection dialog box is displayed.

1. Enter the rollback segment name.
2. Click OK.