In this article, we have documented the details of installation process.
- Configure Security Updates
- You can check the option if you wish to receive security updates via My Oracle Support.
- You can choose the option to update software by providing your credentials or skip it.
- For my purpose, I have selected "Create and configure a database."
- For upgrade, you can select "Upgrade an existing database" option.
- Depends on your system, you can select either
- Desktop Class--for a starter database, which allows minimal configuration
- Server Class--for an advanced database, which allows more advanced configuration options.
- You select the type of database installation you want to perform. For instance, I've chosen "Single instance database installation" here. Other options include:
- Oracle Real Application Clusters database installation
- Oracle RAC One Node database installation
- Two options are available:
- See Figure 1 for details
- Administrative password
- This is the password for "SYS" and "SYSTEM" database accounts. Note that it is case sensitive since Oracle Database 11g Release 1.
- Global Database Name (GDN)
- In a distributed database system, each database should have a unique global database name. Global database names uniquely identify a database in the system.
- For example, we have used orcl.us.oracle.com as our GDN. Note that "orcl" in the GDN will become system identifier (SID).
- We have seen three issues:
- User with Same UID
- You can ignore this although it has some complications; see 
- Swap Size
- See  for how to fix it
- OS Kernel Parameter shmmax
- You should try to fix these issues based on suggestions.
At step 10, a "Data Configuration Assistant" window will be shown. On it, there is a "Password Management" button. At this moment, all database accounts except SYS, SYSTEM and DBSNMP are locked. So, from the Password Management window, you can unlock all other accounts you want to use.
Then an information window "Execute Configuration Scripts" is shown to advise you to execute a script named "root.sh" as "root" user.
Here is the result from the execution of root.sh:
Performing root user operation for Oracle 11g
The following environment variables are set as:
Enter the full pathname of the local bin directory: [/usr/local/bin]: /usr/local/bin
Creating /usr/local/bin directory...
Copying dbhome to /usr/local/bin ...
Copying oraenv to /usr/local/bin ...
Copying coraenv to /usr/local/bin ...
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
Finished product-specific root actions.
At step 11, you should finally see the following message:
- The installtion of Oracle Database was successful.
- Global Database Name
- 11G R2 client install complains about two root users - RHL 5.2
- Swap Size - This Is a Prerequisite Condition Tested during Oracle Installation
- What’s the Difference between the SYS and SYSTEM Schemas?
- Global Database Name in Oracle Database 11g
- Oracle® Database 2 Day DBA 11g Release 1 (11.1)
- Using Database Configuration Assistant to Create Additional Databases
- Using Net Configuration Assistant to Configure a Listener
- How I Simplified Oracle Database Installation on Oracle Linux
- Case Sensitive Passwords in Oracle Database 11g Release 1
- Oracle® Database Installation Guide 11g Release 2 (11.2) for Linux