Quick Installation Guide
10g Release 2 (10.2) for Solaris Operating System (x86)
B31215-01
June 2006
Oracle Database Quick Installation Guide, 10g Release 2 (10.2) for Solaris Operating System (x86)
B31215-01
Copyright © 2006, Oracle. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.
This guide describes how to quickly install Oracle Database 10g on Solaris x86 systems. It includes information about the following:
This guide describes how to install Oracle Database by using the default installation options.
The procedures in this guide describe how to:
Configure your system to support Oracle Database
Install Oracle Database on a local file system by using the Basic Installation option
Configure a general-purpose Oracle Database installation that uses the local file system for database file storage
Results of a Successful Installation
After you successfully install Oracle Database:
The database that you created and the default Oracle Net listener process run on the system.
Oracle Enterprise Manager Database Control and iSQL*Plus are running and can be accessed by using a Web browser.
Tasks Not Described in This Guide
This guide covers the Basic Installation scenario and does not describe how to complete the following tasks:
Using the Advanced Installation option to install the software
Installing the software on a system that has an existing Oracle software installation
Installing Oracle Clusterware and Oracle Real Application Clusters (RAC) on a cluster
Enabling Enterprise Manager e-mail notifications or automated backups
Using alternative storage options such as Automatic Storage Management or raw devices for database storage
Where to Get Additional Installation Information
For more information about installing Oracle Database, including information about the tasks not described in this guide, refer to one of the following guides:
If you want to install the software on a single system, then refer to Oracle Database Installation Guide for Solaris Operating System (x86).
If you want to perform a RAC installation, then refer to Oracle Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide for Solaris Operating System. This guide also describes how to install Oracle Clusterware, which is a prerequisite for RAC installations.
Both these guides are available on the product disc. To access them, use a Web browser to open the welcome.htm file located in the top-level directory of the installation media, and then select the Documentation tab.
Before you install Oracle Database, you must complete several tasks as the root user. To log in as the root user, complete one of the following procedures:
Note:
You must install the software from an X Window System workstation, an X terminal, or a PC or other system with X server software installed.If you are installing the software from an X Window System workstation or X terminal, then:
Start a local terminal session, for example, an X terminal (xterm).
If you are not installing the software on the local system, then enter the following command to enable the remote host to display X applications on the local X server:
$ xhost fully_qualified_remote_host_name
For example:
$ xhost somehost.us.acme.com
If you are not installing the software on the local system, then use the ssh, rlogin, or telnet command to connect to the system where you want to install the software:
$ telnet fully_qualified_remote_host_name
If you are not logged in as the root user, then enter the following command to switch user to root:
$ su - root password: #
If you are installing the software from a PC or other system with X server software installed, then:
Note:
If necessary, refer to your X server documentation for more information about completing this procedure. Depending on the X server software that you are using, you may need to complete the tasks in a different order.Start the X server software.
Configure the security settings of the X server software to permit remote hosts to display X applications on the local system.
Connect to the remote system where you want to install the software, and start a terminal session on that system, for example, an X terminal (xterm).
If you are not logged in as the root user on the remote system, then enter the following command to switch user to root:
$ su - root password: #
The system must meet the following minimum hardware requirements:
At least 512 MB of physical RAM
The following table describes the relationship between installed RAM and the configured swap space requirement.
| RAM | Swap Space |
|---|---|
| Up to 512 MB | 2 times the size of RAM |
| Between 1024 MB and 2048 MB | 1.5 times the size of RAM |
| Between 2049 MB and 8192 MB | Equal to the size of RAM |
| More than 8192 MB | 0.75 times the size of RAM |
400 MB of disk space in the /tmp directory
Between 1.5 GB and 3.5 GB of disk space for the Oracle software, depending on the installation type
1.2 GB of disk space for a preconfigured database that uses file system storage (optional)
Note:
The disk space requirement for databases that use Automatic Storage Management or raw device storage is described later in this chapter.Additional disk space, either on a file system or in an Automatic Storage Management disk group, is required for the flash recovery area if you choose to configure automated backups.
To ensure that the system meets these requirements, follow these steps:
To determine the physical RAM size, enter the following command:
# /usr/sbin/prtconf | grep "Memory size"
If the size of the physical RAM installed in the system is less than the required size, then you must install more memory before continuing.
To determine the size of the configured swap space, enter the following command:
# /usr/sbin/swap -s
If necessary, refer to your operating system documentation for information about how to configure additional swap space.
To determine the amount of free disk space available in the /tmp directory, enter the following command:
# df -k /tmp
If there is less than 400 MB of disk space available in the /tmp directory, then complete one of the following steps:
Delete unnecessary files from the /tmp directory.
Set the TMP and TMPDIR environment variables when setting the oracle user's environment (described later).
Extend the file system that contains the /tmp directory. If required, contact your system administrator for information about extending file systems.
To determine the amount of free disk space available on the system, enter the following command:
# df -k
The following table shows the approximate disk space requirements for software files for each installation type.
| Installation Type | Requirement for Software Files (GB) |
|---|---|
| Enterprise Edition | 2.0 |
| Standard Edition | 1.5 |
| Custom (maximum) | 2.5 |
To determine whether the system architecture can run the software, enter the following command:
# /bin/isainfo -kv
This command displays the processor type. Verify that the processor architecture matches the Oracle software release that you want to install.
The following is the expected output of this command:
32-bit i386 kernel modules
If you do not see the expected output, then you cannot install the software on this system.
The system must meet the following minimum software requirements, depending on the distribution and version of your operating system:
Note:
Oracle Universal Installer performs checks on your system to verify that it meets the listed requirements. To ensure that these checks pass, verify the requirements before you start Oracle Universal Installer.The operating system version must be Solaris 10.
The following packages (or later versions) must be installed:
SUNWarc SUNWbtool SUNWhea SUNWlibm SUNWlibms SUNWsprot SUNWtoo SUNWi1of SUNWi1cs SUNWi15cs SUNWxwfnt
For the Oracle products that you want to install, the system must meet the following product-specific requirements:
Oracle Messaging Gateway
Oracle Messaging Gateway supports the integration of Oracle Streams Advanced Queuing (AQ) with the following software:
IBM MQSeries V6.0, client and server
Tibco Rendezvous 7.2
PL/SQL native compilation, Pro*C/C++, Oracle Call Interface, Oracle C++ Call Interface, and Oracle XML Developer's Kit (XDK)
Sun ONE Studio 10 (C and C++ 5.5)
gcc 3.4.2
Oracle JDBC/OCI Drivers
You can use the following versions of JDK with the Oracle JDBC/OCI drivers:
However, they are not required for the installation.
Sun Java 2 SDK Standard Edition 1.3.1_11 and the JNDI extension
Sun Java 2 SDK Standard Edition 1.2.2_17 and the JNDI extension
Note: JDK 1.4.2_08 is installed with this release.
To ensure that the system meets these requirements, follow these steps:
To determine which version of Solaris is installed, enter the following command:
# uname -r
To determine whether the required packages are installed, enter a command similar to the following:
# pkginfo -i SUNWarc SUNWbtool SUNWhea SUNWlibm \ SUNWlibms SUNWsprot SUNWsprox SUNWtoo SUNWi1of \ SUNWi1cs SUNWi15cs SUNWxwfnt
If a package is not installed, or if the version is lower than the required version, then install it.
In addition, you need to verify that the following patches, or later versions, are installed on the system. The procedure following the table describes how to check these requirements.
Note:
There may be more recent versions of the patches listed installed on the system. If a listed patch is not installed, determine whether a more recent version is installed before installing the version listed.For all installations on Solaris 10, the following patches are required:
118345-03: SunOS 5.10_x86: ld & libc.so.1 Patch
119961-01: SunOS 5.10_x86, x64, Patch for assembler
For PL/SQL native compilation and installation of Pro*C/C++, Oracle Call Interface, Oracle C++ Call Interface, or Oracle XML Developer's Kit (XDK) on Solaris 10, the following patches are required:
117837-05: Optimizer compiler patch for C++ compiler
117846-08: Optimizer Compiler patch for C++ compiler
118682-01: Patch for SS10_x86 debuginfo handling
For Oracle Messaging Gateway installation, the following corrective service diskettes (CSDs) for WebSphere MQ are required:
CSD09 or later for MQSeries V6.0
MQSeries PTF U478911 SupportPac MACE
To ensure that the system meets these requirements, follow these steps:
To determine whether an operating system patch is installed, enter a command similar to the following:
# /usr/sbin/patchadd -p | grep patch_number
If an operating system patch is not installed, then download it from the following Web site and install it:
http://sunsolve.sun.com
If you require a CSD or a SupportPac for WebSphere MQ, refer to the following Web site for download and installation information:
http://www.ibm.com/software/integration/mqfamily/support/summary/sun.html
The following local operating system groups and users are required if you are installing Oracle Database:
The Oracle Inventory group (oinstall)
The OSDBA group (dba)
The Oracle software owner (oracle)
An unprivileged user (nobody)
To determine whether these groups and users already exist, and if necessary, to create them, follow these steps:
To determine whether the oinstall group exists, enter the following command:
# more /var/opt/oracle/oraInst.loc
If the oraInst.loc file exists, then the output from this command is similar to the following:
inventory_loc=/u01/app/oracle/oraInventory inst_group=oinstall
The inst_group parameter shows the name of the Oracle Inventory group, oinstall.
To determine whether the dba group exists, enter the following command:
# grep dba /etc/group
If the output from this commands shows the dba group name, then the group already exists.
If necessary, enter the following commands to create the oinstall and dba groups:
# /usr/sbin/groupadd oinstall # /usr/sbin/groupadd dba
To determine whether the oracle user exists and belongs to the correct groups, enter the following command:
# id -a oracle
If the oracle user exists, this command displays information about the groups to which the user belongs. The output should be similar to the following, indicating that oinstall is the primary group and dba is a secondary group:
uid=440(oracle) gid=200(oinstall) groups=201(dba),202(oper)
If necessary, complete one of the following actions:
If the oracle user exists, but its primary group is not oinstall or it is not a member of the dba group, then enter the following command:
# /usr/sbin/usermod -g oinstall -G dba oracle
If the oracle user does not exist, enter the following command to create it:
# /usr/sbin/useradd -g oinstall -G dba oracle
This command creates the oracle user and specifies oinstall as the primary group and dba as the secondary group.
Enter the following command to set the password of the oracle user:
# passwd -r files oracle
To determine whether the nobody user exists, enter the following command:
# id nobody
If this command displays information about the nobody user, then you do not have to create the user.
If the nobody user does not exist, then enter the following command to create it:
# /usr/sbin/useradd nobody
Verify that the following kernel parameters are set to values greater than or equal to the recommended value shown:
| Parameter | Replaced by Resource Control | Recommended Value |
|---|---|---|
| noexec_user_stack | NA | 1 |
| semsys:seminfo_semmni | project.max-sem-ids |
100 |
| semsys:seminfo_semmns | NA | 1024 |
| semsys:seminfo_semmsl | project.max-sem-nsems |
256 |
| semsys:seminfo_semvmx | NA | 32767 |
| shmsys:shminfo_shmmax | project.max-shm-memory |
4294967295 |
| shmsys:shminfo_shmmin | NA | 1 |
| shmsys:shminfo_shmmni | project.max-shm-ids |
100 |
| shmsys:shminfo_shmseg | NA | 10 |
Note:
If the current value for any parameter is higher than the value listed in this table, then do not change the value of that parameter.To view the current value specified for these kernel parameters, and to change them if necessary, follow these steps:
To view the current values of these parameters, enter the following commands:
# id -p // to verify the project id uid=0(root) gid=0(root) projid=1 (user.root) # prctl -n project.max-shm-memory -i project user.root # prctl -n project.max-sem-ids -i project user.root
If you must change any of the current values, then follow these steps:
To modify the value of max-shm-memory to 6 GB:
# prctl -n project.max-shm-memory -v 6gb -r -i project user.root
To modify the value of max-sem-ids to 256:
# prctl -n project.max-sem-ids -v 256 -r -i project user.root
Note:
When you use theprctl command (Resource Control) to change system parameters, you do not need to restart the system for these parameter changes to take effect. However, the changed parameters do not persist after a system restart.Use the following procedure to modify the resource control project settings, so that the settings are available after a system restart:
By default, Oracle instances are run as the oracle user of the dba group . A project with the group.dba name is created to serve as the default project for the oracle user. Run the id command to verify the default project for the oracle user:
# su - oracle $ id -p uid=100(oracle) gid=100(dba) projid=100(group.dba) $ exit
To set the maximum shared memory size to 2 GB, add the project.max-shm-memory=(privileged, 2147483648,deny) resource control to the last field of the project entries for the Oracle project or run the projmod command:
# projmod -sK "project.max-shm-memory=(privileged, 2G,deny)" group.dba
After these steps are complete, the /etc/project file should contain the following:
# cat /etc/project
The following is the output of the command:
system:0:::: user.root:1:::: noproject:2:::: default:3:::: group.staff:10:::: group.dba:100:Oracle default project:::project.max-shmmemory=(privileged,2147483648,deny)
To verify that the resource control is active, run the id and prctl commands:
# su - oracle
$ id -p
uid=100(oracle) gid=100(dba) projid=100(group.dba)
$ prctl -n project.max-shm-memory -i process $$
process: 5754: -bash
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
project.max-shm-memory
privileged 2.00GB - deny
Note:
For additional information, refer to the Solaris Tunable Parameters Reference Manual.Create directories with names similar to the following, and specify the correct owner, group, and permissions for them:
The Oracle base directory
An optional Oracle data file directory (optional)
The Oracle base directory must have 3 GB of free disk space, or 4 GB of free disk space if you choose not to create a separate Oracle data file directory.
Note:
If you do not want to create a separate Oracle data file directory, you can install the data files in a subdirectory of the Oracle base directory. However, this is not recommended for production databases.To determine where to create these directories:
Enter the following command to display information about all mounted file systems:
# df -k
This command displays information about all the file systems mounted on the system, including:
The physical device name
The total amount, used amount, and available amount of disk space
The mount point directory for that file system
From the display, identify either one or two file systems that meet the following requirements:
A single file system with at least 1.2 GB of free disk space
Two or more file systems with at least 1.2 GB of free disk space in total
Note the name of the mount point directory for each file system that you identified.
In the following examples, /u01 is the mount point directory used for the software, and /u02 is the mount point directory used for the Oracle data file directory. You must specify the appropriate mount point directories for the file systems on your system.
To create the required directories and specify the correct owner, group, and permissions for them:
Note:
In the following procedure, replace/u01 and /u02 with the appropriate mount point directories that you identified in Step 3 previously.Enter the following command to create subdirectories in the mount point directory that you identified for the Oracle base directory:
# mkdir -p /u01/app/oracle
If you intend to use a second file system for the Oracle Database files, then create an oradata subdirectory in the mount point directory that you identified for the Oracle data file directory (shown as /u02 in the examples):
# mkdir /u02/oradata
Change the owner and group of the directories that you created to the oracle user and the oinstall group:
# chown -R oracle:oinstall /u01/app/oracle # chown -R oracle:oinstall /u02/oradata
Change the permissions on the directories that you created to 775:
# chmod -R 775 /u01/app/oracle # chmod -R 775 /u02/oradata
You run Oracle Universal Installer from the oracle account. However, before you start Oracle Universal Installer, you must configure the environment of the oracle user. To configure the environment, you must:
Set the default file mode creation mask (umask) to 022 in the shell startup file.
Set the DISPLAY environment variable.
To set the oracle user's environment:
Start a new terminal session, for example, an X terminal (xterm).
Enter the following command to ensure that X Window applications can display on this system:
$ xhost fully_qualified_remote_host_name
Complete one of the following steps:
If the terminal session is not connected to the system where you want to install the software, then log in to that system as the oracle user.
If the terminal session is connected to the system where you want to install the software, then switch user to oracle:
$ su - oracle
To determine the default shell for the oracle user, enter the following command:
$ echo $SHELL
Open the oracle user's shell startup file in any text editor:
Bourne shell (sh), Bash shell on SUSE (bash), or Korn shell (ksh):
$ vi .profile
C shell (csh or tcsh):
% vi .login
Enter or edit the following line in the shell startup file, specifying a value of 022 for the default file mode creation mask:
umask 022
If the ORACLE_SID, ORACLE_HOME, or ORACLE_BASE environment variable is set in the file, then remove the appropriate lines from the file.
Save the file, and exit from the editor.
To run the shell startup script, enter the following command:
Bash shell:
$ . ./.bash_profile
Bourne shell, or Korn shell:
$ . ./.profile
C shell:
% source ./.login
If you are not installing the software on the local system, then enter a command similar to the following to direct X applications to display on the local system:
Bourne, Bash, or Korn shell:
$ DISPLAY=local_host:0.0 ; export DISPLAY
C shell:
% setenv DISPLAY local_host:0.0
In this example, local_host is the host name or IP address of the system that you want to use to display Oracle Universal Installer (your workstation or PC).
If you determined that the /tmp directory had insufficient free disk space when checking the hardware requirements, then enter the following commands to set the TMP and TMPDIR environment variables. Specify a directory on a file system with sufficient free disk space.
Bourne, Bash, or Korn shell:
$ TMP=/mount_point/tmp $ TMPDIR=/mount_point/tmp $ export TMP TMPDIR
C shell:
% setenv TMP /mount_point/tmp % setenv TMPDIR /mount_point/tmp
Enter commands similar to the following to set the ORACLE_BASE and ORACLE_SID environment variables:
Bourne, Bash, or Korn shell:
$ ORACLE_BASE=/u01/app/oracle $ ORACLE_SID=sales $ export ORACLE_BASE ORACLE_SID
C shell:
% setenv ORACLE_BASE /u01/app/oracle % setenv ORACLE_SID sales
In these examples, /u01/app/oracle is the Oracle base directory that you created earlier, and sales is the name that you want to call the database (typically no more than five characters).
Enter the following commands to ensure that the ORACLE_HOME and TNS_ADMIN environment variables are not set:
Bourne, Bash, or Korn shell:
$ unset ORACLE_HOME $ unset TNS_ADMIN
C shell:
% unsetenv ORACLE_HOME % unsetenv TNS_ADMIN
To verify that the environment has been set correctly, enter the following commands:
$ umask $ env | more
Verify that the umask command displays a value of 22, 022, or 0022 and the environment variables that you set in this section have the correct values.
On most Solaris systems, the product disc mounts automatically when you insert it into the drive. If the disc does not mount automatically, then follow these steps to mount it:
Switch user to root:
$ su - root
If necessary, enter a command similar to the following to eject the currently mounted disc, then remove it from the drive:
# eject
Insert the appropriate disc into the disc drive.
To verify that the disc mounted automatically, enter a command similar to the following:
# ls /dvd/dvd0
If this command fails to display the contents of the disc, then enter a command similar to the following:
# /usr/sbin/mount -r -F hsfs /dev/dsk/cxtydzs2 /dvd
In this example, /dvd is the disc mount point directory and /dev/dsk/cxtydzs2 is the device name for the disc device, for example /dev/dsk/c0t6d0s2.
If Oracle Universal Installer displays the Disk Location dialog box, then enter the disc mount point directory path. For example:
Disc mounted automatically:
/dvd/dvd0
Disc mounted manually:
/dvd
After configuring the oracle user's environment, start Oracle Universal Installer and install Oracle Database, as follows:
Note:
If you are installing the software from a DVD, then use a command similar to the following:
$ /mount_point/db/runInstaller
To start Oracle Universal Installer, enter the following commands:
If the installation files are on disc, enter commands similar to the following, where directory_path is the path of the db directory on the DVD:
$ cd /tmp
$ /directory_path/runInstaller
If the installation files are on the hard disk, change directory to the db directory and enter the following command:
$ ./runInstaller
If Oracle Universal Installer does not start, then refer to Oracle Database Installation Guide for Solaris Operating System (x86) for information about how to troubleshoot X Window display problems.
The following table describes the recommended action for each Oracle Universal Installer screen. Use the following guidelines to complete the installation:
If you need more assistance, or if you want to choose an option that is not a default, then click Help for additional information.
If you encounter errors while installing or linking the software, then refer to Oracle Database Installation Guide for Solaris Operating System (x86) for information about troubleshooting.
Note:
If you have completed the tasks listed previously, then you can complete the installation by choosing the default values on most screens.| Screen | Recommended Action |
|---|---|
| Select Installation Method | The Basic Installation option is selected by default.
Specify the directory path of the Oracle home. Ensure that the UNIX DBA group Note: This screen consists of Basic Installation and Advanced Installation options. Select the Advanced Installation option if you intend to use custom installation. |
| Specify Inventory Directory and Credentials | This screen is displayed only during the first installation of Oracle products on a system.
Specify the full path of the Oracle Inventory directory. Ensure that the operating system group selected is |
| Product-Specific Prerequisite Checks | Verify that all of the prerequisite checks succeed, then click Next.
Oracle Universal Installer checks the system to verify that it is configured correctly to run Oracle software. If you have completed all of the preinstallation steps in this guide, all of the checks should pass. If a check fails, then review the cause of the failure listed for that check on the screen. If possible, rectify the problem and rerun the check. Alternatively, if you are satisfied that your system meets the requirements, then you can select the check box for the failed check to manually verify the requirement. |
| Summary | Review the information displayed on this screen, and then click Install. |
| Install | This screen displays status information while the product is being installed. |
| Configuration Assistants | This screen displays status information for the configuration assistants that configure the software and create a database. When the message is displayed at the end of this process, click OK to continue. |
| Execute Configuration Scripts | When prompted, read the instructions and then run the scripts mentioned on this screen. Click OK to continue. |
| End of Installation | The configuration assistants configure several Web-based applications, including Oracle Enterprise Manager Database Control. This screen displays the URLs configured for these applications. Make a note of the URLs used. The port numbers used in these URLs are also recorded in the following file:
oracle_home/install/portlist.ini
To exit from Oracle Universal Installer, click Exit and then click Yes. |
The Oracle Database 10g Companion CD contains additional products that you can install. Whether you need to install these products depends on which Oracle Database products or features you plan to use. If you plan to use the following products or features, then you must complete the Oracle Database 10g Products installation from the Companion CD:
JPublisher
Oracle JVM
Oracle interMedia
Oracle JDBC development drivers
Oracle SQLJ
Oracle Database Examples
Oracle Text supplied knowledge bases
Oracle Ultra Search
Oracle HTML DB
Oracle Workflow server and middle-tier components
For more information about installing software from the Companion CD, refer to Oracle Database Companion CD Quick Installation Guide for Solaris Operating System (x86).
To become familiar with this release of Oracle Database, it is recommended that you complete the following tasks:
Log in to Oracle Enterprise Manager Database Control using a Web browser.
Oracle Enterprise Manager Database Control is a Web-based application that you can use to manage a single Oracle Database installation. The default URL for Database Control is similar to the following:
http://host.domain:1158/em/
To log in, use the user name SYS and connect as SYSDBA. Use the password that you specified for this user during the Oracle Database 10g installation.
Refer to Oracle Database Installation Guide for Solaris Operating System (x86) for information about required and optional postinstallation tasks, depending on the products that you want to use.
Refer to Oracle Database Installation Guide for Solaris Operating System (x86) for information about how to use Database Control to learn about the configuration of your installed database.
To learn more about using Oracle Enterprise Manager Database Control to administer a database, refer to Oracle Database 2 Day DBA.
This guide, designed for new Oracle DBAs, describes how to use Database Control to manage all aspects of an Oracle Database installation. It also provides information about how to enable e-mail notifications and automated backups, which you might not have configured during the installation.
This section contains information about the following:
You are welcome to install and evaluate the products included in this media pack for 30 days under the terms of the Trial License Agreement. However, you must purchase a program license if you want to continue using any product after the 30 day evaluation period. See the following section for information about purchasing program licenses.
Purchasing Licenses, Version Updates, and Documentation
You can purchase program licenses, updated versions of Oracle products, and printed versions of Oracle documentation from the Oracle Store Web site:
Contacting Oracle Support Services
If you have purchased Oracle Product Support, you can call Oracle Support Services for assistance 24 hours a day, seven days a week. For information about purchasing Oracle Product Support or contacting Oracle Support Services, go to the Oracle Support Services Web site:
Locating Product Documentation
Documentation for Oracle products is available in both HTML and Adobe portable document format (PDF) formats from several locations:
On discs in the media pack:
Platform-specific documentation is available on the product discs. To access this documentation, see the welcome.htm file located in the top-level directory of the installation media.
Generic product documentation is available in the Oracle Documentation Library.
From the Oracle Technology Network Web site:
To view PDF documents, download the free Adobe Acrobat Reader from the Adobe Web site, if necessary:
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
TTY Access to Oracle Support Services
Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.