HPlogo ALLBASE/SQL Release G2 for HP-UX 10.30 Release Notes: HP 9000 Computer Systems > Chapter 3 Compatibility and Installation Requirements

Installation Information and Recommendations

» 

Technical documentation

Complete book in PDF
» Feedback

 » Table of Contents

Before upgrading or installing ALLBASE/SQL, ensure that your system meets the requirements described in this section:

  • HP-UX Version

  • ALLBASE/SQL Configuration

  • The User hpdb

  • The ALLBASE/SQL Filesets

  • RunTime ALLBASE/SQL Considerations

  • HP-UX SWINSTALL Utility

  • Using SQLVER

HP-UX Version

ALLBASE/SQL release G2 is supported on HP-UX release 10.30. If you have a release of the HP-UX operating system prior to 10.0, you must install HP-UX 10.30 on your system in addition to ALLBASE/SQL Release G2.

ALLBASE/SQL Configuration

When running ALLBASE/SQL with a large number of users, increase the configurable parameters accordingly. You can do this when you first create the DBEnvironment or by using SQLUtil. Refer to the "Maintenance" chapter in the ALLBASE/SQL Database Administration Guide for more information setting ALLBASE/SQL parameters. See the ALLBASE/SQL Performance and Monitoring Guidelines for more information about choosing the optimal values for configurable parameters.

The User hpdb

Before creating or connecting to an ALLBASE/SQL DBEnvironment, make sure there is a special user named hpdb with a user id number of 27 and a group id number of 2 on your system. If necessary, add the following line to the /etc/passwd file before invoking the HP-UX SWINSTALL utility to install the ALLBASE/SQL product:

hpdb:*:27:2: hpdb ALLBASE/SQL:/usr:/sbin/sh

In addition, add user hpdb to the group bin in the /etc/group file, as in the following example:

bin::2:root,rootc,bin,daemon,lp,hpdb

The user id number 27 is reserved for the user name hpdb, which is required to execute the ALLBASE/SQL program files. It is not required that the hpdb user belong to the group bin; however, all of the ALLBASE/SQL files are associated with bin. If the user id number 27 does not exist on your system, or if a user other than hpdb is assigned to this user id number, the security and integrity of your DBEnvironments cannot be guaranteed.

The ALLBASE/SQL program files are owned by the user hpdb. Several of the ALLBASE/SQL program files have set the file mode to 4555 which causes the "switch user id bit" to be turned on. Any users executing these ALLBASE/SQL program files have their effective user name changed to hpdb while these program files are executing. The user's group name remains the same as the group name the user is associated with in the file /etc/group. All files that are created as part of the database have the file permissions of 600, are owned by hpdb, and have the file creator's group association. For example, if user peter, who is a member of group dbsupport, creates a DBEnvironment named PartsDBE, the HP-UX file permissions and ownership for the DBECon file (DBEnvironment configuration file) will appear as follows:

-rw-  1 hpdb     dbsupport  12288 Apr 15 17:00 PartsDBE

The ALLBASE/SQL Filesets

The number of filesets on your installation tape depends on which bundle of ALLBASE/SQL you have purchased.

ALLBASE/SQL Development bundle has the following filesets:

  • ALLBASE-SQL.Development.AB-DEV

  • ALLBASE-SQL.Development.AB-NET

  • ALLBASE-SQL.Development.AB-RUN

  • ALLBASE-SQL.Development.AB-SAMPLEDB

ALLBASE/SQL Runtime bundle has the following filesets:

  • ALLBASE-SQL.Runtime.AB-NET,

  • ALLBASE-SQL.Runtime.AB-RUN, and

  • ALLBASE-SQL.Runtime.AB-SAMPLEDB

ALLBASE/SQL Replicate bundle has this fileset:

  • ALLBASE-SQL.Replicate.AB-REPLICATE

You do not need to load the SAMPLEDB fileset. SAMPLEDB is provided as an educational example and is not required for either the runtime or development version of ALLBASE.

Runtime ALLBASE/SQL Considerations

With Release G2, you have the option of installing a runtime version of ALLBASE/SQL. If you are installing only the runtime system, and if you have previously installed a complete earlier version of ALLBASE/SQL on your system, you should remove pre-Release G2 ALLBASE/SQL files from your system to ensure that all database files are consistent. Before removing the ALLBASE/SQL pre-Release G2 files, you may want to make a backup copy of them. If the database files are in their original directories, you may have to remove all previously installed ALLBASE/SQL files.

For example, assume that your system currently has ALLBASE/SQL F0.00. Installing the runtime version of ALLBASE/SQL G2 would result in an F0.00 version of the ALLBASE/SQL preprocessors coexisting with a Release G2 version of the runtime system. In this case the preprocessors will not work correctly.

After removing the old files, install your new ALLBASE/SQL package as shown in the section "HP-UX SWINSTALL Utility."

Client-Only Configuration

The AB-NET fileset contains ALLBASE/NET, which is required for remote database access. If you desire a runtime client-only configuration, this is the only fileset you need to install.

Terminating a Database Process

The kill -9 command, commonly used by a superuser to abort a process, may cause an undetected deadlock condition to occur or other processes connected to the same DBEnvironment to terminate or hang if it is used to abort a database process in a multiuser environment. You should never use the kill -9 command to abort an ALLBASE/SQL database process in a multi-user environment. Instead, use the TERMINATE USER command in ISQL to terminate a specific SessionID or all sessions for a DBEUserID. Refer to the ALLBASE/ISQL Reference Manual for further details.

Remote Database Access

Use ALLBASE/NET to establish remote access to ALLBASE/SQL DBEnvironments.

HP-UX SWINSTALL Utility

The swinstall utility is used by system administrator to add optional software to the system and to update the entire system when necessary. For detailed instructions on the use of swinstall, refer to the appropriate HP-UX Installation manual for your series.

The swinstall command installs the software-selections from a software source (tape) to the local host (root filesystem). The software is configured for use on the target after it is installed.

There are three main steps in the installation process namely:

  • Selection phase

  • Analysis phase

  • Install phase

Type swinstall at the command line.

You will be first asked to specify the target or destination of the software. Then you will be asked for the source from where the software will be installed. Fill up the details for Source Host Name and the Source Depot Path from where the software has to be installed. Press OK. You will get the message saying "Reading the Software source." The Software Selection Window then displays the Software bundle that is available with the tape.

Selection Phase

ALLBASE/SQL is available on both S800 and S700 platforms and is bundled as follows:

  • B5419AA_APX ALLBASE/SQL Runtime Environment (S800)

  • B5421AA_APX ALLBASE/SQL Development Environment (S800)

  • B5425AA_APX ALLBASE/SQL Replicate Environment (S800)

  • B5415AA_APX ALLBASE/SQL Runtime Environment (S700)

  • B5417AA_APX ALLBASE/SQL Development Environment (S700)

  • B5423AA_APX ALLBASE/SQL Replicate Environment (S700)

  • B5419AA_APZ ALLBASE/SQL Runtime Environment (S800)

  • B5415AA_APZ ALLBASE/SQL Runtime Environment (S700)

  • B5421AA_APZ ALLBASE/SQL Development Environment (S800)

  • B5417AA_APZ ALLBASE/SQL Development Environment (S700)

  • B5425AA_APZ ALLBASE/SQL Replicate Environment (S800)

  • B5423AA_APZ ALLBASE/SQL Replicate Environment (S700)

NOTE: Your product tape will only contain the bundles that you have ordered.

Select the software bundle that you need to install.

  1. Select and highlight the names of software bundles to install by pointing and clicking the left mouse button.

  2. Mark the highlighted bundles or products by selecting the Mark For Install item from the Actions menu. You will get the message marked Yes under Marked column of the Software Selection Screen.

Analysis Phase

The Analysis Phase lets you determine if the software can be successfully installed on the system BEFORE it is actually installed. A series of checks are performed on the process and the results are displayed in the window or written to a log file.

  1. Open up the Actions pop-up menu of the Software Selection screen.

  2. Select the option Install(Analysis). There will be a new pop-up window Install Analysis, when the analysis phase is being carried out.

    Once the Analysis Phase is successful, the confirmation window for Installation appears and waits for you to type Yes or No to continue the Installation Process.

  3. Select Yes for installation.

    The Install Window screen appears.

Install Phase

The Install Phase is when the actual installation takes place. The Install window allows you to monitor the progress of the operation as the software is loaded and configured.

This completes the process of Installation of ALLBASE/SQL on HP-UX System. To confirm that the installation is successful and no files are missing, refer to "Using SQLVer" below.

Native Language Support Issues

The default user language for ALLBASE/SQL and HP-UX Release 10.0 is C.

Feedback to webmaster