This article describes the steps required in order to setup Oracle 10g R2 Database (Enterprise Edition) on SUSE Linux Enterprise Server 10. Please note that this is not a supported configuration, and the purpose of this guide is to preview the steps and some new tools or updated tools for managing Oracle that come with SLES 10.
Oracle will probably release an updated version soon(not yet available at the time this article was written) so keep an eye on the support matrix available via:
I have done some extensive testing for Oracle 10g R2 DB on SLES 10 starting with RC3(Release Candidate 3) and now the final version, and the combination seems to be rock solid. The installation steps do not differ greatly between the installation on SLES 9 and SLES 10, only a few minor adjustments are required.
N.B. I recommend that you allocate 1GB or RAM and 1024MB of swap space before you start the installation.
Figure 0: Oracle server pattern through YaST, also available during the installation.
Figure 1: SLES10 comes with some in-the-box utilities/packages for managing Oracle. Make sure the orarun package, and the new ocfs2 packages, are installed.
Figure 2: The orarun package creates a User for Oracle and sets the appropriate Groups, as shown through YaST.
The oracle user is created by the orarun package, but will not be able to login because it is disabled by default. We need to modify /etc/passwd in order to set a shell other than /bin/false for the oracle user.
Figure 3: /etc/passwd file with the oracle user disabled.
Figure 4: /etc/passwd with the shell set to /bin/bash for the oracle user.
We also need to set the password for the oracle user before we can login.
Figure 5: Changing the password for the oracle user.
In order to be able to install Oracle 10g R2 on SLES 10, we need to trick the Oracle Installer into thinking that we are sitting on top of a supported OS(remember that SLES10 is not yet supported for Oracle DB Enterprise Edition). The installer checks one file, /etc/SUSE-release, and we can modify the file temporarily in order for the Installer to proceed.
Figure 6: Making a backup copy of the /etc/SUSE-release file.
Figure 7: /etc/SUSE-release original content for SLES10.
Figure 8: /etc/SUSE-release file modified to trick the Installer into thinking we are installing on SLES9.
Now, we are ready to proceed with the installation. Log out and log back in as oracle, and start a terminal window. Then start the installer from the cd.
Figure 9: Launching the installer from the CD.
Figure 10: The installer first makes sure that the requirements are met. All the tests, including the OS version test, must be Passed(not failed) for the Universal Installer to be launched.
One the requirements are met, Oracle Universal Installer will be started.
Figure 11: Oracle Universal Installer. You can change the UNIX DBA Group to dba or leave it as disk. You can select the Advanced Installation if you need more control over the options. Basic Installation is a good way to get a demonstration instance fast and is probably a good idea for the first time you install.
Figure 12: Default options for the inventory directory and OS group name.
Figure 13: Product-Specific Prerequisite Checks.
It is recommended that each check be successful(Passed) before you move on with the installation. You should note the explanations for the failed check, exit the Installer, address the issues, and then re-launch the installer.
Some errors are critical, while others will still allow the installation to complete successfully. For example, the above error for the port range should not be an issue that will affect the installation.
Figure 14: Example of a failed check for the memory requirements. Note that the memory requirements have been increased with 10g Release 2. The installation will complete successfully anyway with 504MB of memory, but I would not recommend less than 1GB for a production or a real test system in the lab.
Figure 15: Another example, failed swap space requirements. It is recommended that you allocate at least 1008MB(I usually allocate 1024MB) for the swap space.
The swap space requirements have been increased with 10g R2. I was able to successfully complete the installation with 760MB, but that could limit the load on my test system down the road.
Figure 16: If you decide to move forward while some checks have failed, you will get this Warning.
Figure 17: Summary page for the installation.
Figure 18: Progress screen for the installation.
Figure 19: While the installation is progressing, you can return SUSE-release to its original content which would identify the OS version for other applications to be SLES10. Otherwise other applications may believe they are dealing with SLES9…This could become a problem for things like the Updater.
Figure 20: Progress screen for the Database configuration assistant, that is launched automatically by the Installer.
The Database Configuration will provide you with important information that you should write down somewhere.
Figure 21: Database Configuration Assistant info screen.
At this point, you can use the information provided by the Database configuration assistant to launch Enterprise Manager.
Figure 22: Oracle Enterprise Manager login page.
Figure 23: Licensing Information screen for Enterprise Manager.
Figure 24: Enterprise Manager Home page.
Figure 25: Enterprise Manager Performance page.
Now let’s go back to the Installer to complete the installation.
Figure 26: The Installer Configuration Assistants screen showing the initialization of the iSQL*Plus Configuration Assistant.
At this point, the Installer will ask you to execute 2 scripts as the root user.
Figure 27: Scripts to be executed.
Figure 28: Executing the 2 scripts in a terminal window using su.
Figure 29: End of Installation screen. Write down the information.
You can copy the URL for iSQL*Plus into Firefox and access it.
Figure 30: Login page for iSQL*Plus.
Figure 31: Workspace page for iSQL*Plus.
Now that the installation is complete, we will take a look at some of the configuration and startup files created by the orarun package or the Oracle Installer. The first one is /etc/oratab, and we need to replace the N with a Y for the instance to be started when SLES10 starts.
Figure 32: Setting the instance to start automatically through /etc/oratab.
You also need to edit /etc/sysconfig/oracle, a startup file created by the orarun package, in order to automatically start the instance, the listener, and other services. This file also sets the kernel parameters, which would have to be set manually otherwise.
Figure 33: Configuration of Oracle services startup through /etc/sysconfig/oracle, created by orarun.
Figure 34: Options for starting the Database and the Listener automatically.
Figure 35: Options to start the Oracle DB Agent.
Figure 36: Option to start iSQL*Plus automatically. This is a new option with SLES10.
Figure 37: Options to start other services like OID and Real Application Cluster OCFS(Oracle Clustering File System).
Figure 38: Options to set the kernel parameters. The values defined by default by orarun can be accepted or modified(for performance tuning).
Once you have set the correct values for the options and parameters, your Oracle services should start automatically when you start SLES10.
We can take a quick look at some of the new tools available with SLES10 for Oracle, like ocfs2console. In order to be able to fully leverage these new tools, an updated version of Oracle will probably be required. And some additional configuration steps for RAC and OCFS would need to be implemented, so refer to the Oracle documentation if you want to further explore these options, which are outside the scope of this document, which covers a basic installation only.
Figure 39: Starting the new tool ocfs2console. By default, you need root privileges.
Figure 40: Main screen for OCFS2 Console.
Figure 41: Under Tasks, you can use the Format tool to format a raw device for OCFS2.
Figure 42: Once formatted, a device can be browsed using the OCFS2 Console.
Figure 43: General information can also be obtained for OCFS2 formatted devices.
Figure 44: Under the Tasks menu, a tool to perform a File System Check is available. It is also possible to attempt to repair a problem File System from the Tasks menu.
Figure 45: The OCFS2 Console allows the management of multiple nodes in a cluster.
This concludes this document that I created in order to assist others with their exploration of the new features of SUSE Linux Enterprise Server 10 in relations to Oracle, and how to get a preview system up and running by tricking the Oracle Installer. The steps are very similar to the steps for SLES9, which is a good thing, since if one is familiar with the installation on SLES9, SLES10 should not be too much confusing.
Also, some improvements for the orarun package allows services like iSQL*Plus to be started automatically. And packages like openmotif-libs don’t need to be selected specifically, only orarun is required. Also, some new tools like the OCFS2 Console(ocfs2console) can be installed(packages) and explored in a limited fashion as demonstrated in this document. An updated version of Oracle and additional configuration steps for RAC(Real Application Cluster) and OCFS would be required to fully demonstrate the potential of these new tools, but if you are familiar with these concepts, the brief overview we have done through this document gives a good idea about where these new tools could be helpful, for example by replacing some text based scripts with a graphical interface.
Do not hesitate to send me questions, comments, or feedback regarding this document.
I hope that this document will be helpful to you.