Create an Account and Database
Use the following table to determine the type of account you need to set up to use the History Loader component with your RDBMS. For more information about setting up these accounts, see the documentation for your RDBMS.
Necessary RDBMS Accounts
RDBMS | Account |
|---|---|
DB2 | account for the DB2 computer instance that will own the history tables Must have DB2SYSADM authorization. |
Oracle Server | Oracle user account with a unique default tablespace
|
Microsoft SQL Server | login account with the ability to create and remove database objects |
Once you have set up the appropriate account for your RDBMS, you must create a database owned by that account. This database will be used to store history data.
Choosing a History Loader Type
After setting up the proper account and database, you must select the History Loader component type that corresponds to your RDBMS.
To choose a History Loader type for your RDBMS
- Access the host computer application class menu. For more information, see Accessing-KM-Commands-and-InfoBoxes.
- Choose the Patrol History menu command. The Enable/Disable History Loader dialog box is displayed.
- Verify that the Enable History Loader option is selected.
- From the Type list, select the name of your RDBMS. The Type list contains all of the supported RDBMSs on the History Loader computer.
- Click Accept.
- Complete the following steps on a DB2 database:
- Run the db2profile script, which is located in the install_dir/instance_name/sqllib directory to set the necessary environment variables.
- Start the PATROL Agent.
- Start your PATROL console and connect to the PATROL Agent.
- Verify that the appropriate History Loader icon for your RDBMS appears with the operating system application icons in the computer window. For a list of History Loader icons, see Application-Classes-and-Icons.
- It may take a few moments for PATROL to discover the instance that you selected. The instance will be in an offline state until it is configured.