To use a relational database, you must create a database instance at the relational database server and create services at the relational database client. For details about how to create these items, see the documentation for the Oracle database you are using.

(a) Settings in the relational database server

Create a database instance at the relational database server. To do this, use Oracle Database Configuration Assistant.

(b) Settings in the relational database client

Create services at the relational database client. To do this, use one of the following programs:

For Oracle8i

Oracle Net8 Assistant

For Oracle9i

Oracle Net Manager

Specify each service name in the following format:

NETM_connection-destination-server-name

The connection destination server means the PC where the JP1/Software Distribution Manager server is installed. Note that the connection destination server name must not include the DNS name.

Example

When the connection destination server name is dmp380.Hitachi.co.us, the service name is:

NETM_dmp380

If an IP address, not a host name, is specified as the Software Distribution server for the connection destination specified in the Software Distribution Logon dialog box of Remote Installation Manager, you must also specify the IP address in connection-destination-server-name. When you specify the IP address, replace dots (.) with underscores (_).

Example

When the connection destination server name is 172.18.22.31, the server name becomes:

NETM_172_18_22_31

The following shows the parameters that require tuning and describes how to tune them.

(a) Parameters requiring tuning

db_block_buffers

This parameter specifies the number of database blocks. The value of this parameter controls the size of the data cache. The size of the data cache actually allocated is db_block_size x db_block_buffers.

shared_pool_size

This parameter specifies the size of the shared pool in bytes. The shared pool stores Oracle's management information (such as the library cache for SQL code analysis results and the dictionary cache).

processes

This parameter specifies the maximum number of users that can be connected at one time. The following shows the formula for determining the maximum number of simultaneous user connections required by JP1/Software Distribution:

Number of concurrent connections

= 25

+ number of concurrent Remote Installation Manager connections x 5

+ number of concurrent Packager connections x 2

+ number of concurrent client or relay system connections x 2

+ number of concurrent connections from HP NNM x 5

(b) Tuning method

db_block_buffers

This parameter indicates an estimated value for allocation. While the database is active, execute the following SQL code to acquire the hit rate of the data cache. If the hit rate is 90% or lower, increase the number of buffers.

SQL code for acquiring the hit rate of the data cache:

Select (a.value + b.value) "Log_Reads", c.value "Rhy_Reads",

Round(((1 - (c.value / (a.value + b.value))) * 100), 3) "Buffer Hit Ratio"

from v$sysstat a,v$sysstat b,v$sysstat c

where a.name = 'db block gets' and b.name = 'consistent gets'

and c.name = 'physical reads';

shared_pool_size

In this parameter, specify about 32 megabytes. While the database is active, execute the following SQL code to acquire the hit rates of the library cache and dictionary cache. If the hit rates are 90% or lower, increase the allocation size.

SQL code for acquiring the hit rate of the library cache:

Select sum(pins) "Executions", sum(reloads) "Misses",

Round(100*(1-sum(reloads)/sum(pins)),3) "Hit Ratio" from v$librarycache;

SQL code for acquiring the hit rate of the dictionary cache:

Select sum(gets) "Gets", sum(getmisses) "Misses",

Round(100*(1-sum(getmisses)/sum(gets)),3) "Hit Ratio"

from v$rowcache where gets <> 0;

processes

In this parameter, specify the maximum number of users that can be connected at one time.

To use the relational database, you must set access permissions. This subsection describes how to set access permissions.

To create a user after creating a database:

1. Grant CONNECT, EXP_FULL_DATABASE, IMP_FULL_DATABASE, and RESOURCE as role permissions.
2. Grant all permissions to all tables of JP1/Software Distribution as object permissions.
   

   Example: When creating a database with the SYSTEM permission and creating NETM_USER01:

   GRANT ALL ON "SYSTEM"."NETMDM_CABINET" TO "NETM_USER01"

3. Create a synonym to allow users to view all tables of JP1/Software Distribution.
   

   Example: When creating a database with the SYSTEM permission and creating NETM_USER01:

   CREATE SYNONYM "NETM_USER01"."NETMDM_CABINET" FOR "SYSTEM"."NETMDM_CABINET"