• Topic
  • Discussion
  • UdaWikiWeb.NoValidLicenseWasFound(Last) -- Owiki? , 2016-08-19 15:00:36 Edit owiki 2016-08-19 10:00:36

    No valid license was found

    "No valid license was found" errors tend to arise from one of three scenarios:

    1. The licensed environment reports more logical processors than the license permits. Licenses must be obtained for the number of logical processors in the deployment host.
    2. Hyper-threading may cause the environment to report more logical processors than there are physical cores present. Users may choose to disable hyper-threading. Alternatively, users may contact our Sales or Support teams for alternative solutions.
    3. The license in place is for a different major release than the components installed on the machine (e.g., Release 6.x components, with a Release 5.x license). Users should contact our Sales team to obtain an appropriate license.

    If the above are not the issue --

    1. Ensure that you have a valid license file.
    2. Ensure that binary preserving methods were used to transfer the license file(s) from machine to machine.
    3. Ensure that the OpenLink-relevant environment variables were set with the appropriate command for your active shell --


      active shell command
      sh, bash, ksh, zsh, and related . /path/to/openlink.sh
      or
      source /path/to/openlink.sh
      csh, tcsh, and related source /path/to/openlink.csh

    4. Use


      echo $OPL_LICENSE_DIR

      to confirm that the OPL_LICENSE_DIR environment variable has been set. This should be set by the openlink.sh or openlink.csh script above! If not, set and export the variable from the commandline. This PATH variable must include the directory that contains your license file. For example:


      export OPL_LICENSE_DIR=/usr/openlink/bin;/etc/oplmgr

    5. Ensure that you can establish basic ODBC connections using simple applications like odbctest or iodbctest.
    6. If using Oracle HSODBC or DG4ODBC --
      • Ensure that the OpenLink-relevant environment variables were set as part of the Oracle and Listener startup routines.
      • Add the OPL_LICENSE_DIR environment variable to the inithsodbc.ora file, if licensing problems persist. You may also set other environment variables, like ODBCINIor the Single-Tier OPENLINKINI, in inithsodbc.ora, as needed.
    7. Test.

    Referenced by...