Systems Insight Manager 6.2 Installation and Configuration Guide for MS Windows

The database information of the existing HP Systems Insight Manager install is pre-populated. All

information except for the user account cannot be edited. Provide the correct password for the existing

account or provide the credentials for another user account with administrative rights and database

access. The installation tests for the administrative rights. Click Next to proceed.

• Use SQL/SQL Express. This option is applicable if you have SQL Server 2008 or SQL Server

2005 Express Edition SP3 installed and you want to configure HP Systems Insight Manager to use

it.

• Use Oracle. This option is applicable if you have Oracle installed and you want to configure HP

Systems Insight Manager to use it.

Procedure 6-2 Using Oracle

1. From the Database Configuration window, select Use Oracle. Before using the database

you must ensure the database:

• Uses Unicode character set of AL32UTF8 and national character set of AL16UTF16.

• The NLS Length is set to BYTE.

• Has an Oracle user with Database Administrator (DBA) privileges created for the exclusive

use by HP Systems Insight Manager.

• The Oracle database schema is empty. HP Systems Insight Manager must be installed

in an empty Oracle database schema.

• The thin client .jar (ojdbc14.jar) is copied to the system at C:\oracle\ora92\jdbc\lib,

and the location specified during installation.

2. In the Password field, enter the password for the user name specified.

3. In the JarFile field, enter the full path to theojdbc14.jarfile or click Browse and navigate

to the correct location, typically C:\oracle\ora92\jdbc\lib. This path must be accessible

through the file system on the CMS. The installation copies the file to the correct location.

4. Click Next. The Select Installation Type window appears.

NOTE: If an Vulnerability and Patch Manager.full.name; (Vulnerability and Patch Manager)

MSDE database exists (within the HP Systems Insight Manager database instance or located

on a database instance created by Vulnerability and Patch Manager), it is upgraded to SQL