How to Install and Configure Oracle on Linux
Change to the directory where you downloaded the glibc patch file, glibcpatch.tgz. Unpack the file, tar -xvzf glibcpatch.tgz. Run the patch script glibcpatch.sh, sh glibcpatch.sh. The final screen should look something like Figure 18.
Now it is time to create the original database.
Change to your staging directory (cd /home/oracle/orainst/orainst).
Start the installer (./orainst /c).
Select Custom Install.
Press enter twice to bypass the README files.
Select Create/Upgrade Database objects.
Select Create Database Objects.
Press return to acknowledge the environment variables ORACLE_HOME and ORACLE_BASE.
Press return to acknowledge the locations for the log files.
Press return to acknowledge the environment variable ORACLE_SID.
Select Oracle8 Enterprise (RDBMS), tab to INSTALL and press return.
Select Create Product DB Objects (see Figure 19).
Select Filesystem-based Database (see Figure 20).
Select Yes to distribute control files over three mount points (see Figure 21).
Enter the three mount points of /u01, /u02 and /u03 (see Figure 22).
Select the appropriate character set.
Select the appropriate national character set.
Enter the password you want to use for the SYSTEM account. You will be asked to enter it a second time to confirm the password.
Enter the password you want to use for the SYS account. You will be asked to confirm that too.
If you want an internal password for dba and operator, tab to Yes at this prompt. If you don't want an internal password tab to No.
Enter and confirm the password you want to use for the TNS listener.
Click on No to configure the MTS Listener (see Figure 23).
Press return to acknowledge the defaults for the location of the control files.
Press return twice if you wish to accept the defaults for the paths to your data files and their sizes. If you have not done any database sizing and thereby determined you need more space, the default sizes should be appropriate (see Figure 24). You can add space to any data file at a later time, if necessary.
Select Yes to accept the default file names and sizes (see Figure 25).
The installer will now create the initial database. As with the software installation, this is another good time to take a break. As before, we hope to see “The requested action has been performed for selected products.” message. Press return to return to the main install screen; tab to Exit, then press return; select Yes at the confirmation screen.
Log out, then log back in again as root. Copy the oracle user's .profile to root's home directory (cp ~oracle/.profile /root/.profile). Log out, then back in as root. Check that the environment variables in the .profile are set properly by issuing an env command.
Change to the /orainst directory and run the root.sh script.
cd $ORACLE_HOME/orainst sh root.sh
Verify ORACLE_OWNER, ORACLE_HOME and ORACLE_SID are correct. If they are, enter Y.
When it asks for the full path name to your local bin directory, enter /usr/local/bin. The script then tells you ORACLE_HOME does not match the home directory for oracle. This is not a problem. Type a Y and continue. The script will complete. (See Figure 26)
Log on as oracle and shut down the instance (see Figure 27).
svrmgrl connect internal shutdown exit
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide