Release 2.1.7.3
A48486-2
 Library |
 Product |
 Contents |
 Index |
| Oracle Video Server(TM) Installation Guide: Sun SPARC Solaris Release 2.1.7.3 A48486-2 |
|
This chapter describes the tasks you should complete prior to installing the Oracle Video Server (OVS) on a Solaris 2.x system.
Topics covered in this chapter are:
Install Sun Microsystem's operating system patch 101945-34 prior to installing the OVS software.
No patches are required for Solaris 2.5.
OVS software must be run under an administrative user account and group. Log in as the user root and create both a software owner account, and a user group. This guide assumes that these accounts are called oracle.
Refer to your server platform's administration documentation for specific information on creating UNIX groups and user accounts.
Create a directory to hold the OVS software distribution. Give ownership of the directory to the oracle software owner account created in the previous section. This guide uses the directory /home/oracle:
Note that the permissions given to the directory with the chmod utility is 755. This gives the software account owner read, write, and execute privileges, and the group read and execute privileges.
The Oracle Installer will prompt you for this directory during the OVS installation process. Make note of this directory path.
OVS on the Solaris platform uses partitioned disks to store video content. You must designate the number of disks and their partitions which will be used for the storage of video. All disks used by the Oracle Media Data Store must be of the same capacity and type.
All disk devices used by the OVS to store content must be both readable and writable by the group oracle. To do this, give ownership of the devices to the group oracle. For example, if your system contains three disks named c0t0d0s6, c0t1d0s6, and c0t2d0s6, execute the following commands as the root user:
# chgrp oracle /dev/rdsk/c0t0d0s6 /dev/rdsk/c0t1d0s6 /dev/rdsk/c0t2d0s6
# chmod 660 /dev/rdsk/c0t0d0s6 /dev/rdsk/c0t1d0s6 /dev/rdsk/c0t2d0s6
Ensure that you give permission to the actual devices, and not just the link to them.
Solaris disks should be partitioned such that no single partition is greater than 2 GB in size. In addition, you must not assign the first cylinder of a physical disk to any MDS partition. On Solaris, the first page of every physical disk is assumed to contain the disk label and partitioning information. If the first cylinder is included in a raw partition that is then used with MDS, the labelling information will be overwritten. Subsequently relabelling the disk will overwrite MDS information, destroying your volume contents.
For example, a suitable partition mapping for a 4 GB drive is:
Part Tag Flag Cylinders Size Blocks
0 unassigned wm 0 - 0 1.29MB (1/0/0)
1 unassigned wm 0 0 (0/0/0)
2 backup wu 0 - 3173 4.00GB (3174/0/0)
3 unassigned wm 0 0 (0/0/0)
4 unassigned wm 0 0 (0/0/0)
5 unassigned wm 0 0 (0/0/0)
6 mds1 wu 1 - 1586 2.00GB (1586/0/0)
7 mds2 wu 1587 - 3173 2.00GB (1587/0/0)
In this example, partitions s6 and s7 are assigned to different MDS volumes.
The recommended flag setting for MDS partitions is wu (writable and unmountable).
The environment variables in Table 3-1 must be defined in the .login file of the oracle software owner. To set these environment variables, log in as oracle or the user account you previously created to administer the OVS. Please note that the values provided are examples only, your server's environment variables may vary.
Define the following environment variables in the .login file.
ORACLE_HOME defines the directory in which Oracle software is installed. The directory you assign to ORACLE_HOME must have sufficient space to hold the Oracle distribution, and must have read, write, and execute privileges for the oracle software owner.
This example defines ORACLE_HOME as /home/oracle:
% setenv ORACLE_HOME /home/oracle
PATH defines the search path used when you execute a command. The PATH environment variable must include the $ORACLE_HOME/bin directory.
This example defines PATH with the value given to ORACLE_HOME:
% setenv PATH ${PATH}:$ORACLE_HOME/bin
OMN_ADDR defines the Oracle Media Net (OMN) Address, which consists of the server's IP address and a unique UDP port number. You will need to have the OMN_ADDR information when installing OVS with the Oracle Installer.
Obtain the IP address of the network interface card used by OVS from your system or network administrator, or refer to your server computer's documentation on how to obtain the IP address.
The UDP port number can be any port number between 1024 and 65535. The Oracle Installer uses the default value of 5000.
The syntax used to set the OMN_ADDR environment variable is:
UDP:IP_address:port_number
where:
is the IP address of the network interface to be used by OVS
is a unique UDP port number
This example defines OMN_ADDR with an IP address of 192.25.102.201 and a UDP port number of 5000:
% setenv OMN_ADDR UDP:192.25.102.201:5000
OMS_BIN defines the directory which contains OVS executables. Set OMS_BIN to $ORACLE_HOME/bin.
This example defines OMS_BIN:
% setenv OMS_BIN $ORACLE_HOME/bin
LD_LIBRARY_PATH defines the directory which contains OVS library files. LD_LIBRARY_PATH should be set to include the $ORACLE_HOME/lib directory.
This example defines LD_LIBRARY_PATH:
% setenv LD_LIBRARY_PATH ${LD_LIBARY_PATH}:$ ORACLE_HOME/lib
