Click Here

a href="https://ref.adbtc.top/3604752" target="_blank" border="0">

How to configure Linux

 

Verify the root User Path

Verify the path for the system root user. The path must be configured correctly for the STA installation.

  1. Open a terminal session on the STA server and log in as the system root user.

  2. Display the PATH variable and verify that it includes all the following directories:

    /bin
    /sbin
    /usr/bin
    /usr/sbin

    For example:

    # echo $PATH
/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/root/bin:/sbin:/bin:/usr/sbin:/usr/bin

  3. If any directories are missing, use a text editor to open the user profile and add them. For example:

    # vi /root/.bash_profile
PATH=$PATH:/sbin:/bin:/usr/sbin:/usr/bin

    Save and exit the file.

  4. Log out and log in as the system root user.

  5. Confirm that the PATH variable has been updated correctly.

    # echo $PATH
/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/root/bin:/sbin:/bin:/usr/sbin:/usr/bin

Enable the Linux Firewall iptables

Enable the iptables firewall service so the STA installer can set up required port configurations. Once STA is installed, iptables must remain running to support internal port forwarding for SNMP traps.

Linux 6

  1. Open a terminal session on the STA server and log in as the system root user.

  2. Enable the iptables:

    1. Check the current status of the iptables service.

      # service iptables status
iptables: Firewall is not running.

    2. If the firewall is not running, enable it.

      # service iptables restart
iptables: Applying firewall rules:                         [  OK  ]

  3. Configure iptables to start automatically during system startup:

    1. Check whether iptables is currently managed by the chkconfig utility.

      # chkconfig --list iptables
service iptables supports chkconfig, but is not referenced in any runlevel (run 'chkconfig --add iptables')

    2. Add iptables for management by chkconfig. By default, it is configured to restart in runlevels 2 through 5.

      # chkconfig --add iptables
# chkconfig --list iptables
iptables        0:off   1:off   2:on    3:on    4:on    5:on    6:off

Linux 7

  1. Open a terminal session on the STA server and log in as the system root user.

  2. Enable the iptables:

    1. Check the current status of the iptables service.

      # systemctl status iptables

    2. If the firewall is not running, start and enable it.

      # systemctl start iptables
# systemctl enable iptables

Disable SELinux

STA does not support SELinux. Disable SELinux before installing STA.

  1. Open a terminal session on the STA server and log in as the system root user.

  2. Open the SELinux configuration file with a text editor.

    # vi /etc/sysconfig/selinux

  3. In the file, set SELINUX to disabled:

    SELINUX=disabled

  4. Save and exit the file.

  5. Reboot the STA server to make your changes take effect.

Remove SELinux Permissions

Remove SELinux permissions for directories created before you disabled SELinux. This is important if you did not just freshly install Linux. In particular, the Oracle storage home, STA database, STA database local backup, and STA logs locations must not have SELinux permissions.

  1. Open a terminal session and log in as the system root user.

  2. List permissions for the Oracle storage home, STA database, STA database local backup, and STA logs locations. In a brand-new Linux installation these directories likely do no exist yet, but you should verify.

    For example:

    # ls –ld /Oracle /dbdata /dbbackup /var/log/tbi 

drwxr-xr-x. 2 oracle oinstall  4096 Jul 30 14:48 /Oracle
drwxr-xr-x. 3 root   root  4096 Jul 30 14:46 /dbdata
drwxr-xr-x. 3 root   root  4096 Jul 29 14:13 /dbbackup
drwxrwxrwx. 4 root  root 4096 Jul 30 14:46 /var/log/tbi
#

  3. In the output for each command, look for a dot at the end of the permissions. In the following example, note the "." after drxwr-xr-x.

    # ls -ld /Oracle

drxwr-xr-x.  5  oracle oinstall  4096  Jul  30  18:27  /Oracle

  4. If none of the directories contain a dot after the permissions statement, SELinux permissions have not been assigned to the directories and you can proceed to the next task.

    If SELinux permissions are assigned to a directory, enter the following command for that directory.

    # setfattr -h -x security.selinux directory_name

    For example:

    # setfattr -h -x security.selinux /Oracle /dbdata /dbbackup /var/log/tbi

  5. Confirm that the SELinux permissions have been removed.

    # ls –ld /Oracle /dbdata /dbbackup /var/log/tbi 

drwxr-xr-x 2 oracle oinstall  4096 Jul 30 14:48 /Oracle
drwxr-xr-x 3 root   root  4096 Jul 30 14:46 /dbdata
drwxr-xr-x 3 root   root  4096 Jul 29 14:13 /dbbackup
drwxrwxrwx 4 root  root 4096 Jul 30 14:46 /var/log/tbi
#

Set Up the Network Proxy

Configure the STA server to connect to the network directly or through a proxy server.

  1. From the Linux desktop System menu, select Preferences, then select Network Proxy.

  2. In the Network Proxy Preferences dialog box, specify the proxy configuration according to your site requirements.

  3. Click Close.

Setup yum (optional)

Oracle recommends you use yum (Yellowdog Updater, Modified) to install the required RPM (Red Hat Package Manager) Linux software packages.

yum simplifies the installation process by automatically searching RPM package repositories for the latest package versions and their dependencies. See Install Required Linux Packages for the required packages.

Use this procedure to ensure that yum is configured correctly on the STA server.

Note:

In the commands, use ol6 or ol7 depending on your operating system level (the examples show ol7). The "l" is lower-case "L".

  1. Ping the Oracle public-yum server to ensure the network connection is working.

    # ping public-yum.oracle.com

  2. Change to the yum repository directory and determine the yum repository filename.

    # cd /etc/yum.repos.d
# ls
public-yum-ol7.repo

  3. Remove the existing yum repository file.

    # rm public-yum-ol7.repo

  4. Download the latest yum repository file from the yum website.

    # wget http://public-yum.oracle.com/public-yum-ol7.repo

    Note:

    Subsequent executions of this command will copy a new repository file into the yum.repos.d folder with a new extension (for example, public-yum-ol7.repo.1). However, yum always uses the repository file with no extension.

  5. Open the repository file with a text editor.

    # vi public-yum-ol7.repo

  6. In the file, locate the entry that matches your Linux version and enable it by setting enabled=1. Disable all other entries by setting enabled=0.

    For example:

    [Linux_Version]
name=Oracle Linux $releasever Update x installation media copy ($basearch)
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL7/x/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol7
gpgcheck=1
enabled=1

  7. Save and exit the file.

Install Required Linux Packages

STA requires additional RPM packages. The STA installer will check for specific packages and if they are not present, the STA installation will fail.

Note:

RPM package names are case-sensitive. Choose the 64-bit version (x86_64) of any package if more than one version is available.

Required RPM Packages

  • bc

  • binutils

  • compat-libcap1

  • compat-libstdc++-33

  • cronie

  • ed

  • expect

  • gcc

  • gcc-c++

  • glibc

  • glibc-devel

  • libaio

  • libaio-devel

  • libgcc

  • libstdc++

  • libstdc++-devel

  • net-snmp-utils

  • net-tools

  • perl-Data-Dumper

  • perl-Digest-SHA

  • rpm-build

  • sysstat

  • unzip

  • xorg-x11-xauth

  • xorg-x11-utils


Packages that must NOT be installed

The mariadb packages (an alternative to MySQL) must NOT be installed on the STA server as it will cause the MySQL installation to fail.

Mail Services Packages

The STA installer issues a warning if it does not detect a package that supports mail services. STA requires mail services to deliver email notifications for alerts or Resource Monitor threshold notices.

The installer checks for the following: mailx, sendmail, postfix, dovecot.

IMPORTANT: The postfix mail package is NOT acceptable if it has a dependency on the mariadb-libs package.

Using yum to manage the packages

You can use a variety of methods to install the required RPM packages. This procedure describes how to use yum. See Setup yum (optional).

Deinstalling Packages

To de-install the mariadb-libs package (which may have been installed as a dependency):

# yum remove mariadb-libs

This will also remove any dependent packages, including postfix if necessary.

Installing Packages

yum checks for the most current version and then installs the package and any dependencies. Depending on your Linux installation, some of these packages may have already been installed. If a package is already installed and at the most current version, the system notifies you.

  1. Open a terminal session on the STA server.

  2. If you can reach Oracle's public yum server, use one of the following methods to install packages:

    • Install packages one at a time.The specified package will be downloaded and checked, and you must answer all prompts.

      # yum install package_name

    • Install all packages at once with no prompting. The –y option automatically answers "yes" to all installation prompts.

      # yum –y install bc binutils compat-libcap1 compat-libstdc++-33 cronie ed expect gcc gcc-c++ glibc glibc-devel libaio libaio-devel libgcc libstdc++ libstdc++-devel net-snmp-utils net-tools perl-Data-Dumper perl-Digest-SHA rpm-build sysstat unzip xorg-x11-xauth xorg-x11-utils

  3. If your network firewall prohibits external network access, you can use yum to install locally available packages from the Linux media.

    For example:

    # cd /mnt/install_media_mount_location/packages
# yum install ./package_name

Setup SSH

Correctly setup the SSH (secure shell) on the STA server. This will speed up transfers of STA database backups to a remote host.

  1. Open the SSH configuration file with a text editor.

    # vi /etc/ssh/sshd_config

  2. Search for the AddressFamily and UseDNS entries. Modify them so they are not preceded with the comment character and their values are as follows:

    AddressFamily inet
UseDNS no

  3. Save and exit the file.

  4. Restart the sshd daemon.

    Linux 6:

    # service sshd restart

    Linux 7:

    # systemctl restart sshd

Configure DNS Settings

Map the STA server's IP address to its hostname.

  1. Open the hosts file with a text editor.

    # vi /etc/hosts

  2. At the end of the file, add the STA server's IP address, followed by a tab, and then the STA server's hostname. For example:

    127.0.0.1    localhost localhost.localdomain localhost4...
::1          localhost localhost.localdomain localhost6...
192.0.2.20    sta_server

  3. Save and exit the file. You do not need to restart the STA server for the new setting to take effect.

Disable Name Services

Name services (such as LDAP) can conflict with STA installation. Temporarily disable these services.

  1. Open the Name Service Switch configuration file with a text editor.

    # vi /etc/nsswitch.conf

  2. Disable any name service entries. For example, to disable LDAP, comment out "ldap" from the following lines as shown:

    passwd:     files #ldap nis nisplus
shadow:     files #ldap nis nisplus
group:      files #ldap nis nisplus

  3. Save and exit the file. You do not need to restart the STA server for the new setting to take effect. After you install STA, you can modify the nsswitch.conf file to re-enable the name services.

Ensure Local Browser Functionality (optional)

To configure and administer STA locally on the STA server, ensure you have the minimum supported browser versions and plugins installed on your workstation.

Review the User Interface Requirements.

If you will be using HTTPS to access STA, see the STA User's Guide for instructions on ensuring that HTTPS is supported by your browser.

Oracle does not recommend local access to the STA application due to server performance degradation.

You may like these posts

Post a Comment

0 Comments
* Please Don't Spam Here. All the Comments are Reviewed by Admin.