Space banner This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Oracle v10g, 11g or 12c prerequisites on Windows systems


Oracle v10g, 11g or 12c prerequisites on Windows systems

The following Oracle versions are supported for Windows platforms:

  • 10.0 and 10.1 with client 9.2.0.x
  • 10.2.0.3 patch 5846376 

    Note:

    This patch is required on a Windows Oracle Server. If the Oracle Server is installed on a Linux device, 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
  • 12c Release 1 (12.1.0.2)78u78 

    Note:

    Make sure your Oracle client has the same architecture as the CM agent (x86 or x64); otherwise, the CM 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 CM agent can communicate with the Oracle database.

If Oracle v10g, 11g or 12c is already installed as a database engine, you need to execute the following before installing the master:

Note:

If you are using Oracle 10g Release 2, ensure that you have installed all available patches.

Setting the character set to unicode

  1. In the Database Configuration Assistant select the Character Set tab when the Initialization Parameters window appears.
  2. Select the Use Unicode (AL32UTF8) radio button.
  3. In the National Character Set box select the UTF8 value.

Creating a database on Oracle v10g, 11g or 12c

Create a database for the Client Management before running the installation process. This database can be default named as bcmdb or freely named. The name is requested during the CM master installation in the Database Settings dialog box (this applies to Windows platforms only).

Creating tablespaces for Oracle v10g, 11g or 12c

Before installing the master you must also create a user and the tablespaces for the BCM database . This is done through the execution of scripts delivered with the BMC 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/OraData/BmcClientManagement .
  2. Copy the files Create_User_TS.oracle.bat and Create_User_TS.oracle.sql to the temp directory of the machine on which the CM master is to be installed.
  3. Open a command line window on this machine.
  4. Enter the following command line followed by the ENTER button: Create_User_TS.oracle.bat <System_Password> <Net_Service_Name> <Tablespaces_Path> <DB_User_Name> <DB_User_Password> whereby:

    System_Password

    is the password to the Oracle system

    Net_Service_Name

    is the name of the Oracle service

    Tablespaces_Path

    is the path to the directory in which the tablespaces are located, for example, Oracle/OraData/BmcClientManagement

    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

The tablespaces are now created and you can continue with the master installation.

Removing Oracle identification on the client

The following line must be commented with a hash (#) in the following file to remove the Oracle identification on the Oracle client: file: sqlnet.ora line: SQLNET:AUTHENTICATION_SERVICES=(NTS)

Defining language settings on Oracle v10g, 11g or 12c

The following settings are required for the NLS_LANG parameter:

  • The Oracle parameter NLS_LANG (stored as either an environment variable, or in the registry at HKLM/SOFTWARE/ORACLE/HOME0/NLS_LANG) needs to be set properly. It is of the form "Language"_"Location"."Charset" and 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 either an environment variable, or in the registry at HKLM/SOFTWARE/ORACLE/HOME0/NLS_LANG) needs to be set properly. It is of the form "Language"_"Location"."Charset" and Charset needs to be set to AL32UTF8, for example, NLS_LANG=Japanese_Japan.AL32UTF8.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*