This guide describes the installation of Oracle Database 11g R2 for IMC on Red Hat Enterprise Linux Server 7.3. If your installation of Oracle Database 11g R2 uses a different version of Red Hat Enterprise Linux, see the Oracle database installation documents for your Linux version.

To achieve an optimized performance of the system running the Oracle database, see Oracle Database Installation Guide, Oracle Database Quick Installation Guide, and Oracle Universal Installer and OPatch User's Guide, available on the Oracle website.

After you install Oracle Database 11g R2, configure the following Oracle management features to ensure correct operation of IMC:

· Setting the maximum number of Oracle processes and Oracle connection limit

· Adding storage space to the database

· Modifying database memory settings

· Adding redo log groups

· Disabling database auditing

· Disabling database tracing

To install IMC, you must restart the operating system after configuring these features.

Preparing for installation

The following information describes the tasks you must complete in Linux as the root user before installing Oracle Database 11g R2.

To avoid installation errors, use the keyboard to enter your entries rather than using a cut-and-paste function for user input. Also, a 32-bit Linux must use the 32-bit Oracle database, and a 64-bit Linux must use the 64-bit Oracle database.

Disabling the firewall

systemctl stop firewalld.service

systemctl disable firewalld.service

To view the firewall status, use the following command:

systemctl status firewalld.service

Disabling SELinux

1. Open the SELinux configuration file.

vim /etc/selinux/config

2. Set the value for the SELINUX parameter to disabled.

SELINUX=disabled

3. Save the configuration and restart the system.

Setting the number of file descriptors

1. Log in to the system as a root user to view the number of file descriptors.

ulimit –n

2. If the number of file descriptors is less than 65535, open the limits.conf file.

vim /etc/security/limits.conf

3. Add the following parameter settings at the end of the file. If the parameters already exist, make sure the parameter values are greater than 65535.

* soft nofile 65535

* hard nofile 65535

4. Save the configuration and restart the system.

Setting the number of user processes

1. Log in to the system as a root user to open the 20-nproc.conf file.

vim /etc/security/limits.d/20-nproc.conf

2. Change the default value to 40960.

* soft nproc 40960

root soft nproc unlimited

3. Save the configuration and restart the system.

Checking the required software packages

Before installing the Oracle database and IMC, make sure you have installed all required software packages on the Linux operating system.

The software packages are stored in the Packages directory of the Linux installation drive. Use the rpm -ivh --nodeps xxx.rpm command to install the packages without a package dependency check.

IMPORTANT:

· To identify all packages that are already installed on the system, use the rpm –qa command. To determine whether a required software package has been installed, use the rpm -q command.

· RHEL 7.X does not provide the compat-libstdc++-33 installation package. To ensure correct operation of IMC, locate the package in RHEL 6.X or download it from the associated website.

The following 64-bit software packages, or later packages, are required:

· binutils-2.25.1-22.base.el7.x86_64.rpm

· cloog-ppl-0.15.7-1.2.el6.x86_64.rpm

· compat-libcap1-1.10-7.el7.x86_64.rpm

· compat-libstdc++-33-3.2.3-69.el6.x86_64.rpm

· cpp-4.8.5-11.el7.x86_64.rpm

· elfutils-libelf-0.166-2.el7.x86_64.rpm

· elfutils-libelf-devel-0.166-2.el7.x86_64.rpm

· gcc-4.8.5-11.el7.x86_64.rpm

· gcc-c++-4.8.5-11.el7.x86_64.rpm

· glibc-2.17-157.el7.x86_64.rpm

· glibc-common-2.17-157.el7.x86_64.rpm

· glibc-devel-2.17-157.el7.x86_64.rpm

· ksh-20120801-26.el7.x86_64.rpm

· libaio-0.3.109-13.el7.x86_64.rpm

· libaio-devel-0.3.109-13.el7.x86_64.rpm

· libgcc-4.8.5-11.el7.x86_64.rpm

· libstdc++-4.8.5-11.el7.x86_64.rpm

· libstdc++-devel-4.8.5-11.el7.x86_64.rpm

· libXext-1.3.3-3.el7.x86_64.rpm

· make-3.82-23.el7.x86_64.rpm

· mpfr-3.1.1-4.el7.x86_64.rpm

· ppl-0.10.2-11.el6.x86_64.rpm

· sysstat-10.1.5-11.el7.x86_64.rpm

· unixODBC-2.3.1-11.el7.x86_64.rpm

· unixODBC-devel-2.3.1-11.el7.x86_64.rpm

The following 32-bit software packages, or later packages, are required:

· compat-libstdc++-33-3.2.3-69.el6.i686.rpm

· glibc-2.17-157.el7.i686.rpm

· glibc-devel-2.17-157.el7.i686.rpm

· libaio-0.3.109-13.el7.i686.rpm

· libao-1.1.0-8.el7.i686.rpm

· libgcc-4.8.5-11.el7.i686.rpm

· libstdc++-4.8.5-11.el7.i686.rpm

· nss-softokn-freebl-3.16.2.3-14.4.el7.i686.rpm

· compat-libstdc++-33-3.2.3-69.el6.i686.rpm

Checking the disk space

Check the amount of free disk space on the system.

df -k

The following disk space requirements must be met for the Oracle installation:

· A minimum of 10 GB of free space in the /home directory.

· A minimum of 400 MB of free space in the /tmp directory.

The actual disk space requirements depend on the number of managed devices and performance monitoring instances. For more information, see the H3C IMC deployment guides.

Adjusting kernel parameters

To ensure the correct operation of the Oracle database, adjust the kernel parameters:

1. Open the sysctl.conf file.

vi /etc/sysctl.conf

2. Set the following variable values:

kernel.shmall=2097152

kernel.shmmax=4294967295

kernel.shmmni=4096

kernel.sem=250 32000 100 128

fs.file-max=6815744

fs.suid_dumpable=1

fs.aio-max-nr=1048576

net.ipv4.ip_local_port_range=9000 65500

net.core.rmem_default=4194304

net.core.rmem_max=4194304

net.core.wmem_default=262144

net.core.wmem_max=1048576

3. Save and close the file.

4. Validate the new settings.

/sbin/sysctl -p /etc/sysctl.conf

NOTE:

This example uses the minimum values for the kernel parameters. As a best practice, adjust these values for optimal system performance.

Creating operating system users and groups

Create the oracle user, the oinstall group, and the dba group before installing Oracle.

· Only the oracle user can install, start, or stop the Oracle database.

· The oinstall group users can install Oracle software.

· The dba group users can manage the database.

To create the required users and groups:

1. Create the oinstall and the dba groups.

groupadd oinstall

groupadd dba

2. Create the oracle user and set the password of the user.

useradd -g oinstall -G dba –d /home/oracle –m –s /bin/bash oracle

passwd oracle

Modifying the permissions on the Oracle home directory

Grant the oracle user permissions to run the database installation program from the Oracle installation directory (/home/oracle).

chown -R oracle:oinstall /home/oracle/

chmod -R 775 /home/oracle/

Configuring the Oracle base directory

1. Create the Oracle base directory.

mkdir -p /u01/app/

2. Set the directory owner and owner permissions.

chown -R oracle:oinstall /u01/app/

chmod -R 775 /u01/app/

Setting environment variables for the Oracle database

Set environment variables for the Oracle database in the profile file to automatically take effect at Linux startup. Ensure that the environment variables have taken effect before you install the Oracle database.

To set the environment variables:

1. Open the profile file.

¡ To deploy the Oracle database on the same host as the IMC server, edit the /etc/profile file. Execute the following command to open the profile file.

vi /etc/profile

¡ To deploy the Oracle database on a separate host than the IMC server, edit the /home/oracle/.bash_profile file. Execute the following command to open the profile file.

vi /home/oracle/.bash_profile

2. Add the following content to the profile file:

ORACLE_BASE=/u01/app/oracle

ORACLE_HOME=$ORACLE_BASE/product/11.1.0/db_1

ORACLE_SID=orcl

PATH=$PATH:$ORACLE_HOME/bin:$HOME/bin

LD_LIBRARY_PATH=$ORACLE_HOME/lib

export ORACLE_BASE ORACLE_HOME ORACLE_SID PATH LD_LIBRARY_PATH

The variable description is as follows:

¡ ORACLE_BASE—Oracle base directory.

¡ ORACLE_HOME—Oracle home directory.

¡ ORACLE_SID—Oracle database instance ID. Use the same instance ID for Oracle database installation.

3. Save and close the file.

Verifying the environment variable settings

Before you install the Oracle software, verify that the environment variable settings have taken effect:

1. Restart the operating system.

2. Verify that the environment variables have taken effect.

echo $ORACLE_HOME

/u01/app/oracle/product/11.1.0/db_1

echo $LD_LIBRARY_PATH

/u01/app/oracle/product/11.1.0/db_1/lib

echo $ORACLE_SID

orcl

Setting environment variables for the oracle user

1. Open the .bash_profile file.

vi /home/oracle/.bash_profile

2. Set the language environment variable according to the language your system supports.

LANG=en_US.UTF-8

export LANG

3. Add the following content to the end of the file:

umask 022

4. Save the file.

5. Switch to oracle and validate the new settings.

su – oracle

export DISPLAY=localhost:0.0

6. Switch to root.

exit

Setting the NLS_LANG environment variable

1. Open the profile file.

vi /etc/profile

2. Add the following content to the file:

NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P15

export NLS_LANG

3. Save and close the file.

The environment variable automatically takes effect at Linux startup.

IMPORTANT:

· Set the correct value. Otherwise, Oracle database and IMC data cannot be displayed correctly. For more information about determining the NLS_LANG value, see Oracle Database Globalization Support Guide.

· If the Oracle database is deployed on the same server as the IMC server, set the NLS_LANG environment variable.

Adding the IP-to-hostname mapping in /etc/hosts

1. Open the /etc/hosts file.

vi /etc/hosts

2. Add a line of text in the format ip-address localhost localhost.localdomain.

As shown in Figure 1, enter 192.168.7.212 imctest imctest.IMC to map 192.168.7.212 to the host name imctest in the h3c domain.

Figure 1 Modifying the /etc/hosts file

If IMC products use a remote database, add another line of mapping between the IP address of the remote database server and the host name for fast DNS resolution.

3. Save and close the file.

Preparing the installation package

Copy the Oracle installation package to the /home/oracle directory and decompress the package. If you use the installation CD, follow the instructions on the CD.

Database installation requirements for IMC

Install the Oracle database before you install IMC. IMC supports both local and remote databases.

To install a local Oracle database for IMC, perform the steps in "Installing and configuring the Oracle database server."

To install a remote Oracle database for IMC:

1. Install the database server on the remote server.

See "Installing and configuring the Oracle database server" for the operation procedure.

2. Configure the following items on the database server:

¡ A listener for receiving remote connection requests.

¡ A network service name.

¡ A data file folder for storing IMC data. You will need to specify the path to the file during IMC installation. For more information, see the H3C IMC deployment guides.

3. On the server where you plan to install IMC, install the Oracle client for IMC to connect to the Oracle database. The client version must match the version of the Oracle database server.

For more information, see "Installing the Oracle client."

4. Configure the network service name on the client. It must be the same as the network service name that is configured on the database server.

For more information, see "Configuring the Oracle client."

If you plan to deploy IMC in distributed mode, be sure to configure the correct network service names on the IMC servers for them to connect to the database. During IMC installation, you need to specify the network service name to be used by IMC for database connection.

The network service name configuration varies depending on whether IMC uses local or remote databases, as illustrated in the following examples.

· Example 1:

IMC server A (master server), and server B and C (subordinate servers) use their respective local databases.

For each database, you must assign a unique network service name. In this example, TNSNAME_A, TNSNAME_B, and TNSNAME_C are the network service names for accessing the databases on servers A, B, and C, respectively.

For the servers to communicate with each other, you must configure all these network service names on each IMC server. Make sure the settings for each network service name are the same across all servers.

· Example 2:

IMC server A (master server), and servers B and C (subordinate servers) share a remote database server, DBServer_D.

In this scenario, you must configure the servers as follows:

¡ Install the Oracle client on each IMC server to connect to the remote database server.

¡ Configure the same network service name (for example, TNSNAME_D) for accessing the database across all servers, including the IMC servers (Oracle clients) and the database server.

Installing and configuring the Oracle database server

To install and configure the database, log in to Linux as oracle. Execute commands in subsequent sections as oracle, unless otherwise specified.

Installing the Oracle database server

1. Restart Linux after you complete all preparation tasks in "Preparing for installation."

2. Log in to Linux as oracle, and then start the database installation wizard in the Oracle installation package directory.

./runInstaller

The Configure Security Update page opens, as shown in Figure 2.

Figure 2 Configure Security Updates page

3. Configure security updates settings as needed.

¡ To receive security updates, enter an email address, and then click Next.

You can also select I wish to receive security updates via My Oracle Support and enter your password next to My Oracle Support Password to receive security updates.

¡ If you prefer not to receive security updates, click Next without providing the email or password. Click Yes in the dialog box shown in Figure 3, and then click Next.

Figure 3 Email address not specified

The Download Software Updates page opens, as shown in Figure 4.

Figure 4 Download Software Updates page

4. Select Skip software updates, and then click Next.

The Select Installation Option page opens, as shown in Figure 5.

Figure 5 Selecting an installation option

5. Select Create and configure a database, and then click Next.

The System Class page opens, as shown in Figure 6.

Figure 6 System Class page

6. Select Server Class, and then click Next.

The Grid Installation Options page opens, as shown in Figure 7.

Figure 7 Grid Installation Options page

7. Select Single instance database installation, and then click Next.

The Select Install Type page opens, as shown in Figure 8.

Figure 8 Select Install Type page

8. Select Advanced install, and then click Next.

The Select Product Languages page opens, as shown in Figure 9.

Figure 9 Select Product Languages page

9. Select English (United Kingdom), and then click Next.

The Select Database Edition page opens, as shown in Figure 10.

Figure 10 Select Database Edition page

10. Select Enterprise Edition, and then click Next.

The Specify Installation Location page opens, as shown in Figure 11.

Figure 11 Specify Installation Location page

11. Click Next, with the default settings unchanged.

The Create Inventory page opens, as shown in Figure 12.

Figure 12 Create Inventory page

12. Click Next, with the default settings unchanged.

The Select Configuration Type page opens, as shown in Figure 13.

Figure 13 Select Configuration Type page

13. Select General Purpose / Transaction Processing, and then click Next.

The Specify Database Identifiers page opens, as shown in Figure 14.

Figure 14 Specify Database Identifiers page

14. Configure the following parameters:

¡ Enter the global database name. This example uses orcl. The global database name is in the format database name.domain name, where domain name is optional.

¡ Enter the Oracle system identifier (SID), which must be consistent with the ORACLE_SID variable setting in the profile file. This example uses orcl. For more information, see "Setting environment variables for the Oracle database."

15. Click Next.

The Specify Configuration Options page opens, as shown in Figure 15.

Figure 15 Specify Configuration Options page

16. Configure the memory settings as needed. Table 1 lists the recommended memory sizes.

Table 1 Value for setting the memory size

System memory	Local database	Remote database
4 GB	1400 MB	2400 MB
6 GB	2400 MB	3600 MB
8 GB	3600 MB	4800 MB
10 GB or larger	4500 MB	5000 MB

17. Click the Character sets tab, and then specify the character set for the database, as shown in Figure 16.

¡ To prevent unreadable characters, select the correct database character set.

¡ If you are not sure of the language, select Use Unicode (AL32UTF8). This example uses West European WE8ISO8859P15.

For more information about setting the database character set, see the Oracle Database Globalization Support Guide.

Figure 16 Setting the character set

18. Click Next.

The Specify Management Options page opens, as shown in Figure 17.

Figure 17 Specify Management Options page

19. Click Next, with the default settings unchanged.

The Specify Database Storage Options page opens, as shown in Figure 18.

Figure 18 Specify Database Storage Options page

20. Select File System, use the default database file location, and then click Next.

The Specify Recovery Options page opens, as shown in Figure 19.

Figure 19 Specify Recovery Options page

21. Select Do not enable automated backups, and then click Next.

The Specify Schema Passwords page opens, as shown in Figure 20.

Figure 20 Specify Schema Passwords page

22. Set passwords.

¡ You can set different passwords for the database accounts SYS, SYSTEM, SYSMAN, and DBSNMP, or use the same password for all accounts.

¡ For IMC to correctly identify the password of the SYS account during installation, make sure the password does not contain spaces, tabs, or any of the following characters:

` ' " ! ( ) & | \ $ ; @ < > / ^

¡ If you do not want to change the password of the SYS account, create a user account with the same privileges as the SYS account. Make sure the password of the user account does not contain any of the previous characters. For more information about creating a database user, see "Creating a database user."

23. Click Next.

The Privileged Operating System Groups page opens, as shown in Figure 21.

Figure 21 Privileged Operating System Groups page

24. Click Next, with the default settings unchanged.

The Perform Prerequisite Checks page opens, as shown in Figure 22.

Figure 22 Perform Prerequisite Checks page

The installation program checks the environment settings and displays the check results.

25. Manually verify the items that are flagged with warnings or require a manual check, as follows:

a. Modify the environment settings.

b. If the kernel parameter or software package check fails, click Fix & Check again.

The Execute Fixup Scripts dialog box opens.

c. Open a terminal window, switch to root, and then execute the /tmp/CVU_11.2.0.3.0_oracle/runfixup.sh script, as shown in Figure 23.

Figure 23 Executing runfixup.sh

d. Close the terminal window.

e. In the Execute Fixup Scripts dialog box, click OK.

If the software package check fails because later versions of packages are installed, click Ignore all. Because the compat-libstdc++-33 package is not provided in RHEL 7.x, download and install the package if required in the prerequisites check.

26. Click Next.

IMPORTANT:

RHEL 7.X does not provide the pdksh package. The ksh package is used instead.

The Summary page opens, as shown in Figure 24.

Figure 24 Summary page

27. Click Install.

The Install Product page opens, as shown in Figure 25.

Figure 25 Install Product page

The installation program starts to install the database and displays the installation progress. During the installation, the Execute Configuration scripts dialog box opens, as shown in Figure 26.

Figure 26 Execute Configuration scripts dialog box

28. Open a terminal window, switch to root, and then execute the scripts in Figure 26, as shown in Figure 27

Figure 27 Executing configuration scripts

29. Close the terminal window.

30. In the Execute Configuration scripts dialog box, click OK.

The Install Product page displays the installation progress, as shown in Figure 28.

Figure 28 Install Product page

31. Click Next.

The Finish page opens, as shown in Figure 29.

Figure 29 Finish page

32. Click Close.

33. Reboot Linux.

To adjust the database settings to meet your requirements, see "Managing Oracle database 11g R2."

Configuring the Oracle database server

Configuring the Oracle database listener

1. Start Oracle Net Manager in the $ORACLE_HOME/bin directory.

cd $ORACLE_HOME/bin/

./netmgr

2. From the navigation tree, select Local > Listeners > LISTENER.

3. In the right pane, select Database Services from the list, and then click Add Database.

A new database tab opens.

4. Specify the global database name, Oracle home directory, and the SID.

Make sure the global database name and the SID are the same as those specified during database installation (see Figure 14). Figure 30 shows the detailed configurations.

Figure 30 Configuring the listener

Configuring the network service name

After server installation is complete, the system creates a network service name that is the same as the global database name by default.

1. Open a terminal window, and execute the following commands to open the tnsnames.ora file and view the created network service name.

cd $ORACLE_HOME/network/admin/

vi tnsnames.ora

Figure 31 Viewing the network service name

2. By default, the value for HOST is host name. For IMC to operate correctly, change the value for HOST to the IP address of the local host.

Figure 32 Configuring the network service name

3. Enter :wq to save your setting.

Installing and configuring the Oracle database client

To enable IMC to connect to a remote Oracle database server, you must install a compatible Oracle client on the server that will host IMC.

Installing the Oracle client

1. Complete the tasks described in "Preparing for installation."

2. Restart Linux, and then log in as Oracle.

3. Run the installation program from the Oracle client installation directory.

./runInstaller

The Select Installation Type page opens, as shown in Figure 33.

Figure 33 Select Installation Type page

4. Select Custom, and then click Next.

The Download Software Updates page opens, as shown in Figure 34.

Figure 34 Download Software Updates page

5. Select Skip software updates, and then click Next.

The Select Product Languages page opens, as shown in Figure 35.

Figure 35 Select Product Languages page

6. Select English (United Kingdom), and then click Next.

The Specify Installation Location page opens, as shown in Figure 36.

Figure 36 Specify Installation Location page

7. Click Next, with the default settings unchanged.

The Create Inventory page opens, as shown in Figure 37.

Figure 37 Create Inventory page

8. Click Next, with the default settings unchanged.

The Available Product Components page opens, as shown in Figure 38.

Figure 38 Available Product Components page

9. Select the following components:

¡ Oracle SQLJ

¡ Oracle Database Utilities

¡ Oracle Java Client

¡ SQL*Plus

¡ Oracle JDBC/THIN Interfaces

¡ Oracle Call Interface(OCI)

¡ Oracle Connection Manager

¡ Oracle ODBC Driver

¡ Oracle SQL Developer

10. Click Next.

The Perform Prerequisite Checks page opens, as shown in Figure 39.

Figure 39 Perform Prerequisite Checks page

11. Fix any failed check items, and then click Next.

The Summary page opens, as shown in Figure 40.

Figure 40 Summary page

12. Click Install.

The Install Product page opens, as shown in Figure 41.

Figure 41 Install Product page

The system starts installing the Oracle client and displays the installation progress. During installation, the Oracle Net Configuration Assistant opens, as shown in Figure 42.

Use Oracle Net Configuration Assistant to configure the network service name to be used for connecting to the database server.

For more information about network service names, see "Configuring network service names."

Figure 42 Oracle Net Configuration Assistant

13. Select Perform typical configuration, and then click Next.

The Welcome page opens, as shown in Figure 43.

Figure 43 Welcome page

14. Click Next to complete product installation, as shown in Figure 44.

Figure 44 Completing product installation

15. Click Finish.

The Execute Configuration scripts dialog box opens, as shown in Figure 45.

Figure 45 Execute Configuration scripts dialog box

16. Open a terminal window, switch to root, and execute the scripts instructed in Figure 45, as shown in Figure 46.

Figure 46 Executing configuration scripts

17. Close the terminal window.

18. In the Execute Configuration scripts dialog box, click OK.

19. Click Close on the Finish page, as shown in Figure 47.

Figure 47 Finish page

Configuring the Oracle client

Configure a network service name for the Oracle client to connect to the database server.

Network service names can be configured by editing the configuration file, or by using the Oracle Net Manager.

To configure the network service name by using Oracle Net Manager:

1. Go to the $ORACLE_HOME/bin directory and launch netmgr.

cd $ORACLE_HOME/bin/

./netmgr

2. From the navigation tree, select Oracle Net Configuration > Local > Service Naming.

Figure 48 Oracle Net Manager admin page

3. Click the Create icon in the toolbar.

The Net Service Name Wizard opens, as shown in Figure 49.

Figure 49 Net Service Name Wizard

4. Enter orcl, and then click Next. The network service name must be the same as the name configured on the database server.

The Protocol page opens, as shown in Figure 50.

Figure 50 Selecting a protocol

5. Select TCP/IP (Internet Protocol), and then click Next.

The Protocol Settings page opens, as shown in Figure 51.

Figure 51 Protocol Settings page

6. Enter the database server IP address as the Host Name, use the default port number, and then click Next.

The Service page opens, as shown in Figure 52.

Figure 52 Configuring the service

7. Enter the global database name of the database server in the Service Name field, use the default connection type, and then click Next.

The Test page opens, as shown in Figure 53.

Figure 53 Test page

8. Click Test to test the connectivity to the database server, or click Finish to run the test later (see "Testing the connectivity to the server").

The Net Service Name Wizard closes.

9. View the service name configuration by selecting Oracle Net Configuration > Local > Service Naming > orcl from the navigation tree.

Figure 54 Viewing the service name configuration

10. Save your configuration.

Testing the connectivity to the server

1. Log in to Linux as oracle.

2. In the terminal window, log in to the database to test the connectivity. In this example, the username is sys, the password is iMC123, and the network service name is orcl.

sqlplus sys/iMC123@orcl as sysdba

Managing Oracle database 11g R2

To configure the database, you must log in to the system as oracle. Perform the commands in the subsequent sections as oracle unless specified otherwise.

For correct operation of IMC, make sure you follow the procedures in this chapter to set the maximum number of Oracle processes and Oracle connection limit, add storage space to the database, modify database memory settings, add redo log groups, and disable database auditing and tracing. After complete the settings, you must restart the operating system before installing IMC.

In the following examples, sys is the username of the Oracle database administrator and iMC123 is the user password.

Starting the Oracle service manually

1. Start the listener control utility.

cd $ORACLE_HOME/bin

./lsnrctl start

2. Verify that the listener control utility is started.

./lsnrctl service

3. Start the Oracle database.

cd $ORACLE_HOME/bin

./sqlplus sys/iMC123 as sysdba

SQL>startup

SQL>exit

Stopping the Oracle service manually

1. Stop the Oracle database.

cd $ORACLE_HOME/bin

./sqlplus sys/iMC123 as sysdba

SQL>shutdown immediate

SQL>exit

2. Stop the listener control utility.

cd $ORACLE_HOME/bin

./lsnrctl stop

Configuring network service names

IMPORTANT:

If IMC servers use different Oracle databases in a distributed deployment, you must configure a unique network service name for each database.

To enable IMC to connect to remote databases, you must configure correct network service names on the Oracle database server and client.

You can configure network service names by using Oracle Net Manager or Oracle Net Configuration Assistant. This procedure uses Oracle Net Configuration Assistant. To use Oracle Net Manager, see "Configuring the Oracle client."

To configure the network service name by using Oracle Net Configuration Assistant:

1. Start the database service.

See "Starting the Oracle service manually" for the operation procedure.

2. Start Oracle Net Configuration Assistant.

cd $ORACLE_HOME/bin

./netca

The Welcome page opens.

3. Select Local Net Service Name configuration, and then click Next, as shown in Figure 55.

Figure 55 Welcome page

4. Select Add, and then click Next, as shown in Figure 56.

Figure 56 Net Service Name Configuration page

5. Enter the database service name orcl, and then click Next, as shown in Figure 57.

The service name must be the same as the previously configured global database name.

Figure 57 Configuring a service name

6. Select transmission protocol TCP, and then click Next, as shown in Figure 58.

Figure 58 Selecting a protocol

The page for configuring the host name and port number opens, as shown in Figure 59.

7. Configure the following parameters:

¡ Enter the IP address of the database server into the Host Name field.

¡ Select Use the standard port number of 1521. This option is selected by default.

Figure 59 Configuring the host name and port number

8. Click Next.

9. Select Yes, perform a test, and then click Next, as shown in Figure 60.

Figure 60 Testing connectivity to the database server

Oracle Net Configuration Assistant displays the connectivity test result, as shown in Figure 61.

Figure 61 Connectivity test result

10. If the connection attempt fails, click Change Login to change the login username and password, as shown in Figure 62.

Figure 62 Changing login credentials

11. Enter the correct password of the user system, and then click OK.

Oracle Net Configuration Assistant performs a new connection test.

12. When you see a successful test result, click Next, as shown in Figure 63.

Figure 63 Test result

13. Enter a network service name, as shown in Figure 64.

The network service name must be different from the service name orcl. This name is automatically added to the list for selecting a network service name when you install IMC.

Figure 64 Specifying a network service name

14. Click Next.

The page for adding network service names opens, as shown in Figure 65.

Figure 65 Adding network service names as needed

15. To add additional network service names, select Yes. If additional network service names are not needed, click No. In this example, select No, and then click Next.

The configuration complete page opens, as shown in Figure 66.

Figure 66 Completing the network service name configuration

16. Click Next.

17. On the page shown in Figure 67, click Finish.

Figure 67 Finish page

Setting the maximum number of Oracle processes and Oracle connection limit

By default, the Oracle database allows a maximum of 150 connections.

In centralized IMC deployment or when a database error occurs, you might need to modify the Oracle process and connection limits according to the number of deployed IMC components. The number of Oracle connections must be not less than 800.

Table 2 lists the Oracle connection limit required by IMC modules.

Table 2 Oracle connection limit on IMC modules

IMC module	Oracle connection limit
IMC platform	14
Alarm management	24
Syslog management	9
Performance management	11
Report management	10
Guest Access Manager	5
User self-service management	5
Network asset manager	5
Virtual Resource Management	9
Configuration center	9
ACL management	7
VLAN management	11
Security control center	5
Server & Storage Automation	6
VXLAN management	4
VAN Fabric Manager	27
Resource Automation Manager	16
QoS manager	5
Service Health Manager	60
User access management/CAMS accounting manager	100
EAD security policy configuration	25
Desktop asset manager	40
MPLS VPN manager	9
L2VPN manager	17
Application Manager	10
Branch Intelligent Management System	10
IPsec VPN manager	8
VAN Connection Manager	5
Security Service Manager	10
Load Balancing Manager	5
Wireless Service Manager	50

To view and modify the maximum number of Oracle processes and the Oracle connection limit:

1. Switch to the oracle user.

su – oracle

2. Log in to the Oracle database as sysdba.

sqlplus sys/iMC123 as sysdba

In the command, the database username is sys and password is iMC123.

3. View the number of Oracle processes and the Oracle connection limit.

¡ View the number of Oracle processes.

SQL>show parameter processes;

¡ View the Oracle connection limit.

SQL>show parameter sessions;

4. Change the maximum number of Oracle processes and the Oracle connection limit according to the installed IMC modules.

¡ Change the maximum number of Oracle processes. Replace 600 with another value as needed.

SQL>alter system set processes=600 scope=spfile;

¡ Change the Oracle connection limit. Replace 600 with another value as needed.

SQL>alter system set sessions=600 scope=spfile;

5. Restart the Oracle database to make the changes take effect.

Automating Oracle database startup on Linux

1. Log in to Linux as root.

2. Copy the Oracle startup script oracled.tar.gz from the /manual directory of the IMC installation package to the Linux operating system.

3. Decompress the script file.

tar -xzf oracled.tar.gz

4. Copy the decompressed file to the /etc/rc.d/init.d directory.

cp oracled /etc/rc.d/init.d/

5. Change the file permissions.

chmod –R 755 oracled

6. Add the script to the startup configuration file of the Linux operating system.

chkconfig --add oracled

7. Open the Oracle configuration file /etc/oratab.

vi /etc/oratab

8. Set the following line to Y.

orcl:/u01/app/oracle/product/11.1.0/db_1:Y

9. Save and close the file.

The Oracle database automatically starts at the Linux startup.

10. To manually start or stop the Oracle database, use the following commands:

service oracled start

service oracled stop

Creating a database user

1. Log in to the Oracle database as sys.

./sqlplus sys/iMC123@orcl as sysdba

In the command, sys is the database username, iMC123 is the password, and orcl is the network service name.

2. Create a database user named imc and the password imcpassword.

create user imc identified by imcpassword;

IMPORTANT:

For IMC to correctly identify the password during installation, make sure the password does not contain spaces, tabs, or any of the following characters:
` ' " ! ( ) & | \ $ ; @ < > / ^

3. Grant the sysdba privilege to the user.

grant sysdba to imc;

IMPORTANT:

To avoid deployment errors, give database users sysdba privilege for connecting to the database.

Adding storage space to the database

The amount of storage space available on the database for IMC depends on the number of data files in the USERS tablespace. By default, the USERS tablespace has a single data file with a size limit of 32 GB. You can add data files to the USERS tablespace to provide additional storage.

The number of data files to add depends on the disk space required by the IMC components. For example, if IMC requires 300 GB for device management, create a minimum of ten files (300 GB/32 GB = 9.375). If a database is used by multiple IMC components, create data files according to the total disk space required by the installed components.

You can add data files to the USERS tablespace through Oracle Enterprise Manager or by using SQL statements.

Adding database storage space through Oracle Enterprise Manager

1. Log in to the operating system as oracle, and then start the Oracle Enterprise Manager.

emctl start dbconsole

2. Access the Oracle Enterprise Manager at:

https://ip-address:1158/em.

In the URL, ip-address is the IP address of the Oracle database server.

3. Log in to the Oracle Enterprise Manager as SYSTEM, and then select Server > Datafiles, as shown in Figure 68.

Figure 68 Database instance management interface

4. Select the data file that belongs to the USERS tablespace, as shown in Figure 69.

Figure 69 Data file management page

5. Click Go.

The Create Datafile page opens, as shown in Figure 70.

Figure 70 Creating a data file

6. Enter the file name and file directory, or use the default file entries, and then click OK.

7. To add additional data files, repeat the steps in this procedure.

If the system has multiple hard disk drives, distribute the files on different disk drives for I/O load balancing.

Setting database storage space through SQL statements

1. Log in to Linux as oracle.

2. Log in to the Oracle database as sys.

sqlplus sys/iMC123@orcl as sysdba

In the command, sys is the database username, iMC123 is the password, and orcl is the network service name.

3. Display existing data files in the USERS tablespace.

SQL> select file_name from dba_data_files where tablespace_name='USERS';

FILE_NAME

-----------------------------------------------------------

/u01/app/oracle/oradata/orcl/users01.dbf

The output shows that the USERS tablespace contain only one data file in the /u01/app/oracle/oradata/orcl directory.

4. Add a new data file named users02.dbf to the directory.

SQL> alter tablespace USERS add datafile '/u01/app/oracle/oradata/orcl/userdata02.dbf' size 100M autoextend on next 100M maxsize UNLIMITED;

5. Add users03.dbf, users04.dbf, and more data files to the directory. (Details not shown.)

Modifying database memory settings

1. Log in to Linux as oracle.

2. Log in to the Oracle database as sys.

sqlplus sys/iMC123@orcl as sysdba

In the command, sys is the database username, iMC123 is the password, and orcl is the network service name.

3. Set the value of MEMORY_TARGET.

SQL> alter system set MEMORY_TARGET=1700M scope=spfile;

Table 3 lists the recommended memory sizes.

Table 3 Recommended memory sizes

System memory	Local database	Remote database
4 GB	1400 MB	2400 MB
6 GB	2400 MB	3600 MB
8 GB	3600 MB	4800 MB
10 GB or larger	4500 MB	5000 MB

Adding redo log groups

Redo logs record changes made to the database (such as data rollback) and can be used for data recovery. By default, three groups of redo logs are available. Each group contains 50 MB log files. To improve the write efficiency if an excessive amount of data needs to be written, add redo log groups after installing Oracle.

To add redo log groups:

1. Switch to the oracle user.

su – oracle

2. Log in to the Oracle database as sys.

sqlplus sys/iMC123@orcl as sysdba

In the command, sys is the database username, iMC123 is the password, and orcl is the network service name.

3. Locate the storage directory of redo log files.

SQL>select MEMBER from v$logfile;

MEMBER

---------------------------------------

/u01/app/oracle/oradata/orcl/redo03.log

/u01/app/oracle/oradata/orcl/redo02.log

/u01/app/oracle/oradata/orcl/redo01.log

Redo log files are stored in the directory /u01/app/oracle/oradata/orcl.

4. Use the following commands to add three redo log groups, each with a size of 2048 MB.

SQL>alter database add logfile group 4('/u01/app/oracle/oradata/orcl/redo04.log') SIZE 2048M;

SQL>alter database add logfile group 5('/u01/app/oracle/oradata/orcl/redo05.log') SIZE 2048M;

SQL>alter database add logfile group 6('/u01/app/oracle/oradata/orcl/redo06.log') SIZE 2048M;

Disabling database auditing

Database auditing records database activities and monitors user operations, such as database connection, SQL statement executions, and data access. Database auditing is enabled by default and it can produce a large number of audit files. To save system resources, disable the auditing feature as follows:

1. Log in to the Oracle database.

sqlplus sys/iMC123@orcl as sysdba

In the command, sys is the database username, iMC123 is the password, and orcl is the network service name.

2. View the database auditing status.

SQL>show parameter audit_trail;

NAME TYPE VALUE

---- ---- -----

audit_trail string DB

The VALUE field value for audit_trail is DB, which indicates that database auditing is enabled.

3. Disable the database auditing.

SQL>alter system set audit_trail=FALSE scope=spfile;

System altered.

4. Restart the database.

SQL>shutdown immediate;

SQL>startup;

5. Verify that the database auditing feature is disabled.

SQL>show parameter audit_trail;

NAME TYPE VALUE

---- ---- -----

audit_trail string FALSE

The VALUE field value for audit_trail is FALSE, which indicates that database auditing is disabled.

Disabling database tracing

The database tracing feature trails the execution history and code paths of Oracle and provides information for debugging. This feature is enabled by default and it affects the database performance. To upgrade the performance, disable this feature as follows:

1. Log in to the Oracle database.

sqlplus sys/iMC123@orcl as sysdba

In the command, sys is the database username, iMC123 is the password, and orcl is the network service name.

2. View the database tracing status.

SQL>show parameter trace;

NAME TYPE VALUE

------------------------------- ------- -----

log_archive_trace integer 0

sec_protocol_error_trace_action string TRACE

sqltrace bollean FALSE

trace_enabled boolean TRUE

tracefile_identifier string

The VALUE field value for trace_enabled is TRUE, which indicates that the tracing is enabled.

3. Disable database tracing.

SQL>alter system set trace_enabled=FALSE scope=spfile;

System altered.

4. Restart the database.

SQL>shutdown immediate;

SQL>startup;

5. Verify that the database tracing feature is disabled.

SQL>show parameter trace_enabled;

NAME TYPE VALUE

------------- ------- -----

trace_enabled boolean FALSE

The VALUE field value for trace_enabled is FALSE, which indicates that database tracing is disabled.

Removing Oracle Database 11g R2

You can remove the Oracle database by using the uninstall script provided by the database, or manually remove Oracle program files, users, and user groups by executing commands as root.

To manually remove Oracle Database 11g R2:

1. Log in to Linux as root.

2. Stop the Oracle service.

cd $ORACLE_HOME/bin

sqlplus sys/imc123 as sysdba

SQL>shutdown

In the command, imc123 is the password of the sys user.

3. Stop the listener.

cd $ORACLE_HOME/bin

./lsnrctl stop

4. Delete the Oracle installation directory /u01 in the root directory.

cd /

rm –rf /u01

5. Delete the directory /usr/local/bin/oracle (the default is /user/local/bin). This is the directory created by the configuration script during database installation (see Figure 27). The string of asterisks (*) in the command represents the name of the file you want to delete.

rm –rf ****

6. Delete files oratab and oraInst.loc in the /etc directory.

cd /etc

rm –rf oratab

rm –rf oraInst.loc

7. Delete the oracle user.

userdel oracle

8. Delete the oinstall user group.

groupdel oinstall

9. Delete the dba user group.

groupdel dba

10. Delete the /home/oracle directory.

cd /home

rm –rf oracle/

11. Delete the startup service.

chkconfig -–del oracled

12. Reboot Linux.

FAQ

Why does the system display an insufficient disk space error when creating the database instance?

Verify that the etc/sysctl.conf file is correctly configured. For more information, see "Adjusting kernel parameters."

Why are there unreadable characters displayed on IMC that uses the Oracle database?

The following issues can cause unreadable characters:

· Incorrect character set for the database.

The Oracle database character set is incompatible with the language setting of IMC. For example, the Oracle database uses the English character set, but IMC uses a non-English language coding. To resolve the problem, reinstall the Oracle database and select the correct character set.

· Incorrect NLS_LANG variable setting.

The NLS_LANG environment variable is not set correctly. To resolve the problem, correct the NLS_LANG setting, and then restart the server and IMC. For information about setting the NLS_LANG variable, see "Setting the NLS_LANG environment variable."

· Incorrect LANG variable setting for the Oracle database server that uses the default character set.

The LANG variable is not set correctly for a database server that is configured to use the default character set during installation. The default character set is determined by the LANG variable. For more information about setting the LANG variable, see "Setting environment variables for the oracle user."

For example, the LANG variable is set to LANG= en_US.UTF-8 for a database that requires a non-English character set. If the database is configured to use the default character set, which is WE8ISO8859P15 in this example, unreadable characters will be displayed.

To resolve the problem, reinstall the Oracle database with the correct character set. For more information, see "Installing and configuring the Oracle database server."

For more information about setting the database and client character sets, see Oracle Database Globalization Support Guide on the Oracle website.

How do I update database passwords for IMC?

After the database password of an IMC component is changed by using the database management tool, execute pwdmgr.bat to update the password in the server-addr.xml file on the IMC server. The file is located in the /common/conf/server-addr.xml file in the IMC installation path. It stores database passwords of all IMC components in ciphertext.

The following is an example for updating the password of the config_db database stored in IMC:

cd deploy/

./pwdmgr.sh –modify 127.0.0.1 config_db imc_config dbpasswd

Change password successfully

In the example, the dbpasswd string represents the new password of the imc_config user. The config_db string represents the database name. The 127.0.0.1 string represents the IP address of the database. The database IP address and name can be retrieved from the $IMCROOT/common/conf/server-addr.xml file.

If IMC is deployed in distributed mode, you must update the database password on every IMC server.

What should I do if the connection to the database server fails or takes a long time?

By default, DNS first searches the /etc/hosts file for the matching entry of the database server. If no matching entry exists, a resolution request is sent to a DNS server configured in the /etc/resolv.conf file. This file has a maximum of three DNS servers. When resolution fails on one DNS server, the resolution request is sent to another DNS server.

If the host name in the tnsnames.ora file is used for connecting to the database server, verify that the DNS settings are correctly configured in the /etc/resolv.conf file:

cd /etc

vi resolv.conf

nameserver 10.72.66.36

nameserver 10.72.66.37

The IP address of the DNS server is displayed in the nameserver field.

For Oracle 11.1.0.7 and Oracle 11.2.0.1, the connection to the database server might be slow if the IP address in the tnsnames.ora file is used for connection. This is because DNS resolution is first performed by DNS servers configured in the /etc/resolv.conf file. If the resolution fails, DNS waits a time period before searching the /etc/hosts file. This issue has been fixed up in Oracle 11.2.0.2. If this issue persists, verify that the DNS servers are correctly configured in the /etc/resolv.conf file, or delete DNS servers from the file as follows:

cd /etc

vi resolv.conf

#nameserver 10.72.66.36

#nameserver 10.72.66.37

10-Oracle 11g R2 Installation and Configuration Guide

Installing and configuring the Oracle database server

Installing the Oracle database server

Configuring the Oracle database listener

Configuring the network service name

Managing Oracle database 11g R2

Starting the Oracle service manually

Setting database storage space through SQL statements

Modifying database memory settings

Adding redo log groups

Disabling database auditing

Disabling database tracing

Removing Oracle Database 11g R2

Why does the system display an insufficient disk space error when creating the database instance?

Why are there unreadable characters displayed on IMC that uses the Oracle database?

How do I update database passwords for IMC?

What should I do if the connection to the database server fails or takes a long time?

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

Company Information

News & Events

Contact Us