Database and library environment variables

Database environment variables
Database	Syntax and Description
DB2®	DB2DIR=full_dir_path export DB2DIR DB2® installation directory (for example, /usr/lpp/db2_06_01) . full_path_to_db2profile Sources the database configuration for DB2® users (e.g./home/db2inst1/sqllib/db2profile). Note the ". " (period and then a space).
Netezza®	NZ_ODBC_INI_PATH=full_dir_path export NZ_ODBC_INI_PATH Directory location of the odbci.ini file (e.g. /opt/odbc64v51) ODBCINI=full_path_and_file_name export ODBCINI Full path to the odbc.ini file
Oracle	ORACLE_BASE=full_dir_path export ORACLE_BASE Oracle installation directory ORACLE_HOME=full_dir_path export ORACLE_HOME Oracle's home directory (e.g. /home/oracle/OraHome1).
Teradata	ODBCINI=full_path_and_file_name export ODBCINI Full path to the obdc.ini file

If LD_LIBRARY_PATH_64 (for 64-bit linking) is set, remove it. The LD_LIBRARY_PATH variable will be ignored if LD_LIBRARY_PATH_64 is set.

For example: LIBPATH=<Campaign_Home>/bin:<path to DB lib directory>:/usr/lib:$ORACLE_HOME/lib32:$ORACLE_HOME/lib

For example: SHLIB_PATH=<Campaign_Home>/bin:<path to DB lib directory>:/usr/lib:$ORACLE_HOME/lib32:$ORACLE_HOME/lib

Different versions of Oracle have different naming conventions for their lib directories. Older versions used lib for 32-bit and lib64 for 64-bit. Newer versions use lib32 for 32-bit and lib for 64-bit.

If you install 32-bit Campaign, you must include either $ORACLE_HOME/lib32 or $ORACLE_HOME/lib , whichever one contains the 32-bit Oracle libraries.

If you install 64-bit Campaign, you must include either $ORACLE_HOME/lib or $ORACLE_HOME/lib64, whichever one contains the 64-bit Oracle libraries.