Release 2 (9.2.0.2) for hp OpenVMS Alpha
Part Number B10508-01
 Contents |
 Index |
| Oracle9i Installation Guide Release 2 (9.2.0.2) for hp OpenVMS Alpha Part Number B10508-01 |
|
This chapter describes the pre-installation steps required for an Oracle9i software installation.
The following issues and restrictions can affect the installation or use of Oracle9i on HP OpenVMS Alpha.
If you re-install Oracle9i server into an ORACLE_HOME where Oracle9i server Release 2 (9.2.0.2) is already installed, then you must also re-install any product options, such as Oracle Partitioning, that were enabled before you began the re-installation
Do not install Oracle9i Release 2 (9.2.0.2) into the root directory of an existing Oracle installation containing any Oracle Software.
Oracle Corporation recommends that you install Oracle9i Release 2 (9.2.0.2) products into a new ORA_ROOT.
The JRE that is shipped with Oracle9i is used by Oracle Java applications such as the Oracle Universal Installer and is the only Java application that is supported to run with these applications. Customers must 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 Oracle Universal Installer creates the oraInventory directory the first time that it is run in order to keep an inventory of products that it installs (as well as other installation information) on your system.
Installation cannot be performed using character mode with the Oracle Universal Installer (OUI). For non-interactive installations, use the Silent Mode Installation, which is described in Chapter 1, "Oracle9i Installation Planning". The Oracle Universal Installer can be run in the interactive mode directly from your system X-Windows console or via an X-Terminal or PC X-Terminal on a remote system.
If you are upgrading an existing system, then some issues may exist that exceed the scope of this manual.
It is possible to migrate Oracle8i Release 2 (8.1.6) and Oracle8i Release 3 (8.1.7) and Oracle9i Release 1 (9.0.1) to Oracle9i Release 2 (9.2.0.2). To migrate from an Oracle database earlier than these releases, you must first upgrade to an Oracle8i Release 2 or Release 3 or to an Oracle9i Release 1, and then follow the steps outlined in the document ora_rdbms:readmemigvms.doc to migrate to Oracle9i Release 2 (9.2.0.2).
As noted previously (refer to "Oracle9i Release 2 Dependency on ODS-5 Disk Structure"), the Oracle9i release 2 software must be installed on an ODS-5 formatted disk. The datafiles and redolog files, however, can be placed on ODS-2 formatted disks as well.
Oracle9i server must be able to verify that files have been written 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), the Oracle standard set of configuration guidelines for Oracle databases, is not supported on HP OpenVMS Alpha.
If you use the Hummingbird Exceed X Windows emulator while installing and using Oracle9i, then set the window manager to run in Native mode so that Microsoft Windows functions as the window manager. Refer to your Exceed documentation for instructions on configuring the window manager.
Following are common problems with the Hummingbird Exceed X Windows emulator:
Next button during the installation, rendering the screen unreadable. Another display problem is that the expansion of an installer window can display the dialog buttons off the screen so that they are not selectable with a mouse. If one of these display problems occurs, then exit the entire X Windows session and start a new session.
Consumer Name, appears truncated when viewed through Exceed. This dialog box displays as expected when viewed through native X Windows on OpenVMS.
To correct any problems with hidden dialog fields, perform the following steps:
The Add Font Directory dialog box is displayed.
This section provides installation procedure requirements.
Create an HP OpenVMS Alpha user account to administer the Oracle9i Enterprise Edition installation and maintenance, or modify your existing Oracle user account to meet the account quotas and privileges that are specified in this guide.
Setting up an Oracle9i account is the same as setting up any other HP OpenVMS Alpha user account. The following are the steps to set up an Oracle9i account:
To add an account, you must supply the following information:
Although this guide refers to this account as the Oracle9i account, you can assign any name or number to the account with the UIC restrictions noted below.
The Oracle9i 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 Oracle9i Administrator's Guide, the Oracle9i account is sometimes referred to as the DBA account. The Oracle9i 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 Oracle9i 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, then the Oracle9i account cannot issue the following commands:
If your Oracle9i account has a UIC group number that is less than MAXSYSGROUP, then you must create a new account with a UIC group number higher than MAXSYSGROUP before you install Oracle9i.
The following command gives the value of MAXSYSGROUP (in decimal format):
$ 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 Oracle9i /PASSWORD=ORACLE/UIC=[277,100]- /DEVICE=<device>/DIRECTORY=[Oracle9i]/OWNER="ORACLE DBA"
In this example, the account name is Oracle9i. 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, refer to the Hewlett-Packard documentation.
The following privileges are required as both authorized and default privileges for the Oracle9i database administrator account:
|
Note: An exception is explained in "Security Issues with Multiple Databases". |
Appendix B, "Oracle9i 64-bit Feature" has additional information that explains the meanings of the privileges.
Note:
Use the AUTHORIZE utility to set the account privileges for the Oracle9i database administrator account.
At the UAF prompt, use the MODIFY command to add the required default and authorized privileges as follows:
UAF> MODIFY ORACLE9 - /PRIVILEGE=(CMKRNL,NETMBX,OPER,PFNMAP,PRMGBL,PRMMBX,SHARE,SYSGBL, - SYSNAM,TMPMBX,GROUP,GRPNAM,IMPERSONATE,LOG_IO,WORLD,SYSLCK, SYSPRV) - /DEFPRIVILEGE=(CMKRNL,NETMBX,OPER,PFNMAP,PRMGBL,PRMMBX,SHARE, SYSGBL, - SYSNAM,TMPMBX,GROUP,GRPNAM,IMPERSONATE,LOG_IO,WORLD,SYSLCK, SYSPRV)
Use the AUTHORIZE utility to change account quotas to accommodate the requirements of your Oracle9i 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 value to a value of 150:
UAF> MODIFY ORACLE9i/ENQLM=150
The following table lists the Oracle9i account quotas, their minimum recommended values, and their equivalent HP OpenVMS Alpha quota names as displayed by the DCL commands SHOW PROCESS/QUOTA and SHOW WORKING_SET.
Appendix B, "Oracle9i 64-bit Feature" has additional information explaining the meanings of the quotas and how to determine their values.
The Oracle server Database Administrator (DBA) account must be granted one or more process rights identifiers. These identifiers provide the ability to issue the CONNECT / AS SYSDBA 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 Oracle9i account for an instance called TEST, issue the following command:
UAF> ADD/IDENTIFIER ORA_TEST_DBA
Then grant the rights identifier to the Oracle9i account as follows:
UAF> GRANT/IDENTIFIER ORA_TEST_DBA ORACLE9i
If you add the ORA_TEST_DBA rights identifier, but grant only ORA_DBA to ORACLE9i, then 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 to accounts (for example, privileges to start up and shut down the database) in addition to the Oracle9i account. (However, with the Oracle9i account, the user UIC GROUP number must be greater than MAXSYSGROUP). By granting the ORA_<sid>_DBA identifier, you can similarly restrict user privileges to an instance named <sid>.
Releases of the Oracle RDBMS on HP OpenVMS Alpha after Release 7.3.2.3.0 feature a change in the way that the software runs and accesses the SGA. Previous to Release 7.3.2.3.2, the SGA was protected by allowing only processes that are 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, add a rights identifier to the User Authorization File (UAF). Have your system manager adhere to the following directions.
At the UAF> prompt, type:
UAF > ADD/IDENTIFIER/ATTRIBUTES=SUBSYSTEM ORA_SGA
To install the Intelligent Agent, you must add the ORA_AGENT_ID identifier to your system before starting the installation. Use the following command:
UAF > ADD/IDENTIFIER ORA_AGENT_ID
All users that will submit jobs to the Intelligent Agent must have ORA_AGENT_ID. Use the following command:
UAF > GRANT/IDENTIFIER ORA_AGENT_ID <user name>
If your site has several databases managed by different DBAs, then you might not want to grant the CMKRNL privilege to every DBA Oracle9i account. This privilege allows a DBA to activate any process rights identifiers and to install shared images.
For security reasons, Oracle Corporation recommends that the OpenVMS system administrator handle these tasks. This person should be responsible for starting Oracle9i instances from a controlled account with a UIC group greater than MAXSYSGROUP. If this is not possible, then at least one Oracle9i database administrator must have the CMKRNL privilege.
Exit the AUTHORIZE utility.
If the user account that you modified was logged on at the time, then 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
For instructions on calculating MIN_GBLPAGES, MIN_GBLSECTIONS, and MIN_MAXBOBMEM, refer to the READMEVMS.DOC in the RDBMS directory.
Through its interface within the SYSMAN utility, the Reserved Memory Registry allows an HP OpenVMS Alpha system to be configured with large amounts of memory set aside for use within memory-resident global sections. The AUTOGEN utility considers the pre-allocated 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 that is 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 server 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, then the instance startup will fail. In this case, the amount of reserved memory must be adjusted, AUTOGEN must be run, and the system must 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.
To review memory reservations on your node, run the following command:
$ show memory/reserved System Memory Resources on 13-JUL-2001 09:57:11.72 Memory Reservations (Pages) Group Reserved In Use Type ORA_PROD_SGA SYSGBL 5120 0 Allocated ORA_PROD_SGA SYSGBL 5 0 Page Table Total (40.04 Mbytes reserved) 5120 0
Please consult Hewlett-Packard if you need more information about reserving memory.
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. The instructions in this section are directed to 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, and its use is discouraged, except perhaps for checking current values. You must have SYSPRV or BYPASS privilege to run these utilities.
AUTOGEN provides a permanent method for setting parameters, and it documents all changes. AUTOGEN also lets you recalculate any parameters that depend on other parameters that 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, then 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
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 that file.
If your system fails to satisfy any listed requirement, then perform the tasks listed in the next section as necessary to configure your system to meet these requirements.
Table 3-3 lists the requirements for installing Oracle9i on your HP OpenVMS system.
Log in as the system user and perform the following tasks to set up your environment for Oracle9i:
The oracle9 account is the OpenVMS user account that owns the Oracle9i software after installation. Run Oracle Universal Installer with this user account.
Use the AUTHORIZE utility to create an oracle9 account with the following properties:
Table 3-4 lists the properties of Oracle9i accounts.
Sites with multiple ORA_ROOT directories on one system may install Oracle software with the same oracle9 account, or separate accounts. Each oracle9 account must have the same group UIC.
The Apache account is an OpenVMS user account that owns the Apache server after installation. If you use a default Apache configuration (one that listens to ports lower than 1024, which are reserved to System), then Oracle Corporation recommends, for security reasons, that a separate account owner be set up for Apache. Configure the Apache server to assign ownership of listener and module actions to this account. It is not necessary for the Apache user account to have privileges to run the Apache Server on a port < 1023. Images that are linked with privileges during installation in the 'oracle' account ensure that this can be done. For details on how to configure the server to run as a user other than the 'oracle' user, refer to section "Customizing the Server Environment".
The Apache account owner should have minimal user privileges, and should not be a member of any groups whose files are not intended to be visible to the public. The nobody account may serve as a model for the Apache account.
Log in to the Oracle9 account and perform the following tasks as necessary:
Set default file protections for the oracle9 account to ensure that group and world have read and execute permissions, but not write permission, on installed files.
login.com of the oracle9 as follows:
$ SET PROTECTION=(s:RWE, o:RWED, g:RE, w:RE)/default
Before starting the Oracle Universal Installer, set your display appropriately. Enter:
$ SET DISPLAY/CREATE/TRANSPORT=TCPIP/NODE=<workstation_name or IP_address>
and verify that it is correct by using the following command:
$ RUN SYS$SYSTEM:DECW$CLOCK
Refer to each logical entry in this section for instructions on setting the logical correctly.
Do not use the hostname or IP address of the system where the software is being installed unless you are performing the installation from the X-Windows console of that system. Use the machine name or IP address of your own workstation if you are installing from a remote system. If you are not sure of the X server and screen settings, then use 0 (zero) for both.
The following products require pre-installation steps to be completed before you install Oracle9i software:
Complete pre-installation tasks for the precompilers and tools that are required for hp OpenVMS Alpha.
The use of incorrectly aligned binary data (such as COMP-1) in Pro*COBOL applications will generate unaligned access warnings that will prevent optimum compiler performance, but will not affect the application results.
The Java Runtime Environment (JRE) that is certified for use with Oracle9i software is used by Oracle Java applications such as the Oracle Universal Installer and is the only Java application supported to run with these applications. Do not modify this JRE unless you use a patch that is provided by Oracle Support Services.
This section describes tasks that need to be completed prior to installation if you have existing network and system management products.
If you have an existing installation of Oracle Net8 server, then shut down all listeners before installing Oracle Net. To determine if any listeners are running, enter the following command:
$ lsnrctl status [listener_name]
The listener_name field is required if the listener has a name other than the default name listener.
To shut down a running listener, enter the following command:
$ lsnrctl stop listener_name
Oracle Universal Installer automatically installs the TCP/IP protocol with all Oracle9i database installations. Before installing any protocol, verify that the underlying network is functioning and is configured properly.
To verify that the network is functioning properly, transfer and retrieve a test file using the ftp utility by entering the following commands:
$ ftp remote_server_name ftp> put test_filename ftp> get test_filename
|
 Copyright © 2003 Oracle Corporation. All Rights Reserved. |
|