Portal of oraRun lazy package under SUSELinux (Oracle Installation Tips)

I have a lot of oracle databases using the basic platform built by suselinux. When installing oracle, former colleagues directly use the loose package (oraRun *. rpm ). Location

I have a lot of oracle databases that use suse linux as the basic platform. When installing oracle, former colleagues directly use the loose package (oraRun *. rpm ). Location

I have a lot of Oracle databases that use SUSE linux as the basic platform. When installing oracle, former colleagues directly use the loose package (oraRun *. rpm ). The lazy package is naturally quite lazy, saving a lot of effort when installing oracle. This stuff has good, bad, and good manners.

Advantages of the lazy package:

The installation package will automatically help you install the Development Kit required by oracle, automatically create oracle users and related groups, and automatically create environment variables. Of course, you still need to modify the default environment variables, such as SID. The environment variable file is/etc/profile. d/oracle. sh.

Disadvantages of the lazy package:

After a lazy package is used, the * dump directory is directly put into the local disk directory (/OPT). Does the ORACLE_BASE set in the oracle environment variable take effect and seems to cause disorder? As a result, the alert file can only be stored in the opt directory. Currently, no location is found for modifying the ORACLE_BASE variable. The factory Engineers cannot solve this problem.

Summary:

I think this lazy package can still be used. Just pay attention to it, you can steal it and avoid problems. So many packages, especially many 32-bit packages, cannot be installed by default. It is annoying to look at the pile. Experts are always there, as long as they are willing to brainstorm.

1. Install the lazy package

2. Delete the oracle user so that the original oracle. sh will not be used

3. re-create an oracle user. Use the useradd command to automatically create the user environment variable file in/home/oracle. profile. My tests show that the file has a higher priority than oracle. sh, so ORACLE_BASE can solve the * dump directory problem by setting it here.