HP Systems Insight Manager 6.3 Installation and Configuration Guide for Microsoft Windows

Procedure 10 Use SQL or SQL Express
1. From the Database Configuration window, select Use SQL/SQL Express.
2. In the Username field, the installing user account appears and can be edited. The
account specified must be the user name for the database server.
3. In the Password field, enter the password for the database server.
HP Systems Insight Manager does not support the following in a user name and
password:
A blank password
A space followed by a double-quote
A backslash (\)
If you use these characters in your user name or password, the HP Systems
Insight Manager database initialization fails.
4. In the Domain and Host fields, enter the domain name for the database server.
5. Click Next. The Select Installation Type window appears.
Use Oracle. This option is applicable if you have Oracle installed and you want to
configure HP Systems Insight Manager to use it.
Procedure 11 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 HP Insight Vulnerability and Patch Manager software (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 Express. If the Vulnerability and Patch
Manager database upgrade fails, a message displays indicating Failed to Upgrade
Vulnerability and Patch Manager Database to SQL Express, but the HP Systems
Insight Manager installation continues.
44 Upgrading HP Systems Insight Manager