Oracle v9.2.0.6, 10g or 11g prerequisites on Linux systems

The following Oracle versions are supported on Linux platforms:

• 9i from 9.2.0.6 onwards (server and client)
• 10.0 and 10.1 with client 9.2.0.x
• 10.2.0.2 patch 5051602

• Note:

  10.2.0.3 does not work, because Oracle did not report patch 5051602 to this version.

• 10.2.0.4 and 10.2.0.5
• 11.2.0.2 with 10.2.0.4, 10.2.0.5 or 11.2.0.2 client

• 11.2.0.3 

  Note:

  Ensure that your Oracle client has the same architecture as the Client Management - agent (x86 or x64); otherwise, the Client Management - agent cannot communicate with the database. This is because Oracle versions prior to 10.2.0.5 do not include x64 clients, which means that in this case only an x86 Client Management - agent can communicate with the Oracle database.

If Oracle v9.2.0.6, 10g or 11g is already installed as a database engine, you need to execute the following before installing the master:

• If you are using Oracle 10g Release 2, ensure that you have installed all available patches.
• In the Database Configuration Assistant , select the Character Set tab when the Initialization Parameters window appears. In this tab, select the Use Unicode (AL32UTF8) radio button and below, in the National Character Set box, select the UTF8 value.
• Create a database for Client Management before running the installation process. This database can be given the default name bcmdb or can be given a name by the user.
• Before installing the master, you must also create a user and the tablespaces for the CM database . This is done through the execution of scripts delivered with the Client Management installation archive in the support/database directory. Proceed as follows:
  1. Create a new directory under the Oracle installation directory for the tablespaces, for example, $ORACLE_BASE/oradata/bmc-software client-management . Change ownership of this new directory to Oracle user.
  2. Copy the files Create_User_TS.oracle.sh and Create_User_TS.oracle.sql to the tmp directory of the computer on which the CM master is to be installed.
  3. Open a command line window on this computer and change to the tmp directory.

  4. Enter the following command line followed by the ENTER key: Create_User_TS.oracle.sh [System Password] [Instance Name] [Tablespace Directory]
      whereby:

     System Password	is the password to the Oracle system.
     Instance Name	is the Oracle instance on which the CM master is to be located.
     Tablespace Directory	is the directory in which the tablespaces are to be located as created previously under step 1, for example, Oracle/OraData/BmcClientManagement client-management .
     DB_User_Name	is the name of the Oracle account with which you connect to the CM database .
     DB_User_Password	is the corresponding password.

• In the sqlnet.ora file, comment the following line with a hash (#):
  line: SQLNET:AUTHENTICATION_SERVICES=(NTS)
• On Linux systems, ensure that the Oracle library libclntsh.so exists on the master in the oracle_home/lib directory of the Oracle client. It is sometimes possible that this library exists under another name, such as libcIntsh.so.9.2 . If this is the case, create a symbolic link for libclntsh.so pointing to libcIntsh.so.9.2/ . Also ensure that the directory that contains this file is referenced in the /etc/ld.so.conf file. Any changes to this file require ldconfig to be run for the changes to take effect.
• The Oracle parameter NLS_LANG (stored as an environment variable) needs to be set properly. It is in the format of "Language"_"Location" . Charset needs to be set to AL32UTF8 , for example, NLS_LANG=Japanese_Japan.AL32UTF8 .
• If your language is not one of the Western European group, the Oracle parameter NLS_LANG (stored as an environment variable) needs to be set properly. It is of the form "Language"_"Location" . Charset needs to be set to AL32UTF8 , for example, NLS_LANG=Japanese_Japan.AL32UTF8 .
• For a Linux master, you should carry out the following actions:
  1. If the CM agent is already started, stop it with the following command: service BMCClientManagementAgent stop
  2. Open the BMCClientManagementAgent file which is located in the /etc/init.d/ directory (this file corresponds to the service of the CM agent ).

  3. Ensure that the following entries are all listed under the # Some definitions section in this file: 

     
     
     ############### ORACLE START########################################
     PATH=$PATH:/usr/local/bmc-software/client-management/master/bin
     ORACLE_HOME=/usr/lib/oracle/xe/app/oracle/product/10.2.0/client
     export ORACLE_HOME
     NLS_LANG=AMERICAN_AMERICA.AL32UTF8
     export NLS_LANG
     SQLPATH=$ORACLE_HOME/sqlplus
     export SQLPATH
     PATH=$ORACLE_HOME/bin:$PATH
     export PATH
     TNS_ADMIN=$ORACLE_HOME/network/admin
     export TNS_ADMIN
     if [ $?LD_LIBRARY_PATH ]
     then
     LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH
     else
     LD_LIBRARY_PATH=$ORACLE_HOME/lib
     fi
     export LD_LIBRARY_PATH
     ############### ORACLE END###########################################
       

  4. Note:

     The PATH, ORACLE_HOME and NLS_LANG entries might need to be changed to match the path where Client Management is installed, the path where Oracle is installed, and the NLS_LANG defined for the Oracle database respectively.

  5. Save and exit.
  6. Start the CM agent with the following command: service BMCClientManagementAgent start