Requirements for Installation

• Installed WinCC OA version 3.11 SP1.

• Valid license for the RDB archiving system must be available.

Note

After the expiration of the license, the project can be started for another 7 days (emergency period without configuration applications). The RDB manager depends on the emergency period of the Event Manager.

• The minimal requirements to the Oracle client / server runtime version as well as additional requirements can be found in the table below. Only the Standard and Enterprise Editions are supported!
  It is to consider, that depending on the used processor architecture (32/64 bit) the corresponding Oracle runtime version must be used, e.g. a 32bit client setup (with 32bit UI) requires a 32bit Oracle client and a 64bit server setup (with 64bit UI) requires a 64bit Oracle client. For more information about the operating systems and processor architecture supported by WinCC OA please refer to software-requirements.

• Name and password of an Oracle user with system database administrator permissions on the Oracle DB computer are necessary for creating an new RDB schema / user.

• The necessary environment variables must be set for the Oracle server and Oracle client.

• The Oracle-.Net-Client must be installed on he computers where the RDB archiving shall be used

• VC10 support must be available

Note

To check whether the VC10 support is available or not, see if the directory "ORACLE_HOME\oci\lib\msvc\vc10" exist. If the directory does not exist the necessary libraries can be obtained from Oracle. See download Please consider that the environmental variable for the Oracle libraries must be updated according to the location of the newly installed libraries.

• The usage of an Oracle client version 11 with a oracle database version 10 is supported from Oracle but is not advised for the usage with WinCC OA due to the fact that errors could lead to wrong behavior.

• Following restrictions must be considered:

• The Oracle Instant Client is not supported!

• Oracle Dataguard is not supported!

Switch from RAIMA database

If you switch the from a RAIMA (alarm) archiving to RDB archiving, delete all RAIMA alarm file sets (al* files) - excepting the most current one using the archive control panel since otherwise the start time of the RDB manager is extended unnecessarily. You cannot access the RAIMA alarm history afterwards anyway.

Switch from HDB

The switch from a historic database to a relational database is possible. After opening the RDB archive manager the first time using the system management, you will be asked in an information dialog whether you wish to convert the existing data points, which use value archives, to RDB. After confirmation with "Yes", the value archives will be deleted.

Note

When switching from HDB to RDB, the weight configuration of Value Archives (1 to n) has to be changed to the RDB Manager (99).

Compatibility to WinCC OA version 3.6 SP2 with RDB

If the compatibility of the Oracle schema (database schema) with WinCC OA version 3.6 SP2 is needed, the 'i362Compatible' entry from the ARC_CONFIG table has to be set to 1. This may cause that during a redundance switch the values are written into the database twice.

Environment Variables

The environment variables have to be set in the operating system's own shell or DOS box (or in the My Computer/System Settings):

Example on a Windows computer

set ORACLE_SID=stddb

set ORACLE_HOME=D:\oracle\product\11.2.0\db_1

set ORACLE_HOSTNAME=atpcknnc.ww300.siemens.net

set PATH=D:\oracle\product\11.2.0\db_1\bin;

... etc.

Note

In order to avoid that dpGetPeriod() returns wrong values for char-typed data point elements, the user of the Oracle Instant Client on Windows should check whether the NLS_LANG environment variable is set. In standard, Western-European (and American) setups this should be set to "AMERICAN_AMERICA.WE8ISO8859P1".

Example for Solaris/Linux, C-Shell

setenv ORACLE_BASE /disc/oracle

setenv ORACLE_SID db10g

setenv ORACLE_HOME ${ORACLE_BASE}/product/11.2.0/Db_1

setenv PATH ${ORACLE_HOME}/bin:${PATH}

setenv LD_LIBRARY_PATH /usr/local/lib:/usr/lib:${ORACLE_HOME}/lib32:${ORACLE_HOME}/lib

Example for Solaris/Linux, Bourne-Shell

ORACLE_BASE=/disc/oracle

ORACLE_SID=db11g

ORACLE_HOME=${ORACLE_BASE}/product/11.2.0/Db_1

PATH=${ORACLE_HOME}/bin:${PATH}

LD_LIBRARY_PATH=/usr/local/lib:/usr/lib:${ORACLE_HOME}/lib32:${ORACLE_HOME}/lib

export ORACLE_BASE ORACLE_SID ORACLE_HOME PATH LD_LIBRARY_PATH

If these environment variables have been set in the shell, they have to be re-defined after every reboot of the computer or re-login.

In order to load them automatically these have to be defined

• under Windows - advanced settings of the computer properties (system variables or user variables) under Windows or in /etc/profile for all users / .profile for a specific user under Linux/Solaris.
   

• under Linux - The environment variables have to be set according to:

csh -> /etc/profile.d/csh.csh

tcsh -> /etc/profile.d/tcsh.csh

bash -> /etc/profile.d/bash.csh

ksh -> /etc/profile.d/ksh.csh

sh -> /etc/profile.d/sh.csh

If the Oracle client is running on a RedHat 64 bit system, ORACLE_HOME/lib32 has to be specified in the LD_LIBRARY_PATH in addition to ORACLE_HOME/lib.

• under Solaris - save the needed settings using the environment variables in the .profile or .cshrc file of the HOME directory.

csh -> .cshrc/csh.csh

tcsh -> .cshrc/tcsh.csh

bash -> .profile/bash.csh

ksh -> .profile/ksh.csh

sh -> .profile/sh.csh

Enter in the Shell the env command to show the set environment variables.

If the Oracle client is running on a RedHat 64 bit system, ORACLE_HOME/lib32 has to be specified in the LD_LIBRARY_PATH in addition to ORACLE_HOME/lib.