Release 1 (v1.0.2.2) for Sun SPARC Solaris
Part Number A90215-01
 Library |
 Contents |
 Index |
| Oracle9i Application Server Installation Guide Release 1 (v1.0.2.2) for Sun SPARC Solaris Part Number A90215-01 |
|
This chapter guides you through the basic concepts and preinstallation steps for Oracle9i Application Server. The following topics provide information about Oracle9i Application Server, environment variables settings, configuration options, and starting Oracle Universal Installer:
Oracle9i Application Server is a scalable, secure, middle-tier application server. It enables you to deliver Web content, host Web applications, connect to back-office applications, and access your data on wireless devices. Oracle9i Application Server has three installation options:
Oracle9i Application Server, version 1.0.2.2 includes Oracle9iAS Containers for J2EE (OC4J). The J2EE Container runs as a JVM that accepts HTTP and RMI connections, which access servlets, JSP Pages, and EJBs. For more information, including installation steps, refer to Appendix C, "Installing Oracle9iAS Containers for J2EE (OC4J)".
Table 2-1 lists the three installation options for Oracle9i Application Server, and the components that are installed with each option. This is followed by a brief description of each component.
Oracle9iAS Database Cache improves the performance and scalability of applications that access Oracle databases by storing frequently used data on middle tier machines. With Oracle9iAS Database Cache, your applications can process several times as many requests as their original capacity.
Oracle9iAS Discoverer is a business intelligence tool for analyzing data. With Oracle9iAS Discoverer's award-winning user interface, users can access and analyze database data. There are two Oracle9iAS Discoverer components:
Oracle9iAS Forms Services deploys Forms applications with database access to Java clients in a Web environment. Oracle9iAS Forms Services automatically optimizes class downloads, network traffic, and interactions with Oracle database. Applications are automatically load-balanced across multiple servers and, therefore, can easily scale to service any number of requests.
Oracle9iAS Portal is a complete solution for building, deploying and monitoring Web database applications and content-driven Web sites. Oracle9iAS Portal enables you to create and view database objects through an easy-to-use HTML-based interface, and provides tools for creating HTML-based interfaces. It also allows you to resolve performance problems using performance tracking facilities, and enables you to manage database security through its interface.
Oracle9iAS Reports Services provides an easy-to-use, scalable, and manageable solution for high-quality database publishing and reporting by creating dynamic reports for the Web and across the enterprise. It enables you to implement a multi-tiered architecture for running your reports.
Oracle9iAS Web Cache is a server accelerator caching service that improves the performance, scalability, and availability of frequently used e-business Web sites that run on Oracle9i Application Server and Oracle database. By storing frequently accessed URLs in virtual memory, Oracle9iAS Web Cache eliminates the need to repeatedly process requests for those URLs on the Web server, and it caches both static and dynamically-generated HTTP content from one or more applications Web servers.
Oracle9iAS Wireless is a portal service for delivering information and applications to mobile devices. Using Oracle9iAS Wireless, you can create custom portal sites that use different kinds of content, including Web pages, custom Java applications, and XML-based applications. Oracle9iAS Wireless sites make this diverse information accessible to mobile devices without you having to rewrite the content for each target device platform.
Oracle Advanced Security provides a comprehensive suite of security features to protect enterprise networks and securely extend corporate networks to the Internet. It provides a single source of integration with network encryption and authentication solutions, single signon services, and security protocols. By integrating industry standards, it delivers unparalleled security to the Oracle network and beyond.
Oracle Business Components for Java is a 100% Java-compatible, XML-powered framework that enables productive development, portable deployment, and flexible customization of multi-tier, database applications from business components.
The Oracle Database Client Developer Kit contains the following client libraries:
Oracle Enterprise Java Engine is an enterprise-class 100% Java-compatible server environment that supports Enterprise JavaBeans, CORBA, and database stored procedures. Oracle Enterprise Java Engine achieves high scalability through its unique architectural design, which minimizes the burden and complexity of memory management when the number of users increases.
Oracle9i Application Server uses the Oracle HTTP Server, which is built on Apache Web server technology. Oracle HTTP Server offers scalability, stability, speed, and extensibility. It also supports Java Servlets, JavaServer Pages, Perl, PL/SQL, and CGI applications. This component also includes the following sub-components:
mod_oprocmgr
mod_fastcgi
mod_Jserv
mod_mm
mod_ose
mod_plsql
mod_perl, Perl Interpreter
mod_ssl
Oracle Internet File System is a file system and development platform that stores files in an Oracle database. It provides a mechanism for creating, storing, and managing various types of information, from Web pages to email, from spreadsheets to XML files, in a common repository for users to access and update.
LDAP (Lightweight Directory Access Protocol) is the emerging Internet standard for directory services. Oracle LDAP Client Kit supports client interaction with any LDAP-compliant directory server; for example, Oracle Internet Directory. The toolkit provides tools and development libraries to support client calls to directory services, encrypted connections, and enables you to manage your directory data.
Oracle Management Server provides distributed control between the database and Oracle9i Application Server in the network. As a central engine for notifications, it processes all system management tasks and administers the distribution of these tasks across the enterprise. Ensure that you do not have multiple Oracle Management Servers installed on a single machine.
The Oracle XML Developer Kit (XDK) contains the necessary XML components libraries and utilities to give developers the ability to easily XML-enable applications and Web sites. Oracle XDK supports development in Java, C, C++, and PL/SQL with a collection of libraries, command-line utilities, and tools.
The following is a list of the supplemental components that are available with Oracle9i Application Server, version 1.0.2.2:
|
See Also: Appendix D, "Installing Supplemental Components" for overview and installation instructions. |
The preinstallation tasks for Oracle9i Application Server are divided into the following parts.
This section provides an overview of the installation process. Before installing Oracle9i Application Server, review the Release Notes and Release Notes Addendum. You can find the Release Notes Addendum on OTN at:
http://otn.oracle.com
The Oracle9i Application Server installation process is divided into the following three phases:
During the first phase of installation, the users completes the following tasks:
ORACLE_HOME, ORACLE_TERM, DISPLAY, TMP, and TNS_ADMIN.
During the second phase, the Oracle Universal Installer guides the user through the installation screens. Depending on the install type, the user will require the information listed in Table 2-2.
During installation, the user has the following configuration options:
If you are installing Enterprise Edition, the components are installed into two Oracle homes. The first Oracle home contains components that use the 8.1.7 database libraries. The other Oracle home contains components that use the 8.0.6 database libraries. The installer will prompt you to enter a path for both Oracle homes.
During the final phase of the installation process, the user is provided with the following information:
The following environment variables must be set before starting the installer.
Oracle home is the root directory in which Oracle software is installed.
Oracle9i Application Server cannot share the same Oracle home with other Oracle products. If you have installed other Oracle products, then Oracle9i Application Server must be installed in a different Oracle home. If previously-set Oracle homes exist on the machine where you are installing Oracle9i Application Server on, then refer to "Preventing Conflicts Between ORACLE_HOMEs" below.
To prevent a conflict between the software in an existing Oracle home and Oracle9i Application Server, you must remove all references to the existing Oracle home. The following steps describe removing these references.
| C shell | Bourne/Korn shell |
|---|---|
|
|
PATH, CLASSPATH, and LD_LIBRARY_PATH environment variables so they do not use the existing Oracle home value.
To set ORACLE_HOME environment variable, run the following command.
| C shell | Bourne/Korn shell |
|---|---|
|
|
ORACLE_TERM specifies the terminal definition resource file to be used with the installer. If ORACLE_TERM is not set, then the installer uses the value of the UNIX environment variable TERM and searches for an equivalent ORACLE_TERM resource file.
| C shell | Bourne/Korn shell |
|---|---|
|
|
Table 2-3 lists common ORACLE_TERM settings on SUN SPARC Solaris 2.x.
Setting the DISPLAY environment variable enables you to run the Oracle Universal Installer remotely from a local work station. On the system where you run the Oracle Universal Installer, set DISPLAY to the system name or IP address of your local workstation.
If you get an Xlib error similar to "Failed to connect to server", "Connection refused by server", or "Can't open display" when starting the installer, then run the commands on your local workstations as listed in the table below.
During installation, Oracle Universal Installer uses a temporary directory for swap space. This directory must meet the "Hardware Requirements" listed before installing Oracle9i Application Server. The installation may fail if you do not have sufficient space. The installer checks for the TMP environment variable to locate the temporary directory. If this environment variable does not exist, then the installer uses the /tmp directory. The following are instructions for setting the TMP environment variable.
| C shell | Bourne/Korn shell |
|---|---|
|
|
TNS_ADMIN points to the directory where Net8 configuration files are stored.
If TNS_ADMIN is set on your system, you will have conflicts between that directory and the directory where the Oracle9i Application Server Net8 configuration files are created. You will also have conflicts if the configuration files are in a common directory outside of the Oracle home for your other Oracle product. For example, your system may use /var/opt/oracle/tnsnames.ora for database aliases.
To prevent conflicts between the Net8 configuration files for different Oracle products, copy the configuration files from either TNS_ADMIN or the common directory to ORACLE_HOME/network/admin for the other product and unset TNS_ADMIN using the following command.
| C shell | Bourne/Korn shell |
|---|---|
|
|
The following UNIX account and groups are required for the installation process.
Use the admintool or groupadd utility to create a group named oinstall. The oinstall group will own Oracle Universal Installer's oraInventory directory. The oracle user account that runs the installation must have the oinstall group as its primary group.
For more information on these utilities, refer to your operating system documentation.
The oracle account is the UNIX account that owns Oracle software for your system. You must run Oracle Universal Installer from this account.
Create an oracle account with the properties listed in Table 2-4.
|
Note:
Use the |
Two groups, the database operator group and the database administrator group, are required for installation. Oracle documentation refers to these groups as OSOPER and OSDBA, respectively. Databases use these groups for operating system authentication. This is necessary in situations where the database is shutdown and database authentication is unavailable.
The privileges of these groups are given to either a single UNIX group or two corresponding UNIX groups. There are two ways to choose which group(s) get the privileges:
oracle account is a member of the dba group before starting the installer, then dba is given the privileges of both OSOPER and OSDBA.
oracle account is not a member of the dba group, then the installer will prompt you for the group name(s) that get these privileges.
The following table lists the privileges for the OSOPER and OSDBA groups.
If you are migrating from a previous version of Oracle9i Application Server, including version 1.0.2.1, review the Oracle9i Application Server Migration Guide.
Oracle9i Application Server installs another database that listens on port 1521. This is so only if you install Enterprise Edition and configure Oracle9iAS Database Cache. To avoid port conflicts, change the port for the origin database listener to be, for example, 1526.
Oracle HTTP Server does not have a set port number that it listens on. It will automatically attempt to listen on 7777, but if that port number is in use, then it will search unoccupied port numbers such as 7778, 7779 (non SSL mode) to listen on. Similarly, if port 80 is in use for Oracle HTTP Server (SSL-enabled), then it will search unoccupied port numbers such as 7777 and greater, and if 443 is occupied, it will search for ports 4443 and greater.
A file named setupinfo.txt is automatically generated in ORACLE_HOME/Apache/Apache. This file is generated at install time, and is not updated thereafter. If the user restarts Oracle HTTP Server, the information in setupinfo.txt becomes inaccurate.
setupinfo.txt displays the port number information in the following format:
The HTTP Server can be accessed using the following URLs: Non SSL Mode (executed at install time): http://machine_name:7778 SSL mode: (executed at install time) http://machine_name:80 https://machine_name:443
After setting the environment variables and creating UNIX accounts and groups, complete version-specific pre-installation tasks for the Oracle9i Application Server.
The following list directs you to the installation option that you have license to:
Minimal Edition does not require any preinstallation tasks.
Oracle9i Application Server requires an active database connection. The installer uses this connection to add database objects to the origin database. The origin database is the original and primary storage for your data and is typically located on a database server tier.
You have completed the preinstallation tasks for the Oracle9i Application Server. Proceed to "About Oracle Universal Installer" to start the installer.
Perform preinstallation tasks for the following Standard Edition component:
Perform the following tasks on the origin database to set database parameters for Oracle Internet File System:
Installation of Oracle Internet File System requires reconfiguration of specific database parameters on the origin database.
Set the following Oracle initialization parameters to the values specified. These parameters are contained in the initSID.ora file in the ORACLE_HOME/admin/global_database_name/pfile directory.
open_cursors to at least 255.
shared_pool_size at least 50 MB.
processes to at least 200.
To verify that there is at least one online non-system rollback segment, connect to Oracle as the SYS user with SQL*Plus and execute the following SQL statement:
SQL> SELECT segment_name, tablespace_name, status
FROM dba_rollback_segs;
This will result in output that looks like the following table.
| SEGMENT_NAME | TABLESPACE_NAME | STATUS |
|---|---|---|
|
SYSTEM |
SYSTEM |
ONLINE |
|
PUBLIC_RS |
SYSTEM |
ONLINE |
|
USERS_RS |
USERS |
ONLINE |
In this example, USERS_RS is an online non-system rollback segment. To ensure that the rollback segment is always online after a database startup, include the following line in the initSID.ora file:
rollback_segments = (rbs_name1, .... , rbs_namex)
/etc/system file and modify the following variables:
SEMMSL to 10 plus the largest init.ora parameter, PROCESSES of any Oracle database on the machine.
SEMMNS to the sum of the PROCESSES parameter for each Oracle database, adding the largest one twice, then add an additional 10 for each database.
For more information, refer to Oracle8i Installation Guide.
SQL> SELECT name, value FROM v$parameter WHERE name = `open_cursors';
You should see the open_cursors value you entered in the initSID.ora file in step 2.
Oracle9i Application Server requires an active database connection. The installer uses this connection to add database objects to the origin database. The origin database is the original and primary storage for your data and is typically located on a database server tier.
You have completed the preinstallation tasks for the Oracle9i Application Server. Proceed to "About Oracle Universal Installer" to start the installer.
Perform preinstallation tasks for the following Enterprise Edition components:
For TCP/IP performance tuning tips for the computer running Oracle9iAS Web Cache, refer to Oracle HTTP Server powered by Apache Performance Guide available on your product CD.
Perform the following preinstallation tasks for Oracle9iAS Database Cache on the origin database machine:
SID
To use Oracle9iAS Database Cache, the name of your origin database and its System Identifier (SID) must be the same. You can see both the name and SID by executing the following commands in SQL*Plus when logged on as the sys user:
SQL> select value from v$parameter where name = 'db_name'; SQL> select instance_name from v$instance;
If these values are different, then you must perform the following steps on the origin database machine to change the SID:
ORACLE_SID environment variable to the new value. This new value must match the origin database name.
initSID.ora and orapwSID files to use the new SID.
listener.ora and tnsnames.ora files to use the new SID.
To allow remote access by Oracle9iAS Database Cache to the origin database, perform the following steps:
initSID.ora) of the origin database. If the file contains the REMOTE_LOGIN_PASSWORDFILE parameter, then make sure that the value equals SHARED or EXCLUSIVE. Oracle9iAS Database Cache can use either value. If the parameter is already set to either SHARED or EXCLUSIVE, then you do not need to change the value.
SYS and INTERNAL.
SYS and INTERNAL.
If the file does not contain the entry, then add it to the file, specifying either SHARED or EXCLUSIVE as the value. For example, to specify EXCLUSIVE, add the following entry to the file:
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
The initSID.ora file is in the ORACLE_HOME/database directory for of the origin database.
Check if a password file exists for the database. The file is named pwdSID.ora, where SID is the system identifier of the origin database.
orapwd utility with the following commands:
prompt>orapwd file=orapwSIDpassword=syspwentries=maxRemUsers
There are no spaces around the equal sign (=). The parameters have the following meanings:
SYS for the origin database. This parameter sets the password for SYSOPER and SYSDBA. If you issue the ALTER USER statement to change the password after connecting to the origin database, both the password stored in the data dictionary and the password stored in the password file are updated.
You must configure the listener for the origin database so that it listens for external procedure calls. Perform the following test to check for existing external procedure listener:
To test if you have an external procedure listener, you need to do a tnsping on EXTPROC_CONNECTION_DATA from the origin database. The command is:
prompt> tnsping EXTPROC_CONNECTION_DATA
TNS Ping Utility for Solaris: Version 8.1.7.0.0. - Production on 13-APR-2001 09:09:19 (c) Copyright 1997 Oracle Corporation. All rights reserved. Attempting to contact (ADDRESS= (PROTOCOL=IPC) (KEY=EXTPROC)) OK (102 msec)
TNS Ping Utility for Solaris: Version 8.1.7.0.0. - Production on 13-APR-2001 09:09:19 (c) Copyright 1997 Oracle Corporation. All rights reserved. TNS-03505: Failed to resolve name
Perform the following steps to configure an external procedure listener:
tnsnames.ora file for the origin database by adding an entry that enables you to connect to the listener process (and subsequently, the extproc process). For example, add the following entry to the tnsnames.ora file:
EXTPROC_CONNECTION_DATA.US.ORACLE.COM= (DESCRIPTION= (ADDRESS_LIST= (ADDRESS= (PROTOCOL=IPC) (KEY=EXTPROC0)) ) (CONNECT_DATA= (SID=PLSExtProc) (PRESENTATION= RO) ) )
Verify the following:
EXTPROC_CONNECTION_DATA". (Note that the domain name can be set to any value appropriate for your network.)
ADDRESS_LIST contains an ADDRESS entry setting "(PROTOCOL = IPC)".
Make a note of the KEY value (in this example, it is "EXTPROC0"). Also make a note of the SID value (in his example, it is "PLSExtProc"). These values must match the KEY and SID_NAME value, respectively, in the corresponding entry in the listener.ora file.
listener.ora file for the origin database and add the following entries for the external procedure listener:
LISTENER_01= (DESCRIPTION_LIST= (DESCRIPTION= (ADDRESS_LIST= (ADDRESS= (PROTOCOL= TCP) (HOST = my_hostname) (PORT = 1521)) ) (ADDRESS_LIST= (ADDRESS= (PROTOCOL= IPC) (KEY=EXTPROC0)) ) ) )
Verify the following:
ADDRESS_LIST contains an ADDRESS entry setting "(PROTOCOL = IPC)".
ADDRESS_LIST containing "(PROTOCOL = IPC) "has a key value which is the same KEY value from the tnsnames.ora file. In this example, the key value is "EXTPROC0".
Make a note of the name of the listener that will be used for external procedures. In this example, the listener name is "LISTENER_01".
listener.ora file and verify that there is a SID for external procedure listener in the listener's SID list.
SID_LIST_LISTENER= (SID_LIST= (SID_DESC= (SID_NAME=PLSExtProc) (ORACLE_HOME=/dsk1/oracle/rdbms/OraHome) (PROGRAM=extproc) )
...(SID_DESC = (GLOBAL_DBNAME = global_DBname) (ORACLE_HOME = /dsk1/oracle/rdbms/OraHome) (SID_NAME = ias) ) )
Verify the following:
prompt> lsnrctl stop listener_01 prompt> lsnrctl start listener_01
extproc process spawned by the listener inherits the operating system privileges of the listener. So Oracle Corporation strongly recommends that you restrict the privileges for the separate listener process. The process should not have permission to read or write to database files. The owner of this separate process should not be the oracle user (which is the default owner of the server executable and database files). Start the listener from a user account that does not have permission to read or write to database files or the Oracle server address space.
extproc executable in the bin directory under the ORACLE_HOME of the origin database.
sqlnet.ora:
NAMES.DEFAULT_DOMAIN = your.Domain.Name SQLNET.AUTHENTICATION_SERVICES= (NTS) NAMES.DIRECTORY_PATH= (TNSNAMES, ONAMES, HOSTNAME)
Perform the following tasks on the origin database machine to set database parameters for Oracle Internet File System:
Installation of Oracle Internet File System requires reconfiguration of specific database parameters on the origin database.
Set the following Oracle initialization parameters to the values specified. These parameters are contained in the initSID.ora file in the ORACLE_HOME/admin/global_database_name/pfile directory.
open_cursors to at least 255.
shared_pool_size at least 50 MB.
processes to at least 200.
To verify that there is at least one online non-system rollback segment, connect to Oracle as the SYS user with SQL*Plus and execute the following SQL statement:
SQL> SELECT segment_name, tablespace_name, status FROM dba_rollback_segs;
This will result in output that looks like the following table.
| SEGMENT_NAME | TABLESPACE_NAME | STATUS |
|---|---|---|
|
SYSTEM |
SYSTEM |
ONLINE |
|
PUBLIC_RS |
SYSTEM |
ONLINE |
|
USERS_RS |
USERS |
ONLINE |
In this example, USERS_RS is an online non-system rollback segment. To ensure that the rollback segment is always online after a database startup, include the following line in the initSID.ora file:
rollback_segments = (rbs_name1, .... , rbs_namex)
/etc/system file and modify the following variables:
SEMMSL to 10 plus the largest init.ora parameter, PROCESSES of any Oracle database on the machine.
SEMMNS to the sum of the PROCESSES parameter for each Oracle database, adding the largest one twice, then add an additional 10 for each database.
For more information, refer to Oracle8i Installation Guide.
SQL> SELECT name, value FROM v$parameter WHERE name = `open_cursors';
You should see the open_cursors value you entered in the initSID.ora file in step 2.
Oracle9i Application Server requires an active database connection. The installer uses this connection to add database objects to the origin database. The origin database is the original and primary storage for your data and is typically located on a database server tier.
You have completed the preinstallation tasks for the Oracle9i Application Server. Proceed to "About Oracle Universal Installer" to start the installer.
Oracle9i Application Server uses Oracle Universal Installer to configure environment variables and to install components. The installer guides you through each step of the installation process, so you can choose configuration options for a customized product.
The installer includes features that perform the following tasks:
The installer creates the oraInventory directory the first time it is run on your machine. The oraInventory directory keeps an inventory of products that the installer installs on your machine as well as other installation information. If you have previously installed Oracle products, then you may already have an oraInventory directory.
oraInventory directory. If another group attempts to run the installer, then they must have permission to write to the oraInventory directory. If they do not have permission, then the installation will fail.
oraInventory directory and all its files so that you are allowed to run the installer.
oraInventory is defined in /var/opt/oracle/oraInst.loc.
oraInventory_location/logs/installActions.log. Log file names of previous installation sessions take the form installActionsdatetime.log.
oraInventory directory or its contents. Doing so can prevent the installer from locating products that you have installed on your system.
Follow these steps to launch Oracle Universal Installer, which installs Oracle9i Application Server:
The Oracle Product Installation CD-ROM is in RockRidge format. If you are using the Solaris Volume Management software (installed by default in Sun SPARC Solaris), then the CD-ROM is mounted automatically to cdrom/9ias_1022_disk1 when you insert it in the disk drive. To begin installation, insert the CD labelled Disk 1.
If you are not using the Solaris Volume Management software, then you must mount the CD-ROM manually. To manually mount or unmount the CD-ROM, you must have root privileges. Be sure to unmount the CD-ROM before removing it from the drive.
To manually mount Disk 1 CD-ROM, perform the following tasks:
prompt> mkdir mount_point
prompt> mount options device_name mount_point prompt> exit
The following example mounts the CD-ROM manually on /cdrom, without using the Solaris Volume Management software. Execute the following commands as root user.
prompt> mkdir /cdrom prompt> mount -r -F hsfs device_name /cdrom prompt> exit
This launches Oracle Universal Installer through which you can install Oracle9i Application Server.
The list below navigates you to installation instructions for the Oracle9i Application Server edition you are licensed to:
|
 Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|