AppNote: Installing Oracle 10g Application Server on SLES9
Novell Cool Solutions: AppNote
By Michel Bluteau
Digg This -
Posted: 23 Sep 2005
Note: This article references another article - 15855 - from CoolSolutions on installing Oracle 10g DataBase on SLES9. This article is written separately for Application Server because there are some major differences in the prerequisites and installation steps.
I used a copy of Oracle Application Server 10g 10.1.2 that I downloaded from the Oracle web site (evaluation software) and combined that with SUSE Linux Enterprise Server 9, SP1.
Some prerequisites must be met before you start the installation. I suggest 1GB or RAM, and a 2 Gb Swap partition (1536 is the minimum). Also, you must use YaST (or the install process) to add the following optional packages included in the SLES9 distro:
- orarun (to take care of config files, kernel parameters and the like)
If you had these packages after the initial installation, I suggest you then run YaST Online Update to update the packages you got on the CDs. You may have to downgrade some packages while installing additional packages, so YOU will tie everything back together.
You should end up with 2 CDs if you download version 10.1.2 for Linux from the Oracle web site. The first step is to log as the oracle user (created by orarun, see the article on 10g Database for more details) and install a pair of patches.
1. As root (using su), run the 2 Perl scripts on the CD.
Figure 1: Running the Perl scripts
2. Start the runInstaller.
Figure 2: Starting runInstaller
The Installer warns you that some files need to be removed.
Figure 3: Installer warning
3. Use root (with su) to rename the files as shown.
Figure 4: Renaming files
4. Since you installed the 2 patches already, type Y then press Enter.
Figure 5: Proceeding after rename
The Installer warns you that a script must be executed using root.
Figure 6: Installer warning
5. Execute the script as root.
Figure 7: Script executed as root
The installer will run some diagnostics. Resolve any errors before you proceed.
Figure 8: Installer diagnostics
The Oracle Universal Installer appears.
6. Select the installation type, the instance name and the global database name, and type the password (must contain letters and numbers). Write this info down.
The Oracle Universal Installer appears.
Figure 9: Oracle Universal Installer
7. Run the following script as root before you continue.
Figure 10: Another script executed as root
Figure 11: Executing the script as root
The Preparing to Install window appears.
Figure 12: Preparing to Install window
The Install window now shows the progress bar.
Figure 13: Install window with progress bar
You may or may not see the error window shown below, or a similar one. If it indicates that the README file is missing from the CDs, note that this file is not essential.
Figure 14: Error window
You can ignore the error, or create an empty file so the Installer can assign the rights to it. Use the Oracle account and the touch command to do this.
Figure 15: Creating an empty file so Installer can assign rights
The Database Configuration Assistant will launch.
Figure 16: Database Configuration Assistant
Several Configuration Assistants will run in turns.
Figure 17: Configuration Assistants
Troubleshooting during the Install
You may get the error shown below during the installation, because some components are installed twice.
Figure 18: Error - some components installed twice
To handle this, you can again create an empty file using the Oracle account.
Figure 19: Empty file with Oracle account
You may also get error windows like this one during the Configuration Assistants:
Figure 20: Error window during the Configuration Assistants
This time, the OC4J Instance Configuration Assistant seems to indicate that concurrent changes to a config file is the source of the problem. You can click the Retry button until the component successfully installs.
Figure 21: Error- concurrent changes to a config file
After 2 Retry clicks, I was able to overcome my error on OC4J.
Figure 22: Resolving the error
Once you complete the installation successfully, the following window appears. You should write down this information or save it to a text file on the desktop - or a create a shortcut for the setupinfo.txt file on the desktop.
Figure 23: Success window
1. Modify the file /etc/oratab using root so the database starts automatically. Otherwise, you must use commands like "/etc/init.d/oracle start".
Figure 24: Modifying the /etc/oratab file
2. Copy oratab to /var/opt/oracle/ because at startup this is where Oracle will look for it.
Figure 25: Copying oratab to /var/opt/oracle/
3. Edit /etc/sysconfig/oracle to make sure that the Database will start automatically.
Figure 26: Editing /etc/sysconfig/oracle
4. Indicate that Apache should start automatically.
Figure 27: Indicating Apache auto-start
5. You also want Oracle Internet Directory to start automatically.
Figure 28: Indicating Oracle Internet Directory auto-start
6. Use a browser like Mozilla to access Application Server, using the info contained in setupinfo.txt.
Accessing the Application Server via Mozilla
7. Authenticate using ias_admin and the password you selected earlier.
Figure 30: Authenticate with ias_admin and password
Once authenticated, you will see the welcome page for Enterprise Manager. You can see 2 instances - one for the Application Server and one for the Infrastructure.
Figure 31: Welcome page for Enterprise Manager - Application Server and Infrastructure.
For each instance, you can obtain information on resource usage, troubleshooting problems, etc.
Figure 32: Info on resource usage, troubleshooting, etc.
The installation process also installed some client tools like sqlplus and oidadmin:
Figure 33: Client tools sqlplus and oidadmin8. Launch oidadmin from a shell screen using the Oracle account.
Figure 34: Launching oidadmin from a shell screen
9. Create a Directory Server Connection before you administer OID.
Figure 35: Creating a Directory Server Connection
10. When the Directory Server Name Manager appears, click Add.
Figure 36: Directory Server Name Manager
11. In the Enterprise Manager, under Infrastructure, figure out which port OID is listening on.
Figure 37: Determining the port where OID listens
12. Create a Directory Server Connection using this information.
Figure 38: Creating a Directory Server Connection
13. Click Select to connect.
Figure 39: Connecting to the Directory Server
14. To log in, specify user cn=orcladmin and use the same password you selected for ias_admin.
Figure 40: Logging in
The Oracle Directory Manager Welcome screen appears.
Figure 41: Oracle Directory Manager Welcome screen.
In the Oracle Directory Manager you can browse entries:
Figure 42: Oracle Directory Manager, browsing entries
Some services may need to be started manually after a restart.In order to manually start OID,
- Log in as "oracle".
- Export ORACLE_HOME=/opt/oracle/product/10.1.2/OracleAS_3/infra/
- cd /opt/oracle/product/10.1.2/OracleAS_3/infra/bin
- Run this command: ./oidmon connect=Ora10gAS start&
In order to manually start the Enterprise Management Service and Portal, use the following steps:
- Log in as "oracle".
- cd /opt/oracle/product/10.1.2/OracleAS_3/portal/bin
- Run this command: ./emctl start iasconsole&
- Use your browser to connect to http://ora10gas.novl.ca:1811
- Log in as "ias_admin", then select to restart all services.
See the Oracle Application Server 10g Documentation for more options.
I introduced Oracle Internet Directory in this article so I can leverage OID in an upcoming article on how to integrate Oracle with Novell eDirectory and Identity Manager.
Feedback, comments and questions are welcome, as usual. I hope that this article will prove to be useful to you.
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com