Release 3 (8.1.7) for Alpha OpenVMS
Part Number A86708-01
 Library |
 Contents |
 Index |
| Oracle8i Installation Guide Release 3 (8.1.7) for Alpha OpenVMS Part Number A86708-01 |
|
Completing a quick, successful installation depends on the local system satisfying the software dependencies and space requirements for Oracle software. This chapter describes the requirements for installing Oracle8i on Alpha OpenVMS and any restrictions with this release. Before starting the installation, verify if your system meets the requirements described in this chapter.
Installing Oracle8i involves the following steps:
Oracle 8i Release 3 (8.1.7) for Alpha OpenVMS comes with one set of products bundled together as a single group. If you are using ORACLIENS to install Oracle, your choice of products determines your type of installation. Typically, if you choose only the following products:
you will get a "client" type of installation. If you choose RDBMS and its options, you will get an "Enterprise Edition Server" installation.
Verify if your system meets the requirements described in the following sections before you install Oracle8i Release 3 (8.1.7) products.
Installation time varies depending on the number of products being installed and the type of hardware being used. Duration of Typical installation takes about 1 to 3 hours.
To install Oracle8i products included with this release, your Alpha OpenVMS system must meet the minimum hardware requirements listed in Table 1-2.
To determine the amount of RAM memory installed on your system, as well as the amount of swap space currently configured on your system, enter the following command:
$ SHOW MEMORY
The Oracle Universal Installer allows you to choose your installation category and type as described in "Product Installation Categories and Installation Types". Your choices will determine how much disk space you will need as shown in the following tables. Disk space requirements do not account for the size of your database. A production Oracle database server supporting many users requires significantly greater disk space and memory.
| Installation Type | Required Disk Space |
|---|---|
|
Typical |
1250 MB |
|
Minimal |
1050 MB |
|
Custom |
Up to a maximum of 1500 MB |
Two shared images that are linked with client code are built and installed when you link Oracle8i Enterprise Edition. The new shared images reduce the size of all Oracle client executable images (including precompiled user programs) by removing direct references to SQL*Net and other common routines.
The image names are in the form of: ORACLIENT_<imageid>.EXE and ORACLIENT64_<imageid>.EXE, where <imageid> is the identifier chosen during installation time.
To install Oracle8i products included with this release, your Alpha OpenVMS system must meet the operating system requirements listed in the following table.
| OS Software | Requirements |
|---|---|
|
Operating System |
OpenVMS, Version 7.2-1 |
|
Operating System Patch |
Use the latest patch kit from Compaq. Compaq provides patch information at www.compaq.com/support. |
|
SQL*Net 8.1.7 Requirements |
SQL*Net 8.1.7 on Alpha OpenVMS is developed and certified using Compaq's TCP/IP Services for OpenVMS (UCX). If you wish to use the TCP/IP protocol adapter for SQL*Net, you should have Version 5.0A or higher of TCP/IP Services for Alpha OpenVMS installed. TCP/IP protocol stacks from other vendors may work with Oracle, but customers use these products at their own risk. Any TCP/IP problems that cannot be reproduced using TCP/IP Services for Alpha OpenVMS will simply be referred to the TCP/IP vendor. Vendor-provided protocol services are usually upward-compatible, so that existing applications will continue to work without modification. Thus, later releases of TCP/IP are upward compatible with SQL*Net, provided that the vendor-specified Application Programming Interface (API) does not change with new releases. |
|
Foot 1Window Manager |
X-windows must be installed on the system from where the Installer is run. Use any Compaq-supported X-windows server, for example, |
|
1
Required only if you wish to install Oracle8i using Oracle Universal Installer (OUI). |
To determine your current operating system information, enter one of the following commands:
$ SHOW SYSTEM /NOPROCESS /FUL
To see information about all nodes in a cluster, add the /CLUSTER qualifier to the above command.
To determine if your X-windows system is working properly on your local system, enter the following command:
$ RUN SYS$SYTEM:DECW$CLOCK
If a clock is not displayed on your screen, X-windows is not configured correctly. See "DISPLAY" for instructions on configuring X-windows.
The SQL*Net VMS Mailbox driver (protocol IPC) is included in NETCONFIG. You do not need a SQL*Net license to use the VMS Mailbox driver.
The following DEC compilers were used to certify the programmatic interfaces:
| Programmatic Interfaces | Certification Release |
|---|---|
|
Pro*C |
Compaq C++ release 6.2 |
|
Pro*COBOL |
DEC COBOL release 2.6 |
|
Pro*FORTRAN |
DEC FORTRAN release 7.1 |
|
SQL*Module |
DEC ADA 3.4-2 |
Some Oracle products depend on other Oracle products to work properly. Use the following tables to determine the product dependencies. This section has the following subsections:
In the following cases, you need to install the required product before or at the same time you install the product that requires it.
Oracle recommends that you build the products at the same time in order to save time. You must also make sure to configure the product to include (or link against) the dependent product and vice versa.
Review the compatibility issues given in this section:
|
Note: To install National Language Support (NLS), build all Oracle products first. Then install NLS. The product directories must exist before NLS message files can be copied into them. |
To view online documentation included with the Oracle8i CD-ROM, use any HTML compatible browser available on OpenVMS. To view PDF documents, you need Adobe Acrobat Reader version 3.0 or higher. Online documentation included with Oracle8i Release 3 (8.1.7) for Alpha OpenVMS can only be viewed on Alpha OpenVMS systems.
This section provides product-specific information in addition to hardware and software requirements provided earlier in this chapter. For descriptions of these products, see Appendix A, "Oracle8i Products".
All network products require the underlying software and operating system libraries for the supported network. The network software must be installed and running prior to installation of Net8 products. Refer to operating system and third party vendor networking product documentation for more information. Net8 Release 8.1.7 products require Oracle8i Release 3 (8.1.7) and Net8 Release 8.1.7.
| Product Name | Restrictions and Requirements |
|---|---|
|
Oracle TCP/IP with SSL Protocol Support, 8.1.7 |
SSL 3.0 or later |
Oracle Advanced Security is an add-on product to the standard Net8 Server or Net8 Client. It must be purchased and installed on both the client and the server.
Oracle Advanced Security Release 8.1.7 requires Net8 Release 8.1.7 and supports Oracle8i Enterprise Edition. Install Oracle Advanced Security on each client and server where Oracle Advanced Security is required.
Table 1-7 describes requirements for authentication protocols supported by Oracle Advanced Security. See the Oracle Advanced Security Administrator's Guide for additional information.
This section lists restrictions for Alpha OpenVMS at this time.
The following areas have restrictions on Alpha OpenVMS:
Moving executables from one OpenVMS machine to another is not recommended due to the usage of shared libraries and the difficulty of ensuring valid referencing. Therefore, we recommend that you relink executables.
Oracle8i is not supported under the Posix shell on OpenVMS.
Oracle8i Enterprise Edition Release 3 (8.1.7) supports only two-task configurations.
Keep the following guidelines in mind when linking SQL*Net:
The following table shows the range of use for SQL*Net drivers in client/server and distributed database configurations. This table assumes that clients in a client/server configuration run the Oracle tool and that servers run the Oracle database. For distributed database examples, the clients and servers both run an Oracle tool and the Oracle database.
| Client/Server | Distributed RDBMS | |||
|---|---|---|---|---|
| Client Tool | RDBMS Server | Client | Server | |
|
SQL*Net TCP/IP |
Yes |
Yes |
Yes |
Yes |
|
SQL*Net OpenVMS Mailbox |
Limited* |
Limited* |
Limited* |
Limited* |
*Only for communication between products on the same machine.
The following issues and restrictions can affect the installation or use of Oracle8i on Alpha OpenVMS. Check the Release Notes that accompany this release in the ORA_ROOT:[ORACLEDOC]PRODUCTS.HTM file before using Oracle8i.
Re-Installing Oracle8i Release 3 (8.1.7)
If you re-install Oracle8i Server into an ORACLE_HOME where Oracle8i Server Release 3 (8.1.7) is already installed, you must also re-install any product options, such as Oracle Partitioning, that were enabled before you began the re-installation
Do not install Oracle8i Release 3 (8.1.7) into root directory of an Oracle installation containing any Oracle Software.
Oracle Corporation recommends that you install Oracle8i Release 3 (8.1.7) products into a new ORA_ROOT.
If you wish to run Oracle8i Release 3 (8.1.7) concurrently with Oracle8i Release 2 (8.1.6), Oracle 8i Release 3 must be installed into a new ORA_ROOT.
The JRE shipped with Oracle8i is used by Oracle Java applications such as the Oracle Universal Installer and is the only one supported to run with these applications. Customers should not modify this JRE, unless it is done through a patch provided by Oracle Support Services.
The inventory can contain multiple versions of the JRE, each of which can be used by one or more products or releases. The Installer creates the oraInventory directory the first time it is run to keep an inventory of products that it installs on your system as well as other installation information.
Installation cannot be performed using character mode with the Oracle Universal Installer (OUI). For character mode installations, use the ORACLEINS installer. The Installer can be run in interactive mode (non-interactive is not currently supported), directly from your system's X-windows console or via an X-terminal or PC X-terminal on a remote system.
If you are upgrading an existing system, there are issues which exceed the scope of this manual.
It is possible to migrate an Oracle7 database, Release 7.3.4 or higher, or upgrade an Oracle8 database, Release 8.0.5.1 or higher, to Oracle8i Release 3 (8.1.7). To migrate from an Oracle7 database lower than 7.3.4, you must first upgrade to an Oracle7 database, Release 7.3.4 or higher, and then follow the steps outlined in the document ora_rdbms:readmemigvms.doc to migrate to Oracle8i.
Oracle8i Server must be able to verify that file writes have been made to disk. File systems that do not support this verification are not supported for use with Oracle databases, although Oracle software can be installed on them.
Optimal Flexible Architecture (OFA), Oracle's standard set of configuration guidelines for Oracle databases, is not supported on OpenVMS.
Oracle8i Release 3 (8.1.7) includes native support for datafile sizes upto 4 GB.
This section gives installation procedure requirements.
Create an Alpha OpenVMS user account to administer the Oracle8i Enterprise Edition installation and maintenance, or modify your existing Oracle7 user account to meet the account quotas and privileges specified in this guide.
Setting up an Oracle8i account is the same as setting up any other Alpha OpenVMS user account. The following are the steps to set up an Oracle8i account:
|
Additional Information: See Compaq's OpenVMS System Management Utilities Reference Manual for more information about running the AUTHORIZE utility |
To add an account, you must supply the following information:
Although this guide refers to this account as the Oracle8i account, you can assign any name or number to the account with the UIC restrictions noted below.
The Oracle8i account will own the runtime libraries and executable images for every Oracle product. Therefore, the database administrator (DBA) should manage this account and install all Oracle products from it.
In the Oracle8i for Alpha OpenVMS Server and Tools Administrator's Guide, the Oracle8i account is sometimes referred to as the DBA account. The Oracle8i account is not the same as the SYS or SYSTEM database usernames that are created for every database; it is an OpenVMS account name.
The UIC GROUP number of the Oracle8i account must be greater than the system parameter MAXSYSGROUP (which defaults to octal 10). GROUP numbers 1 through MAXSYSGROUP are reserved for use by the OpenVMS operating system itself. If the UIC GROUP number is not greater than the system parameter MAXSYSGROUP, the Oracle8i account cannot issue the following commands:
If your Oracle8i account has a UIC group number that is less than MAXSYSGROUP, you must create a new account with a UIC group number higher than MAXSYSGROUP before you install Oracle8i.
The following command gives the value of MAXSYSGROUP:
$ WRITE SYS$OUTPUT F$GETSYI("MAXSYSGROUP")
Use the AUTHORIZE utility to create or modify records in the User Authorization File (UAF):
$ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE
UAF> ADD Oracle8 /PASSWORD=ORACLE/UIC=[277,100]- /DEVICE=<device>/DIRECTORY=[Oracle8]/OWNER="ORACLE DBA"
In this example, the account name is Oracle8i. Note that the UIC GROUP number is 277. The UIC GROUP number must be larger than MAXSYSGROUP.
After adding the account, you must alter the account privileges and quotas. Although this can be done in any order, usually the account privileges are set before the account quotas.
For more information on using AUTHORIZE, see the chapter on "Managing User Accounts" in Compaq's OpenVMS System Manager's Manual.
The following privileges are required as both authorized and default privileges for the Oracle8i database administrator account:
|
Note: Appendix B, "Oracle8i 64-bit Feature" has additional information explaining the meanings of the privileges. |
Use the AUTHORIZE utility to set the account privileges for the Oracle8i database administrator's account.
At the UAF prompt, use the MODIFY command to add the required default and authorized privileges as follows:
UAF> MODIFY ORACLE8 - /PRIVILEGE=(CMKRNL,NETMBX,PFNMAP,PRMGBL,PRMMBX,SYSGBL, - SYSNAM,TMPMBX,IMPERSONATE,LOG_IO,WORLD,SYSLCK, SYSPRV) - /DEFPRIVILEGE=(CMKRNL,NETMBX,PFNMAP,PRMGBL,PRMMBX,SYSGBL - SYSNAM,TMPMBX,IMPERSONATE,LOG_IO,WORLD,SYSLCK, SYSPRV)
You use the AUTHORIZE utility to change account quotas to accommodate the requirements of your Oracle8i installation.
After adding a record with the default quotas, use the MODIFY command to alter the default values. The following example changes the Enqueue quota (ENQLM) from the default to 150:
UAF> MODIFY ORACLE/ENQLM=150
The following table lists the Oracle8i account quotas, their minimum recommended values, and their equivalent Alpha OpenVMS quota names as displayed by the DCL commands SHOW PROCESS/QUOTA and SHOW WORKING_SET.
|
Note: These quotas depend on the number of logfiles, the number of databases, the number of network connections, and other logicals on your system. You might need to customize them. |
Appendix B, "Oracle8i 64-bit Feature" has additional information explaining the meanings of the quotas and how to determine their values.
The Oracle Server Database Administrator account must be granted one or more process rights identifiers. These identifiers provide the ability to issue the CONNECT INTERNAL command that is required to perform database administration functions. The following table displays the combinations of adding and granting rights identifiers to this account:
For example, to grant the ORA_<sid>_DBA rights identifier to the Oracle8i account for an instance called TEST, issue the following command:
UAF> ADD/IDENTIFIER ORA_TEST_DBA
Then grant the rights identifier to the Oracle8i account as follows:
UAF> GRANT/IDENTIFIER ORA_TEST_DBA ORACLE8
If you add the ORA_TEST_DBA rights identifier, but grant only ORA_DBA to ORACLE8, the account would have insufficient privileges to administer the instance TEST.
The third line of the table shows that you can add and grant different identifiers, thereby restricting control of a particular instance while still granting control to other instances.
You can grant database maintenance privileges (for example, privileges to start up and shut down the database) to accounts in addition to the Oracle8i account. (However, with the Oracle8i account, the user's UIC GROUP number must be greater than MAXSYSGROUP.) By granting the ORA_<sid>_DBA identifier, you can similarly restrict a user's privileges to an instance named <sid>.
Oracle releases of RDBMS on Alpha OpenVMS after Release 7.3.2.3.0 feature a change in the way the software runs and accesses the SGA. Previous to Release 7.3.2.3.2, the SGA was protected by allowing only processes running in supervisor mode to access it directly. Starting with Release 7.3.2.3.2, the SGA is protected by an Access Control List to accommodate the kernel remaining in user mode.
Before bringing up a database later than 7.3.2.3.0, add a rights identifier to the User Authorization File (UAF). Have your system manager follow these directions.
At the UAF> prompt, type:
UAF > ADD/IDENTIFIER/ATTRIBUTES=SUBSYSTEM ORA_SGA
|
Warning: DO NOT GRANT THE RIGHTS IDENTIFIER TO ANY USER. Oracle takes care of assigning it when it starts the database. |
To install the Intelligent Agent, you must add the ORA_AGENT_ID identifier to your system before starting the install. Use the following:
UAF > ADD/IDENTIFIER ORA_AGENT_ID
All users that will submit jobs to the Intelligent Agent must have ORA_AGENT_ID. Use the following:
UAF > GRANT/IDENTIFIER ORA_AGENT_ID <user name>
If your site has several databases managed by different DBAs, you might not want to grant the CMKRNL privilege to every DBA's Oracle8i account. This privilege allows a DBA to activate any process rights identifiers and install shared images.
For security reasons, Oracle Corporation recommends that the OpenVMS system administrator handle these tasks. This person should be responsible for starting Oracle8i instances from a controlled account with a UIC group greater than MAXSYSGROUP. If this is not possible, at least one Oracle8i database administrator must have the CMKRNL privilege.
Exit the AUTHORIZE utility.
If the user account that you modified was logged on at the time, this user must log out and log back in before the changes take effect.
Use the following command to verify that your account has the correct privileges and rights identifiers:
$ SHOW PROCESS/PRIVILEGE
Please refer to the READMEVMS.DOC in the RDBMS directory for instructions on calculating MIN_GBLPAGES, MIN_GBLSECTIONS, and MIN_MAXBOBMEM.
Through its interface within the SYSMAN utility, the Reserved Memory Registry allows an Alpha OpenVMS system to be configured with large amounts of memory set aside for use within memory-resident global sections. The AUTOGEN utility considers the preallocated reserved memory when it tunes the system.
The advantages to reserving memory for an SGA are as follows:
To reserve memory for an SGA, use the SYSMAN utility. The size qualifier is specified in megabytes. For example, to reserve memory for a 6 GB SGA for the SID named TEST, use the following commands:
$ MCR SYSMAN SYSMAN> RESERVED_MEMORY ADD ORA_TEST_SGA/SIZE=6144/ALLOCATE/ZERO/PAGE SYSMAN> EXIT
Then run AUTOGEN and reboot the system to allow AUTOGEN to adjust other system parameters for the reduced amount of memory available to the rest of the system.
Memory for multiple SGAs may be reserved. Any change to the name or size of a piece of reserved memory may require rebooting the system. During instance startup, Oracle compares the size of the reserved memory, if any, with the size of the SGA. If appropriate, one of the following messages will be included in the Alert log:
** Reserved memory size = <size> greater than
created SGA size = <size>**
** Please reduce reserved memory size to avoid wasting memory. **
** Memory was not reserved for the SGA. SGA size = <size> **
** There might be performance advantages to allocating memory for
the SGA in the VMS reserved memory registry. **
If memory is reserved for an SGA but not enough memory is reserved, the instance startup will fail. In this case, the amount of reserved memory should be adjusted, AUTOGEN should be run, and the system should be rebooted. For example, to expand the SGA to 6.5 GB for the TEST instance, use the following commands:
$ MCR SYSMAN SYSMAN> RESERVED_MEMORY REMOVE ORA_TEST_SGA SYSMAN> RESERVED_MEMORY ADD ORA_TEST_SGA/SIZE=6656/ALLOCATE/ZERO/PAGE SYSMAN> EXIT
Then run AUTOGEN and reboot the system.
To avoid rebooting the system, SYSMAN can be used to free the memory reservation. Then you may start the instance. The risk is that the system may not have enough fluid pages to create the SGA. Also, the performance advantages of using reserved memory are not available.
|
Additional Information: For more information about the reserved memory registry, see Compaq's Alpha OpenVMS Guide to 64-Bit Addressing and VLM Features |
Because SYSGEN parameters affect the entire operating system, your system administrator is the only person who should modify them. Of course at some sites, the DBA and system administrator may be the same person. In this section, we assume we are addressing the system administrator.
For setting or modifying SYSGEN parameters, OpenVMS provides the AUTOGEN utility. You can also use SYSGEN, but this is an older utility whose use is discouraged, except perhaps for checking current values. You must have SYSPRV or BYPASS privilege to run these utilities.
AUTOGEN provides a permanent way of setting parameters, and it documents all changes. AUTOGEN also lets you recalculate any parameters that depend on other parameters you might have changed. Remember to record parameter values before changing them, and determine beforehand what results you expect from your changes. If the expected changes do not occur, restore the old values before trying again.
$ @SYS$UPDATE:AUTOGEN SAVPARAMS GETDATA
This step saves current parameters to a file named AGEN$FEEDBACK.DAT.
$ @SYS$UPDATE:AUTOGEN GETDATA
MIN_GBLSECTIONS=3000 MIN_GBLPAGES=300000
The MIN prefix indicates that you are setting a lower limit for the specified parameter. To use the MIN prefix, identify the current value of the specified parameter (using SYSGEN) and the amount by which you want to increase the parameter. The sum of these two values is used for the MIN_<parameter> entry.
$ @SYS$UPDATE:AUTOGEN GENPARAMS REBOOT
|
Warning: The REBOOT parameter in this example will cause the system to automatically reboot when the SYSGEN is complete. |
This step generates new SYSGEN parameters in a file named SETPARAMS.DAT and runs the SYSGEN utility to set these parameter values as specified in this file.
|
 Copyright © 2000 Oracle Corporation. All Rights Reserved. |
|