Installing the Oracle Client (OCI) libraries

The AppScan® Source installation does not install the Oracle Client (OCI) libraries. If you are deploying AppScan Source using an Oracle database, every client machine running AppScan Source products must have an Oracle client installed in order to communicate with the database. To use an Oracle client you already have installed, you must ensure that the client libraries can be found by AppScan Source, according to the instructions in this topic. After the installation is complete, if you see a connection error in <data_dir>\logs\scanner_exceptions.log (on Windows™) or <data_dir>/logs/scanner_exceptions.log (on Linux™) (where <data_dir> is the location of your AppScan Source program data, as described in Installation and user data file locations), this may be because the Oracle Client libraries cannot be found. On Linux, this error will state that libclntsh.so could not be found. On Windows, it will state that ociw32.dll could not be found.

Note: AppScan Source server components, such as the AppScan Source Database, are not supported on macOS.

If you do not have an existing Oracle client installation, the Oracle Client can be downloaded by accessing the downloads section of http://www.oracle.com/.

In order to create the Oracle schema, the AppScan Source installer must either be run on the same machine on which the Oracle database is installed, or on a machine on which the full Oracle client is installed. This is required so that the installer can access the Oracle sqlplus and sqlldr utilities.

On Linux

If it does not already exist on your system, you need to create a symbolic link in the $Oracle_Home\lib directory. This link should be called libclntsh.so, and should point to a specific version of this file. For example:

  • Oracle Version 12 client: lrwxrwxrwx 1 oracle oracle 69 Apr 5 15:07 libclntsh.so -> /home/oracle/app/oracle/product/12.1.0/client/lib/libclntsh.so.12.1
  • Oracle Version 11 client: lrwxrwxrwx 1 oracle oracle 63 Oct 2 14:16 libclntsh.so -> /u01/app/oracle/home/lib/libclntsh.so.11.1

In addition, the directory containing libclntsh.so must be included in your $LD_LIBRARY_PATH prior to running the installer.

You may also need to set values for the NLS_LANG and ORA_NLS10 (or ORA_NLS11) environment variables. For example:

export NLS_LANG=AMERICAN_AMERICA.AL32UTF8
export ORA_NLS10=$ORACLE_HOME/nls/data

See your Oracle documentation for information about these variables.

Automation Server: If you are using the AppScan Source for Automation server, you may have to edit the /etc/init.d/ounceautod start script to ensure that the Oracle client libraries are included in the $LD_LIBRARY_PATH for the user account of the ounceautod daemon.

On Windows

The %ORACLE_HOME%/bin directory must be included in your PATH environment variable.

Oracle Instant Client

The Oracle Instant Client is only supported when you are connecting to an existing Oracle database that has AppScan Source schema applied.

  • On Linux: The libclntsh.so symbolic link should be created in the same directory as your Oracle Instant Client libraries and this directory should be included in $LD_LIBRARY_PATH.
    Note: When using the Basic Lite version of the Oracle Instant Client, you should not set the ORA_NLS10 (or ORA_NLS11) variable.
  • On Windows: Ensure the Oracle Instant Client .dll files can be found in your PATH.